Google Cloud Platform (GCP)

Atlas supports deploying clusters onto Google Cloud Platform (GCP). This page provides reference material related to Atlas cluster deployments on GCP .

Atlas supports the following GCP regions. The Atlas API uses the corresponding Atlas Region.

GCP RegionLocationAtlas RegionM0 Free Tier SupportM2/M5 Shared-Tier Support
us-central1Iowa, USACENTRAL_US
us-east1South Carolina, USAEASTERN_US
us-east4North Virginia, USAUS_EAST_4
northamerica-northeast1Montreal, CanadaNORTH_AMERICA_NORTHEAST_1
southamerica-east1Sao Paulo, BrazilSOUTH_AMERICA_EAST_1
us-west1Oregon, USAWESTERN_US
us-west2Los Angeles, CA, USAUS_WEST_2
us-west3Salt Lake City, UT, USAUS-WEST_3
us-west4Las Vegas, NV, USAUS-WEST_4

Each Atlas cluster tier comes with a default set of resources. Atlas provides the following resource configuration options:

The size of the server root volume. Atlas clusters deployed onto GCP use SSD persistent storage [1].

Info With Circle IconCreated with Sketch.Note
RAM Availability

The actual amount of RAM available to each cluster tier might be slightly less than the stated amount, due to memory that the kernel reserves.

The following cluster tiers are available:

Cluster TiersDefault StorageDefault RAM
M22 GBShared
M55 GBShared
M1010 GB1.7 GB
M2020 GB3.8 GB
M3040 GB7.5 GB
M4080 GB15 GB
M40 Low-CPU (R40) 280 GB16 GB
M50160 GB30 GB
M50 Low-CPU (R50) 2160 GB32 GB
M60320 GB60 GB
M60 Low-CPU (R60) 2320 GB64 GB
M80750 GB120 GB
M80 Low-CPU (R80) 2750 GB128 GB
M2001500 GB240 GB
M200 Low-CPU (R200) 21500 GB256 GB
M300 12000 GB360 GB
M300 Low-CPU (R300) 22000 GB384 GB
M400 Low-CPU (R400) 23000 GB512 GB
M400 Low-CPU (R600) 24096 GB640 GB

1 Unavailable in the following regions:


2 Atlas limits R-class instances to the following regions:

  • asia-east1
  • asia-northeast1
  • asia-southeast1
  • europe-west1
  • europe-west2
  • europe-west4
  • us-central1
  • us-west1
Info With Circle IconCreated with Sketch.Note
Cluster Tier & API Naming Conventions

For purposes of management with the Atlas API, cluster tier names that are prepended with R instead of an M (R40 for example) run a low-CPU version of the cluster. When creating or modifying a cluster with the API, be sure to specify your desired cluster class by name with the providerSettings.instanceSizeName attribute.

Important With Circle IconCreated with Sketch.Important
Multi-Cloud Low-CPU clusters

Low-CPU cluster tiers (R40, R50, R60, etc) are available in multi-cloud cluster configurations as long as the cluster tier is available for all the regions that the cluster uses.

Workloads typically require less than 2TB of storage.

Atlas configures the following resources automatically and does not allow user modification:

The input/output operations per second (IOPS) [1] the system can perform. This value is fixed at 30 IOPS per GB for reads and 30 IOPS per GB for writes for a total of 60 IOPS per GB.

Beaker IconExample

The M30 cluster has a default storage size of 40 GB. This results in a maximum read speed of 1,200 IOPS and a maximum write speed of 1,200 IOPS . Increasing the storage size to 100 GB per cluster increases the maximum read speed of 3,000 IOPS and a maximum write speed of 3,000 IOPS .

GCP storage volumes are always encrypted.

Each GCP region includes a set number of independent zones. Each zone has power, cooling, networking, and control planes that are isolated from other zones. For regions that have at least three zones (3Z), Atlas deploys clusters across three zones. For regions that only have two zones (2Z), Atlas deploys clusters across two zones.

The Atlas Add New Cluster form marks regions that support 3Z clusters as Recommended, as they provide higher availability.

The number of zones in a region has no effect on the number of MongoDB nodes Atlas can deploy. MongoDB Atlas clusters are always made of replica sets with a minimum of three MongoDB nodes.

For general information on GCP regions and zones, see the Google documentation on regions and zones.

If the selected GCP region has at least three zones, Atlas clusters are split across three zones. For example, a three node replica set cluster would have one node deployed onto each zone.

A 3-node replica set deployed across a 3-zone GCP region.

3Z clusters have higher availability compared to 2Z clusters. However, not all regions support 3Z clusters.

[1](1, 2) For detailed documentation on Google storage options, see Storage Options.
Give Feedback