liveBook · Manning

VPC peering

As explained in MongoDB 8.0 in Action, Third Edition

A VPC peering connection is a private network connection that routes traffic between two virtual private clouds.

VPC peering creates a private network connection between an application VPC and an Atlas VPC, routing database traffic without exposing it to the public internet. It suits sensitive-data workloads, compliance requirements, and applications that benefit from private, low-latency access. section 20.6.2 section 20.6

Apply the following constraints when evaluating a peering design:

  • Use network peering with dedicated Atlas clusters on AWS, GCP, or Azure, and with multicloud sharded clusters. section 20.6.2
  • Do not select it for M0 or Flex clusters; those tiers do not support network peering. section 20.6.2
  • Choose private IP-only access when traffic must remain private, or combine private and public access according to the IP access list. section 20.6.2
  • Compare peering with IP access lists and private endpoints: peering enables private routing between VPCs, while private endpoints preserve a stricter boundary by preventing Atlas from initiating connections back to your VPC. section 20.6 section 20.8

Application VPC connected to Atlas

An AWS Customer VPC uses CIDR block 10.0.0.0/16 and hosts application servers behind an Elastic load balancer. It peers with an Atlas VPC using 172.31.248.0/21; Atlas cluster nodes span three availability zones, and traffic follows private routes between the two networks. section 20.6.2

Figure 20.4 Atlas VPC peered to an AWS VPC (Image © MongoDB 2024 CC BY-NC-SA 3.0)
A screenshot of a computer program

Description automatically generated

Use the topology figure to inspect how application servers, load balancing, CIDR ranges, availability zones, and Atlas cluster nodes fit across the peered VPCs. section 20.6.2

How MongoDB 8.0 in Action, Third Edition covers it

How deep it goes
Defines private routing, access modes, supported deployments, and a CIDR-based topology, but defers setup procedures.
Examples
Illustrates an AWS application VPC with 10.0.0.0/16 peered to an Atlas VPC with 172.31.248.0/21 across three availability zones.
What you can do after
Evaluate whether private VPC routing fits security, compliance, latency, and Atlas tier requirements.
How it connects
Relates network peering to IP access lists, private endpoints, network access controls, dedicated clusters, and multicloud sharded clusters.

Also explained in

Compare how 2 books explain VPC peering →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of MongoDB 8.0 in Action, Third Edition. The section links point to the parts of the book it draws on.