ARCHIVED - How do I instrument AWS AMI Linux instances?

To manually install an agent of Amazon Linux running under AWS

To manage Linux instances on AWS using AWS System Manager

To manually install an agent of Amazon Linux running under AWS:

These instructions apply to the manual installation of an agent on Amazon Linux running under AWS.

1. Connect to the AWS AMI Linux instance that you want to instrument.
   
   
2. Install required packages by entering:

   sudo yum install perl-Switch perl-DateTime perl-Sys-Syslog perl-LWP-Protocol-https -y

3. Download the Cloudwatch monitoring scripts with curl http://aws-cloudwatch.s3.amazonaws.com/downloads/CloudWatchMonitoringScripts-1.2.1.zip -O
   
   
4. Unzip CloudWatchMonitoringScripts-1.2.1.zip
   
   
5. Remove CloudWatchMonitoringScripts-1.2.1.zip
   
   
6. Change to the directory aws-scripts-mon
   
   
7. Copy awscreds.template to awscreds.conf
   
   
8. Edit awscreds.conf and enter your AWS Access Key and your AWS Secret Key, e.g.:

   AWSAccessKeyID=<AWS Access Key>

   or

   AWSSecretKey=<Secret Key>

9. Check it works by running the command:

   ./mon-put-instance-data.pl --mem-util --aws-credential-file=./awscreds.conf

   Note, you must ensure you have the perl-Digest-SHA model installed, to check for which you can use the following command:

   sudo yum install perl-Digest-SHA

   If successful, metrics will be reported to CloudWatch. Reference Id: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
   
   
10. Add to cronjob, and schedule the regular data upload every five minutes by adding the following line to crontab:

    */5 * * * * ~/aws-scripts-mon/mon-put-instance-data.pl --mem-used-incl-cache-buff --mem-util --disk-space-util --disk-path=/ --from-cron

To manage Linux instances on AWS using AWS System Manager:

For ENA v17.0 P01 onwards, Entuity also supports SM deployed Linux CloudWatch agents.

1. In the EC2 Parameter store (for the required Region), create a new parameter called "CloudWatchConfigLin"
2. Enter: 

   {

         "agent": {

           "metrics_collection_interval": 60,

           "logfile": "/opt/aws/amazon-cloudwatch-agent/logs/amazon-cloudwatch-agent.log",

           "debug": true

         },

         "metrics": {

           "metrics_collected": {

             "disk": {

              "measurement": [

                 {"name": "used_percent",  "unit": "Percent"},

                 {"name": "free", "unit": "Megabytes" },

                 {"name": "total", "unit": "Megabytes" },

                 {"name": "used", "unit": "Megabytes" }

               ],

               "resources": [

                 "*"

               ]

             },

             "mem": {

               "measurement": [

                 {"name": "available", "unit": "Megabytes" }

               ]

             }

           },

           "append_dimensions": {

             "InstanceId": "${aws:InstanceId}"

           }

         }     

       }

3. Ensure that instances requiring monitoring have a CloudWatch capable IAM role - e.g. see the Windows AWS instrumentation notes for IAM role: "CloudWatchServerAgentMonitoringRole" and verify that "Enable CloudWatch detailed monitoring" is enabled.
4. Then deploy and configure the CW Agent using SM:
   1. AWS -> EC2 -> Systems Manager Services -> Run Command -> "Run a command"
      1. Choose "AWS-ConfigureAWSPackage"
      2. Select the instance(s). Note, if the IAM role has only just been assigned to the instance, it might take several minutes before it appears in the "select instances" list.
      3. Set "Action" to "Install"
      4. In "Name", type "AmazonCloudWatchAgent"
      5. Check "Version" is "latest"
      6. "Run"
      7. Click "view result"
      8. Wait until status has changed from "In Progress" to "Success" or "Failed". If failed, check output of the job to see what went wrong.
   2. Then in SMS, configure the agent (to check that the config pull works):
      1. Run Command: "AmazonCloudWatch-ManageAgent"
      2. Select instance(s)
      3. Action: configure
      4. Mode: ec2
      5. Optional Configuration Source: ssm
      6. Optional Configuration Location: CloudWatchConfigLin
      7. Optional Restart: yes
      8. "Run"
   3. Check the full set of metrics appears in Entuity - CPU, Guest memory, Disks' names + utilization %, network traffic in and out, bytes and packets.