Amazon Web Services CloudWatch provides monitoring for AWS resources and customer-run applications. AWS can collect data, gain insight, and alert users to fix problems within applications and organizations. AWS CloudWatch gives system-wide visibility into resource utilization and notifications can be set for when any metrics cross a specified threshold. These alarms can be automatically sent to PagerDuty, which then reliably alerts the correct on-call person through their preferred contact methods.
Follow the instructions below to configure your AWS Cloudwatch with PagerDuty. If you have any questions or need any assistance, please contact our support team at firstname.lastname@example.org.
Note: Alarms from CloudSearch, DynamoDB, EBS, EC2, ECS, ElastiCache, ELB, ES, Kinesis, Lambda, ML, Redshift, RDS, SNS, SQS, S3, SWF, StorageGateway, and WAF are supported. Alarms from Route53 and custom metrics will create incidents however, they will not be as detailed. Autoscaling messages are not currently supported. For more custom need, you can integrate using an email integration
If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +New Integration button.
If you are creating a new service for your integration, in General Settings, enter a Name for your new service. Then, in Incident Settings, specify the Escalation Policy, Notification Urgency, and Incident Behavior for your new service.
Alarms from CloudSearch, DynamoDB, EBS, EC2, ECS, ElastiCache, ELB, ES, Kinesis, Lambda, ML, Redshift, RDS, SNS, SQS, S3, SWF, StorageGateway, and WAF are supported. Alarms from Route53 and custom metrics will create incidents however, they will not be as detailed. Autoscaling messages are not currently supported.
An alarm with status ALARM will trigger incidents, and status OK will resolve them. Alarms with status INSUFFICIENT_DATA will not affect a PagerDuty incident. If you need INSUFFICIENT_DATA to resolve an incident, we recommend using an email integration instead.
If you send a confirmation email to your service’s PagerDuty address, you will be able to view the message body and verify that address from the PagerDuty console. To do so, find the incident that is created by the email and view its details to verify the email address.