AWS Transform for migrations now supports all AWS commercial regions as migration targets
Migrate workloads to any AWS commercial region—including 16 newly added—making data residency compliance far simpler.
View original announcement →Visual Summary
graph TD
A{{AWS Transform Region Expansion}}:::announced
B((Customer)):::external
C([Target Region Selection]):::feature
D(AWS Migration Hub):::compute
E(Application Migration Service):::compute
F(Amazon S3):::storage
G([Landing Zone Build]):::feature
H([Network Infrastructure]):::feature
I([Data Residency Compliance]):::feature
J(CloudFormation StackSets):::compute
B ==>|"initiates migration"| A
A -->|"workflow step"| C
C -->|"deploys to"| G
C -->|"provisions"| H
A -->|"orchestrates"| D
A -->|"rehost servers"| E
A -->|"read/write"| F
A -.->|"multi-account"| J
C -.->|"enables"| I
classDef announced fill:#ff9900,stroke:#ec7211,color:#fff,font-weight:bold
classDef compute fill:#e3f2fd,stroke:#1565c0,color:#1565c0
classDef storage fill:#e8f5e9,stroke:#2e7d32,color:#2e7d32
classDef feature fill:#fff3e0,stroke:#e65100,color:#e65100
classDef external fill:#f5f5f5,stroke:#616161,color:#616161
What's New
AWS Transform for migrations has expanded its migration target region support to cover all AWS commercial regions, adding 16 new regions to the previously supported set. A migration target region is where migrated resources—including landing zones, network infrastructure, and rehosted servers—are actually deployed after migration. This expansion enables customers to migrate workloads to any commercial AWS region, directly addressing data residency and sovereignty requirements that previously constrained migration destination choices.
How It Works
- Target region selection: During the AWS Transform for migrations workflow, users can now select any AWS commercial region as the destination for migrated resources, including landing zones, VPC/network infrastructure, and rehosted servers.
- Single and multi-account support: Migrations can target a single AWS account (where the connector and target account are the same) or span multiple accounts via an AWS Organizations management account or Delegated Administrator account registered for AWS Transform MGN and CloudFormation StackSets.
- Connector-based deployment: A target account connector is configured to grant AWS Transform the necessary permissions—covering Amazon S3, AWS Migration Hub, and AWS Application Migration Service (MGN)—to orchestrate resource deployment in the chosen region.
- MAP integration: If the migration is part of the AWS Migration Acceleration Program (MAP 2.0), users provide an MPE ID, and the
map-migratedtag is automatically applied to all resources across network, landing zone, and server rehost stages in the target region. - Consistent workflow: The region selection step is embedded in the existing Transform for migrations workflow, requiring no separate process or tooling change—users simply select the desired target region during connector configuration.
Why It's Important
- Data residency compliance: Organizations operating under strict data sovereignty laws (e.g., GDPR, local data localization mandates) can now migrate workloads to the specific AWS region required by regulation, without workarounds or exceptions.
- Broader geographic reach: The addition of regions such as Africa (Cape Town), Middle East (Tel Aviv), Asia Pacific (Kuala Lumpur, Bangkok, Taipei, New Zealand), and Mexico (Querétaro) opens AWS Transform to customers in markets that were previously unsupported as migration targets.
- Reduced migration friction: Customers no longer need to use alternative migration tooling for specific regions, allowing a single, consistent workflow across all commercial AWS regions.
- Enterprise and regulated industry enablement: Financial services, healthcare, and government customers with strict locality requirements can now fully leverage AWS Transform's automated landing zone and rehosting capabilities in their required regions.
- Operational consistency: Uniform tooling across all regions simplifies training, runbooks, and governance processes for large-scale migration programs.
How It's Different
- Previously limited region set: Before this update, AWS Transform for migrations only supported a subset of AWS commercial regions as migration targets; customers in unsupported regions had to rely on other tools or manual processes.
- Full commercial parity: Unlike many AWS services that roll out region support incrementally over months or years, this update achieves full commercial region coverage in a single release, eliminating regional gaps immediately.
- Integrated vs. point-tool approach: Competing or complementary migration tools (e.g., CloudEndure, manual MGN configurations) require separate setup per region; AWS Transform provides a unified workflow that now spans all commercial regions.
- Automated infrastructure deployment: AWS Transform automates landing zone creation, network migration, and server rehosting as a coordinated pipeline—not just server lift-and-shift—making the region expansion more comprehensive than simple replication-tool updates.
- MAP tag propagation across regions: The automatic application of MAP 2.0 tags to all resources in any target region ensures customers receive migration credits regardless of which commercial region they target.
When to Prefer It
- Strict data residency requirements: Choose AWS Transform when your organization must deploy migrated workloads in a specific country or jurisdiction (e.g., South Africa, Switzerland, New Zealand) to comply with local data protection laws.
- Large-scale VMware migrations: Use AWS Transform when migrating VMware-based workloads at scale and you need automated landing zone provisioning, network setup, and server rehosting in a newly supported region.
- MAP-enrolled migration programs: Prefer AWS Transform when your migration is part of AWS MAP 2.0 and you need automatic tag propagation to all resources in the target region to ensure credit eligibility.
- Multi-account enterprise migrations: Use this service when migrating workloads across multiple AWS accounts in regions like Asia Pacific (Jakarta) or Europe (Zurich), where centralized orchestration via Organizations is required.
- Standardizing migration tooling globally: Prefer AWS Transform when your organization wants a single, consistent migration workflow across all global AWS regions rather than managing region-specific tooling variations.
- Emerging market expansions: Ideal when a business is establishing a new AWS presence in regions like Mexico (Querétaro), Asia Pacific (Bangkok), or Africa (Cape Town) and wants to migrate existing on-premises workloads directly into those regions.
Availability
- GA status: This feature is generally available as of June 22, 2026, with no preview or beta designation indicated.
- New target regions added: US East (N. California), Africa (Cape Town), Asia Pacific (Bangkok, Hong Kong, Hyderabad, Jakarta, Kuala Lumpur, Melbourne, New Zealand, Taipei), Canada (Calgary), Europe (Milan, Spain, Zurich), Mexico (Querétaro), and Middle East (Tel Aviv).
- Full commercial region coverage: All AWS commercial regions are now supported as migration targets; the previously supported regions remain available alongside the 16 new additions.
- Pricing: No separate pricing is stated for the region expansion; AWS Transform for migrations pricing applies as previously established (refer to the AWS Transform pricing page for current details).
- Limitations: AWS GovCloud and other non-commercial partitions are not included; users should consult the official supported migration target region list in the documentation for the most current availability details, as the list may be updated over time.
- Access point: Target region selection is available directly within the AWS Transform for migrations workflow in the AWS Management Console.
