Navigation

Google Cloud Platform

Synopsis

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:

GCP Region Location M0 Free Tier Support M2/M5 Shared Tier Support
us-central1 Iowa, USA check square icon check square icon
us-east1 South Carolina, USA    
us-east4 North Virginia, USA    
us-west1 Oregon, USA    
us-west2 Los Angeles, USA    
northamerica-northeast1 Montréal, CA    
southamerica-east1 São Paulo, Brazil    
europe-north1 Finland    
europe-west1 Belgium check square icon check square icon
europe-west2 London, UK    
europe-west3 Frankfurt, Germany    
europe-west4 Netherlands    
asia-south1 Mumbai, India    
asia-southeast1 Singapore check square icon  
asia-east1 Taiwan   check square icon
asia-east2 Hong Kong    
asia-northeast1 Tokyo, Japan    
australia-southeast1 Sydney, Australia    

Instance Configuration Options

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

Custom Storage Size

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

The minimum custom storage size for all instances is 10GB.

For M10 instances, the maximum custom storage size is 3TB.

For M20+ instances, the maximum custom storage size is 4TB.

Workloads typically require less than 2TB.

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

Storage Speed

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.

Example

The M30 instance size has a default storage size of 40GB per instance and a max storage speed of 1200 max IOPS. Increasing the storage size to 100GB per instance increases the max storage speed to ( 30 IOPS / GB * 100 GB) or 3000 IOPS.

Encrypted Storage Volumes
GCP storage volumes are always encrypted.

GCP Zones

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 affect 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

Regions with at Least Three 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.