# AWS Health Dashboard Integration Guide | PagerDuty Configure the AWS Health Dashboard integration ## AWS Health Dashboard + PagerDuty Benefits - The AWS Health Dashboard integration allows you to automate response workflows for infrastructure problems that may be impacting your AWS services. - Send issues and scheduled changes from AWS to PagerDuty. ## Requirements **To Configure the Integration**: - **In PagerDuty**: Managers, Admins, Global Admins and the Account Owner can configure the integration. - **In AWS**: Users who set up and manage AWS Config must have full-access permissions. Please read Amazon’s AWS Config documentation for more information about managing permissions in AWS. ## How it Works - When AWS is experiencing problems, Amazon EventBridge sends AWS Health Dashboard events to PagerDuty. - These events then generate PagerDuty incidents and notify responders. ## Version This guide details configuration of the **AWS Health Dashboard V1** integration. ## Integration Walkthrough ### In PagerDuty There are three ways to integrate AWS Health Dashboard with PagerDuty: - [Integrate With Event Orchestration](#integrate-with-event-orchestration): Integrating with [Event Orchestration](/ai-automation/aiops/event-orchestration) may be beneficial if you want to build nested rules based on the payload coming from AWS. - [Integrate With Rulesets](#integrate-with-rulesets): Integrating with [global or service-level event rules](/ai-automation/aiops/rulesets) may be beneficial if you want to build different rules based on the payload coming from AWS. - [Integrate With a PagerDuty Service](#integrate-with-a-pagerduty-service): Integrating with a [PagerDuty service](/incident-management/services/services-and-integrations) 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 Orchestration to perform actions such as [suppressing](/ai-automation/aiops/event-orchestration#incident-data). **Integrate With Event Orchestration** ##### Configure a Global Orchestration Integration 1. [Configure a Global Orchestration](/ai-automation/aiops/event-orchestration#global-orchestrations) in your PagerDuty account. 2. Navigate to **AIOps** → **Event Orchestration** → click the **name** of your Global Orchestration. 3. Click **Integrations** and then copy the **Integration Key**. 4. Once you have your **Integration Key**, the **Integration URL** will be: `https://events.pagerduty.com/x-ere/[YOUR_INTEGRATION_KEY_HERE]` You can now proceed to the [In the AWS Management Console](#in-the-aws-management-console) section below. **Integrate With Rulesets** > **End-of-Life:** Rulesets and Event Rules reached end-of-life on January 31, 2025 and are no longer visible in the PagerDuty web app. We highly recommend that you [migrate to Event Orchestration](/ai-automation/aiops/migrate-to-event-orchestration). Access and modifications to event rules are still possible via the [API](/developer/global-event-rules-api). ##### Configure a Global Ruleset Integration 1. Utilize our [API](/developer/api/reference/rest/rulesets/list-rulesets) to list your rulesets and their **routing keys**. The routing key will be used as the **Integration Key**. 2. Once you have your **Integration Key**, the **Integration URL** will be: `https://events.pagerduty.com/x-ere/[YOUR_INTEGRATION_KEY_HERE]` Keep this URL in a safe place for later use. You can now proceed to the [In the AWS Management Console](#section-in-the-aws-management-console) section below. **Integrate With a PagerDuty Service** ##### Add to a New Service 1. To [add the integration to a new service](/incident-management/services/services-and-integrations#create-a-service), navigate to **Services** → **Service Directory** and click **New Service**. 2. Follow the prompts and [configure the service](/incident-management/services/services-and-integrations#create-a-service) to your preferences. On the Integrations screen, select **AWS Health Dashboard** from the search bar dropdown. 3. Enter your service settings and click **Create Service**. 4. You will now be in the service’s Integrations tab. Find your integration in the list and click to view and copy your **Integration URL**. Keep it in a safe place for later use. 5. You can now proceed to the [In the AWS Management Console](#in-the-aws-management-console) section below. ##### Add to an Existing Service 1. To [add an integration to an existing service](/incident-management/services/services-and-integrations#add-integrations-to-an-existing-service), go to **Services** → **Service Directory** and select the **service** where you would like to configure the integration. Select the **Integrations** tab and click **Add an Integration**. 2. Select **AWS Health Dashboard** from the search bar dropdown. 3. Click **Add**. Find your integration in the list and click to the right to view and copy your **Integration URL**. Keep it in a safe place for later use. 4. You can now proceed to the [In the AWS Management Console](#in-the-aws-management-console) section below. ### In the AWS Management Console #### Create a Topic and Subscription 1. In the Services search bar, search and select **Simple Notification Service**. In the SNS dashboard left menu, select **Topics** and click **Create Topic** on the right. This topic will be used to route alerts to PagerDuty from AWS. 2. Select the **Standard** Topic **Type**. 3. Next, perform the following: - **Name**: Enter a **name** for your topic. You may want to name your topic after your PagerDuty service’s name. - **Display name** (_optional_): Enter an optional **display name**. - Click **Create topic**. 4. Now that your topic has been created, select **Subscriptions** in the left menu and click **Create Subscription**. 5. Perform the following: | Field | Instructions | | :------------------------------ | :------------------------------------------------------------------------ | | **Topic ARN** | Select the **Topic ARN** of the topic you just created. | | **Protocol** | Select **HTTPS**. | | **Endpoint** | Paste your **Integration URL** from PagerDuty (generated in steps above). | | **Enable raw message delivery** | Ensure this checkbox is **unchecked**. | 6. Click **Create Subscription**. Your subscription should be automatically confirmed. Refresh the page to make sure the **Status** is `Confirmed` and not `PendingConfirmation`. #### Create an EventBridge Rule 1. Next you will create a rule to [trigger an EventBridge alarm](https://docs.aws.amazon.com/health/latest/ug/cloudwatch-events-health.html). Search and select **Amazon EventBridge** in the Services search bar. 2. Select **Rules** in the left menu and then click **Create rule** on the right. 3. On the next screen, perform the following: | Field | Instructions | | :-------------------------------------------- | :---------------------------------------------------------- | | **Name** | Enter a **name** that can be easily identified. | | **Description** | Enter a **description** of the rule, pattern and target(s). | | **Event Bus** | Select **default**. | | **Enable the rule on the selected event bus** | Toggle to the **on** position. | | **Rule with an event pattern** | This will automatically be preselected. | Click **Next** to continue. 4. On the next screen, perform the following: | Field | Instructions | | :--------------------------------- | :--------------------------------------------------------------------------------------------------------------------- | | **Event source** | Select **AWS events or EventBridge partner events**. | | **Sample event type** (_optional_) | If you would like to view sample events, you may do so in this section. | | **Method** | Select **Use pattern form**. | | **Event pattern - Event source** | Select **AWS services**. | | **AWS service** | Select **Health**. | | **Event type** | You may select **All Events**, **AWS API Call via CloudTrail** or **Specific Health Events** based on your preference. | Click **Next** to continue. 5. On the next screen, perform the following: | Field | Instructions | | :------------------ | :--------------------------------------------------------- | | **Target types** | Select **AWS service**. | | **Select a target** | Search and select **SNS topic**. | | **Topic** | Search and select the **topic** created in previous steps. | Configure other additional settings to your preference. Click **Next** to continue. 6. _Optionally_ add tags to your preference. Click **Next** to continue. 7. On the final screen, review your settings and click **Create Rule**. If you would like to create more rules, repeat the steps to create additional EventBridge rules. Now that you have configured EventBridge to send AWS Health Dashboard notifications to PagerDuty, your responders will immediately be notified when AWS is experiencing problems. ## Uninstall the AWS Health Dashboard Integration Please refer to our [Services and Integrations](/incident-management/services/services-and-integrations#delete-an-integration) article to learn more about uninstalling or deleting an integration. ## FAQ **Why are my EventBridge events not triggering incidents in PagerDuty?** Events that are not sent properly from EventBridge will be dropped and will not trigger alerts in PagerDuty. This integration expects to find in the `Message` property a nested JSON-encoded object from which meaningful data about the alert can be extracted to compose the PagerDuty incident. You can find details on [Amazon's SNS Message attributes here](https://docs.aws.amazon.com/sns/latest/dg/sns-message-attributes.html). You can also refer to the Sample Events provided by Amazon in step 4 of [Create an EventBridge Rule](#create-an-eventbridge-rule) to see a Health Event example.