Configure a webhook in AWS

Subscribe your endpoint webhook to a topic so that the endpoint receives messages published to that topic.

Before you begin

Ensure you have an account in AWS and have created a topic.

Role required: Responder, Manager, or Administrator

About this task

Note: While this integration with a third-party product is supported, the documentation here is based upon information provided by that third-party. More current information about the operation of that third-party’s system may be available from them directly.


  1. Log in to the AWS console.
    The AWS console.
  2. Search for Simple Notification Service.
    Simple Notification Service.
  3. Open Simple Notification Service.
    Simple Notification Service.
  4. On the navigation pane, click Topics.
    Click to open the Topics option.
  5. From the existing Topics list, click to open the topic for which you want to create a subscription.
    Open topic for subscription.
  6. Click the Subscriptions tab.
    The Create subscription option.
  7. Click Create subscription.
    Figure 1. Create subscription form
    Create subscription form.
  8. On the form, fill in the fields.
    Field Description
    Topic ARN The Amazon Resource Name (ARN) of a topic. This field is automatically set.
    Note: An Amazon Resource Name (ARN) is a file naming convention used to identify a particular resource in the Amazon Web Services (AWS) public cloud. ARNs, which are specific to AWS, help an administrator track and use AWS items and policies across AWS products and API calls.
    Protocol Type of endpoint. Select HTTPS.
    Endpoint Webhook URL that can receive notifications from AWS. For more information on how to generate a webhook URL, see Create a webhook endpoint for CloudWatch.
    Enable raw message delivery Option to avoid having endpoints process the JSON formatting of messages.
    Subscription filter policy (Optional) Attribute names and a list of values to each attribute name.
    Redrive policy (dead-letter queue) (Optional) A dead-letter queue to target for messages that can't be delivered to subscribers successfully. Messages that can't be delivered due to client errors or server errors are held in the dead-letter queue for further analysis or reprocessing.
    Create subscription form.
  9. Click Create subscription.
    If the subscription is successful, the subscription status will be changed to confirmed from pending.
    Message for a successful subscription.

    You are ready to subscribe to messages on the topic.

What to do next

Create a CloudWatch alarm in AWS