AWS Personal Health Dashboard Integration Guide | PagerDuty

Integration Guide for AWS Personal Health Dashboard

Integration Overview

PagerDuty’s integration with AWS Personal Health dashboard enables you to immediately receive notifications about problems with AWS Services, via PagerDuty. This can be especially helpful when there are infrastructure problems that may be impacting your services. This is a one-way integration, sending both issues and scheduled changes to PagerDuty.

Follow the instructions below to configure AWS Personal Health Dashboard with PagerDuty. If you have any questions or need any assistance, please contact our Support team.

In PagerDuty

There are two ways that AWS Personal Health Dashboard can be integrated with PagerDuty: via Event Rules or through an integration on a PagerDuty Service.

Integrating with Event Rules

Integrating with global or service-level event rules may be beneficial if you want to build different rules based on the payload coming from AWS. If you would like to learn more, please visit our article on Rulesets.

Configure a Global Event Rules Integration

  1. From the Automation menu, select Event Rules and click your Default Global Ruleset.
  2. On the Event Rules screen, copy your Integration Key.
  1. Once you have your Integration Key, the Integration URL will be:[YOUR_INTEGRATION_KEY_HERE]

You can now proceed to the In the AWS Management Console section below.

Configure a Service Event Rules Integration

To use service-level event rules:

  1. Navigate to Services Service Directory select your preferred service Integrations tab Add a new integration.
  2. Enter an Integration Name, select Use our API directly and select your preferred Events API version (Events API v2 or Events API v1). Click Add Integration.
  3. Find the new integration in your integrations list and click its name. On the next page, copy the Integration Key and paste it into the following URL:[YOUR_INTEGRATION_KEY_HERE]/enqueue

You can now proceed to the In the AWS Management Console section below.

Integrating with a PagerDuty Service

Integrating with a PagerDuty Service directly can be beneficial if you don’t need to route alerts from AWS to different responders based on the event payload. You can still use service-level event rules to perform actions such as suppressing.

  1. From the Services menu, select Service Directory.

  2. On your Services page: If you are creating a new service for your integration, click + New Service. It is recommended that you create a service specifically for AWS Personal Health Dashboard notifications.
    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 Add a new integration.

  3. Select AWS Personal Health Dashboard from the Integration Type menu and enter an Integration Name.
    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.

  4. Click the Add Service or Add Integration button to save your new integration. You will be redirected to the Integrations page for your service.

  5. Copy the Integration URL for your new integration.

In the AWS Management Console

  1. In the Services search bar, search and select Simple Notification Service (SNS). On the SNS dashboard, select Topics from the left menu and click Create Topic. This will be used to route alerts to PagerDuty from AWS
  2. Enter a Topic name (you may want to name your topic after your PagerDuty service’s name) and Display name, then click Create topic.
  3. Now that your topic has been created, Select Subscriptions in the left menu and click Create Subscription.
  4. Make sure HTTPS is the selected Protocol. Paste your Integration URL from step 5 (above) into the Endpoint field, ensure that the Enable raw message delivery checkbox is unchecked and click Create Subscription.
  5. Your subscription should be automatically confirmed. Click the refresh icon to make sure the Subscription ID is not PendingConfirmation.
  1. To navigate to the AWS Personal Health Dashboard, click the Alerts bell icon in the console navigation bar, then select View all alerts, and then select Dashboard in the left navigation bar.

  2. To create an alarm, click Set up notifications with CloudWatch Events in the upper right hand corner. Enter Health as the Service Name.
    Decide if you want to route all AWS Personal Health Dashboard notifications or only ones for specific services. For all events, set Event Type to All Events or alternatively select Specific Health events then choose the services you are interested in.

  1. Click Add target, select SNS topic in the dropdown menu, select the Topic you created above (in steps 1-5) and then click Configure details. In the Configure rule details section, assign a name and optional description for the rule, then click Create Rule.
  1. Now that you have configured CloudWatch to send AWS Personal Health Dashboard notifications to PagerDuty, your responders will immediately be notified when AWS is experiencing problems.

Congratulations, you have now integrated AWS Personal Health Dashboard with PagerDuty! For more information on how to adjust settings to deduplicate events within PagerDuty, please visit our article on Event Management.

Did this page help you?