## About

Cavisson's AWS Integration allows you to monitor the AWS Services that influence the performance of your AWS-hosted applications. Collect CloudWatch metrics and events from many other AWS products. You can view graphs per service instance and create custom graphs in your dashboards. Collect the metrics for all AWS services: AWS EC2, AWS Redshift, AWS AWS Application ELB, AWS IoT, AWS EKS Container insights, AWS ECS, and many more.

## Pre-Requisites

Before beginning with the configuration of AWS monitors, make sure that you have the following details ready:

- An active AWS account.
- AWS Access Key & AWS Secret Access Key, which are used to sign programmatic requests that you make to AWS. If you don't have access keys, you can create them from the AWS Management Console by following the below link:
- https://docs.aws.amazon.com/powershell/latest/userguide/pstools-appendix-sign-up.html
- The AWS component that you want to monitor should be enabled on an AWS account, such as AWS EC2, AWS IoT, etc.
- AWS Accounts should have read permissions for region-based monitoring services.

## Configuration

1. Enable the AWS integration in the monitor UI by entering the below information:
   - AWS Account Name - The account name is the unique name under which AWS metrics will be shown in the metric tree during the monitoring session.
   - AWS Access Key - As mentioned in the pre-requisites, obtain the Access key and pass the value in this field.
   - AWS Secret Access Key - As mentioned in the pre-requisites, obtain the Secret access key and pass the value in this field.
2. Advance Settings
   - Limit Monitoring of Selected Region(s) - Select the region for region monitoring to perform location-related tasks.
   - Proxy Settings(Optional)
     - Host - Provide the hostname/IP of the machine on which the AWS setup resides.
     - Port - The port on your AWS server, on which the connection will be made.
     - Username - Enter either an existing user with read-only permissions.
     - Password - Password of the existing or newly created read-only user.
   - Exclude Monitors(Optional) - By default, all the monitors that you have selected from the Monitor(s) section are applied to all the accounts added via configuration. In case you need to exclude monitoring any specific AWS component, click on the Advanced Setting section, and from the Exclude Monitors dropdown list, select the components that you do not want to monitor.

Once you have provided the relevant details, go to the Monitor(s) section and select the different AWS components that you want to monitor. After selecting the required components, get back to the configuration page and click on the Add button to start monitoring your AWS application.

#### Edit/Delete Added Accounts:

- Once you have added the account(s), you can edit the configurations in case you want to change the Access key/regions by clicking on the Edit icon under the Actions column. To delete the configured account, click on the Delete icon.

#### Validation

- To validate the successful implementation of AWS monitor is validated after completing the above fields, it automatically comes on the monitoring homepage UI with the number of monitors that are successfully running or failed details.
- Also, validate the AWS metrics under the given account name in the metrics tree.

#### Troubleshooting

- The AWS account should be active and the instances for which monitoring is configured should be running.
- Metrics should be available for the monitored instance i.e. the service/component that you have selected should be successfully deployed and running on the instance for which the account key is provided.