How do I migrate my Application Integration resources to another region?

If you are migrating data from the Middle East (UAE) Region (me-central-1), then you might experience increased error rates as we continue making progress with restoration efforts. For additional information about recovery efforts and service updates that impact your AWS accounts, see the AWS Personal Health Dashboard. For assistance with this event, contact AWS Support through the AWS Management Console or the AWS Support Center.

This is part of a series of articles that provide general guidance on migrating resources form one Region to another. It covers the following services:

• Amazon Simple Notification Service (Amazon SNS)
• Amazon Simple Queue Service (Amazon SQS)

For general guidance and a full list of domain and service-specific migration guides, see How do I migrate my resources to another region?

For other domains, see the following resources:

• How do I migrate my Security, Identity and Compliance resources to another region?
• How do I migrate my Compute and Container resources to another region?
• How do I copy an EBS Snapshot to another region using coldsnap and the EBS Direct APIs?
• How do I migrate my Database resources to another region?
• How do I migrate my Database resources to another region using a logical dump?
• How do I migrate my Networking and Content Delivery resources to another region?
• How do I migrate my Storage resources to another region?

Amazon Simple Notification Service (SNS)

Key Considerations and Preparation

• SNS topics are regional
• Topic ARNs will change in the new region
• Subscriptions must be recreated
• KMS keys are regional

Recreate Topics and Subscriptions

Create the SNS topics and their subscriptions in the target region.

1. Recreate topics using the Creating an Amazon SNS topic console or the create-topic CLI
2. Recreate subscriptions (HTTP, Email, SMS, Lambda, SQS) using the What is Amazon SNS? console or the subscribe CLI
3. Review and recreate KMS configuration if applicable using Securing Amazon SNS data with server-side encryption and Create a KMS key

Amazon Simple Queue Service (Amazon SQS)

Key Considerations and Preparation

• SQS queues are regional
• Queue URLs and ARNs will change in the new region
• Dead-letter queues must be recreated
• Lambda event source mappings must be updated
• KMS keys are regional

Recreate Queues and Configure Integrations

Create the SQS queues and reconnect any dependent services in the target region.

1. Recreate queues (Standard or FIFO) using the Creating an Amazon SQS standard queue and sending a message console or the create-queue CLI
2. Configure dead-letter queues using the Configure a dead-letter queue using the Amazon SQS console console or the create-queue CLI
3. Subscribe SQS queues to SNS topics (if applicable) using the Subscribing a queue to an Amazon SNS topic using the Amazon SQS console console or the subscribe CLI
4. Add Lambda event source mappings (if applicable) using the Configuring an Amazon SQS queue to trigger an AWS Lambda function console or the create-event-source-mapping CLI
5. Review and recreate KMS configuration if applicable using Encryption at rest in Amazon SQS and Create a KMS key

In collaboration with Vania Toma and Nymus Booysen