1{2 "_what_this_is": "Azure region -> default AWS region. Consumed by design-refs/index.md's region handling and by Clarify's global.target_region default.",3 "_selection_rule": "Nearest AWS region by geography, preferring the same country where one exists and the same regulatory bloc otherwise. This is a DEFAULT, not a determination.",4 "_override": "global.target_region in preferences.json ALWAYS wins. A customer with a data-residency obligation, an existing AWS footprint, or a latency requirement has a reason this table cannot see.",5 "_residency_warning": "Several Azure regions have no AWS region in the same country. Where _same_country is false, the move crosses a border, and that can breach a residency commitment the customer has made to their own customers. Emit a warning; never resolve it silently.",6 "_provenance": "Authored from published region geographies. Region availability changes; verify the target region offers the services in the design before committing.",7
25 "note": "No AWS region in the Netherlands. eu-central-1 (Frankfurt) is the alternative and is often the better latency choice for Dutch and German users."
72 "note": "AWS Asia Pacific (New Zealand), ap-southeast-6, GA since 2025-09-30. Same-country default; confirm the specific services needed are available there and the account has opted in, otherwise fall back to ap-southeast-2 (Sydney)."
73 },
74 "chinanorth3": {
75 "aws": null,
76 "same_country": true,
77 "geo": "China",
78 "note": "Azure China is operated by 21Vianet under a separate tenant and separate ARM endpoints. AWS China (Beijing / Ningxia) is likewise operated separately and requires its own account and ICP filing. This is NOT a region mapping -- it is a separate migration with its own legal entity work. STOP and say so."
85 "note": "Azure Government to AWS GovCloud. Separate partition, separate credentials, and compliance scope carries over rather than being re-derived."
90 "_unlisted_region": "Resolve by geography from the Azure region's published location, prefer the same country, and record sizing_provenance-style honesty: state that the region default was derived rather than looked up. Never invent an AWS region name -- an invalid region makes every downstream price wrong and the Terraform unapplyable."