How do I migrate my services to another region?

This article is still being updated with guides for additional services. Please check back frequently for guidance on any services that are not covered. (latest update 06 March 2026 16:20 UTC)

This is part of a series of articles that provide general guidance on migrating resources from one Region to another. Domain-specific articles are linked at the end of this document.

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.

Obtain help from AWS Support

If you need additional assistance while following this guide or at any point, reach out to AWS Support to create a support case using the Support Center. You can start a support interaction that will guide you to get further support, including creating a case, or you can use the legacy experience to create a case.

Prepare an action plan to move Regions

• Be aware of any data residency requirements that you need to adhere to. Work with your compliance departments and authorities to ensure that you comply with these requirements.
• Have your infrastructure teams prepare the infrastructure in your destination Region while you prepare for data migration.
• Request Service Quota increases in the destination Regions as soon as possible to prevent delays while you wait for the quota increase to be fulfilled.
• Migrate your most critical workloads and data first to make sure that they are available in the shortest amount of time.
• Migrate any historical or bulk data that is not critical to the operation of your systems after all critical functions have been migrated.
• If you are using scripts or other automations for migration, then make sure to include backoff and retry logic to gracefully handle API throttling. For more information, see Retry with backoff pattern.

General Considerations

• If APIs, including the AWS Command Line Interface (AWS CLI), are unresponsive for an Availability Zone, then data migration from that Availability Zone is not possible using AWS methods.
• If APIs, including the AWS CLI, are unresponsive for a Region, then data migration from that Region is not possible using AWS methods.
• Inter-AZ and inter-Region migrations will have higher latency the further that your destination Region is from your source.
• Inter-AZ and inter-Region networking might experience congestion during recovery periods because of higher traffic caused by other migrations and external traffic trying to access recovered services.

Troubleshoot console access issues

If your console appears down, then first try explicitly going to another Region using a direct link. To find all the Region console endpoints, see AWS Management Console endpoints and quotas.

If you have turned on multi-session support in the past, this configuration might prevent you from accessing Regions that are in an impaired state. To turn off multi-session support, clear your browser cookies, or complete the following steps:

• Log in to https://us-east-1.console.aws.amazon.com/
• In the navigation bar, click on the down arrow next to the account at the top right to open the account menu.
• Choose Turn off multi-session support.
• On the screen that pops up, take the following actions:
  • Select Something else.
  • Choose Disable multi-session support and sign out.
• Log back in, and then use the Region selector to navigate to your Region of choice.

Use AWS CloudShell to run AWS CLI commands

If you don't have an AWS CLI-ready environment, then use AWS CloudShell to run CLI commands with the permissions of the user/role that you are logged into the AWS Console as. For more information, see the AWS CloudShell User Guide.

Enable the Region

Not all regions are enabled by default in AWS. Before beginning your migration, verify that the destination Region is enabled in your account. To enable a region in a standalone account, see Enable or disable a Region for standalone accounts. For accounts in an organization, see Enable or disable a Region in your organization.

To view a list of default Regions and opt-in Regions, see Regional availability reference.

Manage Service Quotas

Service Quotas (limits) in one Region are independent from quotas in another Region. When you migrate workloads to a new Region, make sure that your destination Region has sufficient Service Quotas to support your workloads.

Use the Service Quotas Replicator to compare Service Quotas

Use the aws-samples/sample-service-quotas-replicator-for-aws tool to automate quota comparison and replication across Regions. The tool automatically identifies all service quotas in source Region, compares them with the quotas in destination Region, and then generates a list of quotas that need increases.

Manual Service Quota comparison

If you can't use the Service Quotas Replicator, then complete the following steps to manually compare Service Quotas:

1. View your Service Quotas in the source Region.
2. View your Service Quotas in the destination Region.

Request Service Quota Increases

1. Request a quota increase in the destination Region to match your source Region using the AWS Management Console or the AWS CLI.
2. For urgent requests or if you can't increase a quota through the console, open a support case to request a service quota increase. When opening a support case, add context about the Region that you are migrating from and why it is urgent. These details help expedite the request.

Migrate your service

Article: How do I migrate my Security, Identity and Compliance resources to another region?
Services covered:

• AWS Identity and Access Management (IAM)
• AWS Security Token Service (AWS STS)
• AWS Key Management Service (AWS KMS)
• Amazon Cognito
• Amazon GuardDuty
• AWS Identity and Access Management Access Analyzer
• AWS IAM Identity Center
• AWS Secrets Manager
• AWS Certificate Manager (ACM)

Article: How do I migrate my Compute and Container resources to another region?
Services covered:

• Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Elastic Block Store (Amazon EBS)
• Amazon Elastic Container Service (Amazon ECS)
• Amazon Elastic Kubernetes Service (Amazon EKS)

How do I copy an EBS Snapshot to another region using coldsnap and the EBS Direct APIs? compliments the snapshot based approach used to migrate some of the services in How do I migrate my Compute and Container resources to another region?

Article: How do I migrate my Database resources to another region?
Services covered:

• Amazon Aurora
• Amazon DynamoDB
• Amazon ElastiCache
• Amazon Redshift
• Amazon Relational Database Service (Amazon RDS)

How do I migrate my Database resources to another region using a logical dump? compliments the snapshot based approach used to migrate some of the services in How do I migrate my Database resources to another region?

Article: How do I migrate my Networking and Content Delivery resources to another region?
Services covered:

• Amazon API Gateway
• Amazon Route 53
• AWS Client VPN
• AWS Direct Connect
• AWS Network Firewall
• AWS Site-to-Site VPN
• AWS Transit Gateway
• AWS WAF
• Elastic Load Balancing (ELB), including Application Load Balancer and Network Load Balancer

Article: How do I migrate my Storage resources to another region?
Services covered:

• Amazon FSx for NetApp ONTAP
• Amazon FSx for Windows File Server
• Amazon Simple Storage Service (Amazon S3)
• AWS Storage Gateway
• AWS Backup

Article: How do I migrate my Application Integration resources to another region?
Services covered:

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

---

In collaboration with Vania Toma and Francesco Penta