MongoDB Atlas AWS Networking
Parent: MongoDB Atlas · researched 2026-05-27T19:53:59.734Z· 10 sources · 18 concepts · skill mongodb-aws-networking
MongoDB Atlas on AWS supports two private networking models: VPC Peering (legacy) and AWS PrivateLink (recommended). Both complement the Network Access List (IP allowlist) for controlling cluster acce
Overview
- MongoDB Atlas on AWS supports two private networking models: VPC Peering (legacy) and AWS PrivateLink (recommended). Both complement the Network Access List (IP allowlist) for controlling cluster access. [source]
Private Endpoint Connection String
Network Access Lists
- Security Groups as access list entries: For applications running in EC2/ECS/Lambda within a VPC, using Security Group IDs as access list entries is more dynamic and avoids managing CIDR ranges. [source]
DNS/SRV Resolution
Transit Gateway Patterns
- For centralized networking with many VPCs: [source]
- Create Atlas PrivateLink endpoint in a "hub" VPC [source]
- Connect hub VPC to AWS Transit Gateway [source]
- All application VPCs access Atlas via Transit Gateway → hub → PrivateLink [source]
- Route table: 10.0.0.0/8 → Transit Gateway in spoke VPCs [source]
- Transit Gateway also enables cross-account Atlas access without creating separate PrivateLink endpoints per account. [source]
AWS KMS Encryption at Rest (BYOK)
- Atlas uses IAM role assumption (not IAM user credentials) to access the KMS key. Configure via Atlas Cloud Provider Access (Unified AWS Access) → creates a cross-account IAM role. [source]
- Failsafe: If KMS is inaccessible, running mongod continues (DEK cached in memory) but will not restart. [source]
AWS EventBridge Integration
AWS ISV Accelerate Partnership
- MongoDB is an AWS ISV Accelerate partner: [source]
- Co-sell eligibility: MongoDB opportunities can qualify for AWS funding [source]
- AWS Marketplace listing for Atlas (PAYG and committed-use) [source]
- AWS Marketplace purchases appear on AWS invoice [source]
- ISV Workload Migration Program: potential AWS credits for customer migration projects [source]
Common Troubleshooting
- Connection timeout after PrivateLink setup: [source]
- Verify using the PrivateLink connection string (not standard) [source]
- Check security group allows outbound TCP 27017 (or 1024-65535 for SRV) [source]
- Verify private_dns_enabled = false on the AWS endpoint [source]
- Confirm Atlas private endpoint status = AVAILABLE [source]
- DNS resolving to public IP: [source]
- Route53 private hosted zone may be interfering [source]
- Verify no conflicting private hosted zone for mongodb.net [source]
- From EC2 in VPC: nslookup <private-endpoint-hostname> should return private IP [source]
- VPC Peering connection not routing: [source]
- Route table in application VPC must include route to Atlas VPC CIDR [source]
- Route table in Atlas VPC (managed by MongoDB) is auto-updated [source]
- CIDR overlap check: Atlas VPC uses 192.168.x.x - ensure no overlap with your VPC [source]
References
Children
- VPC Peering (frontier)
- AWS PrivateLink (frontier)
- Network Access Lists (frontier)
- DNS and SRV Records (frontier)
- Multi-Region Networking (frontier)
- Transit Gateway Patterns (frontier)
- TLS Encryption (frontier)
- Security Groups (frontier)
- Connection Troubleshooting (frontier)
- AWS CloudFormation Atlas (frontier)
- Terraform Atlas Provider (frontier)
- EventBridge Integration (frontier)
- Lambda Integration (frontier)
- KMS Encryption at Rest (frontier)
- IAM Authentication (frontier)
- AWS ISV Accelerate (frontier)
- AWS Marketplace Atlas (frontier)
- EDP Credits (frontier)
Frontier under this node: AWS CloudFormation Atlas, AWS ISV Accelerate, AWS Marketplace Atlas, AWS PrivateLink, Connection Troubleshooting, DNS and SRV Records, EDP Credits, EventBridge Integration, IAM Authentication, KMS Encryption at Rest, Lambda Integration, Multi-Region Networking, Network Access Lists, Security Groups, TLS Encryption, Terraform Atlas Provider, Transit Gateway Patterns, VPC Peering