MongoDB Atlas Multi-Cloud
Parent: MongoDB Atlas · researched 2026-05-28T15:23:05.663Z· 10 sources · 12 concepts · skill mongodb-atlas-multicloud
- Designing Atlas PrivateLink on Azure — steps, CLI, Terraform, AKO
When to Use This Skill
- Designing Atlas PrivateLink on Azure - steps, CLI, Terraform, AKO [source]
- Setting up GCP Private Service Connect for Atlas [source]
- Planning multi-cloud replica set topology (write-concern latency tradeoffs) [source]
- Evaluating Atlas marketplace billing and MACC/CUD applicability [source]
- Architecting cross-cloud DR with Atlas [source]
- Auditing egress cost for multi-cloud clusters [source]
- Skip for: Deep Azure-only content (DNS zones, NSG, Entra ID OIDC, AKS) → use mongodb-atlas-azure; Deep GCP-only content (Shared VPC, Workload Identity, GKE, Vertex AI) → use mongodb-atlas-gcp; AWS-only networking → use mongodb-aws-networking. [source]
Setup Steps
- Request Private Endpoint in Atlas UI/API: POST /api/atlas/v2/groups/{groupId}/privateEndpoint/azure/endpointService [source]
- Atlas creates Azure Private Link Service backed by Standard Load Balancer [source]
- Azure creates NIC in your subnet with private IP [source]
- Status sequence: Creating → Available [source]
DNS
Legacy vs Port-Mapped
DNS for PSC
- Cloud DNS private zone. Allow TCP 27017 + high ports (1024-65535) through VPC firewall rules for SRV connection strings. [source]
Topology Options
- 3-node across 2 clouds (HA across clouds): [source]
- Primary: AWS US_EAST_1 [source]
- Secondary: GCP EASTERN_US [source]
- Secondary: Azure EASTUS [source]
- Write-concern latency: W:majority in multi-cloud = at least one write acknowledged from another cloud. Cross-cloud RTT typically 10-50ms. Use wtimeoutMS to prevent write stalls. [source]
- Read preference: Route reads to local secondary with readPreference: nearest + maxStalenessSeconds. [source]
Cross-Cloud DR Pattern
- Primary cloud (AWS): 3 electable nodes [source]
- DR cloud (Azure/GCP): 1-2 non-electable nodes (priority=0) or hidden secondaries [source]
- Hidden secondary in DR cloud: receives replication without being elected [source]
- Failover: promote DR nodes by changing priority [source]
- RPO: Near-zero (replication lag typically <1 second for healthy cluster) [source]
- RTO: 10-30 seconds for automatic election after primary failure [source]
Egress Cost Analysis
- Cross-cloud data transfer incurs egress charges: [source]
- AWS→GCP: ~$0.08/GB (US East) [source]
- AWS→Azure: ~$0.08/GB (US East) [source]
- GCP→AWS: ~$0.08/GB (US Central) [source]
- For a 3-replica-set with 10 GB/day replication across clouds: ~$0.80/day in egress costs. [source]
- Mitigation: Keep primary and majority of nodes in lowest-cost cloud. Use hidden secondaries in DR cloud to limit replication traffic. [source]
Azure MACC
- Atlas purchased via Azure Marketplace counts toward Microsoft Azure Consumption Commitment (MACC). Direct MongoDB invoices are NOT MACC-eligible. [source]
- MACC-eligible purchases: Atlas cluster compute/storage, Advanced Security, Dedicated Search Nodes, Stream Processing. [source]
- Azure Native MongoDB (ANM): First-party Azure resource in Azure Portal. Billing on Azure invoice (MACC-eligible). Generally at feature parity with standard Atlas. [source]
GCP Committed Use Discounts (CUD)
- GCP Marketplace Atlas purchases are EDP (Estimated Discount Program) eligible. GCP startup credits can be stacked. Committed use via GCP CUD contracts. [source]
AWS ISV Accelerate / ISV Workload Migration Program
- MongoDB is an AWS ISV Accelerate partner. Atlas clusters on AWS can qualify for AWS partner funding for customer migrations. [source]
Azure Preferred Solutions / MACC Impact Program
- MongoDB Atlas is an Azure Preferred Solution. Purchases via Marketplace impact partner competency and incentive credits. [source]
GCP Startup Ecosystem
- MongoDB participates in Google for Startups Cloud Program. Atlas credits available for eligible startups. [source]
Anti-Patterns
- Multi-cloud without read preference tuning: Default primary read preference sends all reads cross-cloud → high latency. Set readPreference: nearest. [source]
- Majority writes in high-latency multi-cloud setups without wtimeoutMS: Writes can block indefinitely if cross-cloud replication stalls. Always set wtimeoutMS. [source]
- Using VNet peering instead of Private Link for new Azure deployments: Private Link is recommended and simpler (no IP overlap constraints). [source]
- Legacy GCP PSC endpoints without migration plan: Must migrate to port-mapped before April 30, 2027. [source]
- Forgetting cross-cloud egress costs in TCO analysis: Multi-cloud replication incurs ~$0.08/GB egress. [source]
References
Children
- Atlas on Azure (frontier)
- Azure Private Link for Atlas (frontier)
- Atlas on GCP (frontier)
- GCP Private Service Connect for Atlas (frontier)
- Multi-Cloud Replica Sets (frontier)
- Multi-Cloud Global Clusters (frontier)
- Multi-Cloud Billing (frontier)
- Azure Partnership and MACC (frontier)
- GCP Partnership and Marketplace (frontier)
- Multi-Cloud DR Pattern (frontier)
- Cross-Cloud Egress Costs (frontier)
- Multi-Cloud Failure Modes (frontier)
Frontier under this node: Atlas on Azure, Atlas on GCP, Azure Partnership and MACC, Cross-Cloud Egress Costs, GCP Partnership and Marketplace, GCP Private Service Connect for Atlas, Multi-Cloud Billing, Multi-Cloud DR Pattern, Multi-Cloud Failure Modes, Multi-Cloud Global Clusters, Multi-Cloud Replica Sets