Get started with Opsgenie as a user
Learn how to configure your profile, get notifications from Opsgenie and view on-call schedules.
Integrate Opsgenie with Amazon Route 53 Health Check
Overview
What does the integration offer?
Use the Amazon Route 53 Health Check Integration to forward Amazon Route 53 Health Check alerts 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 an alert is created in Amazon Route 53 Health Check, an alert is automatically created in Opsgeniethrough the integration.
Set up the integration
Amazon Route 53 Health Check is an API-based integration. Setting it up involves the following steps:
Add an Amazon Route 53 Health Check integration in Opsgenie
Configure the integration in Amazon Route 53 Health Check
Add Amazon Route 53 Health Check 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.
Go to Teams and select your team.
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 Route 53 Health Check integration in Opsgenie:
Go to Settings > Integrations.
Select Add integration.
Run a search and select “Amazon Route 53 Health Check”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.Expand the Steps to configure the integration section and copy the integration URL, which includes Opsgenie endpoint and the API key.
You will use this URL while configuring the integration in Amazon Route 53 Health Check later.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 Route 53 Health Check
1. Create an SNS topic.
For details, see Getting started with Amazon SNS.
2. Add an HTTPS subscription to your topic with the URL you copied while adding the integration in Opsgenie as the endpoint.
If the configuration is successful, a confirmation alert is created in Opsgenie.
For details on how to add an HTTPS subscription, see What is an Amazon SNS?
3. Configure a health check to send notifications to the SNS topic you created.
a. For Create alarm, select Yes.
b. For Send Notification to, select Existing SNS Topic and select the SNS topic that you created.
c. Select Create health check.
For more details, see Monitoring health check status and getting notifications.
4. On the Get notified when health check fails window, do the following:
a. Select Yes and Send Notification to Existing Topic.
b. Select the topic created for Opsgenie.
c. Select Create Health Check.
Sample Webhook Message from Amazon Route 53 Health Check plugin
Sample Webhook message (in JSON format)
1
2
3
4
5
6
7
8
9
10
11
12
{
"Type" : "Notification",
"MessageId" : "fa97d391-ae96-585b-97dc-830e0d4935e9",
"TopicArn" : "arn:aws:sns:us-east-1:72918xxxxxxx:test-sns-for-route53",
"Subject" : "ALARM: \"try2-awsroute53-23065a3c-3d3d-467f-8930-xxxxxx-Low-Health...\" in US East - N. Virginia",
"Message" : "{\"AlarmName\":\"try2-awsroute53-23065a3c-3d3d-xxxx-x0-82cbb897a5ab-Low-HealthCheckStatus\",\"AlarmDescription\":null,\"AWSAccountId\":\"729181xxxxxx\",\"NewStateValue\":\"ALARM\",\"NewStateReason\":\"Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0).\",\"StateChangeTime\":\"2016-11-11T10:46:55.660+0000\",\"Region\":\"US East - N. Virginia\",\"OldStateValue\":\"INSUFFICIENT_DATA\",\"Trigger\":{\"MetricName\":\"HealthCheckStatus\",\"Namespace\":\"AWS/Route53\",\"Statistic\":\"MINIMUM\",\"Unit\":null,\"Dimensions\":[{\"name\":\"HealthCheckId\",\"value\":\"23065a3c-xxxx-467f-8930-82cbb897a5ab\"}],\"Period\":60,\"EvaluationPeriods\":1,\"ComparisonOperator\":\"LessThanThreshold\",\"Threshold\":1.0}}",
"Timestamp" : "2016-11-11T10:46:55.762Z",
"SignatureVersion" : "1",
"Signature" : "YuaEzc4ZGxWI68sBukJ0+Bn5NpI2uLpKJwmVU5uhj7+xxxxS+YprbcNH0fT22QyzxCt5oyouFMJO860ULeV8KNd0GZjJhg6xukxiXQJk3pTe9ecvqRDQVsTnVOZUII9+ITZNEFgsQ3mIZXElb8hhJixnPZJEVYSutqyDtA807HS9LSL5aLrnNCOBzqAx493phcf6b60DeyX2+m1N8WAjclDTC6UwJwaIRX+5OHnfi2+xxxxxxxxxxxxxHRcgaj2XLhe5jApIHp5L8QnVGhBpopJ56gNytvCj7/5FWg==",
"SigningCertURL" : "https://sns.us-east-1.amazonaws.com/SimpleNotificationService-b95095bebxxxxxafc7f4149a.pem",
"UnsubscribeURL" : "https://sns.us-east-1.amazonaws.com/?Action=Unsubscribe&SubscriptionArn=arn:aws:sns:us-east-1:72918xxxxxx:test-sns-for-route53:d6533783-f9a2-xxxxxd2-3bcedd92a8ec"
}
Payload parsed by Opsgenie (in JSON format)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
[
"Type" : "Notification",
"MessageId" : "fa97d391-ae96-xxxxx-830e0d4935e9",
"TopicArn" : "arn:aws:sns:us-east-1:72918xxxxxx:test-sns-for-route53",
"Subject" : "ALARM: \"try2-awsroute53-23065a3c-3xxxxx4xxx-82cbb897a5ab-Low-Health...\" in US East - N. Virginia",
"AlarmName" : "try2-awsroute53-23065a3c-3d3d-467xxxxxxxx-Low-HealthCheckStatus",
"AlarmDescription" : null,
"AWSAccountID" : "72918xxxxxx",
"NewStateValue" : "ALARM",
"NewStateReason" : "Threshold Crossed: 1 datapoint (0.0) was less than the threshold (1.0).",
"StateChangeTime" : "2016-11-11T10:46:55.660+0000",
"Region" : "US East - N. Virginia",
"OldStateValue" : "INSUFFICIENT_DATA"
]
Was this helpful?
Still need help?
The Atlassian Community is here for you.