AWS management pack (solution) is now available out of the box. An AWS account has multiple types of credentials associated with the account. Sign-in credentials are used to access the AWS web-based console, key pairs are used to access EC2 instances, and access keys are used in the REST API that AWS exposes.
Because the AWS adapter is based on the REST API, you must use access keys when you set up the adapter. You generate access keys from the AWS console. You can create credentials on a per user basis. Access keys are not a user name-password pair, but a generated sequence of characters.
Highlights of AWS managemnet pack:
- Collects resource information and performance details from AWS through Cloudwatch.
- Provides pre-configured dashboards and alerts for health, performance, and capacity of AWS resources and services.
- provide Deep Metrics set for : Application Load Balance, Auto Scaling Group, Amazon Relational Database Service, Virtual Private Cloud, S3 and more.
Creating Read-Only AWS Access Service Account
Read-only access in an AWS environment is useful for when someone needs to look into your cloud environment without being able to change anything. This way an AWS vendor can view a potential client’s setup and existing AWS applications before signing a contract and committing to helping them with AWS environments.
From the main console screen, type in IAM. And select the suggested link.
From the IAM dashboard select the Users section and then Add user button.
Enter the new username for your read-only user (VROPS-AWS in this example), select the Programmatic access and AWS Management Console Access. Than select Next: Permissions.
Select the Attach existing policies directly button, than use the search bar to search for ReadOnlyAccess policy. Select the check box beside that policy. Than select Next: Review.
*NOTE: it’s imperative that you select Read Only Access Policy and set the right permissions. Otherwise you’ll grant too much control to your potential new party.
choose the ReadOnlyAccess Policy to provide full View Access.
Adding Tagging is a must within AWS Platform , i have configure a single Tag but for production i will expect this number to raise.
Press Create User to process the request.
On this screen, you will need to share the following credentials with your new user: the access key id, the secret access key (select the show option), and the password (select the show option)
Note – i am showing the Access Key ID because i have deleted all ready the Account including the Secret Access Key, never share this info because that can lead very fast hacking.
Generate Required Access Keys
The Easy way to access the AWS Platform is Access keys , save you the time when you want to access the servers but lead for better Security, please follow this steps to create the access key that we will use with our Management pack.
To configure the Management Pack for AWS, you must acquire an access key and secret key from the Amazon server. You can acquire these keys as an Amazon Web Services Admin user or as an Amazon Identity and Access Management (IAM) user.
VROPS 8 AWS Adapter Configuration steps
click Administration and in the left pane, click Solutions > Cloud Accounts.
On the Cloud Accounts page, click Add Accounts and then click AWS.
Configure the instance settings.
Configure the AWS Cloud Account Credential
- Obtain the Access Key and Secret Key values. See Generate Required Access Keys. These values are not the same as your log in credentials for the Amazon Web Services site.
- Determine the services for which you collect metrics. See, Supported AWS Services
- Determine the regions to which you subscribe. Amazon Web Services is divided into nine regions. The default value * includes all regions in your subscription. If you do not want to subscribe to all regions, you can specify region identifiers in the Regions text box.
- Determine any black list or white list filters. These filters use regular expressions to filter in or out specific objects by name. For example, a white list filter of .*indows.* allows only objects with a name including “indows”. A blacklist filter of .*indows.* filters out all objects with that string in their name.
Test The Adapter to see the End Result, and then Save the Adapter.
Verify that the Status of the VROPS AWS Management pack is OK.
How to Create EC2 Instance in AWS
Lets Schedule a few EC2 Instances to see Result and Metrics collected by AWS VM’s Platform.
- Login to your AWS account and go to the AWS Services tab at the top left corner.
- Here, you will see all of the AWS Services categorized as per their area viz. Compute, Storage, Database, etc. For creating an EC2 instance, we have to choose Compute EC2 as in the next step.
Click on Launch Instance button in the section of Create Instance
You will be asked to choose an AMI of your choice. (An AMI is an Amazon Machine Image. It is a template basically of an Operating System platform which you can use as a base to create your instance). Once you launch an EC2 instance from your preferred AMI, the instance will automatically be booted with the desired OS.
Click on “Configure Instance Details” for further configurations
Remember to choose EC2 that is included with the Free Tier Platform.
We will choose t2.micro instance type, which is a 1vCPU and 1GB memory server offered by AWS.
No. of instances- you can provision up to 20 instances at a time. Here we are launching one instance.
- Network section will give a list of VPCs available in our platform.
- Select an Default VPC.
we will review all our choices and parameters and go ahead to launch our instance.
In the next step you will be asked to create a key pair to login to you an instance. A key pair is a set of public-private keys.
AWS stores the private key in the instance, and you are asked to download the private key. Make sure you download the key and keep it safe and secured; if it is lost you cannot download it again.
- Create a new key pair
- Give a name to your key
- Download and save it in your secured folder
Once you are done downloading and saving your key, launch your instance.
Click on the ‘Instances’ option on the left pane where you can see the status of the instance as ‘Pending’ for a brief while.
Once your instance is up and running, you can see its status as ‘Running’ now.
and here is the end result , we are able to start Monitoring the new EC2 we have deployed.
Pretty nice Metrics we can track with the AWS Management pack