Note while I work with AWS Cross-regions working: This is an interesting topic that I should write a separated one on this. However some brief information including: SQS (queue-owner) subscribes to SNS (topic-owner) in another account : When it is within one account it sounds more simple, but when cross-accounts things get more complicated. And it boils down to SQS and SNS policies . It can be done in two ways: from SQS and from SNS. I experience the later case: Imagine you have an existing SQS queue in one account and want to send information from different services (SNS, lambda...) to that queue. In this case you want to add a subscription from services to SQS. SQS must confirms the subscriptions before SNS can send the message. SQS policy always should allow sqs:SendMessage from the subscription account. In case of lambda service, lambda role needs to allow ... In case of SNS service, SNS needs to create subscription. This subscription message will be sent to SQS queue for confirm...