• Products
  • Get started
  • Documentation
  • Resources

Integrate Opsgenie with Amazon CloudWatch Events

Overview

When resources change state, they automatically send Amazon CloudWatch events into an event stream. Create rules that match selected events in the stream and route them to targets to take action. Use rules to also take action on a pre-determined schedule.

What does the integration offer?

Use the Amazon CloudWatch Events integration in Opsgenie to forward Amazon CloudWatch Events notifications to Opsgenie. Opsgenie determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, and iOS & Android push notifications, and escalates alerts until they are acknowledged or closed.

How does the integration work?

When a state changes in your AWS resources, an alert is automatically created in Opsgenie through the integration.

Set up the integration

Amazon CloudWatch Events is an API-based integration. Setting it up involves the following steps:

  • Add an Amazon CloudWatch Events integration in Opsgenie

  • Configure the integration in Amazon CloudWatch Events

Add an Amazon CloudWatch Events integration

If you're using Opsgenie's Free or Essentials plan or if you’re using Opsgenie with Jira Service Management's Standard plan, you can add this integration from your team dashboard only. The Integrations page under Settings is not available in your plan.

  1. Go to Teams and select your team.

  2. Select Integrations on the left navigation and then select Add integration.

Adding the integration from your team dashboard will make your team the owner of the integration. This means Opsgenie will assign the alerts received through this integration to your team only. Follow the rest of the steps in this section to set up the integration.

To add an Amazon CloudWatch Events Events integration in Opsgenie:

  1. Go to Settings > Integrations.

  2. Select Add integration.

  3. Run a search and select “Amazon CloudWatch Events”.

  4. On the next screen, enter a name for the integration.

  5. Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.

  6. Select Continue.
    The integration is saved at this point.

  7. Expand the Steps to configure the integration section and copy the endpoint URL generated for your account.
    You will use this URL while configuring the integration in Amazon CloudWatch Eventslater.

  8. Select Turn on integration.
    The rules you create for the integration will work only if you turn on the integration.

Configure the integration in Amazon CloudWatch Events

1. Go to the SNS dashboard and select Create Topic.

2. Fill in the required fields in the dialog and select Create topic.

3. On the Topic details page, select Create subscription.

4. Select HTTPS for Protocol.

5. In the Endpoint field, paste the URL you copied while adding the integration in Opsgenie.

CloudWatch Events create subscription

6. Select Create subscription.
If the configuration is successful, a confirmation alert is created in Opsgenie.

7. Go to the CloudWatch dashboard.

8. From the left side menu, select Events > Rules.

9. Select Create rule.

10. Select an Event Source to get notifications from.

11. Add the SNS topic previously created as the target.

CloudWatch event target

12. Select Configure details.

13. Enter a name for the rule and select Create rule.

Sample payload (in JSON format)

1 2 3 4 5 6 7 8 9 10 11 { "Type": "Notification", "MessageId": "96d4c7c2-999e-57ab-aade-95f2f518987f", "TopicArn": "arn:aws:sns:us-west-2:450xxxxxxx:test", "Message": "{\"version\":\"0\",\"id\":\"3ee38987-e0ce-29f1-91a1-32704265286f\",\"detail-type\":\"EC2 Instance State-change Notification\",\"source\":\"aws.ec2\",\"account\":\"4500xxxxxx\",\"time\":\"2017-09-11T10:49:41Z\",\"region\":\"us-west-2\",\"resources\":[\"arn:aws:ec2:us-west-2:4500xxxxxxx:instance/i-04d6ebefdb7xxxx\"],\"detail\":{\"instance-id\":\"i-04xxxxxx\",\"state\":\"terminated\"}}", "Timestamp": "2017-09-11T10:49:42.630Z", "SignatureVersion": "1", "Signature": "Iv8exxxx/DIfFd0eZ4eyo4vjrb/wEEoNji9S3xGQtpo1E9gXyMM8spmrULq20o25+OKXwZd5tRue7D69olvdcUdqRAN/bBfaHHq6tKVxnVnidgNq1VknAMeQRgd8qwVW1gARXTdO2z9AeDrOCH/ozEgNK3vwoFsDDxwKFxlFa9aioxxOu0uGlyuUpIb2rOaOwSo0aloE14XY9tgWrGlAxp+YwyHJbwXj36oAAU0GZOZV5C4TMhnRIdBnI9Yxxxxxxxx/tj6+gRnP4KeldOFHpaBGdw3/hOMdq9vA8yH934sA==", "SigningCertURL": "https://sns.us-west-2.amazonaws.com/SimpleNotificationService-433026a4050d2xxxxxxxxxx.pem", "UnsubscribeURL": "https://sns.us-west-2.amazonaws.com/?Action=Unsubscribe&SubscriptionArn=arn:aws:sns:us-west-2:4500xxxxxxx:test:5c91fe30-xxxxx-4627-a7f7-xxxxxxx" }

Payload parsed by Opsgenie (in JSON format)

1 2 3 4 5 6 7 8 9 { "id":"5c1f7731-23e0-0e90-124f-38ddb2811b49", "detail-type":"EC2 Instance State-change Notification", "source":"aws.ec2", "account":"4500xxxxxxx", "time":"2017-09-11T10:03:33Z", "region":"us-west-2", "detail":{"instance-id":"i-04d6ebxxxxxxxxx","state":"stopping"}}" }

Still need help?

The Atlassian Community is here for you.