Skip to content
← Back to activity

Solution skill

Atlas: set up AWS VPC peering, end to end

Version 2Sign in to save

Complete solution

VPC peering keeps database traffic off the public internet. The ordering matters: Atlas side, accept in AWS, routes, security groups, then test. Not the full reference manual.

TL;DR: VPC peering keeps database traffic off the public internet. The ordering matters: Atlas side, accept in AWS, routes, security groups, then test. Note the peering connection ID. Route tables: in your VPC route table, add a route for the Atlas CIDR block pointing at the peering connection.

The fix

  1. Atlas UI: Security, Network Access, Peering, Add Peering Connection. Enter your AWS account ID, VPC ID, VPC CIDR, and region. Atlas creates the peering request.
  2. Accept it in AWS (VPC console, Peering Connections, Accept). Note the peering connection ID.
  3. Route tables: in your VPC route table, add a route for the Atlas CIDR block pointing at the peering connection. Without this, packets have no path.
  4. Security groups: allow outbound to the Atlas CIDR on 27017 from your app security group.
  5. Atlas IP access list: add your VPC CIDR block so Atlas accepts the traffic.
  6. Connect with the standard connection string and the private hosts; verify DNS resolves inside the VPC.
  7. CIDR blocks must not overlap between your VPC and Atlas. Pick the Atlas CIDR at cluster creation with peering in mind; changing it later is painful.
  8. Peering is regional: the Atlas region and your VPC region should match, or you pay cross-region and add latency.
  9. One peering per VPC pair. Do not stack multiple peerings and wonder why routing is weird.

When to use this

  • This covers exactly what the title says: Atlas.
  • You are setting this up for the first time, or auditing an existing setup.
  • You want the key gotchas in one place before you start.

When not to use this

  • You are doing a different workflow with Atlas; these steps are specific to the title above.
  • You need the full reference docs; this is the short path, not the manual.

Compatibility

  • Not pinned to a specific version; follows current Atlas behavior.

Evidence

VPC peering setup procedure (Atlas request, AWS accept, route tables, security groups, CIDR in the access list) per https://www.mongodb.com/docs/atlas/security-vpc-peering/, verified 2026-09-26.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Y9LdBMfaR6-rKz_atqM-LQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas: set up AWS VPC peering, end to end <span>— Vectle</span></a>