> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt # Google Cloud **Important:** The feature described on this page is not currently supported on Atlas Infinite clusters during public preview. For the features supported in public preview, see [Public Preview Availability.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing/#public-preview-availability) Atlas supports deploying clusters onto Google Cloud. Atlas supports the following Google Cloud regions. While all of the following regions support dedicated clusters (`M10+`), some regions don't support Free clusters (formerly known as `M0`) or Flex clusters. The Atlas [API](https://www.mongodb.com/docs/atlas/api.md#std-label-graphql-api-overview) uses the corresponding Atlas Region. ### Americas | Google Cloud Region | Location | Atlas Region | `Free` Support | `Flex` Support | `M10+` Support | | --- | --- | --- | --- | --- | --- | | `us-central1` | Iowa, USA | `CENTRAL_US` | | | | | `us-east1` | South Carolina, USA | `EASTERN_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` | | | | | `northamerica-south1` | Querétaro, Mexico | `NORTH_AMERICA_SOUTH_1` | | | | ## 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 different SSD (Solid State Disk) types depending on their [cluster generation:](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-cluster-generation) - Gen1, `M10`, and `M20` clusters use Persistent Disk storage. - Gen2 cluster use Hyperdisk storage . **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 | | Flex | 5 GB | 5 GB | Flex | | 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 | | M50 | 10 GB to 4 TB | 160 GB | 32 GB | | M60 | 10 GB to 4 TB | 320 GB | 64 GB | | M80 | 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 | | M250 | 10 GB to 4 TB | 1750 GB | 320 GB | | M300 | 10 GB to 4 TB | 2000 GB | 360 GB | | M400 | 10 GB to 4 TB | 3000 GB | 512 GB | | M600 | 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-east1`, South Carolina, USA) - `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](https://www.mongodb.com/docs/atlas/api.md#std-label-atlas-api), cluster tier names that are prepended with `R` instead of an `M` (`R40` for example) run a [low-CPU](https://www.mongodb.com/docs/atlas/customize-storage.md#std-label-storage-class-ui) version of the cluster. When [creating](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster) or [modifying](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupcluster) a cluster with the API, be sure to specify your desired cluster class by name with the `replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize` attribute. **Important: Multi-Cloud Low-CPU clusters** Low-CPU cluster tiers (M40 Low-CPU, M50 Low-CPU, M60 Low-CPU, and so on) are available in [multi-cloud cluster configurations](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-create-cluster-multi-region) 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 #### Encrypted Storage Volumes Google Cloud storage volumes are [always encrypted.](https://cloud.google.com/security/encryption-at-rest/) ## Google Cloud 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](https://www.mongodb.com/docs/atlas/tutorial/create-new-cluster.md#std-label-create-new-cluster) form marks regions that support 3Z (Three Zone) clusters as Recommended, as they provide higher availability. To learn more, see [regions and zones](https://cloud.google.com/compute/docs/regions-zones/regions-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. ![A 3-node replica set deployed across a 3-zone GCP region.](/images/google-gcp-3az.svg) 3Z (Three Zone) clusters have higher availability compared to 2Z (Two Zone) clusters. However, not all regions support 3Z (Three Zone) clusters. To learn more, see [Storage Options](https://cloud.google.com/compute/docs/disks/) in the Google documentation. ## GCP Gen2 Dedicated clusters Atlas supports configuring `M30+` Dedicated clusters deployed on Google Cloud as [Gen2 clusters.](https://www.mongodb.com/docs/atlas/manage-clusters.md#std-label-gen2-clusters) ### Available Cluster Tiers The following tables show the instance machine, vCPU counts, and RAM for each supported Gen2 cluster tier: ### General | Atlas Gen2 Tier | Instance Machine | vCPU | RAM | | --- | --- | --- | --- | | M30 | `c4a-standard-2` | 2 | 8 GB | | M40 | `c4a-standard-4` | 4 | 16 GB | | M50 | `c4a-standard-8` | 8 | 32 GB | | M60 | `c4a-standard-16` | 16 | 64 GB | | M80 | `c4a-standard-32` | 32 | 128 GB | | M140 | `c4a-standard-48` | 48 | 192 GB | | M200 | `c4a-standard-64` | 64 | 256 GB | ### Supported Regions The following tables list the Google Cloud regions that support Gen2 Dedicated clusters. The Atlas [API](https://www.mongodb.com/docs/atlas/api.md#std-label-graphql-api-overview) uses the corresponding Atlas Region. ### Americas | Google Cloud Region | Location | Atlas Region | | --- | --- | --- | | `us-central1` | Iowa, USA | `CENTRAL_US` | | `us-east1` | South Carolina, USA | `EASTERN_US` | | `us-east4` | North Virginia, USA | `US_EAST_4` | | `northamerica-south1` | Querétaro, Mexico | `NORTH_AMERICA_SOUTH_1` | | `us-east5` | Columbus, OH, USA | `US_EAST_5` | | `us-west2` | Los Angeles, CA, USA | `US_WEST_2` | | `us-west4` | Las Vegas, NV, USA | `US_WEST_4` | ## Dedicated Search Nodes ### Supported Regions Atlas supports deploying separate [Search Nodes](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-configure-search-nodes) for `M10` and higher clusters in most Google Cloud regions. **Note:** Search Nodes are currently not available in the following Google Cloud regions: - Johannesburg, South Africa (`africa-south1`) - Berlin, Germany (`europe-west10`) - Dammam, Saudi Arabia (`me-central2`) - Querétaro, Mexico (`northamerica-south1`) - South Carolina, USA (`us-east1`) ### Available Search Tiers Atlas provides different [search tiers](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-select-tiers-for-search-nodes) for Search Nodes deployed on Google Cloud. The following table lists the search tiers available for each class of hardware (low-CPU and high-CPU), with default RAM and storage measured in gibibytes (GiB): ### Low-CPU | Instance Size | Instance Details | | --- | --- | | S30 | **Default RAM**: 8 GiB; **Default Storage**: 128 GiB; **vCPU**: 2 | | S40 | **Default RAM**: 16 GiB; **Default Storage**: 337 GiB; **vCPU**: 2 | | S50 | **Default RAM**: 32 GiB; **Default Storage**: 337 GiB; **vCPU**: 4 | | S60 | **Default RAM**: 64 GiB; **Default Storage**: 337 GiB; **vCPU**: 8 | | S70 | **Default RAM**: 96 GiB; **Default Storage**: 674 GiB; **vCPU**: 12 | | S80 | **Default RAM**: 128 GiB; **Default Storage**: 674 GiB; **vCPU**: 16 | | S90 | **Default RAM**: 256 GiB; **Default Storage**: 1348 GiB; **vCPU**: 32 | | S100 | **Default RAM**: 384 GiB; **Default Storage**: 2697 GiB; **vCPU**: 48 | | S130 | **Default RAM**: 768 GiB; **Default Storage**: 5394 GiB; **vCPU**: 96 | **Note:** Most Search Nodes use NVMe (non-volatile memory express)-attached [Local SSD disks](https://cloud.google.com/compute/docs/disks/local-ssd) for storage. Search nodes with the following search tiers use SCSI (Small Computer System Interface)-attached SSD (Solid State Disk) [Persistent Disks](https://cloud.google.com/compute/docs/disks/persistent-disks) : - `S20` High-CPU Instances - `S30` Low-CPU Instances ## Stream Processing Workspaces **Important:** To request an unlisted region, add your feedback to the [MongoDB Feedback Portal](https://feedback.mongodb.com/?category=7529546585152608284). Your input helps prioritize future expansions of Atlas Stream Processing coverage. Atlas supports deploying [Stream Processing Workspaces](https://www.mongodb.com/docs/atlas/atlas-stream-processing/manage-processing-instance.md#std-label-atlas-sp-manage-spi) in the following Google Cloud regions: | Geography | Google Cloud Region | Location | Atlas Region | | --- | --- | --- | --- | | Americas | `us-central1` | Iowa, USA | `CENTRAL_US` | | Americas | `us-east4` | North Virginia, USA | `US_EAST_4` | | Americas | `us-west1` | Oregon, USA | `WESTERN_US` | | Asia Pacific | `asia-south1` | Mumbai, India | `ASIA_SOUTH_1` | | Europe | `europe-west1` | Belgium | `WESTERN_EUROPE` | ## Integrations Along with [global region support](https://www.mongodb.com/docs/atlas/reference/google-gcp.md#std-label-google-gcp), 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 Google Cloud](https://www.mongodb.com/docs/atlas/security-vpc-peering.md#std-label-vpc-peering) ### Security and Identity Services - Google Identity: [Sign up and log into Atlas with Google](https://www.mongodb.com/docs/atlas/tutorial/create-atlas-account.md#std-label-create-atlas-account) - Google Cloud Key Management Service (KMS): - [Configure Atlas disk encryption with KMS](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption) - [Configure client-side field level encryption with KMS](https://www.mongodb.com/docs/manual/core/security-client-side-encryption-key-management/) ### Procurement - Google Cloud Marketplace: [Pay for Atlas usage via Google Cloud](https://console.cloud.google.com/marketplace/product/mongodb/atlas-pro?pli=1) ## More Information For more information on how to use Google Cloud with Atlas most effectively, review the following best practices, guides, and case studies: - Case Study: [Why build apps on a cloud-native database like MongoDB Atlas?](https://cloud.google.com/blog/products/databases/why-build-apps-on-cloud-native-database-like-mongodb-atlas) - Google Datastream: [Streamline your real-time data pipeline with Datastream and MongoDB](https://cloud.google.com/blog/products/databases/get-real-time-analytics-data-with-datastream-and-mongodb)