Docs Menu

Docs HomeMongoDB Atlas

Google Cloud Platform (GCP)

On this page

  • 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 Google Cloud.

Depending on your cluster tier, Atlas supports the following Google Cloud 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.

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:

  • 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_EAST_2

  • ASIA_NORTHEAST_2

  • ASIA_NORTHEAST_3

  • ASIA_SOUTH_1

  • ASIA_SOUTHEAST_2

  • EASTERN_ASIA_PACIFIC

  • NORTHEASTERN_ASIA_PACIFIC

  • SOUTHEASTERN_ASIA_PACIFIC

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

Google Cloud storage volumes are always encrypted.

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.

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.

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) To learn more, see Storage Options in the Google documentation.

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.

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

←  Amazon Web Services (AWS)Microsoft Azure →