> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# AWS EventBridge Alert Events

> Sync AWS EventBridge alert events to Flashduty via webhook for automated alert noise reduction

Sync AWS EventBridge alert events to Flashduty via webhook for automated alert noise reduction.

<div class="hide">
  ## In Flashduty

  ***

  You can obtain an integration push URL through either of these two methods:

  ### Using Private Integration

  Choose this simpler option when you don't need to route alert events to different channels.

  <details>
    <summary>Expand</summary>

    1. Go to the Flashduty console, select **Channel**, and enter a channel's details page
    2. Select the **Integrations** tab, click **Add Integration** to enter the integration page
    3. Choose **AWS EventBridge** integration and click **Save** to generate a card
    4. Click the generated card to view the **push URL**, copy it for later use, and you're done
  </details>

  ### Using Shared Integration

  Choose this option when you need to route alerts to different channels based on the alert event payload.

  <details>
    <summary>Expand</summary>

    1. Go to the Flashduty console, select **Integration Center=>Alert Events** to enter the integration selection page
    2. Select **AWS EventBridge** integration:
       * **Integration Name**: Define a name for this integration
    3. Configure the default route and select the corresponding channel (after the integration is created, you can go to `Route` to configure more routing rules)
    4. Click **Save** and copy the newly generated **push URL** for later use
    5. Done
  </details>
</div>

## In AWS EventBridge

***

<div class="md-block">
  ## I. AWS EventBridge Alert Push Configuration

  <span id="1" />

  ### Step 1: Create Connection in API destinations

  1. Log in to your AWS Console, search for `Amazon EventBridge` product, and enter the corresponding product console
  2. Select `Integration=>API destinations` from the left navigation bar
  3. Click `Connections`, then click `Create connection`

  <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-3.png" />

  4. In the `Connection details` section, enter `Flashduty` for `Connection name`
  5. In the `Authorization` section, select `Other` for `Destination type`
  6. Select `API Key` for `Authorization type`
  7. Enter `Flashduty` for `API key name`, and enter the `integration_key` from the integration push URL for `Value`
  8. Click `Create` to save

  <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-4.png" />

  ### Step 2: Create API destination

  1. Return to the `API destinations` interface and click `Create API destination`

  <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-5.png" />

  2. Fill in the information in the `API destination detail` editing interface, enter `Flashduty` for `Name`
  3. Enter the integration push URL for `API destination endpoint`
  4. Select `POST` for `HTTP method`
  5. Select `Use an existing connection` for `Connection type` and choose the `Flashduty` Connection added in Step 1
  6. Click `Create` to save

  <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-6.png" />

  ### Step 3: Use the API destination created in Step 2 in EventBridge Rules

  1. Log in to your AWS Console, search for `Amazon EventBridge` product, and enter the corresponding product console
  2. Select `Buses=>Rules` from the left navigation bar, create or edit existing rules
  3. Other configurations are omitted here
  4. For `Target types`, select `EventBridge API destination` as the target type
  5. Under `API destination`, select `Use an existing API destination` and choose the `Flashduty` API destination created in Step 2 from the dropdown
  6. Click `Next`, configure as needed, and save

  <img alt="drawing" width="600" src="https://download.flashcat.cloud/flashduty/doc/aws-eb-7.png" />

  ## II. Status Mapping

  <div class="md-block">
    1. Since AWS EventBridge events don't have severity levels, all events pushed to Flashduty will have a Warning severity
    2. AWS EventBridge events only have triggers without recovery states, so events received by Flashduty won't automatically associate with recovery
  </div>
</div>