Google Cloud Platform (GCP)
On this page
Atlas supports deploying clusters and Serverless instances onto Google Cloud Platform (GCP).
Atlas supports the following Google Cloud regions. While all of the
following regions support dedicated clusters (M10+
),
some regions don't support free and Shared clusters (M0/M2/M5
) or
Serverless instances. The Atlas API
uses the corresponding Atlas Region.
Google Cloud Region | Location | Atlas Region | M0/M2/M5 Support | Flex Support | M10+ Support | Serverless Instance Support |
---|---|---|---|---|---|---|
us-central1 | Iowa, USA | CENTRAL_US | ||||
us-east4 | North Virginia, USA | US_EAST_4 | ||||
us-east5 | Columbus, OH, USA | US_EAST_5 | ||||
northamerica-northeast1 | Montreal, Canada | NORTH_AMERICA_NORTHEAST_1 | ||||
northamerica-northeast2 | Toronto, Canada | NORTH_AMERICA_NORTHEAST_2 | ||||
southamerica-east1 | Sao Paulo, Brazil | SOUTH_AMERICA_EAST_1 | ||||
southamerica-west1 | Santiago, Chile | SOUTH_AMERICA_WEST_1 | ||||
us-west1 | Oregon, USA | WESTERN_US | ||||
us-west2 | Los Angeles, CA, USA | US_WEST_2 | ||||
us-west3 | Salt Lake City, UT, USA | US_WEST_3 | ||||
us-west4 | Las Vegas, NV, USA | US_WEST_4 | ||||
us-south1 | Dallas, TX, USA | US_SOUTH_1 |
GCP Region | Location | Atlas Region | M0/M2/M5 Support | Flex Support | M10+ Support | Serverless Instance Support |
---|---|---|---|---|---|---|
asia-east1 | Taiwan | EASTERN_ASIA_PACIFIC | ||||
asia-east2 | Hong Kong, China | ASIA_EAST_2 | ||||
asia-northeast1 | Tokyo, Japan | NORTHEASTERN_ASIA_PACIFIC | ||||
asia-northeast2 | Osaka, Japan | ASIA_NORTHEAST_2 | ||||
asia-northeast3 | Seoul, Korea | ASIA_NORTHEAST_3 | ||||
asia-southeast1 | Singapore | SOUTHEASTERN_ASIA_PACIFIC | ||||
asia-south1 | Mumbai, India | ASIA_SOUTH_1 | ||||
asia-south2 | Delhi, India | ASIA_SOUTH_2 | ||||
australia-southeast1 | Sydney, Australia | AUSTRALIA_SOUTHEAST_1 | ||||
australia-southeast2 | Melbourne, Australia | AUSTRALIA_SOUTHEAST_2 | ||||
asia-southeast2 | Jakarta, Indonesia | ASIA_SOUTHEAST_2 |
GCP Region | Location | Atlas Region | M0/M2/M5 Support | Flex Support | M10+ Support | Serverless Instance Support |
---|---|---|---|---|---|---|
europe-west1 | Belgium | WESTERN_EUROPE | ||||
europe-north1 | Finland | EUROPE_NORTH_1 | ||||
europe-west2 | London, UK | EUROPE_WEST_2 | ||||
europe-west3 | Frankfurt, Germany | EUROPE_WEST_3 | ||||
europe-west4 | Netherlands | EUROPE_WEST_4 | ||||
europe-west6 | Zurich, Switzerland | EUROPE_WEST_6 | ||||
europe-west10 | Berlin, Germany | EUROPE_WEST_10 | ||||
europe-central2 | Warsaw, Poland | EUROPE_CENTRAL_2 | ||||
europe-west8 | Milan, Italy | EUROPE_WEST_8 | ||||
europe-west9 | Paris, France | EUROPE_WEST_9 | ||||
europe-west12 | Turin, Italy | EUROPE_WEST_12 | ||||
europe-southwest1 | Madrid, Spain | EUROPE_SOUTHWEST_1 |
GCP Region | Location | Atlas Region | M0/M2/M5 Support | Flex Support | M10+ Support | Serverless Instance Support |
---|---|---|---|---|---|---|
me-west1 | Tel Aviv, Israel | MIDDLE_EAST_WEST_1 | ||||
me-central1 | Doha, Qatar | MIDDLE_EAST_CENTRAL_1 | ||||
me-central2 | Dammam, Saudi Arabia | MIDDLE_EAST_CENTRAL_2 |
Cluster Configuration Options
Each Atlas cluster tier comes with a default set of resources. Atlas provides the following resource configuration options.
Custom Storage Size
Storage size reflects the size of the server root volume. Atlas clusters deployed onto Google Cloud use SSD persistent storage [1].
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 Tiers | Storage Range | Default Storage | Default RAM |
---|---|---|---|
M0 | .5 GB | .5 GB | Shared |
M2 | 2 GB | 2GB | Shared |
M5 | 5 GB | 5 GB | Shared |
M10 | 10 GB to 128 GB | 10 GB | 1.7 GB |
M20 | 10 GB to 256 GB | 20 GB | 3.8 GB |
M30 | 10 GB to 512 GB | 40 GB | 8 GB |
M40 | 10 GB to 1 TB | 80 GB | 16 GB |
R40 | 10 GB to 1 TB | 80 GB | 16 GB |
M50 | 10 GB to 4 TB | 160 GB | 32 GB |
R50 | 10 GB to 4 TB | 160 GB | 32 GB |
M60 | 10 GB to 4 TB | 320 GB | 64 GB |
R60 | 10 GB to 4 TB | 320 GB | 64 GB |
M80 | 10 GB to 4 TB | 750 GB | 128 GB |
R80 | 10 GB to 4 TB | 750 GB | 128 GB |
M140 | 10 GB to 4 TB | 1000 GB | 192 GB |
M200 | 10 GB to 4 TB | 1500 GB | 256 GB |
R200 | 10 GB to 4 TB | 1500 GB | 256 GB |
M250 | 10 GB to 4 TB | 1750 GB | 320 GB |
M300 | 10 GB to 4 TB | 2000 GB | 360 GB |
R300 | 10 GB to 4 TB | 2000 GB | 384 GB |
R400 | 10 GB to 4 TB | 3000 GB | 512 GB |
R600 | 10 GB to 4 TB | 4096 GB | 640 GB |
Can use this tier for a multi-cloud cluster.
Unavailable in the following regions:
AUSTRALIA_SOUTHEAST_1
EUROPE_WEST_3
NORTHEASTERN_ASIA_PACIFIC
SOUTH_AMERICA_EAST_1
EUROPE_WEST_8
EUROPE_WEST_9
EUROPE_SOUTHWEST_1
Atlas limits R-class instances to the following regions:
Americas
CENTRAL_US
EASTERN_US
US_EAST_4
WESTERN_US
US_WEST_3
US_WEST_4
NORTH_AMERICA_NORTHEAST_1
NORTH_AMERICA_NORTHEAST_2
SOUTH_AMERICA_EAST_1
Asia Pacific
ASIA_EAST_2
ASIA_NORTHEAST_2
ASIA_NORTHEAST_3
ASIA_SOUTH_1
ASIA_SOUTHEAST_2
EASTERN_ASIA_PACIFIC
NORTHEASTERN_ASIA_PACIFIC
SOUTHEASTERN_ASIA_PACIFIC
Europe
WESTERN_EUROPE
EUROPE_NORTH_1
EUROPE_WEST_2
EUROPE_WEST_3
EUROPE_WEST_4
EUROPE_WEST_6
EUROPE_WEST_8
EUROPE_WEST_9
EUROPE_SOUTHWEST_1
Note
Cluster Tier & API Naming Conventions
For purposes of management with the Atlas Administration 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
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:
Storage Speed
Encrypted Storage Volumes
Storage Speed
Storage speed is the number of input/output operations per second (IOPS) [1] that the system performs. This value is fixed at:
30 IOPS per GB for reads
30 IOPS per GB for writes, for a total of 60 IOPS per GB
For example, an M30
cluster with 40 GB of default storage has a
maximum read speed of 1,200 IOPS and a maximum write speed of 1,200 IOPS.
If you increase the storage size to 100 GB per cluster, this increases
the maximum read speed by 3,000 IOPS and a maximum write speed by
3,000 IOPS.
IOPS smaller than 16B are counted as one IO. IOPS larger than 16KB are counted as multiple IOs. For example, a 128KB IO counts as eight IOs.
Encrypted Storage Volumes
Google Cloud storage volumes are always encrypted.
GCP Zones
Each Google Cloud 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 multiple zones, such as 2Z (for two zones) or 3Z (for 3 zones), Atlas deploys clusters across these zones.
The Atlas Add New Cluster form marks regions that support 3Z clusters as Recommended, as they provide higher availability.
To learn more, see regions and zones in the Google documentation.
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.
Regions with at Least Three Zones
If the selected Google Cloud 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.
3Z clusters have higher availability compared to 2Z clusters. However, not all regions support 3Z clusters.
[1] | (1, 2, 3) To learn more, see Storage Options in the Google documentation. |
Dedicated Search Nodes
Supported Regions
Atlas supports deploying separate Search Nodes for M10
and higher
clusters in any Google Cloud region.
Available Search Tiers
Atlas provides different search tiers for Search Nodes deployed on Google Cloud. These search tiers are available for each class of hardware, low-CPU or high-CPU:
Instance Size | Instance Details |
---|---|
S30 |
|
S40 |
|
S50 |
|
S60 |
|
S80 |
|
S90 |
|
S100 |
|
S110 |
|
S120 |
|
S130 |
|
S140 |
|
Instance Size | Instance Details |
---|---|
S20 |
|
S30 |
|
S40 |
|
S50 |
|
S60 |
|
S70 |
|
S80 |
|
Note
Most Search Nodes use NVMe-attached Local SSD disks for storage. Search nodes with the following search tiers use SCSI-attached SSD Persistent Disks [1]:
S20
High-CPU InstancesS30
Low-CPU Instances
Integrations
Along with global region support, the following product integrations enable applications running on Google Cloud, such as Google Compute Engine, Google Cloud Functions, Google Cloud Run, and Google App Engine, to use Atlas instances easily and securely.
Networking Services
Google Virtual Private Cloud (VPC): Set up network peering connections with GCP
Security and Identity Services
Google Identity: Sign up and log into Atlas with Google
Google Cloud Key Management Service (KMS):
Procurement
GCP Marketplace: Pay for Atlas usage via GCP
More Information
For more information on how to use Google Cloud with Atlas most effectively, review the following best practices, guides, and case studies: