![]() ![]() The deployed VM must have credentials that allow reading and writing CloudWatch data.Īssigning an IAM role is the recommended method, to avoid the need for placing plain-text credentials in a script. If you're using your own custom script to enable memory usage monitoring, you must disable memory usage monitoring in the service catalog blueprint.Īssign credentials with CloudWatch permissions.You can also enable memory usage monitoring during manual deployment. ![]() The two AWS memory metrics and their Commander equivalents are:įor more information, see Monitor Memory Usage(VM templates only). The script then downloads CloudWatch Monitoring scripts from AWS and sets up a Cron job to send VM memory usage statistics to AWS every five minutes. The script downloads and installs prerequisites (Perl modules) using yum, apt_get or zypper, depending on the Linux distribution. The script is added to any other user data configured for the new VM. When you enable memory usage monitoring for a new Linux VM, during provisioning, Commander runs a script as AWS user data. Enable memory usage monitoring for new VMs: Overview To support another version, you can edit the script as explained below. Supported Linux distributionsĬommander supports memory metrics for the following Linux distributions:īy default, Open SUSE Linux Enterprise Server 12 SP1 is supported. See also Monitor Memory Metrics for EC2 Windows Instances. ![]() This topic explains how to enable memory usage monitoring for new Amazon EC2 Linux instances deployed by Commander.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |