Upgrades a flex cluster to a dedicated cluster (M10+) in the specified project. To use this resource, the requesting Service Account or API Key must have the Project Cluster Manager role.
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})$.
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 body should be in the prettyprint format.
Default value is false.
Details of the flex cluster upgrade in the specified project.
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.
Group of settings that configures a subset of the advanced configuration details.
The custom OpenSSL cipher suite list for TLS 1.2. This field is only valid when tlsCipherConfigMode is set to CUSTOM.
Values are TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 or TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
The custom OpenSSL cipher suite list for TLS 1.3. This field is only valid when tlsCipherConfigMode is set to CUSTOM.
Not more than 4 elements. Values are TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256, TLS_AES_128_GCM_SHA256, or TLS_AES_128_CCM_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, TLS1_2, or TLS1_3.
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 or DEFAULT.
Flag that indicates whether the cluster can perform backups. If set to true, the cluster can perform backups. You must set this value to true for NVMe clusters. Backup uses Cloud Backups for dedicated clusters and Shared Cluster Backups for tenant clusters. If set to false, the cluster doesn't use backups.
Default value is false.
Settings needed to configure the MongoDB Connector for Business Intelligence for this cluster.
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, or SECONDARY if there are no ANALYTICS nodes.
Values are PRIMARY, SECONDARY, or ANALYTICS.
Configuration of nodes that comprise the cluster.
Values are REPLICASET, SHARDED, or GEOSHARDED.
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 or FIXED_TO_DEDICATED. Default value is ATLAS_MANAGED.
Disk warming mode selection.
Values are FULLY_WARMED or VISIBLE_EARLIER. Default value is FULLY_WARMED.
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, or GCP.
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.
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.
MongoDB employee granted access level and expiration for a cluster.
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, or CLUSTER_INFRASTRUCTURE_AND_APP_SERVICES_SYNC_DATA.
MongoDB major version of the cluster. Set to the binary major version.
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.
Human-readable label that identifies the 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.
Enable or disable log redaction.
This setting configures the mongod or mongos to redact any document field contents from a message accompanying a given log event before logging. This prevents the program from writing potentially sensitive data stored on the database to the diagnostic log. Metadata such as error or operation codes, line numbers, and source file names are still visible in the logs.
Use redactClientLogData in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.
Note: changing this setting on a cluster will trigger a rolling restart as soon as the cluster is updated.
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, or NODE_TYPE. Default value is WORKLOAD_TYPE.
List of settings that configure your cluster regions. This array has one object per shard representing node configurations in each shard. For replica sets there is only one object representing node configurations.
Details that explain how MongoDB Cloud replicates data on the specified MongoDB database.
Hardware specifications for nodes set for a given region. Each regionConfigs object must be unique by region and cloud provider within the replicationSpec. 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.
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.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hardware specifications for nodes deployed in the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are M0, M2, or M5.
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 is 7.
Example: If you have three regions, their priorities would be 7, 6, and 5 respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be 4 and 3 respectively.
Minimum value is 0, maximum value is 7.
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to AWS, GCP, AZURE or TENANT.
Value is AWS.
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.
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_EAST_2, AP_NORTHEAST_1, AP_NORTHEAST_2, AP_NORTHEAST_3, AP_SOUTHEAST_1, AP_SOUTHEAST_2, AP_SOUTHEAST_3, AP_SOUTHEAST_4, AP_SOUTHEAST_5, AP_SOUTHEAST_6, AP_SOUTHEAST_7, 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, MX_CENTRAL_1, or GLOBAL.
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, NEW_ZEALAND_NORTH, US_GOV_VIRGINIA, US_GOV_ARIZONA, or US_GOV_TEXAS.
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, or ASIA_SOUTHEAST_2.
Options that determine how this cluster handles resource scaling.
Options that determine how this cluster handles CPU scaling.
Flag that indicates whether instance size reactive auto-scaling is enabled.
true to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize.false to disable instance size reactive auto-scaling.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.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Options that determine how this cluster handles resource scaling.
Options that determine how this cluster handles CPU scaling.
Flag that indicates whether instance size reactive auto-scaling is enabled.
true to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize.false to disable instance size reactive auto-scaling.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.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hardware specifications for nodes deployed in the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are M0, M2, or M5.
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 is 7.
Example: If you have three regions, their priorities would be 7, 6, and 5 respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be 4 and 3 respectively.
Minimum value is 0, maximum value is 7.
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to AWS, GCP, AZURE or TENANT.
Value is AZURE.
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.
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_EAST_2, AP_NORTHEAST_1, AP_NORTHEAST_2, AP_NORTHEAST_3, AP_SOUTHEAST_1, AP_SOUTHEAST_2, AP_SOUTHEAST_3, AP_SOUTHEAST_4, AP_SOUTHEAST_5, AP_SOUTHEAST_6, AP_SOUTHEAST_7, 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, MX_CENTRAL_1, or GLOBAL.
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, NEW_ZEALAND_NORTH, US_GOV_VIRGINIA, US_GOV_ARIZONA, or US_GOV_TEXAS.
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, or ASIA_SOUTHEAST_2.
Options that determine how this cluster handles resource scaling.
Options that determine how this cluster handles CPU scaling.
Flag that indicates whether instance size reactive auto-scaling is enabled.
true to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize.false to disable instance size reactive auto-scaling.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.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Options that determine how this cluster handles resource scaling.
Options that determine how this cluster handles CPU scaling.
Flag that indicates whether instance size reactive auto-scaling is enabled.
true to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize.false to disable instance size reactive auto-scaling.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.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hardware specifications for nodes deployed in the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are M0, M2, or M5.
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 is 7.
Example: If you have three regions, their priorities would be 7, 6, and 5 respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be 4 and 3 respectively.
Minimum value is 0, maximum value is 7.
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to AWS, GCP, AZURE or TENANT.
Value is GCP.
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.
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_EAST_2, AP_NORTHEAST_1, AP_NORTHEAST_2, AP_NORTHEAST_3, AP_SOUTHEAST_1, AP_SOUTHEAST_2, AP_SOUTHEAST_3, AP_SOUTHEAST_4, AP_SOUTHEAST_5, AP_SOUTHEAST_6, AP_SOUTHEAST_7, 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, MX_CENTRAL_1, or GLOBAL.
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, NEW_ZEALAND_NORTH, US_GOV_VIRGINIA, US_GOV_ARIZONA, or US_GOV_TEXAS.
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, or ASIA_SOUTHEAST_2.
Options that determine how this cluster handles resource scaling.
Options that determine how this cluster handles CPU scaling.
Flag that indicates whether instance size reactive auto-scaling is enabled.
true to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize.false to disable instance size reactive auto-scaling.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.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Options that determine how this cluster handles resource scaling.
Options that determine how this cluster handles CPU scaling.
Flag that indicates whether instance size reactive auto-scaling is enabled.
true to enable instance size reactive auto-scaling. If enabled, you must specify a value for replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize.false to disable instance size reactive auto-scaling.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.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Hardware specifications for nodes deployed in the region.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hardware specifications for nodes deployed in the region.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target IOPS (Input/Output Operations Per Second) desired for storage attached to this hardware.
You can set different IOPS values on different shards when provisioned IOPS are supported.
Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName to AWS.set replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize to M30 or greater (not including Mxx_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.
M10 to M40 have a ratio of disk capacity to system memory of 60:1.M40 have a ratio of 120:1.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 or PROVISIONED. Default value is STANDARD.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M400_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
replicationSpecs[n].regionConfigs[m].providerName : Azure.replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize : M40 or greater not including Mxx_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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
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, or M600_NVME.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instance sizes in this region in this shard. Each instance size has a default storage and memory capacity. Electable nodes and read-only nodes (known as "base nodes") within a single shard must use the same instance size. Analytics nodes can scale independently from base nodes within a shard. Both base nodes and analytics nodes can scale independently from their equivalents in other shards.
Values are M10, M20, M30, M40, M50, M60, M80, M140, M200, M250, M300, M400, R40, R50, R60, R80, R200, R300, R400, or R600.
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
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.
Storage capacity of instance data volumes expressed in gigabytes. Increase this number to add capacity.
This value must be equal for all shards and node types.
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.
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are M0, M2, or M5.
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 is 7.
Example: If you have three regions, their priorities would be 7, 6, and 5 respectively. If you added two more regions for supporting electable nodes, the priorities of those regions would be 4 and 3 respectively.
Minimum value is 0, maximum value is 7.
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to AWS, GCP, AZURE or TENANT.
Value is TENANT.
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.
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_EAST_2, AP_NORTHEAST_1, AP_NORTHEAST_2, AP_NORTHEAST_3, AP_SOUTHEAST_1, AP_SOUTHEAST_2, AP_SOUTHEAST_3, AP_SOUTHEAST_4, AP_SOUTHEAST_5, AP_SOUTHEAST_6, AP_SOUTHEAST_7, 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, MX_CENTRAL_1, or GLOBAL.
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, NEW_ZEALAND_NORTH, US_GOV_VIRGINIA, US_GOV_ARIZONA, or US_GOV_TEXAS.
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, or ASIA_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 is M0, M2 or M5.
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 Create Flex Cluster API for such configurations moving forward.
Values are AWS, GCP, or AZURE.
Human-readable label that describes the zone this shard belongs to in a Global Cluster. Provide this value only if clusterType : GEOSHARDED but not selfManagedSharding : true.
Flag that indicates whether the cluster retains backups.
Default value is false.
Root Certificate Authority that MongoDB Atlas cluster uses. MongoDB Cloud supports Internet Security Research Group.
Value is ISRGROOTX1. Default value is ISRGROOTX1.
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.
Constant that defines the set of the tag. For example, environment in the environment : production tag.
Minimum length is 1, maximum length is 255.
Variable that belongs to the set of the tag. For example, production in the environment : production tag.
Minimum length is 1, maximum length is 255.
Flag that indicates whether termination protection is enabled on the cluster. If set to true, MongoDB Cloud won't delete the cluster. If set to false, MongoDB Cloud will delete the cluster.
Default value is false.
Flag that indicates whether AWS time-based snapshot copies will be used instead of slower standard snapshot copies during fast Atlas cross-region initial syncs. This flag is only relevant for clusters containing AWS nodes.
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 or CONTINUOUS. Default value is LTS.
OK
Flex backup configuration.
Flag that indicates whether backups are performed for this flex cluster. Backup uses flex cluster backups.
Default value is true.
Flex cluster topology.
Value is REPLICASET. Default value is REPLICASET.
Collection of Uniform Resource Locators that point to the MongoDB database.
Public connection string that you can use to connect to this cluster. This connection string uses the mongodb:// protocol.
Public connection string that you can use to connect to this flex cluster. This connection string uses the mongodb+srv:// protocol.
Date and time when MongoDB Cloud created this instance. This parameter expresses its value in ISO 8601 format in UTC.
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 instance.
Format should match the following pattern: ^([a-f0-9]{24})$.
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.
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.
Version of MongoDB that the instance runs.
Format should match the following pattern: ([\d]+\.[\d]+\.[\d]+).
Human-readable label that identifies the instance.
Format should match the following pattern: ^[a-zA-Z0-9][a-zA-Z0-9-]*$.
Group of cloud provider settings that configure the provisioned MongoDB flex cluster.
Cloud service provider on which MongoDB Cloud provisioned the flex cluster.
Values are AWS, AZURE, or GCP.
Storage capacity available to the flex cluster expressed in gigabytes.
Human-readable label that identifies the provider type.
Value is FLEX. Default value is FLEX.
Human-readable label that indicates any current activity being taken on this cluster by the Atlas control plane. With the exception of CREATING and DELETING states, clusters should always be available and have a Primary node even when in states indicating ongoing activity.
IDLE: Atlas is making no changes to this cluster and all changes requested via the UI or API can be assumed to have been applied.CREATING: A cluster being provisioned for the very first time returns state CREATING until it is ready for connections. Ensure IP Access List and DB Users are configured before attempting to connect.UPDATING: A change requested via the UI, API, AutoScaling, or other scheduled activity is taking place.DELETING: The cluster is in the process of deletion and will soon be deleted.REPAIRING: One or more nodes in the cluster are being returned to service by the Atlas control plane. Other nodes should continue to provide service as normal.Values are IDLE, CREATING, UPDATING, DELETING, or REPAIRING.
List that contains key-value pairs between 1 to 255 characters in length for tagging and categorizing the instance.
Key-value pair that tags and categorizes a MongoDB Cloud organization, project, or cluster. For example, environment : production.
Constant that defines the set of the tag. For example, environment in the environment : production tag.
Minimum length is 1, maximum length is 255.
Variable that belongs to the set of the tag. For example, production in the environment : production tag.
Minimum length is 1, maximum length is 255.
Flag that indicates whether termination protection is enabled on the cluster. If set to true, MongoDB Cloud won't delete the cluster. If set to false, MongoDB Cloud will delete the cluster.
Default value is false.
Method by which the cluster maintains the MongoDB versions.
Value is LTS. Default value is LTS.
Bad Request.
Bad request detail.
Describes the specific conditions or reasons that cause each type of error.
HTTP status code returned with this error.
Application error code returned with this error.
Parameters used to give more information about the error.
Application error message returned with this error.
Unauthorized.
Bad request detail.
Describes the specific conditions or reasons that cause each type of error.
HTTP status code returned with this error.
Application error code returned with this error.
Parameters used to give more information about the error.
Application error message returned with this error.
Payment Required.
Bad request detail.
Describes the specific conditions or reasons that cause each type of error.
HTTP status code returned with this error.
Application error code returned with this error.
Parameters used to give more information about the error.
Application error message returned with this error.
Forbidden.
Bad request detail.
Describes the specific conditions or reasons that cause each type of error.
HTTP status code returned with this error.
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.
Bad request detail.
Describes the specific conditions or reasons that cause each type of error.
HTTP status code returned with this error.
Application error code returned with this error.
Parameters used to give more information about the error.
Application error message returned with this error.
Conflict.
Bad request detail.
Describes the specific conditions or reasons that cause each type of error.
HTTP status code returned with this error.
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.
Bad request detail.
Describes the specific conditions or reasons that cause each type of error.
HTTP status code returned with this error.
Application error code returned with this error.
Parameters used to give more information about the error.
Application error message returned with this error.
atlas api flexClusters tenantUpgrade --help
import (
"os"
"context"
"log"
sdk "go.mongodb.org/atlas-sdk/v20241113001/admin"
)
func main() {
ctx := context.Background()
clientID := os.Getenv("MONGODB_ATLAS_CLIENT_ID")
clientSecret := os.Getenv("MONGODB_ATLAS_CLIENT_SECRET")
// See https://dochub.mongodb.org/core/atlas-go-sdk-oauth
client, err := sdk.NewClient(sdk.UseOAuthAuth(clientID, clientSecret))
if err != nil {
log.Fatalf("Error: %v", err)
}
params = &sdk.TenantGroupFlexClusterUpgradeApiParams{}
sdkResp, httpResp, err := client.FlexClustersApi.
TenantGroupFlexClusterUpgradeWithParams(ctx, params).
Execute()
}
curl --include --header "Authorization: Bearer ${ACCESS_TOKEN}" \
--header "Accept: application/vnd.atlas.2024-11-13+json" \
--header "Content-Type: application/json" \
-X POST "https://cloud.mongodb.com/api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade" \
-d '{ <Payload> }'
curl --user "${PUBLIC_KEY}:${PRIVATE_KEY}" \
--digest --include \
--header "Accept: application/vnd.atlas.2024-11-13+json" \
--header "Content-Type: application/json" \
-X POST "https://cloud.mongodb.com/api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade" \
-d '{ <Payload> }'
{
"acceptDataRisksAndForceReplicaSetReconfig": "2026-05-04T09:42:00Z",
"advancedConfiguration": {
"customOpensslCipherConfigTls12": [
"TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"
],
"customOpensslCipherConfigTls13": [
"TLS_AES_256_GCM_SHA384"
],
"minimumEnabledTlsProtocol": "TLS1_0",
"tlsCipherConfigMode": "CUSTOM"
},
"backupEnabled": false,
"biConnector": {
"enabled": true,
"readPreference": "PRIMARY"
},
"clusterType": "REPLICASET",
"configServerManagementMode": "ATLAS_MANAGED",
"diskWarmingMode": "FULLY_WARMED",
"encryptionAtRestProvider": "NONE",
"globalClusterSelfManagedSharding": true,
"labels": [
{
"key": "string",
"value": "string"
}
],
"mongoDBEmployeeAccessGrant": {
"expirationTime": "2026-05-04T09:42:00Z",
"grantType": "CLUSTER_DATABASE_LOGS"
},
"mongoDBMajorVersion": "string",
"name": "string",
"paused": true,
"pitEnabled": true,
"redactClientLogData": true,
"replicaSetScalingStrategy": "WORKLOAD_TYPE",
"replicationSpecs": [
{
"regionConfigs": [
{
"electableSpecs": {
"diskSizeGB": 42.0,
"diskIOPS": 42,
"ebsVolumeType": "STANDARD",
"instanceSize": "M10",
"nodeCount": 42
},
"priority": 42,
"providerName": "AWS",
"regionName": "US_GOV_WEST_1",
"analyticsAutoScaling": {
"compute": {
"enabled": true,
"scaleDownEnabled": true
},
"diskGB": {
"enabled": true
}
},
"analyticsSpecs": {
"diskIOPS": 42,
"diskSizeGB": 42.0,
"ebsVolumeType": "STANDARD",
"instanceSize": "M10",
"nodeCount": 42
},
"autoScaling": {
"compute": {
"enabled": true,
"scaleDownEnabled": true
},
"diskGB": {
"enabled": true
}
},
"effectiveAnalyticsSpecs": {
"diskIOPS": 42,
"diskSizeGB": 42.0,
"ebsVolumeType": "STANDARD",
"instanceSize": "M10",
"nodeCount": 42
},
"effectiveElectableSpecs": {
"diskIOPS": 42,
"diskSizeGB": 42.0,
"ebsVolumeType": "STANDARD",
"instanceSize": "M10",
"nodeCount": 42
},
"effectiveReadOnlySpecs": {
"diskIOPS": 42,
"diskSizeGB": 42.0,
"ebsVolumeType": "STANDARD",
"instanceSize": "M10",
"nodeCount": 42
},
"readOnlySpecs": {
"diskIOPS": 42,
"diskSizeGB": 42.0,
"ebsVolumeType": "STANDARD",
"instanceSize": "M10",
"nodeCount": 42
}
}
],
"zoneName": "string"
}
],
"retainBackups": false,
"rootCertType": "ISRGROOTX1",
"tags": [
{
"key": "string",
"value": "string"
}
],
"terminationProtectionEnabled": false,
"useAwsTimeBasedSnapshotCopyForFastInitialSync": false,
"versionReleaseSystem": "LTS"
}
{
"backupSettings": {
"enabled": true
},
"clusterType": "REPLICASET",
"connectionStrings": {
"standard": "string",
"standardSrv": "string"
},
"createDate": "2026-05-04T09:42:00Z",
"groupId": "32b6e34b3d91647abb20e7b8",
"id": "32b6e34b3d91647abb20e7b8",
"links": [
{
"href": "https://cloud.mongodb.com/api/atlas",
"rel": "self"
}
],
"mongoDBVersion": "string",
"name": "string",
"providerSettings": {
"backingProviderName": "AWS",
"diskSizeGB": 42.0,
"providerName": "FLEX",
"regionName": "string"
},
"stateName": "IDLE",
"tags": [
{
"key": "string",
"value": "string"
}
],
"terminationProtectionEnabled": false,
"versionReleaseSystem": "LTS"
}
{
"error": 400,
"detail": "(This is just an example, the exception may not be related to this endpoint) No provider AWS exists.",
"reason": "Bad Request",
"errorCode": "VALIDATION_ERROR"
}
{
"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": 402,
"detail": "(This is just an example, the exception may not be related to this endpoint)",
"reason": "Payment Required",
"errorCode": "NO_PAYMENT_INFORMATION_FOUND"
}
{
"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": 409,
"detail": "(This is just an example, the exception may not be related to this endpoint) Cannot delete organization link while there is active migration in following project ids: 60c4fd418ebe251047c50554",
"reason": "Conflict",
"errorCode": "CANNOT_DELETE_ORG_ACTIVE_LIVE_MIGRATION_ATLAS_ORG_LINK"
}
{
"error": 500,
"detail": "(This is just an example, the exception may not be related to this endpoint)",
"reason": "Internal Server Error",
"errorCode": "UNEXPECTED_ERROR"
}