Return All Clusters in One Project
Returns the details for all clusters in the specific project to which you have access. Clusters contain a group of hosts that maintain the same data set. The response includes multi-cloud clusters. To use this resource, the requesting Service Account or API Key must have the Project Read Only role. This feature is not available for serverless clusters.
This endpoint can also be used on Flex clusters that were created using the createCluster endpoint or former M2/M5 clusters that have been migrated to Flex clusters until January 2026. Please use the listFlexClusters endpoint for Flex clusters instead.
Path parameters
-
Unique 24-hexadecimal digit string that identifies your project. Use the /groups endpoint to retrieve all projects to which the authenticated user has access.
NOTE: Groups and projects are synonymous terms. Your group id is the same as your project id. For existing groups, your group/project id remains the same. The resource and corresponding endpoints use the term groups.
Format should match the following pattern:
^([a-f0-9]{24})$
.
Query parameters
-
Flag that indicates whether Application wraps the response in an
envelope
JSON object. Some API clients cannot access the HTTP response headers or status code. To remediate this, set envelope=true in the query. Endpoints that return a list of results use the results object as an envelope. Application adds the status parameter to the response body.Default value is
false
. -
Flag that indicates whether the response returns the total number of items (totalCount) in the response.
Default value is
true
. -
Number of items that the response returns per page.
Minimum value is
1
, maximum value is500
. Default value is100
. -
Number of the page that displays the current set of the total objects that the response returns.
Minimum value is
1
. Default value is1
. -
Flag that indicates whether the response body should be in the prettyprint format.
Default value is
false
.Prettyprint -
Flag that indicates whether to return Clusters with retain backups.
Default value is
false
.
Responses
-
OK
Hide response attributes Show response attributes object
-
List of one or more Uniform Resource Locators (URLs) that point to API sub-resources, related API resources, or both. RFC 5988 outlines these relationships.
Web Linking Specification (RFC 5988) Hide links attributes Show links attributes object
-
Uniform Resource Locator (URL) that points another API resource to which this response has some relationship. This URL often begins with
https://cloud.mongodb.com/api/atlas
. -
Uniform Resource Locator (URL) that defines the semantic relationship between this resource and another API resource. This URL often begins with
https://cloud.mongodb.com/api/atlas
.
-
-
List of returned documents that MongoDB Cloud provides when completing this request.
Hide results attributes Show results attributes object
-
If reconfiguration is necessary to regain a primary due to a regional outage, submit this field alongside your topology reconfiguration to request a new regional outage resistant topology. Forced reconfigurations during an outage of the majority of electable nodes carry a risk of data loss if replicated writes (even majority committed writes) have not been replicated to the new primary node. MongoDB Atlas docs contain more information. To proceed with an operation which carries that risk, set acceptDataRisksAndForceReplicaSetReconfig to the current date. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
Reconfiguring a Replica Set during a regional outage -
Group of settings that configures a subset of the advanced configuration details.
Hide advancedConfiguration attributes Show advancedConfiguration attributes object
-
The custom OpenSSL cipher suite list for TLS 1.2. This field is only valid when
tlsCipherConfigMode
is set toCUSTOM
.Values are
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
orTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
. -
Minimum Transport Layer Security (TLS) version that the cluster accepts for incoming connections. Clusters using TLS 1.0 or 1.1 should consider setting TLS 1.2 as the minimum TLS protocol version.
Values are
TLS1_0
,TLS1_1
, orTLS1_2
.This option corresponds to the `netssldisabledProtocols` `mongod` configuration file option -
The TLS cipher suite configuration mode. The default mode uses the default cipher suites. The custom mode allows you to specify custom cipher suites for both TLS 1.2 and TLS 1.3.
Values are
CUSTOM
orDEFAULT
.
-
-
Flag that indicates whether the cluster can perform backups. If set to
true
, the cluster can perform backups. You must set this value totrue
for NVMe clusters. Backup uses Cloud Backups for dedicated clusters and Shared Cluster Backups for tenant clusters. If set tofalse
, the cluster doesn't use backups.Default value is
false
. -
Settings needed to configure the MongoDB Connector for Business Intelligence for this cluster.
MongoDB Connector for Business Intelligence Hide biConnector attributes Show biConnector attributes object
-
Flag that indicates whether MongoDB Connector for Business Intelligence is enabled on the specified cluster.
-
Data source node designated for the MongoDB Connector for Business Intelligence on MongoDB Cloud. The MongoDB Connector for Business Intelligence on MongoDB Cloud reads data from the primary, secondary, or analytics node based on your read preferences. Defaults to
ANALYTICS
node, orSECONDARY
if there are noANALYTICS
nodes.Values are
PRIMARY
,SECONDARY
, orANALYTICS
.Read preferences for BI Connector
-
-
Configuration of nodes that comprise the cluster.
Values are
REPLICASET
,SHARDED
, orGEOSHARDED
. -
Config Server Management Mode for creating or updating a sharded cluster.
When configured as ATLAS_MANAGED, atlas may automatically switch the cluster's config server type for optimal performance and savings.
When configured as FIXED_TO_DEDICATED, the cluster will always use a dedicated config server.
Values are
ATLAS_MANAGED
orFIXED_TO_DEDICATED
. Default value isATLAS_MANAGED
.MongoDB Sharded Cluster Config Servers -
Describes a sharded cluster's config server type.
Values are
DEDICATED
orEMBEDDED
.MongoDB Sharded Cluster Config Servers -
Collection of Uniform Resource Locators that point to the MongoDB database.
Connection string URI format Hide connectionStrings attributes Show connectionStrings attributes object
-
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to MongoDB Cloud through the interface endpoint that the key names.Network Peering Connection Hide awsPrivateLink attribute Show awsPrivateLink attribute object
-
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to MongoDB Cloud through the interface endpoint that the key names.Network Peering Connection
-
-
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to Atlas through the interface endpoint that the key names. If the cluster uses an optimized connection string,awsPrivateLinkSrv
contains the optimized connection string. If the cluster has the non-optimized (legacy) connection string,awsPrivateLinkSrv
contains the non-optimized connection string even if an optimized connection string is also present.Network Peering Connection Hide awsPrivateLinkSrv attribute Show awsPrivateLinkSrv attribute object
-
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to Atlas through the interface endpoint that the key names. If the cluster uses an optimized connection string,awsPrivateLinkSrv
contains the optimized connection string. If the cluster has the non-optimized (legacy) connection string,awsPrivateLinkSrv
contains the non-optimized connection string even if an optimized connection string is also present.Network Peering Connection
-
-
Network peering connection strings for each interface Virtual Private Cloud (VPC) endpoint that you configured to connect to this cluster. This connection string uses the
mongodb+srv://
protocol. The resource returns this parameter once someone creates a network peering connection to this cluster. This protocol tells the application to look up the host seed list in the Domain Name System (DNS). This list synchronizes with the nodes in a cluster. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to append the seed list or change the URI if the nodes change. Use this URI format if your driver supports it. If it doesn't, use connectionStrings.private. For Amazon Web Services (AWS) clusters, this resource returns this parameter only if you enable custom DNS.Network Peering Connection -
List of private endpoint-aware connection strings that you can use to connect to this cluster through a private endpoint. This parameter returns only if you deployed a private endpoint to all regions to which you deployed this clusters' nodes.
Private endpoint-aware connection string that you can use to connect to this cluster through a private endpoint.
Hide privateEndpoint attributes Show privateEndpoint attributes object
-
Private endpoint-aware connection string that uses the
mongodb://
protocol to connect to MongoDB Cloud through a private endpoint. -
List that contains the private endpoints through which you connect to MongoDB Cloud when you use connectionStrings.privateEndpoint[n].connectionString or connectionStrings.privateEndpoint[n].srvConnectionString.
Details of a private endpoint deployed for this cluster.
Hide endpoints attributes Show endpoints attributes object
-
Private endpoint-aware connection string that uses the
mongodb+srv://
protocol to connect to MongoDB Cloud through a private endpoint. Themongodb+srv
protocol tells the driver to look up the seed list of hosts in the Domain Name System (DNS). This list synchronizes with the nodes in a cluster. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to append the seed list or change the Uniform Resource Identifier (URI) if the nodes change. Use this Uniform Resource Identifier (URI) format if your application supports it. If it doesn't, use connectionStrings.privateEndpoint[n].connectionString. -
Private endpoint-aware connection string optimized for sharded clusters that uses the
mongodb+srv://
protocol to connect to MongoDB Cloud through a private endpoint. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to change the Uniform Resource Identifier (URI) if the nodes change. Use this Uniform Resource Identifier (URI) format if your application and Atlas cluster supports it. If it doesn't, use and consult the documentation for connectionStrings.privateEndpoint[n].srvConnectionString. -
MongoDB process type to which your application connects. Use
MONGOD
for replica sets andMONGOS
for sharded clusters.Values are
MONGOD
orMONGOS
.
-
-
Network peering connection strings for each interface Virtual Private Cloud (VPC) endpoint that you configured to connect to this cluster. This connection string uses the
mongodb+srv://
protocol. The resource returns this parameter when someone creates a network peering connection to this cluster. This protocol tells the application to look up the host seed list in the Domain Name System (DNS). This list synchronizes with the nodes in a cluster. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to append the seed list or change the Uniform Resource Identifier (URI) if the nodes change. Use this Uniform Resource Identifier (URI) format if your driver supports it. If it doesn't, useconnectionStrings.private
. For Amazon Web Services (AWS) clusters, this parameter returns only if you enable custom DNS.Network Peering Connection -
Public connection string that you can use to connect to this cluster. This connection string uses the
mongodb://
protocol.Connection String URI Format -
Public connection string that you can use to connect to this cluster. This connection string uses the
mongodb+srv://
protocol.Connection String URI Format
-
-
Date and time when MongoDB Cloud created this cluster. This parameter expresses its value in ISO 8601 format in UTC.
-
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value is not configurable on M0/M2/M5 clusters.
MongoDB Cloud requires this parameter if you set replicationSpecs.
If you specify a disk size below the minimum (10 GB), this parameter defaults to the minimum disk size value.
Storage charge calculations depend on whether you choose the default value or a custom value.
The maximum value for disk storage cannot exceed 50 times the maximum RAM for the selected cluster. If you require more storage space, consider upgrading your cluster to a higher tier.
Customize Storage -
Disk warming mode selection.
Values are
FULLY_WARMED
orVISIBLE_EARLIER
. Default value isFULLY_WARMED
.Reduce Secondary Disk Warming Impact -
Cloud service provider that manages your customer keys to provide an additional layer of encryption at rest for the cluster. To enable customer key management for encryption at rest, the cluster replicationSpecs[n].regionConfigs[m].{type}Specs.instanceSize setting must be
M10
or higher and"backupEnabled" : false
or omitted entirely.Values are
NONE
,AWS
,AZURE
, orGCP
.Encryption at Rest using Customer Key Management -
Feature compatibility version of the cluster.
-
Feature compatibility version expiration date. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
-
Set this field to configure the Sharding Management Mode when creating a new Global Cluster.
When set to false, the management mode is set to Atlas-Managed Sharding. This mode fully manages the sharding of your Global Cluster and is built to provide a seamless deployment experience.
When set to true, the management mode is set to Self-Managed Sharding. This mode leaves the management of shards in your hands and is built to provide an advanced and flexible deployment experience.
This setting cannot be changed once the cluster is deployed.
Creating a Global Cluster -
Unique 24-hexadecimal character string that identifies the project.
Format should match the following pattern:
^([a-f0-9]{24})$
. -
Unique 24-hexadecimal digit string that identifies the cluster.
Format should match the following pattern:
^([a-f0-9]{24})$
. -
Collection of key-value pairs between 1 to 255 characters in length that tag and categorize the cluster. The MongoDB Cloud console doesn't display your labels.
Cluster labels are deprecated and will be removed in a future release. We strongly recommend that you use Resource tags instead.
Human-readable labels applied to this MongoDB Cloud component.
Resource Tags -
List of one or more Uniform Resource Locators (URLs) that point to API sub-resources, related API resources, or both. RFC 5988 outlines these relationships.
Web Linking Specification (RFC 5988) Hide links attributes Show links attributes object
-
Uniform Resource Locator (URL) that points another API resource to which this response has some relationship. This URL often begins with
https://cloud.mongodb.com/api/atlas
. -
Uniform Resource Locator (URL) that defines the semantic relationship between this resource and another API resource. This URL often begins with
https://cloud.mongodb.com/api/atlas
.
-
-
MongoDB employee granted access level and expiration for a cluster.
Hide mongoDBEmployeeAccessGrant attributes Show mongoDBEmployeeAccessGrant attributes object
-
Expiration date for the employee access grant. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
-
Level of access to grant to MongoDB Employees.
Values are
CLUSTER_DATABASE_LOGS
,CLUSTER_INFRASTRUCTURE
, orCLUSTER_INFRASTRUCTURE_AND_APP_SERVICES_SYNC_DATA
. -
List of one or more Uniform Resource Locators (URLs) that point to API sub-resources, related API resources, or both. RFC 5988 outlines these relationships.
Web Linking Specification (RFC 5988) Hide links attributes Show links attributes object
-
Uniform Resource Locator (URL) that points another API resource to which this response has some relationship. This URL often begins with
https://cloud.mongodb.com/api/atlas
. -
Uniform Resource Locator (URL) that defines the semantic relationship between this resource and another API resource. This URL often begins with
https://cloud.mongodb.com/api/atlas
.
-
-
-
MongoDB major version of the cluster.
On creation: Choose from the available versions of MongoDB, or leave unspecified for the current recommended default in the MongoDB Cloud platform. The recommended version is a recent Long Term Support version. The default is not guaranteed to be the most recently released version throughout the entire release cycle. For versions available in a specific project, see the linked documentation or use the API endpoint for project LTS versions endpoint.
On update: Increase version only by 1 major version at a time. If the cluster is pinned to a MongoDB feature compatibility version exactly one major version below the current MongoDB version, the MongoDB version can be downgraded to the previous major version.
Available MongoDB Versions in Atlas -
Version of MongoDB that the cluster runs.
Format should match the following pattern:
([\d]+\.[\d]+\.[\d]+)
. -
Human-readable label that identifies the advanced cluster.
Format should match the following pattern:
^[a-zA-Z0-9][a-zA-Z0-9-]*$
. -
Flag that indicates whether the cluster is paused.
-
Flag that indicates whether the cluster uses continuous cloud backups.
Continuous Cloud Backups -
Set this field to configure the replica set scaling mode for your cluster.
By default, Atlas scales under WORKLOAD_TYPE. This mode allows Atlas to scale your analytics nodes in parallel to your operational nodes.
When configured as SEQUENTIAL, Atlas scales all nodes sequentially. This mode is intended for steady-state workloads and applications performing latency-sensitive secondary reads.
When configured as NODE_TYPE, Atlas scales your electable nodes in parallel with your read-only and analytics nodes. This mode is intended for large, dynamic workloads requiring frequent and timely cluster tier scaling. This is the fastest scaling strategy, but it might impact latency of workloads when performing extensive secondary reads.
Values are
SEQUENTIAL
,WORKLOAD_TYPE
, orNODE_TYPE
. Default value isWORKLOAD_TYPE
.Modify the Replica Set Scaling Mode -
List of settings that configure your cluster regions. For Global Clusters, each object in the array represents a zone where your clusters nodes deploy. For non-Global sharded clusters and replica sets, this array has one object representing where your clusters nodes deploy.
Details that explain how MongoDB Cloud replicates data on the specified MongoDB database.
Hide replicationSpecs attributes Show replicationSpecs attributes object
-
Unique 24-hexadecimal digit string that identifies the replication object for a zone in a Multi-Cloud Cluster. If you include existing zones in the request, you must specify this parameter. If you add a new zone to an existing Multi-Cloud Cluster, you may specify this parameter. The request deletes any existing zones in the Multi-Cloud Cluster that you exclude from the request.
Format should match the following pattern:
^([a-f0-9]{24})$
. -
Positive integer that specifies the number of shards to deploy in each specified zone. If you set this value to
1
and clusterType isSHARDED
, MongoDB Cloud deploys a single-shard sharded cluster. Don't create a sharded cluster with a single shard for production environments. Single-shard sharded clusters don't provide the same benefits as multi-shard configurations.If you are upgrading a replica set to a sharded cluster, you cannot increase the number of shards in the same update request. You should wait until after the cluster has completed upgrading to sharded and you have reconnected all application clients to the MongoDB router before adding additional shards. Otherwise, your data might become inconsistent once MongoDB Cloud begins distributing data across shards.
Minimum value is
1
. -
Hardware specifications for nodes set for a given region. Each regionConfigs object describes the region's priority in elections and the number and type of MongoDB nodes that MongoDB Cloud deploys to the region. Each regionConfigs object must have either an analyticsSpecs object, electableSpecs object, or readOnlySpecs object. Tenant clusters only require electableSpecs. Dedicated clusters can specify any of these specifications, but must have at least one electableSpecs object within a replicationSpec. Every hardware specification must use the same instanceSize.
Example:
If you set
"replicationSpecs[n].regionConfigs[m].analyticsSpecs.instanceSize" : "M30"
, set"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" :
"M30"if you have electable nodes and
"replicationSpecs[n].regionConfigs[m].readOnlySpecs.instanceSize" :"M30"
if you have read-only nodes.One of: Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes Show attributes
electableSpecs
object Hardware specifications for all electable nodes deployed in the region. Electable nodes can become the primary and can enable local reads. If you don't specify this option, MongoDB Cloud deploys no electable nodes to the region.
One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,M2
,M5
, orM0
. -
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,M2
, orM5
.
-
-
Precedence is given to this region when a primary election occurs. If your regionConfigs has only readOnlySpecs, analyticsSpecs, or both, set this value to
0
. If you have multiple regionConfigs objects (your cluster is multi-region or multi-cloud), they must have priorities in descending order. The highest priority is7
.Example: If you have three regions, their priorities would be
7
,6
, and5
respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be4
and3
respectively.Minimum value is
0
, maximum value is7
. -
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,GCP
,AZURE
orTENANT
.Value is
AWS
. regionName
string Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of: Physical location where MongoDB Cloud deploys your AWS-hosted MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. MongoDB Cloud assigns the VPC a CIDR block. To limit a new VPC peering connection to one CIDR block and region, create the connection first. Deploy the cluster after the connection starts.
Values are
US_GOV_WEST_1
,US_GOV_EAST_1
,US_EAST_1
,US_EAST_2
,US_WEST_1
,US_WEST_2
,CA_CENTRAL_1
,EU_NORTH_1
,EU_WEST_1
,EU_WEST_2
,EU_WEST_3
,EU_CENTRAL_1
,EU_CENTRAL_2
,AP_EAST_1
,AP_NORTHEAST_1
,AP_NORTHEAST_2
,AP_NORTHEAST_3
,AP_SOUTHEAST_1
,AP_SOUTHEAST_2
,AP_SOUTHEAST_3
,AP_SOUTHEAST_4
,AP_SOUTH_1
,AP_SOUTH_2
,SA_EAST_1
,CN_NORTH_1
,CN_NORTHWEST_1
,ME_SOUTH_1
,ME_CENTRAL_1
,AF_SOUTH_1
,EU_SOUTH_1
,EU_SOUTH_2
,IL_CENTRAL_1
,CA_WEST_1
,AP_SOUTHEAST_5
,AP_SOUTHEAST_7
,MX_CENTRAL_1
, orGLOBAL
.Microsoft Azure Regions.
Values are
US_CENTRAL
,US_EAST
,US_EAST_2
,US_NORTH_CENTRAL
,US_WEST
,US_SOUTH_CENTRAL
,EUROPE_NORTH
,EUROPE_WEST
,US_WEST_CENTRAL
,US_WEST_2
,US_WEST_3
,CANADA_EAST
,CANADA_CENTRAL
,BRAZIL_SOUTH
,BRAZIL_SOUTHEAST
,AUSTRALIA_CENTRAL
,AUSTRALIA_CENTRAL_2
,AUSTRALIA_EAST
,AUSTRALIA_SOUTH_EAST
,GERMANY_WEST_CENTRAL
,GERMANY_NORTH
,SWEDEN_CENTRAL
,SWEDEN_SOUTH
,SWITZERLAND_NORTH
,SWITZERLAND_WEST
,UK_SOUTH
,UK_WEST
,NORWAY_EAST
,NORWAY_WEST
,INDIA_CENTRAL
,INDIA_SOUTH
,INDIA_WEST
,CHINA_EAST
,CHINA_NORTH
,ASIA_EAST
,JAPAN_EAST
,JAPAN_WEST
,ASIA_SOUTH_EAST
,KOREA_CENTRAL
,KOREA_SOUTH
,FRANCE_CENTRAL
,FRANCE_SOUTH
,SOUTH_AFRICA_NORTH
,SOUTH_AFRICA_WEST
,UAE_CENTRAL
,UAE_NORTH
,QATAR_CENTRAL
,POLAND_CENTRAL
,ISRAEL_CENTRAL
,ITALY_NORTH
,SPAIN_CENTRAL
,MEXICO_CENTRAL
, orNEW_ZEALAND_NORTH
.Google Compute Regions.
Values are
EASTERN_US
,EASTERN_US_AW
,US_EAST_4
,US_EAST_4_AW
,US_EAST_5
,US_EAST_5_AW
,US_WEST_2
,US_WEST_2_AW
,US_WEST_3
,US_WEST_3_AW
,US_WEST_4
,US_WEST_4_AW
,US_SOUTH_1
,US_SOUTH_1_AW
,CENTRAL_US
,CENTRAL_US_AW
,WESTERN_US
,WESTERN_US_AW
,NORTH_AMERICA_NORTHEAST_1
,NORTH_AMERICA_NORTHEAST_2
,NORTH_AMERICA_SOUTH_1
,SOUTH_AMERICA_EAST_1
,SOUTH_AMERICA_WEST_1
,WESTERN_EUROPE
,EUROPE_NORTH_1
,EUROPE_WEST_2
,EUROPE_WEST_3
,EUROPE_WEST_4
,EUROPE_WEST_6
,EUROPE_WEST_8
,EUROPE_WEST_9
,EUROPE_WEST_10
,EUROPE_WEST_12
,EUROPE_SOUTHWEST_1
,EUROPE_CENTRAL_2
,MIDDLE_EAST_CENTRAL_1
,MIDDLE_EAST_CENTRAL_2
,MIDDLE_EAST_WEST_1
,AUSTRALIA_SOUTHEAST_1
,AUSTRALIA_SOUTHEAST_2
,AFRICA_SOUTH_1
,EASTERN_ASIA_PACIFIC
,NORTHEASTERN_ASIA_PACIFIC
,SOUTHEASTERN_ASIA_PACIFIC
,ASIA_EAST_2
,ASIA_NORTHEAST_2
,ASIA_NORTHEAST_3
,ASIA_SOUTH_1
,ASIA_SOUTH_2
, orASIA_SOUTHEAST_2
.-
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes Show analyticsAutoScaling attributes object
-
Options that determine how this cluster handles CPU scaling.
Hide compute attributes Show compute attributes object
-
Flag that indicates whether instance size reactive auto-scaling is enabled.
- Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize. - Set to
false
to disable instance size reactive auto-scaling.
- Set to
maxInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.minInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.-
Flag that indicates whether predictive instance size auto-scaling is enabled.
- Set to
true
to enable predictive instance size auto-scaling. MongoDB Cloud requires replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled to betrue
in order to enable this feature. - Set to
false
to disable predictive instance size auto-scaling.
- Set to
-
Flag that indicates whether the instance size may scale down via reactive auto-scaling. MongoDB Cloud requires this parameter if replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled is
true
. If you enable this option, specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.minInstanceSize.
-
-
Setting that enables disk auto-scaling.
-
analyticsSpecs
object One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
.
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.
-
-
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes Show autoScaling attributes object
-
Options that determine how this cluster handles CPU scaling.
Hide compute attributes Show compute attributes object
-
Flag that indicates whether instance size reactive auto-scaling is enabled.
- Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize. - Set to
false
to disable instance size reactive auto-scaling.
- Set to
maxInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.minInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.-
Flag that indicates whether predictive instance size auto-scaling is enabled.
- Set to
true
to enable predictive instance size auto-scaling. MongoDB Cloud requires replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled to betrue
in order to enable this feature. - Set to
false
to disable predictive instance size auto-scaling.
- Set to
-
Flag that indicates whether the instance size may scale down via reactive auto-scaling. MongoDB Cloud requires this parameter if replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled is
true
. If you enable this option, specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.minInstanceSize.
-
-
Setting that enables disk auto-scaling.
-
readOnlySpecs
object One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
.
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.
-
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes Show attributes
electableSpecs
object Hardware specifications for all electable nodes deployed in the region. Electable nodes can become the primary and can enable local reads. If you don't specify this option, MongoDB Cloud deploys no electable nodes to the region.
One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,M2
,M5
, orM0
. -
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,M2
, orM5
.
-
-
Precedence is given to this region when a primary election occurs. If your regionConfigs has only readOnlySpecs, analyticsSpecs, or both, set this value to
0
. If you have multiple regionConfigs objects (your cluster is multi-region or multi-cloud), they must have priorities in descending order. The highest priority is7
.Example: If you have three regions, their priorities would be
7
,6
, and5
respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be4
and3
respectively.Minimum value is
0
, maximum value is7
. -
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,GCP
,AZURE
orTENANT
.Value is
AZURE
. regionName
string Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of: Physical location where MongoDB Cloud deploys your AWS-hosted MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. MongoDB Cloud assigns the VPC a CIDR block. To limit a new VPC peering connection to one CIDR block and region, create the connection first. Deploy the cluster after the connection starts.
Values are
US_GOV_WEST_1
,US_GOV_EAST_1
,US_EAST_1
,US_EAST_2
,US_WEST_1
,US_WEST_2
,CA_CENTRAL_1
,EU_NORTH_1
,EU_WEST_1
,EU_WEST_2
,EU_WEST_3
,EU_CENTRAL_1
,EU_CENTRAL_2
,AP_EAST_1
,AP_NORTHEAST_1
,AP_NORTHEAST_2
,AP_NORTHEAST_3
,AP_SOUTHEAST_1
,AP_SOUTHEAST_2
,AP_SOUTHEAST_3
,AP_SOUTHEAST_4
,AP_SOUTH_1
,AP_SOUTH_2
,SA_EAST_1
,CN_NORTH_1
,CN_NORTHWEST_1
,ME_SOUTH_1
,ME_CENTRAL_1
,AF_SOUTH_1
,EU_SOUTH_1
,EU_SOUTH_2
,IL_CENTRAL_1
,CA_WEST_1
,AP_SOUTHEAST_5
,AP_SOUTHEAST_7
,MX_CENTRAL_1
, orGLOBAL
.Microsoft Azure Regions.
Values are
US_CENTRAL
,US_EAST
,US_EAST_2
,US_NORTH_CENTRAL
,US_WEST
,US_SOUTH_CENTRAL
,EUROPE_NORTH
,EUROPE_WEST
,US_WEST_CENTRAL
,US_WEST_2
,US_WEST_3
,CANADA_EAST
,CANADA_CENTRAL
,BRAZIL_SOUTH
,BRAZIL_SOUTHEAST
,AUSTRALIA_CENTRAL
,AUSTRALIA_CENTRAL_2
,AUSTRALIA_EAST
,AUSTRALIA_SOUTH_EAST
,GERMANY_WEST_CENTRAL
,GERMANY_NORTH
,SWEDEN_CENTRAL
,SWEDEN_SOUTH
,SWITZERLAND_NORTH
,SWITZERLAND_WEST
,UK_SOUTH
,UK_WEST
,NORWAY_EAST
,NORWAY_WEST
,INDIA_CENTRAL
,INDIA_SOUTH
,INDIA_WEST
,CHINA_EAST
,CHINA_NORTH
,ASIA_EAST
,JAPAN_EAST
,JAPAN_WEST
,ASIA_SOUTH_EAST
,KOREA_CENTRAL
,KOREA_SOUTH
,FRANCE_CENTRAL
,FRANCE_SOUTH
,SOUTH_AFRICA_NORTH
,SOUTH_AFRICA_WEST
,UAE_CENTRAL
,UAE_NORTH
,QATAR_CENTRAL
,POLAND_CENTRAL
,ISRAEL_CENTRAL
,ITALY_NORTH
,SPAIN_CENTRAL
,MEXICO_CENTRAL
, orNEW_ZEALAND_NORTH
.Google Compute Regions.
Values are
EASTERN_US
,EASTERN_US_AW
,US_EAST_4
,US_EAST_4_AW
,US_EAST_5
,US_EAST_5_AW
,US_WEST_2
,US_WEST_2_AW
,US_WEST_3
,US_WEST_3_AW
,US_WEST_4
,US_WEST_4_AW
,US_SOUTH_1
,US_SOUTH_1_AW
,CENTRAL_US
,CENTRAL_US_AW
,WESTERN_US
,WESTERN_US_AW
,NORTH_AMERICA_NORTHEAST_1
,NORTH_AMERICA_NORTHEAST_2
,NORTH_AMERICA_SOUTH_1
,SOUTH_AMERICA_EAST_1
,SOUTH_AMERICA_WEST_1
,WESTERN_EUROPE
,EUROPE_NORTH_1
,EUROPE_WEST_2
,EUROPE_WEST_3
,EUROPE_WEST_4
,EUROPE_WEST_6
,EUROPE_WEST_8
,EUROPE_WEST_9
,EUROPE_WEST_10
,EUROPE_WEST_12
,EUROPE_SOUTHWEST_1
,EUROPE_CENTRAL_2
,MIDDLE_EAST_CENTRAL_1
,MIDDLE_EAST_CENTRAL_2
,MIDDLE_EAST_WEST_1
,AUSTRALIA_SOUTHEAST_1
,AUSTRALIA_SOUTHEAST_2
,AFRICA_SOUTH_1
,EASTERN_ASIA_PACIFIC
,NORTHEASTERN_ASIA_PACIFIC
,SOUTHEASTERN_ASIA_PACIFIC
,ASIA_EAST_2
,ASIA_NORTHEAST_2
,ASIA_NORTHEAST_3
,ASIA_SOUTH_1
,ASIA_SOUTH_2
, orASIA_SOUTHEAST_2
.-
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes Show analyticsAutoScaling attributes object
-
Options that determine how this cluster handles CPU scaling.
Hide compute attributes Show compute attributes object
-
Flag that indicates whether instance size reactive auto-scaling is enabled.
- Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize. - Set to
false
to disable instance size reactive auto-scaling.
- Set to
maxInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.minInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.-
Flag that indicates whether predictive instance size auto-scaling is enabled.
- Set to
true
to enable predictive instance size auto-scaling. MongoDB Cloud requires replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled to betrue
in order to enable this feature. - Set to
false
to disable predictive instance size auto-scaling.
- Set to
-
Flag that indicates whether the instance size may scale down via reactive auto-scaling. MongoDB Cloud requires this parameter if replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled is
true
. If you enable this option, specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.minInstanceSize.
-
-
Setting that enables disk auto-scaling.
-
analyticsSpecs
object One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
.
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.
-
-
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes Show autoScaling attributes object
-
Options that determine how this cluster handles CPU scaling.
Hide compute attributes Show compute attributes object
-
Flag that indicates whether instance size reactive auto-scaling is enabled.
- Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize. - Set to
false
to disable instance size reactive auto-scaling.
- Set to
maxInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.minInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.-
Flag that indicates whether predictive instance size auto-scaling is enabled.
- Set to
true
to enable predictive instance size auto-scaling. MongoDB Cloud requires replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled to betrue
in order to enable this feature. - Set to
false
to disable predictive instance size auto-scaling.
- Set to
-
Flag that indicates whether the instance size may scale down via reactive auto-scaling. MongoDB Cloud requires this parameter if replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled is
true
. If you enable this option, specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.minInstanceSize.
-
-
Setting that enables disk auto-scaling.
-
readOnlySpecs
object One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
.
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.
-
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes Show attributes
electableSpecs
object Hardware specifications for all electable nodes deployed in the region. Electable nodes can become the primary and can enable local reads. If you don't specify this option, MongoDB Cloud deploys no electable nodes to the region.
One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,M2
,M5
, orM0
. -
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,M2
, orM5
.
-
-
Precedence is given to this region when a primary election occurs. If your regionConfigs has only readOnlySpecs, analyticsSpecs, or both, set this value to
0
. If you have multiple regionConfigs objects (your cluster is multi-region or multi-cloud), they must have priorities in descending order. The highest priority is7
.Example: If you have three regions, their priorities would be
7
,6
, and5
respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be4
and3
respectively.Minimum value is
0
, maximum value is7
. -
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,GCP
,AZURE
orTENANT
.Value is
GCP
. regionName
string Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of: Physical location where MongoDB Cloud deploys your AWS-hosted MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. MongoDB Cloud assigns the VPC a CIDR block. To limit a new VPC peering connection to one CIDR block and region, create the connection first. Deploy the cluster after the connection starts.
Values are
US_GOV_WEST_1
,US_GOV_EAST_1
,US_EAST_1
,US_EAST_2
,US_WEST_1
,US_WEST_2
,CA_CENTRAL_1
,EU_NORTH_1
,EU_WEST_1
,EU_WEST_2
,EU_WEST_3
,EU_CENTRAL_1
,EU_CENTRAL_2
,AP_EAST_1
,AP_NORTHEAST_1
,AP_NORTHEAST_2
,AP_NORTHEAST_3
,AP_SOUTHEAST_1
,AP_SOUTHEAST_2
,AP_SOUTHEAST_3
,AP_SOUTHEAST_4
,AP_SOUTH_1
,AP_SOUTH_2
,SA_EAST_1
,CN_NORTH_1
,CN_NORTHWEST_1
,ME_SOUTH_1
,ME_CENTRAL_1
,AF_SOUTH_1
,EU_SOUTH_1
,EU_SOUTH_2
,IL_CENTRAL_1
,CA_WEST_1
,AP_SOUTHEAST_5
,AP_SOUTHEAST_7
,MX_CENTRAL_1
, orGLOBAL
.Microsoft Azure Regions.
Values are
US_CENTRAL
,US_EAST
,US_EAST_2
,US_NORTH_CENTRAL
,US_WEST
,US_SOUTH_CENTRAL
,EUROPE_NORTH
,EUROPE_WEST
,US_WEST_CENTRAL
,US_WEST_2
,US_WEST_3
,CANADA_EAST
,CANADA_CENTRAL
,BRAZIL_SOUTH
,BRAZIL_SOUTHEAST
,AUSTRALIA_CENTRAL
,AUSTRALIA_CENTRAL_2
,AUSTRALIA_EAST
,AUSTRALIA_SOUTH_EAST
,GERMANY_WEST_CENTRAL
,GERMANY_NORTH
,SWEDEN_CENTRAL
,SWEDEN_SOUTH
,SWITZERLAND_NORTH
,SWITZERLAND_WEST
,UK_SOUTH
,UK_WEST
,NORWAY_EAST
,NORWAY_WEST
,INDIA_CENTRAL
,INDIA_SOUTH
,INDIA_WEST
,CHINA_EAST
,CHINA_NORTH
,ASIA_EAST
,JAPAN_EAST
,JAPAN_WEST
,ASIA_SOUTH_EAST
,KOREA_CENTRAL
,KOREA_SOUTH
,FRANCE_CENTRAL
,FRANCE_SOUTH
,SOUTH_AFRICA_NORTH
,SOUTH_AFRICA_WEST
,UAE_CENTRAL
,UAE_NORTH
,QATAR_CENTRAL
,POLAND_CENTRAL
,ISRAEL_CENTRAL
,ITALY_NORTH
,SPAIN_CENTRAL
,MEXICO_CENTRAL
, orNEW_ZEALAND_NORTH
.Google Compute Regions.
Values are
EASTERN_US
,EASTERN_US_AW
,US_EAST_4
,US_EAST_4_AW
,US_EAST_5
,US_EAST_5_AW
,US_WEST_2
,US_WEST_2_AW
,US_WEST_3
,US_WEST_3_AW
,US_WEST_4
,US_WEST_4_AW
,US_SOUTH_1
,US_SOUTH_1_AW
,CENTRAL_US
,CENTRAL_US_AW
,WESTERN_US
,WESTERN_US_AW
,NORTH_AMERICA_NORTHEAST_1
,NORTH_AMERICA_NORTHEAST_2
,NORTH_AMERICA_SOUTH_1
,SOUTH_AMERICA_EAST_1
,SOUTH_AMERICA_WEST_1
,WESTERN_EUROPE
,EUROPE_NORTH_1
,EUROPE_WEST_2
,EUROPE_WEST_3
,EUROPE_WEST_4
,EUROPE_WEST_6
,EUROPE_WEST_8
,EUROPE_WEST_9
,EUROPE_WEST_10
,EUROPE_WEST_12
,EUROPE_SOUTHWEST_1
,EUROPE_CENTRAL_2
,MIDDLE_EAST_CENTRAL_1
,MIDDLE_EAST_CENTRAL_2
,MIDDLE_EAST_WEST_1
,AUSTRALIA_SOUTHEAST_1
,AUSTRALIA_SOUTHEAST_2
,AFRICA_SOUTH_1
,EASTERN_ASIA_PACIFIC
,NORTHEASTERN_ASIA_PACIFIC
,SOUTHEASTERN_ASIA_PACIFIC
,ASIA_EAST_2
,ASIA_NORTHEAST_2
,ASIA_NORTHEAST_3
,ASIA_SOUTH_1
,ASIA_SOUTH_2
, orASIA_SOUTHEAST_2
.-
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes Show analyticsAutoScaling attributes object
-
Options that determine how this cluster handles CPU scaling.
Hide compute attributes Show compute attributes object
-
Flag that indicates whether instance size reactive auto-scaling is enabled.
- Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize. - Set to
false
to disable instance size reactive auto-scaling.
- Set to
maxInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.minInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.-
Flag that indicates whether predictive instance size auto-scaling is enabled.
- Set to
true
to enable predictive instance size auto-scaling. MongoDB Cloud requires replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled to betrue
in order to enable this feature. - Set to
false
to disable predictive instance size auto-scaling.
- Set to
-
Flag that indicates whether the instance size may scale down via reactive auto-scaling. MongoDB Cloud requires this parameter if replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled is
true
. If you enable this option, specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.minInstanceSize.
-
-
Setting that enables disk auto-scaling.
-
analyticsSpecs
object One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
.
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.
-
-
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes Show autoScaling attributes object
-
Options that determine how this cluster handles CPU scaling.
Hide compute attributes Show compute attributes object
-
Flag that indicates whether instance size reactive auto-scaling is enabled.
- Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize. - Set to
false
to disable instance size reactive auto-scaling.
- Set to
maxInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.minInstanceSize
string Instance size boundary to which your cluster can automatically scale.
One of: Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
.Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.-
Flag that indicates whether predictive instance size auto-scaling is enabled.
- Set to
true
to enable predictive instance size auto-scaling. MongoDB Cloud requires replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled to betrue
in order to enable this feature. - Set to
false
to disable predictive instance size auto-scaling.
- Set to
-
Flag that indicates whether the instance size may scale down via reactive auto-scaling. MongoDB Cloud requires this parameter if replicationSpecs[n].regionConfigs[m].autoScaling.compute.enabled is
true
. If you enable this option, specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.minInstanceSize.
-
-
Setting that enables disk auto-scaling.
-
readOnlySpecs
object One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
.
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
Hardware specifications for read-only nodes in the region. Read-only nodes can never become the primary member, but can enable local reads.If you don't specify this parameter, no read-only nodes are deployed to the region.
Hide attributes Show attributes
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
.
-
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes Show attributes
electableSpecs
object Hardware specifications for all electable nodes deployed in the region. Electable nodes can become the primary and can enable local reads. If you don't specify this option, MongoDB Cloud deploys no electable nodes to the region.
One of: Hardware specifications for nodes deployed in the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M100
,M140
,M200
,M300
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,R700
,M40_NVME
,M50_NVME
,M60_NVME
,M80_NVME
,M200_NVME
, orM400_NVME
. -
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" to "AWS"
. set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" to "M30"
or greater (not includingMxx_NVME
tiers).set
"replicationSpecs[n].regionConfigs[m].electableSpecs.ebsVolumeType" to "PROVISIONED"
.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost. MongoDB Cloud enforces minimum ratios of storage capacity to system memory for given cluster tiers. This keeps cluster performance consistent with large datasets.
- Instance sizes
M10
toM40
have a ratio of disk capacity to system memory of 60:1. - Instance sizes greater than
M40
have a ratio of 120:1.
- set
-
Type of storage you want to attach to your AWS-provisioned cluster.
STANDARD
volume types can't exceed the default input/output operations per second (IOPS) rate for the selected volume size.PROVISIONED
volume types must fall within the allowable IOPS range for the selected volume size. You must set this value to (PROVISIONED
) for NVMe clusters.
Values are
STANDARD
orPROVISIONED
. Default value isSTANDARD
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M90
,M200
,R40
,R50
,R60
,R80
,R200
,R300
,R400
,M60_NVME
,M80_NVME
,M200_NVME
,M300_NVME
,M400_NVME
, orM600_NVME
. -
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
- set
"replicationSpecs[n].regionConfigs[m].providerName" : "Azure"
. - set
"replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize" : "M40"
or greater not includingMxx_NVME
tiers.
The maximum input/output operations per second (IOPS) depend on the selected .instanceSize and .diskSizeGB. This parameter defaults to the cluster tier's standard IOPS value. Changing this value impacts cluster cost.
Programmatic API Keys - set
-
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
Hardware specification for the instance sizes in this region. Each instance size has a default storage and memory capacity. The instance size you select applies to all the data-bearing hosts of the node type.
Values are
M10
,M20
,M30
,M40
,M50
,M60
,M80
,M140
,M200
,M250
,M300
,M400
,R40
,R50
,R60
,R80
,R200
,R300
,R400
, orR600
. -
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hide attributes Show attributes
-
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,M2
,M5
, orM0
. -
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,M2
, orM5
.
-
-
Precedence is given to this region when a primary election occurs. If your regionConfigs has only readOnlySpecs, analyticsSpecs, or both, set this value to
0
. If you have multiple regionConfigs objects (your cluster is multi-region or multi-cloud), they must have priorities in descending order. The highest priority is7
.Example: If you have three regions, their priorities would be
7
,6
, and5
respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be4
and3
respectively.Minimum value is
0
, maximum value is7
. -
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,GCP
,AZURE
orTENANT
.Value is
TENANT
. regionName
string Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of: Physical location where MongoDB Cloud deploys your AWS-hosted MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. MongoDB Cloud assigns the VPC a CIDR block. To limit a new VPC peering connection to one CIDR block and region, create the connection first. Deploy the cluster after the connection starts.
Values are
US_GOV_WEST_1
,US_GOV_EAST_1
,US_EAST_1
,US_EAST_2
,US_WEST_1
,US_WEST_2
,CA_CENTRAL_1
,EU_NORTH_1
,EU_WEST_1
,EU_WEST_2
,EU_WEST_3
,EU_CENTRAL_1
,EU_CENTRAL_2
,AP_EAST_1
,AP_NORTHEAST_1
,AP_NORTHEAST_2
,AP_NORTHEAST_3
,AP_SOUTHEAST_1
,AP_SOUTHEAST_2
,AP_SOUTHEAST_3
,AP_SOUTHEAST_4
,AP_SOUTH_1
,AP_SOUTH_2
,SA_EAST_1
,CN_NORTH_1
,CN_NORTHWEST_1
,ME_SOUTH_1
,ME_CENTRAL_1
,AF_SOUTH_1
,EU_SOUTH_1
,EU_SOUTH_2
,IL_CENTRAL_1
,CA_WEST_1
,AP_SOUTHEAST_5
,AP_SOUTHEAST_7
,MX_CENTRAL_1
, orGLOBAL
.Microsoft Azure Regions.
Values are
US_CENTRAL
,US_EAST
,US_EAST_2
,US_NORTH_CENTRAL
,US_WEST
,US_SOUTH_CENTRAL
,EUROPE_NORTH
,EUROPE_WEST
,US_WEST_CENTRAL
,US_WEST_2
,US_WEST_3
,CANADA_EAST
,CANADA_CENTRAL
,BRAZIL_SOUTH
,BRAZIL_SOUTHEAST
,AUSTRALIA_CENTRAL
,AUSTRALIA_CENTRAL_2
,AUSTRALIA_EAST
,AUSTRALIA_SOUTH_EAST
,GERMANY_WEST_CENTRAL
,GERMANY_NORTH
,SWEDEN_CENTRAL
,SWEDEN_SOUTH
,SWITZERLAND_NORTH
,SWITZERLAND_WEST
,UK_SOUTH
,UK_WEST
,NORWAY_EAST
,NORWAY_WEST
,INDIA_CENTRAL
,INDIA_SOUTH
,INDIA_WEST
,CHINA_EAST
,CHINA_NORTH
,ASIA_EAST
,JAPAN_EAST
,JAPAN_WEST
,ASIA_SOUTH_EAST
,KOREA_CENTRAL
,KOREA_SOUTH
,FRANCE_CENTRAL
,FRANCE_SOUTH
,SOUTH_AFRICA_NORTH
,SOUTH_AFRICA_WEST
,UAE_CENTRAL
,UAE_NORTH
,QATAR_CENTRAL
,POLAND_CENTRAL
,ISRAEL_CENTRAL
,ITALY_NORTH
,SPAIN_CENTRAL
,MEXICO_CENTRAL
, orNEW_ZEALAND_NORTH
.Google Compute Regions.
Values are
EASTERN_US
,EASTERN_US_AW
,US_EAST_4
,US_EAST_4_AW
,US_EAST_5
,US_EAST_5_AW
,US_WEST_2
,US_WEST_2_AW
,US_WEST_3
,US_WEST_3_AW
,US_WEST_4
,US_WEST_4_AW
,US_SOUTH_1
,US_SOUTH_1_AW
,CENTRAL_US
,CENTRAL_US_AW
,WESTERN_US
,WESTERN_US_AW
,NORTH_AMERICA_NORTHEAST_1
,NORTH_AMERICA_NORTHEAST_2
,NORTH_AMERICA_SOUTH_1
,SOUTH_AMERICA_EAST_1
,SOUTH_AMERICA_WEST_1
,WESTERN_EUROPE
,EUROPE_NORTH_1
,EUROPE_WEST_2
,EUROPE_WEST_3
,EUROPE_WEST_4
,EUROPE_WEST_6
,EUROPE_WEST_8
,EUROPE_WEST_9
,EUROPE_WEST_10
,EUROPE_WEST_12
,EUROPE_SOUTHWEST_1
,EUROPE_CENTRAL_2
,MIDDLE_EAST_CENTRAL_1
,MIDDLE_EAST_CENTRAL_2
,MIDDLE_EAST_WEST_1
,AUSTRALIA_SOUTHEAST_1
,AUSTRALIA_SOUTHEAST_2
,AFRICA_SOUTH_1
,EASTERN_ASIA_PACIFIC
,NORTHEASTERN_ASIA_PACIFIC
,SOUTHEASTERN_ASIA_PACIFIC
,ASIA_EAST_2
,ASIA_NORTHEAST_2
,ASIA_NORTHEAST_3
,ASIA_SOUTH_1
,ASIA_SOUTH_2
, orASIA_SOUTHEAST_2
.-
Cloud service provider on which MongoDB Cloud provisioned the multi-tenant cluster. The resource returns this parameter when providerName is
TENANT
and electableSpecs.instanceSize isM0
,M2
orM5
.Please note that using an instanceSize of M2 or M5 will create a Flex cluster instead. Support for the instanceSize of M2 or M5 will be discontinued in January 2026. We recommend using the createFlexCluster API for such configurations moving forward.
Values are
AWS
,GCP
, orAZURE
.createFlexCluster API
-
Unique 24-hexadecimal digit string that identifies a zone in a Global Cluster.
Format should match the following pattern:
^([a-f0-9]{24})$
. -
Human-readable label that identifies the zone in a Global Cluster. Provide this value only if
"clusterType" : "GEOSHARDED"
.
-
-
Root Certificate Authority that MongoDB Atlas cluster uses. MongoDB Cloud supports Internet Security Research Group.
Value is
ISRGROOTX1
. Default value isISRGROOTX1
. -
Human-readable label that indicates the current operating condition of this cluster.
Values are
IDLE
,CREATING
,UPDATING
,DELETING
, orREPAIRING
. -
List that contains key-value pairs between 1 to 255 characters in length for tagging and categorizing the cluster.
Key-value pair that tags and categorizes a MongoDB Cloud organization, project, or cluster. For example,
environment : production
.Resource Tags Hide tags attributes Show tags attributes object
-
Constant that defines the set of the tag. For example,
environment
in theenvironment : production
tag.Minimum length is
1
, maximum length is255
. -
Variable that belongs to the set of the tag. For example,
production
in theenvironment : production
tag.Minimum length is
1
, maximum length is255
.
-
-
Flag that indicates whether termination protection is enabled on the cluster. If set to
true
, MongoDB Cloud won't delete the cluster. If set tofalse
, MongoDB Cloud will delete the cluster.Default value is
false
. -
Method by which the cluster maintains the MongoDB versions. If value is
CONTINUOUS
, you must not specify mongoDBMajorVersion.Values are
LTS
orCONTINUOUS
. Default value isLTS
.
-
-
Total number of documents available. MongoDB Cloud omits this value if
includeCount
is set tofalse
. The total number is an estimate and may not be exact.Minimum value is
0
.
-
-
Unauthorized.
Hide response attributes Show response attributes object
-
Bad request detail.
Hide badRequestDetail attribute Show badRequestDetail attribute object
-
Describes the specific conditions or reasons that cause each type of error.
-
HTTP status code returned with this error.
External documentation -
Application error code returned with this error.
-
Parameters used to give more information about the error.
-
Application error message returned with this error.
-
-
Forbidden.
Hide response attributes Show response attributes object
-
Bad request detail.
Hide badRequestDetail attribute Show badRequestDetail attribute object
-
Describes the specific conditions or reasons that cause each type of error.
-
HTTP status code returned with this error.
External documentation -
Application error code returned with this error.
-
Parameters used to give more information about the error.
-
Application error message returned with this error.
-
-
Not Found.
Hide response attributes Show response attributes object
-
Bad request detail.
Hide badRequestDetail attribute Show badRequestDetail attribute object
-
Describes the specific conditions or reasons that cause each type of error.
-
HTTP status code returned with this error.
External documentation -
Application error code returned with this error.
-
Parameters used to give more information about the error.
-
Application error message returned with this error.
-
-
Internal Server Error.
Hide response attributes Show response attributes object
-
Bad request detail.
Hide badRequestDetail attribute Show badRequestDetail attribute object
-
Describes the specific conditions or reasons that cause each type of error.
-
HTTP status code returned with this error.
External documentation -
Application error code returned with this error.
-
Parameters used to give more information about the error.
-
Application error message returned with this error.
-
curl \ --request GET 'https://cloud.mongodb.com/api/atlas/v1.5/groups/32b6e34b3d91647abb20e7b8/clusters' \ --header "Authorization: Bearer $ACCESS_TOKEN"
{ "links": [ { "href": "https://cloud.mongodb.com/api/atlas", "rel": "self" } ], "results": [ { "acceptDataRisksAndForceReplicaSetReconfig": "2025-05-04T09:42:00Z", "advancedConfiguration": { "customOpensslCipherConfigTls12": [ "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384" ], "minimumEnabledTlsProtocol": "TLS1_0", "tlsCipherConfigMode": "CUSTOM" }, "backupEnabled": false, "biConnector": { "enabled": true, "readPreference": "PRIMARY" }, "clusterType": "REPLICASET", "configServerManagementMode": "ATLAS_MANAGED", "configServerType": "DEDICATED", "connectionStrings": { "awsPrivateLink": { "additionalProperty1": "string", "additionalProperty2": "string" }, "awsPrivateLinkSrv": { "additionalProperty1": "string", "additionalProperty2": "string" }, "private": "string", "privateEndpoint": [ { "connectionString": "string", "endpoints": [ { "endpointId": "string", "providerName": "AWS", "region": "string" } ], "srvConnectionString": "string", "srvShardOptimizedConnectionString": "string", "type": "MONGOD" } ], "privateSrv": "string", "standard": "string", "standardSrv": "string" }, "createDate": "2025-05-04T09:42:00Z", "diskSizeGB": 42.0, "diskWarmingMode": "FULLY_WARMED", "encryptionAtRestProvider": "NONE", "featureCompatibilityVersion": "string", "featureCompatibilityVersionExpirationDate": "2025-05-04T09:42:00Z", "globalClusterSelfManagedSharding": true, "groupId": "32b6e34b3d91647abb20e7b8", "id": "32b6e34b3d91647abb20e7b8", "labels": [ { "key": "string", "value": "string" } ], "links": [ { "href": "https://cloud.mongodb.com/api/atlas", "rel": "self" } ], "mongoDBEmployeeAccessGrant": { "expirationTime": "2025-05-04T09:42:00Z", "grantType": "CLUSTER_DATABASE_LOGS", "links": [ { "href": "https://cloud.mongodb.com/api/atlas", "rel": "self" } ] }, "mongoDBMajorVersion": "string", "mongoDBVersion": "string", "name": "string", "paused": true, "pitEnabled": true, "replicaSetScalingStrategy": "WORKLOAD_TYPE", "replicationSpecs": [ { "id": "32b6e34b3d91647abb20e7b8", "numShards": 42, "regionConfigs": [ { "": { "instanceSize": "M10", "diskIOPS": 42, "ebsVolumeType": "STANDARD", "nodeCount": 42 }, "priority": 42, "providerName": "AWS", "regionName": "US_GOV_WEST_1", "analyticsAutoScaling": { "compute": { "enabled": true, "": "M10", "predictiveEnabled": true, "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "analyticsSpecs": { "nodeCount": 42, "instanceSize": "M10", "diskIOPS": 42, "ebsVolumeType": "STANDARD" }, "autoScaling": { "compute": { "enabled": true, "": "M10", "predictiveEnabled": true, "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "readOnlySpecs": { "nodeCount": 42, "instanceSize": "M10", "diskIOPS": 42, "ebsVolumeType": "STANDARD" } } ], "zoneId": "32b6e34b3d91647abb20e7b8", "zoneName": "string" } ], "rootCertType": "ISRGROOTX1", "stateName": "IDLE", "tags": [ { "key": "string", "value": "string" } ], "terminationProtectionEnabled": false, "versionReleaseSystem": "LTS" } ], "totalCount": 42 }
{ "error": 401, "detail": "(This is just an example, the exception may not be related to this endpoint)", "reason": "Unauthorized", "errorCode": "NOT_ORG_GROUP_CREATOR" }
{ "error": 403, "detail": "(This is just an example, the exception may not be related to this endpoint)", "reason": "Forbidden", "errorCode": "CANNOT_CHANGE_GROUP_NAME" }
{ "error": 404, "detail": "(This is just an example, the exception may not be related to this endpoint) Cannot find resource AWS", "reason": "Not Found", "errorCode": "RESOURCE_NOT_FOUND" }
{ "error": 500, "detail": "(This is just an example, the exception may not be related to this endpoint)", "reason": "Internal Server Error", "errorCode": "UNEXPECTED_ERROR" }