Multi-Region Networking
Parent: MongoDB Atlas AWS Networking · Published reference · snapshot 2026-10-15
↓ Facts as markdownall context files
Depth-first rabbithole dossier for Multi-Region Networking; source-anchored research pack.
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.
Structure and components
- [medium] For multi-region MongoDB Atlas clusters, you must create a private endpoint for each region that contains a node, and private endpoints are only available if a node within each spanned region has a private endpoint configured. Sources: https://www.mongodb.com/docs/atlas/troubleshoot-private-endpoints.md, https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
How it works
- [low] For multi-region deployments using GCP port mapped endpoint services, port mapped connection strings work only when a port mapped endpoint service exists in every region where the cluster is deployed. This requirement does not apply if you have a regionalized private endpoint. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
- [low] When moving from a multi-region to a single-region cluster, you can remove old private endpoints only after verifying the cluster is fully functional in the new setup and all traffic is directed through the new single-region configuration. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
Measurements and reference values
- [low] Organizations can scale seamlessly with horizontal and vertical auto-scaling, maintain low latency with multi-region clusters, and benefit from a 99.995% uptime SLA. (verified as of 2026-10-15) Sources: https://aws.amazon.com/marketplace/pp/prodview-pp445qepfdy34 [source]
Facts and statements
- [low] For multi-region deployments, you can combine legacy and port mapped endpoint services to test port mapped endpoints before completing migration off legacy endpoints. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
- [low] For a multi-region cluster, the cluster's own cloud provider private link service (AWS PrivateLink, Azure Private Link, or GCP Private Service Connect) must be active in every region where the cluster is deployed; otherwise the private endpoint configuration is incomplete and the SRV connection string might not resolve. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
- [low] The private endpoint connection string for a multi-region cluster uses an index of 0, and MongoDB automatically updates the connection string to use this index if a different index is provided. Sources: https://www.mongodb.com/docs/atlas/troubleshoot-private-endpoints.md [source]
- [low] If you are performing maintenance on a multi-region cluster, do not alter or remove private endpoints until maintenance is complete to avoid cluster downtime. Sources: https://www.mongodb.com/docs/atlas/security-private-endpoint.md [source]
Related concepts
- Multi-Region — is a part of Multi-Region Networking
Children
- No children recorded.