Sending Amazon SNS messages to an Amazon SQS queue in a different account - Amazon Simple Notification Service

Sending Amazon SNS messages to an Amazon SQS queue in a different account

You can publish a notification to an Amazon SNS topic with one or more subscriptions to Amazon SQS queues in another account. You set up the topic and queues the same way you would if they were in the same account (see Fanout to Amazon SQS queues). The major difference is how you handle subscription confirmation, and that depends on how you subscribe the queue to the topic.

Queue owner creates subscription

The account that created the Amazon SQS queue is the queue owner. When the queue owner creates a subscription, the subscription doesn't require confirmation. The queue begins to receive notifications from the topic as soon as the Subscribe action completes. To let the queue owner subscribe to the topic owner's topic, the topic owner must give the queue owner's account permission to call the Subscribe action on the topic.

Step 1: To set the topic policy using the AWS Management Console

  1. Sign in to the Amazon SNS console.

  2. On the navigation panel, choose Topics.

  3. Select a topic and then choose Edit.

  4. On the Edit MyTopic page, expand the Access policy section.

  5. Enter the following policy:

    { "Statement":[{ "Effect":"Allow", "Principal":{ "AWS":"111122223333" }, "Action":"sns:Subscribe", "Resource":"arn:aws:sns:us-east-2:123456789012:MyTopic" }] }

    This policy gives account 111122223333 permission to call sns:Subscribe on MyTopic in account 123456789012.

  6. Choose Save changes.

    A user with the credentials for account 111122223333 can subscribe to MyTopic.

Step 2: To add an Amazon SQS queue subscription to a topic in another AWS account using the AWS Management Console

Before you begin, make sure you have the ARNs for your topic and queue and that you have given permission to the topic to send messages to the queue.

  1. On the navigation panel, choose Subscriptions.

  2. On the Subscriptions page, choose Create subscription

  3. On the Create subscription page, in the Details section, do the following:

    1. For Topic ARN, enter the ARN of the topic.

    2. For Protocol, choose Amazon SQS.

    3. For Endpoint, enter the ARN of the queue.

    4. Choose Create subscription.

      • To be able to communicate with the service, the queue must have permissions for Amazon SNS.

      • Because you are the owner of the queue, you don't have to confirm the subscription.

A user who does not own the queue creates subscription

Any user who creates a subscription but isn't the owner of the queue must confirm the subscription.

When you use the Subscribe action, Amazon SNS sends a subscription confirmation to the queue. The subscription is displayed in the Amazon SNS console, with its subscription ID set to Pending Confirmation.

To confirm the subscription, a user with permission to read messages from the queue must visit the subscription URL. Until the subscription is confirmed, no notifications published to the topic are sent to the queue. To confirm the subscription, you can use the Amazon SQS console or the ReceiveMessage action.


Before you subscribe an endpoint to the topic, make sure that the queue can receive messages from the topic by setting the sqs:SendMessage permission for the queue. For more information, see Step 2: Give permission to the Amazon SNS topic to send messages to the Amazon SQS queue.

To confirm a subscription using the AWS Management Console

  1. Sign in to the Amazon SQS console.

  2. Select the queue that has a pending subscription to the topic.

  3. Choose Queue Actions, View/Delete Messages and then choose Start Polling for Messages.

    A message with the subscription confirmation is received in the queue.

  4. In the Body column, do the following:

    1. Choose More Details.

    2. In the Message Details dialog box, find and note the SubscribeURL value, for example:
  5. In a web browser, navigate to the URL.

    An XML response is displayed, for example:

    <ConfirmSubscriptionResponse> <ConfirmSubscriptionResult> <SubscriptionArn>arn:aws:sns:us-east-2:123456789012:MyTopic:1234a567-bc89-012d-3e45-6fg7h890123i</SubscriptionArn> </ConfirmSubscriptionResult> <ResponseMetadata> <RequestId>abcd1efg-23hi-jkl4-m5no-p67q8rstuvw9</RequestId> </ResponseMetadata> </ConfirmSubscriptionResponse>

    The subscribed queue is ready to receive messages from the topic.

  6. (Optional) If you view the topic subscription in the Amazon SNS console, you can see that the Pending Confirmation message has been replaced by the subscription ARN in the Subscription ID column.