Obtaining an Access key and Secret key

To monitor the Amazon cloud infrastructure, the eG agent has to be configured with the access key and secret key of a user with a valid AWS account.

For this purpose, you need to follow the following broad steps:

  1. Create a special user on the AWS cloud for monitoring purposes.
  2. Configure the eG agent with the access key and secret key of the special user.

To create a user on the AWS cloud, do the following:

  1. Login to the AWS management console as a root user.
  2. Upon successful login, Figure 1 will appear. Keep scrolling down Figure 1 until you view the IAM option (highlighted by Figure 2).

    Figure 1 : The AWS Services page that appears as soon as a root user logs into the AWS management console

Figure 2 : Scrolling down the AWS Services page to view the IAM option

  1. Figure 3 will then appear. The first step to creating a user is to create a policy that defines the rights and privileges of that user. To create a policy, click on the Policies link in the left panel (as indicated by Figure 3).

    Figure 3 : Clicking on the Policies link in the left panel

  1. Figure 4 will then appear listing all the policies that pre-exist. Click on Create Policy to create a new policy.

    Figure 4 : Clicking on Create Policy

  1. Figure 5 will then appear. Click on the JSON tab page in Figure 5.

    Figure 5 : Switching to the JSON tab page

  1. Figure 6 will then appear.

    Figure 6 : The JSON tab page

  1. Replace the contents of the JSON tab page with the following (see Figure 7):

  2. {

    "Version": "2012-10-17",

    "Statement": [

    {

    "Action": [

    "acm:DescribeCertificate",

    "acm:ListCertificates",

    "acm:GetCertificate",

    "acm:Certificate*",

    "autoscaling:Describe*",

    "budgets:Describe*",

    "cloudfront:List*",

    "cloudfront:GetDistributionConfig",

    "cloudfront:GetStreamingDistributionConfig",

    "cloudsearch:Describe*",

    "cloudtrail:DescribeTrails",

    "cloudtrail:GetTrailStatus",

    "cloudwatch:Describe*",

    "cloudwatch:Get*",

    "cloudwatch:List*",

    "dynamodb:List*",

    "dynamodb:Describe*",

    "ec2:Describe*",

    "ec2:Get*",

    "ecs:List*",

    "ecs:Describe*",

    "elasticache:Describe*",

    "elasticache:List*",

    "elasticbeanstalk:Describe*",

    "elasticbeanstalk:List*",

    "elasticfilesystem:Describe*",

    "elasticloadbalancing:Describe*",

    "elasticmapreduce:Describe*",

    "elasticmapreduce:List*",

    "iam:Get*",

    "iam:List*",

    "iam:GenerateCredentialReport",

    "iot:Describe*",

    "iot:List*",

    "kinesis:List*",

    "kinesis:Describe*",

    "kinesis:Get*",

    "lambda:List*",

    "logs:Get*",

    "logs:Describe*",

    "logs:FilterLogEvents",

    "logs:TestMetricFilter",

    "logs:OutputLogEvent",

    "opsworks:Describe*",

    "polly:Describe*",

    "polly:GetLexicon",

    "polly:ListLexicons",

    "rds:Describe*",

    "rds:List*",

    "redshift:Describe*",

    "redshift:ViewQueriesInConsole",

    "route53:List*",

    "s3:Get*",

    "s3:List*",

    "s3:S3Object*",

    "s3:ObjectListing",

    "ses:ListIdentities",

    "ses:Get*",

    "support:*",

    "sns:Get*",

    "sns:List*",

    "sns:Publish",

    "sqs:List*",

    "sqs:Get*",

    "storagegateway:Describe*",

    "storagegateway:List*",

    "waf:List*",

    "waf:Get*",

    "workspaces:Describe*",

    "Organizations:List*",

    "Organizations:Describe*"

    ],

    "Effect": "Allow",

    "Resource": "*"

    }

    ]

    }

     

    Note:

    If you copy the above code block directly from this document and paste it in the JSON tab page, you will find that the page numbers in the document also get copied on to the tab page inadvertently. Therefore, after copying the code block to the JSON tab page, make sure you remove the page numbers from the code block and then proceed.

Figure 7 : Replacing the contents of the JSON tab page

  1. Then, click the Review policy button in Figure 7 to review the policy that you have defined. This will open Figure 8, where you have to provide a name for the new policy and a brief description of the policy.

    Figure 8 : Reviewing the policy

  2. The Summary section of Figure 8 lists all the services that this policy allows access to, the level of access (whether Full or Limited), and the resources that can be accessed.
  3. Then, click on the Create Policy button in Figure 8 to create the new policy.
  1. Figure 9 will then appear displaying the new policy.

    Figure 9 : Viewing the newly created policy

  2. Now, proceed to create a new user. For that, first click the Users option in the left panel (as indicated by Figure 10).

    Figure 10 : Clicking on the Users option

  1. This will open Figure 11. Here, specify the name of the new user and set Programmatic access as the Access type. Then, click the Next: Permissions button to move to the next step of the user creation.

    Figure 11 : Creating a new user

  2. Clicking on the Next: Permissions button, will invoke Figure 12. Click the Attach Existing Policies Directly button in Figure 12 to associate the newly created policy with the new user. Then, from the list of policies displayed therein, click the check box corresponding to the policy that you created newly, and then click the Next: Review button.

Figure 12 : Associating the new policy with the new user

  1. Figure 13 will then appear. Click the Create User button in Figure 13 to create the user.

Figure 13 : Reviewing the new user's details

  1. Figure 14 will then appear displaying the new user and the access and secret keys assigned to the new user. Click on the Show link adjacent to the encrypted secret key to view it. Once you are able to view both keys, make a note of the keys.

    Figure 14 : Viewing the access and secret key of the new user

Make sure to configure the eG tests with the access key and secret key that you see in Figure 14.