Skip to main content
Skip table of contents

AWS S3-SQS Cross Account Access Configuration

Instructions in this section contain the following designations:

  • Account A refers to the AWS Production account
  • Account B refers to the AWS Development account


  • Two separate AWS accounts that you can use, one to represent the Production account (Account A), and one to represent the Development account (Account B).
  • An Amazon S3 bucket created in Account A (Production). For instructions on how to create your S3 bucket, see
  • An SQS Queue on Account B (Development). 
    • Each SQS Queue must be in the same AWS Region as the S3 bucket on Account A.
    • Each S3 bucket requires ReceiveMessage, DeleteMessage, and GetQueueUrl Actions in the SQS Queue.

Configure S3-SQS Cross-Account Access

Update SQS Access policy 

  1. Log on to Account B as a user with administrator privileges.
  2. On the top menu bar, click Services, and then click Simple Queue Service.
  3. In the top-right corner, select your queue region.
  4. Select your queue from the queue list. 
  5. At the top of the window, click Edit.

  6. Click Access Policy, and then at the bottom click Policy generator.

    A new tab opens.
  7. In the Principal field under Step 2: Add Statement(s), type *.
  8. In the Actions drop down list, select Delete Message, Get Queue Url, Receive Message, and Send Message.
  9. In the Amazon Resource Name (ARN) field, enter your Queue ARN in the following format (replace <accountid> with the account ID of Account B and <queue name> with your queue name):

  10.  Click Add conditions
    1. In the Condition drop down list, select ArnLike.
    2. In the Key drop down list, select aws:sourceArn.
    3. In the Value field, enter arn:aws:s3:::<bucket_name> (replace <bucket_name> with the name of the bucket you created on Account A). 
      To add more than one bucket, enter the additional buckets separated with a comma.
  11. Click Add condition. The added condition will display and you will be allowed to add more conditions.
    1. In the Condition drop down list, select StringEquals
    2. In the Key drop down list, select aws:SourceAccount.
    3. In the Value field, enter the account IDs for Account A and Account B separated by a comma (for example, Account_A_ID, Account_B_ID).
      (Replace Account_A_ID, Account_B_ID with their actual account IDs.)
  12. Click Add Condition. Both of the added conditions will display.
  13. Click Add Statement

    The entire statement appears.
  14. Click Generate Policy.
  15. Copy the generated policy JSON.
  16. Go back to the SQS policy tab, and paste the generated policy JSON into the access policy text box. If you already have an SQS policy in use, then append it.
  17. Click Save.

Configure S3 Bucket on Account A to Send Message on SQS of Account B

  1. Log on to Account A as a user with administrator privileges.
  2. On the menu bar at the top, click Services, and then click S3.
  3. Click on the S3 bucket. (It should be in the same region as SQS on Account B).
  4. Click the Properties tab.
  5. Under Advanced settings, click Events.
  6. Select the Event identifier. 
  7. Click Edit.
    1. In the Events list, select All object create events.
    2. In the Send to drop down list, select SQS Queue.
    3. In the SQS to drop down list, select Add SQS queue ARN.
    4. In the SQS queue ARN field, type the SQS ARN of Account B.
  8. Click Save.

Verify the Configuration

  1. Log on to AWS Account A.
  2. On the menu bar at the top, click Services, and then click S3.
  3. Select the S3 bucket you just configured.
  4. Upload any file on the bucket.
  5. Log on to AWS Account B.
  6. On the top menu bar, click Services.

  7. In the search field, enter sqs, and then select Simple Queue Service from the suggested search results.

  8. Select the SQS you just configured.
  9. In the top-right of the window, click Send and receive messages.
  10. Click Receive messages.
  11. At the bottom, click Poll for messages.

    A list of received messages appears.
  12.  Click on the message to view the body of message and verify the file name that you previously uploaded on the bucket.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.