Atlas Mapped: Private Network Peering on Azure & GCP

The MongoDB Atlas platform is constantly evolving and the Atlas Mapped series keeps you up to date with what's launched in Atlas over the past few weeks. In this edition, we look at the latest in private network peering options available on Azure and Google Cloud Platform.

Network peering for Atlas customers on Azure and GCP

Virtual networks are one element of how cloud resources ensure they are operating on an isolated network. They have different names on the various cloud platforms. AWS or GCP customers will know these virtual networks as Virtual Private Clouds or VPCs; on Azure, they’re simply called Virtual Networks or VNets.

By being able to link virtual networks, an infrastructure architect can bring isolated resources together to create their own secure cloud.

In MongoDB Atlas, database clusters are grouped into projects, with each project getting its own virtual network. And it is through those virtual networks that you can attach your application servers using Network peering.

Network peering allows you to establish a network connection between the network containing your application instances with the Atlas virtual network containing your managed MongoDB databases, enabling you to route traffic between them using private IP addresses. In other words, it allows your application instances to communicate with Atlas clusters as if they are within the same network. This capability has been available for customers deploying Atlas on AWS, including cross-region VPC peering, and is now available for customers deploying on both Azure and GCP.

  • On Google Cloud, a single VPC can span multiple regions without communicating across the public internet. This means you don’t need cross-region support and connections in every region.
  • On Azure, each cloud region within an Atlas project gets its own VNet. So while Atlas does support cross-region VNet peering to connect databases to application servers in another region, your Atlas cluster must reside in a single cloud region.

As a reminder, peering is only available for clusters M10 and larger. The smaller shared M0, M2, and M5 database clusters do not support network peering. To learn more about setting up a peering connection with MongoDB Atlas, visit our docs.

New Atlas regions

We’re excited to report that customers can now deploy Atlas in Johannesburg on Azure and in Zurich on GCP. This marks the first time Atlas is available in those respective countries and regions. And while it's not a new geographical region of the world, we are very pleased to report that with the arrival of AWS support for Hong Kong, that Hong Kong is now supported on all three cloud platforms. For those keeping count, this brings the total number of cloud regions supported by Atlas to 63 (across all Azure, GCP, and AWS), the most of any database service.