AWS

AWS – Monitoring the Memory of your Virtual Machine (AMI)

Out of the box, AWS CloudWatch by default monitors 4 things:

  1. CPU
  2. Network
  3. Disk
  4. Status Checks

Can you tell which resource CloudWatch doesn’t monitor out of the box? Memory! (update:  According to AWS technical support “Right now, you do not need to deploy anything in you AMI to monitor your instance. Metrics like memory utilization and disk space require us to look into the OS running in the instance and that is why we do not have these valuable metrics.  We are looking at ways to provide more insight into your OS and applications and will have more details as we firm up the plans”).  Amazon provides 2 articles for doing this, one for most Linux flavors and another for Windows. This article is basically a walkthrough of the Linux article (since I know Windows and want to learn more Linux anyway).

  1. Create a CloudWatch role in IAM (if you don’t know how to do this see my previous article)
  2. Spin up a new Amazon Linux AMI instance using the new CloudWatch role in the IAM section of the instance creation (check out THIS article if you get stuck)
  3. SSH into your new instance & run the following command:
    1. sudo yum install perl-Switch perl-DateTime perl-Sys-Syslog perl-LWP-Protocol-https
    2. curl http://aws-cloudwatch.s3.amazonaws.com/downloads/CloudWatchMonitoringScripts-1.2.1.zip -O
    3. unzip CloudWatchMonitoringScripts-1.2.1.zip
    4. rm CloudWatchMonitoringScripts-1.2.1.zip
    5. cd aws-scripts-mon
  4. At this point you have downloaded and unzipped the Perl script necessary to make the remote calls to CloudWatch and installed the Perl bits needed to run said script.

 

To read the rest of Chris’ post, click here!

 

By Chris Williams, Enterprise Consultant