Use this page to set up, view, and remove network peering connections between your Atlas project and your cloud provider network. For an overview of network peering, including limitations and best practices, see Network Peering.
Note
The MongoDB Atlas Shared Responsibility Model defines the complementary duties of MongoDB and its customers in maintaining a secure and resilient data environment. Under this framework, MongoDB manages the security and operational integrity of the underlying platform, while customers are responsible for the configuration, management, and data policies of their specific deployments. For a detailed breakdown of ownership across security and operational excellence, see Shared Responsibility Model.
Required Access
To set up a network peering connection, you must have Organization Owner, Project Owner, or Project Network Access Manager access to the project.
Limitations
Atlas does not support network peering between clusters deployed in a single region on different cloud providers. For example, you cannot set up network peering between an Atlas cluster hosted in a single region on AWS and an application hosted in a single region on Google Cloud.
Free clusters (formerly known as
M0) and Flex clusters do not support VPC peering. To use private networking, you must use a dedicated cluster.
Configure an Atlas Network Peering Connection
To configure Atlas network peering for a cluster, complete the steps for your interface and your cluster's cloud provider. You also configure the Atlas VPC CIDR during this procedure.