Navigation

Google Cloud Platform (GCP)

On this page

  • Synopsis
  • Cluster Configuration Options
  • GCP Zones
  • Integrations
  • More Information

Atlas supports deploying clusters onto Google Cloud Platform (GCP). This page provides reference material related to Atlas cluster deployments on GCP. You can't deploy serverless instances on GCP.

Note

Serverless instances are in a preview release and do not support some Atlas features at this time.

To learn more, see Serverless Instance Limitations.

Depending on your cluster tier, Atlas supports the following GCP regions. While all of the following regions support M10+ clusters, some regions don't support Free or Shared-Tier clusters. A check mark indicates support for Free or Shared-Tier clusters. The Atlas API uses the corresponding Atlas Region.

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].

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
Default Storage
Default RAM
M2
2 GB
Shared
M5
5 GB
Shared
M10
10 GB
1.7 GB
M20
20 GB
3.8 GB
M30
40 GB
7.5 GB
M40
80 GB
15 GB
R40
80 GB
16 GB
M50
160 GB
30 GB
R50
160 GB
32 GB
M60
320 GB
60 GB
R60
320 GB
64 GB
M80
750 GB
120 GB
R80
750 GB
128 GB
M200
1500 GB
240 GB
R200
1500 GB
256 GB
M300
2000 GB
360 GB
R300
2000 GB
384 GB
R400
3000 GB
512 GB
R600
4096 GB
640 GB

Can use this tier for a multi-cloud cluster.

Unavailable in the following regions:

  • SOUTH_AMERICA_EAST_1
  • EUROPE_WEST_3
  • NORTHEASTERN_ASIA_PACIFIC
  • AUSTRALIA_SOUTHEAST_1

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

Example

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.

Along with global region support, the following product integrations enable applications running on GCP, such as Google Compute Engine, Google Cloud Functions, Google Cloud Run, and Google App Engine, to use Atlas instances easily and securely.

For more information on how to use GCP with Atlas most effectively, review the following best practices, guides, and case studies:

Give Feedback

On this page

  • Synopsis
  • Cluster Configuration Options
  • GCP Zones
  • Integrations
  • More Information