GCP Regions Atlas Mapping
Parent: MongoDB Atlas on GCP · Published reference · snapshot 2026-10-23 · skill mongodb-cohort-e97ebaff6742
↓ Facts as markdownall context files
Source-anchored research for GCP Regions Atlas Mapping. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Comparisons and alternatives
- Atlas cluster management uses Atlas region identifiers rather than native GCP location strings. Google’s deployment tutorial explicitly keeps separate atlas_cluster_region and google_cloud_region inputs. (high confidence) [source]
- The cached Atlas GCP reference says all listed regions support M10+ dedicated clusters, while Free/Flex coverage varies. Gen2 has a separate supported-region table. Check the relevant feature and generation rather than assuming one universal region matrix. (low confidence) (verified as of 2026-10-14) [source]
Facts and statements
- Mappings include us-central1 → CENTRAL_US, us-east1 → EASTERN_US, us-west1 → WESTERN_US, and europe-west1 → WESTERN_EUROPE. These aliases make a general hyphen-to-underscore uppercase conversion unsafe. (high confidence) [source]
- Other legacy mappings include asia-east1 → EASTERN_ASIA_PACIFIC, asia-northeast1 → NORTHEASTERN_ASIA_PACIFIC, and asia-southeast1 → SOUTHEASTERN_ASIA_PACIFIC; us-east4 maps to US_EAST_4. (high confidence) [source]
- Relaycorp’s Awala codelab pairs google_region = europe-west1 with the Atlas backing-provider region WESTERN_EUROPE. This independently illustrates the Belgium mapping, but its historical serverless resource is not evidence of current tier availability. (high confidence) [source]
- The Atlas CLI documentation illustrates its GCP endpoint command with --region CENTRAL_US, consistent with the Atlas identifier for us-central1. (high confidence) [source]
- The terraform-mongodbatlas-atlas-gcp module documents atlas_to_gcp_region as an overridable map and accepts either naming format in its region inputs. This is module behavior, not evidence that the underlying Atlas API accepts both. (low confidence) (verified as of 2026-10-23) [source]
- Atlas documents that different hardware in certain GCP regions can prevent some multi-region M10/M20 combinations. Gen2 multi-region configurations also require every participating region to support Gen2. (low confidence) (verified as of 2026-10-18) [source]
- For GCP clusters, us-central1 maps to CENTRAL_US, us-east1 to EASTERN_US, us-west1 to WESTERN_US, and us-east4 to US_EAST_4. (high confidence) [source]
- Do not derive Atlas identifiers by merely uppercasing Google region names and replacing hyphens: CENTRAL_US and WESTERN_EUROPE are counterexamples. Use an explicit mapping. (high confidence) [source]
- A matching region identifier does not establish tier availability. Atlas separates tier support, and Google’s deployment tutorial explicitly requires selecting a region that supports its chosen M0 tier. (high confidence) [source]
- Google’s October 10, 2022 tutorial prints us-central1/US_CENTRAL, but the Atlas reference and module map use CENTRAL_US. Treat US_CENTRAL in that tutorial as a conflicting example, not the cluster mapping. (high confidence) [source]
Children
- No children recorded.