[metadata]
description: Creates one cluster in the specified project. Clusters contain a group of hosts that maintain the same data set. This resource can create clusters with asymmetrically-sized shar...
og:description: Creates one cluster in the specified project. Clusters contain a group of hosts that maintain the same data set. This resource can create clusters with asymmetrically-sized shar...
og:image: https://bump.sh/rails/active_storage/representations/redirect/eyJfcmFpbHMiOnsiZGF0YSI6IjIyOWQxZWM5LTkxNmYtNGIwYS05Mjk4LTFiN2Y3MmY3MjU5OCIsInB1ciI6ImJsb2JfaWQifX0=--5902a8b23b49f87570f7d00133eb6ea4427f5b3c/eyJfcmFpbHMiOnsiZGF0YSI6eyJmb3JtYXQiOiJwbmciLCJyZXNpemVfYW5kX3BhZCI6WzEyMDAsNjI3XX0sInB1ciI6InZhcmlhdGlvbiJ9fQ==--1aa381eb604f1a5e97e735d88705b44779772394/meta_generic.png
og:title: Create One Cluster in One Project | Atlas Admin API v2 documentation
og:type: article
og:url: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster
theme-color: #ffffff
twitter:card: summary_large_image
twitter:creator: @bump_hq
twitter:description: Creates one cluster in the specified project. Clusters contain a group of hosts that maintain the same data set. This resource can create clusters with asymmetrically-sized shar...
twitter:image: https://bump.sh/rails/active_storage/representations/redirect/eyJfcmFpbHMiOnsiZGF0YSI6IjIyOWQxZWM5LTkxNmYtNGIwYS05Mjk4LTFiN2Y3MmY3MjU5OCIsInB1ciI6ImJsb2JfaWQifX0=--5902a8b23b49f87570f7d00133eb6ea4427f5b3c/eyJfcmFpbHMiOnsiZGF0YSI6eyJmb3JtYXQiOiJwbmciLCJyZXNpemVfYW5kX3BhZCI6WzEyMDAsNjI3XX0sInB1ciI6InZhcmlhdGlvbiJ9fQ==--1aa381eb604f1a5e97e735d88705b44779772394/meta_generic.png
twitter:title: Create One Cluster in One Project | Atlas Admin API v2 documentation
viewport: width=device-width, initial-scale=1, shrink-to-fit=no

[canonical-links]
https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster

[document-links]
(Deprecated) Atlas Admin API v1: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v1
(Deprecated) MongoDB Atlas Data API v1: https://www.mongodb.com/docs/api/doc/atlas-data-api-v1
/docs/api/doc/atlas-admin-api-v2
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-acceptdatarisksandforcereplicasetreconfig
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-adaptivecapacity
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-customopensslcipherconfigtls12
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-customopensslcipherconfigtls13
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-minimumenabledtlsprotocol
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-tlscipherconfigmode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-backupenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-biconnector
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-biconnector-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-biconnector-readpreference
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-clustertype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-configservermanagementmode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-configservertype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-awsprivatelink
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-awsprivatelinksrv
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-private
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-connectionstring
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-endpoints
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-endpoints-endpointid
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-endpoints-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-endpoints-region
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-srvconnectionstring
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-srvshardoptimizedconnectionstring
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privateendpoint-type
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-privatesrv
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-standard
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-connectionstrings-standardsrv
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-createdate
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-diskwarmingmode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-id
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-analyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-analyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveelectablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveelectablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveelectablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveelectablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveelectablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveelectablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectiveelectablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectivereadonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-readonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-readonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-readonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-readonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-readonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-readonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azure-object-readonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveanalyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveanalyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveanalyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveanalyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveanalyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveanalyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveanalyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveelectablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveelectablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveelectablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveelectablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveelectablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveelectablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectiveelectablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectivereadonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectivereadonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectivereadonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectivereadonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectivereadonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectivereadonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-effectivereadonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-analyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveelectablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-readonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-readonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-readonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-readonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-readonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-readonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcp-object-readonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-gcphardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-readonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-readonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-readonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-readonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-readonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-readonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-readonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-backingprovidername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-electablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-electablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-electablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-electablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-electablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-electablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-electablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-regionname
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-effectiveinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-zoneid
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-effectivereplicationspecs-zonename
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-encryptionatrestprovider
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-featurecompatibilityversion
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-featurecompatibilityversionexpirationdate
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-globalclusterselfmanagedsharding
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-groupid
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-id
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-internalclusterrole
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-labels
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-labels-key
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-labels-value
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-links
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-links-href
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-links-rel
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbemployeeaccessgrant
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbemployeeaccessgrant-expirationtime
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbemployeeaccessgrant-granttype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbemployeeaccessgrant-links
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbemployeeaccessgrant-links-href
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbemployeeaccessgrant-links-rel
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbmajorversion
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-mongodbversion
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-name
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-paused
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-pitenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-redactclientlogdata
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicasetscalingstrategy
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-id
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-azurehardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveanalyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveelectablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveelectablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveelectablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveelectablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveelectablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveelectablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectiveelectablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectivereadonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-effectivereadonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-gcphardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-readonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-readonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-readonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-readonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-readonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-readonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-readonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azurehardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveanalyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveanalyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveanalyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveanalyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveanalyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveanalyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveanalyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveelectablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveelectablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveelectablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveelectablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveelectablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveelectablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectiveelectablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectivereadonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectivereadonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectivereadonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectivereadonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectivereadonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectivereadonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-effectivereadonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute-maxinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute-mininstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-azurehardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveanalyticsspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveelectablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectiveelectablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-effectivereadonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-gcphardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-readonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-readonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-readonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-readonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-readonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-readonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-readonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-analyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-analyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-analyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectiveanalyticsspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectiveanalyticsspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectiveanalyticsspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectiveelectablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectiveelectablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectiveelectablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectivereadonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectivereadonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-effectivereadonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-readonlyspecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-readonlyspecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcphardwarespec20240805-readonlyspecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-readonlyspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-readonlyspecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-readonlyspecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-readonlyspecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-readonlyspecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-readonlyspecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-readonlyspecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-backingprovidername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-diskthroughput
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-regionname
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-effectiveinstancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-zoneid
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-replicationspecs-zonename
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-retainbackups
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-rootcerttype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-statename
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-tags
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-tags-key
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-tags-value
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-terminationprotectionenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-useawstimebasedsnapshotcopyforfastinitialsync
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-body-application-vnd-atlas-2024-10-23-json-versionreleasesystem
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-ratelimit-limit
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-201-ratelimit-remaining
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-400-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-401-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-402-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-403-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-404-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-409-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-ratelimit-limit
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-ratelimit-remaining
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-429-retry-after
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-badrequestdetail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-badrequestdetail-fields
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-badrequestdetail-fields-description
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-badrequestdetail-fields-field
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-detail
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-error
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-errorcode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-parameters
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-500-body-application-json-reason
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-acceptdatarisksandforcereplicasetreconfig
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-adaptivecapacity
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-customopensslcipherconfigtls12
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-customopensslcipherconfigtls13
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-minimumenabledtlsprotocol
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-advancedconfiguration-tlscipherconfigmode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-backupenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-biconnector
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-biconnector-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-biconnector-readpreference
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-clustertype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-configservermanagementmode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-diskwarmingmode
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-encryptionatrestprovider
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-globalclusterselfmanagedsharding
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-labels
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-labels-key
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-labels-value
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-mongodbmajorversion
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-name
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-paused
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-pitenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-redactclientlogdata
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicasetscalingstrategy
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-azure-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-analyticsautoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-compute-scaledownenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-diskgb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-autoscaling-diskgb-enabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-gcp-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-azurehardwarespec20240805-electablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-backingprovidername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-diskiops
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-ebsvolumetype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-electablespecs-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-gcphardwarespec20240805-electablespecs-object-nodecount
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-priority
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-providername
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-regionname
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-disksizegb
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-regionconfigs-tenant-object-tenanthardwarespec20240805-electablespecs-object-instancesize
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-replicationspecs-zonename
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-retainbackups
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-rootcerttype
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-tags
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-tags-key
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-tags-value
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-terminationprotectionenabled
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-useawstimebasedsnapshotcopyforfastinitialsync
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-body-application-vnd-atlas-2024-10-23-json-versionreleasesystem
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-envelope
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-groupid
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-headers
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-path
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-pretty
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-query
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-responses
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-use-effective-fields-replication-specs
/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster#operation-creategroupcluster-use-effective-instance-fields
2023-01-01: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2023-01-01
2023-02-01: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2023-02-01
2023-10-01: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2023-10-01
2023-11-15: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2023-11-15
2024-05-30: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-05-30
2024-08-05: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-08-05
2024-10-23: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-10-23
2024-11-13: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2024-11-13
2025-02-19: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2025-02-19
2025-03-12: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/2025-03-12
ACID Transactions: https://www.mongodb.com/resources/basics/databases/acid-transactions
AI Model API Keys: /docs/api/doc/atlas-admin-api-v2/group/endpoint-ai-model-api-keys
AI Model Rate Limits: /docs/api/doc/atlas-admin-api-v2/group/endpoint-ai-model-rate-limits
API Changelog: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/changelog/
AWS Clusters DNS: /docs/api/doc/atlas-admin-api-v2/group/endpoint-aws-clusters-dns
Accept One Incoming VPC Peering Connection POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-acceptgroupstreamvpcpeeringconnection
Access Tracking: /docs/api/doc/atlas-admin-api-v2/group/endpoint-access-tracking
Acknowledge One Alert from One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-acknowledgegroupalert
Activity Feed: /docs/api/doc/atlas-admin-api-v2/group/endpoint-activity-feed
Add Access List Entries for One Organization Service Account POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgserviceaccountaccesslist
Add Access List Entries for One Project Service Account POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupserviceaccountaccesslist
Add Entries to Project IP Access List POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupaccesslistentry
Add Multiple Teams to One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addgroupteams
Add One Custom Zone Mapping to One Global Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusterglobalwritecustomzonemapping
Add One MongoDB Cloud User to One Organization POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorguser
Add One MongoDB Cloud User to One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addgroupaccessuser
Add One MongoDB Cloud User to One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addgroupusers
Add One MongoDB Cloud User to One Team POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addorgteamuser
Add One Organization Role to One MongoDB Cloud User POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addorguserrole
Add One Project Role to One MongoDB Cloud User POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addgroupuserrole
Add Pinned Namespaces PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclustercollstatpinnednamespaces
Agent Memory: https://www.mongodb.com/resources/basics/artificial-intelligence/agent-memory
Alert Configurations: /docs/api/doc/atlas-admin-api-v2/group/endpoint-alert-configurations
Alerts: /docs/api/doc/atlas-admin-api-v2/group/endpoint-alerts
Artificial Intelligence: https://www.mongodb.com/solutions/use-cases/artificial-intelligence
Assign MongoDB Cloud Users in One Organization to One Team POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addorgteamusers
Assign One Organization API Key to One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-addgroupapikey
Assign One Service Account to One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-invitegroupserviceaccount
Atlas Admin API v2: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2
Atlas Build and scale with an AI-ready platform: https://www.mongodb.com/products/platform
Atlas Embedding and Reranking API: https://www.mongodb.com/docs/api/doc/atlas-embedding-and-reranking-api
Atlas Search: /docs/api/doc/atlas-admin-api-v2/group/endpoint-atlas-search
Atlas Status: https://status.mongodb.com/
Auditing: /docs/api/doc/atlas-admin-api-v2/group/endpoint-auditing
Authentications: /docs/api/doc/atlas-admin-api-v2/authentication
Authorize One Cloud Provider Access Role PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-authorizegroupcloudprovideraccessrole
Available MongoDB Versions in ...: https://www.mongodb.com/docs/atlas/reference/faq/database/#which-versions-of-mongodb-do-service-clusters-use-
Back to Atlas Docs: https://www.mongodb.com/docs/atlas/
Back to hub page: https://www.mongodb.com/docs/api/
Blog Read articles and announcements: https://www.mongodb.com/company/blog
Books Read books and e-books about MongoDB: https://www.mongodb.com/books
Cancel One Restore Job for One Cluster DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-cancelgroupclusterbackuprestorejob
Careers Start your next adventure: https://www.mongodb.com/company/careers
Careers: https://www.mongodb.com/company/careers
Cloud Backups: /docs/api/doc/atlas-admin-api-v2/group/endpoint-cloud-backups
Cloud Backups: https://docs.atlas.mongodb.com/backup/cloud-backup/overview/
Cloud Migration Service: /docs/api/doc/atlas-admin-api-v2/group/endpoint-cloud-migration-service
Cloud Provider Access: /docs/api/doc/atlas-admin-api-v2/group/endpoint-cloud-provider-access
Cluster Outage Simulation: /docs/api/doc/atlas-admin-api-v2/group/endpoint-cluster-outage-simulation
Clusters: /docs/api/doc/atlas-admin-api-v2/group/endpoint-clusters
Collection Level Metrics: /docs/api/doc/atlas-admin-api-v2/group/endpoint-collection-level-metrics
Community Edition Develop locally with MongoDB: https://www.mongodb.com/products/self-managed/community-edition
Community Edition: https://www.mongodb.com/try/download/community
Community Join a community of developers: https://www.mongodb.com/community
Company Learn more about who we are: https://www.mongodb.com/company
Compass Work with MongoDB data in a GUI: https://www.mongodb.com/products/tools/compass
Configure One Query Limit for One Federated Database Instance PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-setgroupdatafederationlimit
Connect with an expert: https://www.mongodb.com/company/contact
Connection String URI Format: https://docs.mongodb.com/manual/reference/connection-string/
Connection string URI format.: https://docs.mongodb.com/manual/reference/connection-string/
Contact Us: https://www.mongodb.com/company/contact
Continuous Cloud Backups: https://docs.atlas.mongodb.com/backup/cloud-backup/overview/
Create Flex Cluster API: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Flex-Clusters/operation/createFlexCluster
Create Flex Cluster: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Flex-Clusters/operation/createFlexCluster
Create Invitation for One MongoDB Cloud User in One Organization POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorginvite
Create Invitation for One MongoDB Cloud User in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupinvite
Create New AI Model API Key POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupaimodelapikey
Create One Access List Entry for One Organization API Key POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgapikeyaccesslistentry
Create One Alert Configuration in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupalertconfig
Create One Atlas Resource Policy POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgresourcepolicy
Create One Atlas Search Index POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusterftsindex
Create One Atlas Search Index POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclustersearchindex
Create One Cloud Provider Access Role POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcloudprovideraccess
Create One Cluster in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster
Create One Collection Restore Job POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclustercollectionrestorejob
Create One Cost Explorer Query Process POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgbillingcostexplorerusageprocess
Create One Custom Role POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcustomdbrolerole
Create One Database User in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupdatabaseuser
Create One Failover Stream Connection POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupstreamconnectionfailoverconnection
Create One Federated Database Instance and Online Archive Private Endpoint for One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupprivatenetworksettingendpointid
Create One Federated Database Instance in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupdatafederation
Create One Flex Cluster in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupflexcluster
Create One Identity Provider POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createfederationsettingidentityprovider
Create One Invoice Report POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorginvoicereport
Create One Legacy Backup Restore Job POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusterrestorejob
Create One Link-Token POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorglivemigrationlinktoken
Create One Log Integration POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategrouplogintegration
Create One MCP Configuration for One Organization POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgmcpconfig
Create One MCP Configuration for One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupmcpconfig
Create One Managed Namespace in One Global Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusterglobalwritemanagednamespace
Create One Metric Integration POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupmetricintegration
Create One Migration for One Local Managed Cluster to MongoDB Atlas POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategrouplivemigration
Create One MongoDB Cloud User POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createuser
Create One Network Peering Connection POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategrouppeer
Create One Network Peering Container POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcontainer
Create One Object Storage Private Endpoint for Cloud Backups for One Cloud Provider in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupbackupprivateendpoint
Create One Online Archive POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusteronlinearchive
Create One Organization API Key POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgapikey
Create One Organization POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorg
Create One Organization Service Account POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgserviceaccount
Create One Organization Service Account Secret POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgserviceaccountsecret
Create One Private Endpoint Service for One Provider POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupprivateendpointendpointservice
Create One Private Endpoint for Encryption at Rest Using Customer Key Management for One Cloud Provider in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupencryptionatrestprivateendpoint
Create One Private Endpoint for One Provider POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupprivateendpointendpointserviceendpoint
Create One Private Endpoint for One Serverless Instance POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupprivateendpointserverlessinstanceendpoint
Create One Private Link Connection POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupstreamprivatelinkconnection
Create One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroup
Create One Project Service Account POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupserviceaccount
Create One Project Service Account Secret POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupserviceaccountsecret
Create One Push-Based Log Export Configuration in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategrouppushbasedlogexport
Create One Restore Job for One Flex Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupflexclusterbackuprestorejob
Create One Restore Job for One Serverless Instance POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupserverlessbackuprestorejob
Create One Restore Job of One Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusterbackuprestorejob
Create One Role Mapping in One Organization Configuration POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createfederationsettingconnectedorgconfigrolemapping
Create One Rolling Index POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusterindexrollingindex
Create One Secret for One Organization MCP Configuration POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgmcpconfigsecret
Create One Secret for One Project MCP Configuration POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupmcpconfigsecret
Create One Snapshot Export Bucket POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupbackupexportbucket
Create One Snapshot Export Job POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclusterbackupexport
Create One Stream Connection POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupstreamconnection
Create One Stream Processor POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupstreamprocessor
Create One Stream Workspace POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupstreamworkspace
Create One Stream Workspace with Sample Connections POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-withgroupstreamsampleconnections
Create One Team in One Organization POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-createorgteam
Create One Third-Party Service Integration POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupintegration
Create One X.509 Certificate for One Database User POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupdatabaseusercert
Create Search Nodes POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupclustersearchdeployment
Create and Assign One Organization API Key to One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupapikey
Creating a Global Cluster: https://dochub.mongodb.org/core/global-cluster-management
Custom Database Roles: /docs/api/doc/atlas-admin-api-v2/group/endpoint-custom-database-roles
Customer Portal: https://support.mongodb.com/
Customer Support: https://www.mongodb.com/services/support
Customize Storage: https://dochub.mongodb.org/core/customize-storage
Cut Over One Migrated Cluster PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-cutovergrouplivemigration
Data Federation: /docs/api/doc/atlas-admin-api-v2/group/endpoint-data-federation
Database Deploy a multi-cloud database: https://www.mongodb.com/products/platform/atlas-database
Database Users: /docs/api/doc/atlas-admin-api-v2/group/endpoint-database-users
Deauthorize One Cloud Provider Access Role DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deauthorizegroupcloudprovideraccessrole
Defer One Maintenance Window for One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-defergroupmaintenancewindow
Delete Existing AI Model API Key DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupaimodelapikey
Delete One Atlas Resource Policy DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgresourcepolicy
Delete One Federation Settings Instance DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletefederationsetting
Delete One Identity Provider DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletefederationsettingidentityprovider
Delete One MCP Configuration for One Organization DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgmcpconfig
Delete One MCP Configuration for One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupmcpconfig
Delete One Object Storage Private Endpoint for Cloud Backups for One Cloud Provider from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupbackupprivateendpoint
Delete One Organization Service Account DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgserviceaccount
Delete One Organization Service Account Secret DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgserviceaccountsecret
Delete One Private Endpoint for Encryption at Rest Using Customer Key Management for One Cloud Provider from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-requestgroupencryptionatrestprivateendpointdeletion
Delete One Private Link Connection DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupstreamprivatelinkconnection
Delete One Project Service Account Secret DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupserviceaccountsecret
Delete One Query Limit for One Federated Database Instance DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupdatafederationlimit
Delete One Secret for One Organization MCP Configuration DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgmcpconfigsecret
Delete One Secret for One Project MCP Configuration DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupmcpconfigsecret
Delete One Snapshot Export Bucket DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupbackupexportbucket
Delete One Stream Connection DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupstreamconnection
Delete One Stream Failover Connection DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupstreamconnectionfailoverconnection
Delete One Stream Processor DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupstreamprocessor
Delete One Stream Workspace DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupstreamworkspace
Delete One VPC Peering Connection DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupstreamvpcpeeringconnection
Delete Search Nodes DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclustersearchdeployment
Digest auth: /docs/api/doc/atlas-admin-api-v2/authentication#doc-authentication-digest-auth
Disable Backup Compliance Policy Settings DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-disablegroupbackupcompliancepolicy
Disable Connect via Peering-Only Mode for One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-disablegroupprivateipmodepeering
Disable Customer-Managed X.509 DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-disablegroupusersecuritycustomerx509
Disable Managed Slow Operation Threshold DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-disablegroupmanagedslowms
Disable Push-Based Log Export for One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegrouppushbasedlogexport
Document Databases: https://www.mongodb.com/resources/basics/databases/document-databases
Documentation General Information Documentation Community Forums Blog University: https://mongodb.com/docs/site-search/
Documentation Learn how to build with MongoDB and get started today: https://www.mongodb.com/docs/
Download Audit Logs for One Atlas Stream Processing Workspace GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-downloadgroupstreamauditlogs
Download Logs for One Cluster Host in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-downloadgroupclusterlog
Download One Flex Cluster Snapshot POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-downloadgroupflexclusterbackup
Download Online Archive Query Logs GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-downloadgroupclusteronlinearchivequerylogs
Download Operational Logs for One Atlas Stream Processing Workspace GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-downloadgroupstreamoperationallogs
Download Query Logs for One Federated Database Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-downloadgroupdatafederationquerylogs
Download: https://www.mongodb.com/try/download/community
Download: https://www.mongodb.com/try/download/enterprise
Edge and Mobile: https://www.mongodb.com/solutions/use-cases/edge-and-mobile
Enable Managed Slow Operation Threshold POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-enablegroupmanagedslowms
Encryption at Rest using Custo...: https://www.mongodb.com/docs/atlas/security-kms-encryption/
Encryption at Rest using Customer Key Management: /docs/api/doc/atlas-admin-api-v2/group/endpoint-encryption-at-rest-using-customer-key-management
End One Outage Simulation DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-endgroupclusteroutagesimulation
English: https://mongodb.com
Enterprise Advanced Run and manage MongoDB yourself: https://www.mongodb.com/products/self-managed/enterprise-advanced
Enterprise Advanced: https://www.mongodb.com/try/download/enterprise
Español: https://mongodb.com/es
Events and Webinars Find an event or webinar near you: https://www.mongodb.com/events
Events: /docs/api/doc/atlas-admin-api-v2/group/endpoint-events
External documentation: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
Federated Authentication: /docs/api/doc/atlas-admin-api-v2/group/endpoint-federated-authentication
Financial Services: https://www.mongodb.com/solutions/industries/financial-services
Flex Clusters: /docs/api/doc/atlas-admin-api-v2/group/endpoint-flex-clusters
Flex Restore Jobs: /docs/api/doc/atlas-admin-api-v2/group/endpoint-flex-restore-jobs
Flex Snapshots: /docs/api/doc/atlas-admin-api-v2/group/endpoint-flex-snapshots
Follow Us: https://www.mongodb.com/company/contact/social-media-hub
Gaming: https://www.mongodb.com/solutions/use-cases/gaming
Get Started: https://www.mongodb.com/cloud/atlas/register
GitHub: https://github.com/mongodb
Global Clusters: /docs/api/doc/atlas-admin-api-v2/group/endpoint-global-clusters
Grant MongoDB Employee Cluster Access for One Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-grantgroupclustermongodbemployeeaccess
Healthcare: https://www.mongodb.com/solutions/industries/healthcare
Integrations Integrations with third-party services: https://cloud.mongodb.com/ecosystem?filter=integration
Intelligent Search: https://www.mongodb.com/solutions/use-cases/intelligent-search
Introduction: /docs/api/doc/atlas-admin-api-v2
Investor Relations: https://investors.mongodb.com
Invoices: /docs/api/doc/atlas-admin-api-v2/group/endpoint-invoices
JSON OpenAPI specification: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2.json
LDAP Configuration: /docs/api/doc/atlas-admin-api-v2/group/endpoint-ldap-configuration
Leadership Meet our executive team: https://www.mongodb.com/company/leadership
Learn more: https://investors.mongodb.com/
Learn more: https://www.mongodb.com/solutions/startups
Learn more: https://www.mongodb.com/solutions/use-cases/modernize
Legacy Backup: /docs/api/doc/atlas-admin-api-v2/group/endpoint-legacy-backup
Legal: https://www.mongodb.com/legal
Load Sample Dataset into One Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-requestgroupsampledatasetload
Log Redaction: https://www.mongodb.com/docs/manual/administration/monitoring/#log-redaction
MEAN Stack: https://www.mongodb.com/resources/languages/mean-stack
MERN Stack: https://www.mongodb.com/resources/languages/mern-stack
Maintenance Windows: /docs/api/doc/atlas-admin-api-v2/group/endpoint-maintenance-windows
Manufacturing: https://www.mongodb.com/solutions/industries/manufacturing
Metric Integrations: /docs/api/doc/atlas-admin-api-v2/group/endpoint-metric-integrations
Migrate One Project to Another Organization POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-migrategroup
Modernization: https://www.mongodb.com/solutions/use-cases/modernize
Modify the Replica Set Scaling...: https://dochub.mongodb.org/core/scale-nodes
MongoDB 8.0 Our fastest version ever: https://www.mongodb.com/products/updates/version-release
MongoDB Atlas App Services Admin API 3.0: https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3
MongoDB Atlas Status API: https://www.mongodb.com/docs/api/doc/cloud-status
MongoDB Atlas: https://www.mongodb.com/cloud/atlas/register
MongoDB Cloud Users: /docs/api/doc/atlas-admin-api-v2/group/endpoint-mongodb-cloud-users
MongoDB Connector for Business...: https://docs.mongodb.com/bi-connector/current/
MongoDB Relational Migrator REST API: https://www.mongodb.com/docs/api/doc/mongodb-relational-migrator-rest-api
MongoDB Sharded Cluster Config...: https://dochub.mongodb.org/docs/manual/core/sharded-cluster-config-servers
MongoDB for Educators Take advantage of educator resources: https://www.mongodb.com/academia
MongoDB for Students Take advantage of student benefits: https://www.mongodb.com/students
Monitoring and Logs: /docs/api/doc/atlas-admin-api-v2/group/endpoint-monitoring-and-logs
Network Peering Connection: https://docs.atlas.mongodb.com/security-vpc-peering/#std-label-vpc-peering/
Network Peering: /docs/api/doc/atlas-admin-api-v2/group/endpoint-network-peering
Newsroom Read press releases and news stories: https://www.mongodb.com/company/newsroom
NoSQL Databases: https://www.mongodb.com/resources/basics/databases/nosql-explained
Online Archive: /docs/api/doc/atlas-admin-api-v2/group/endpoint-online-archive
Organizations: /docs/api/doc/atlas-admin-api-v2/group/endpoint-organizations
Partners Learn about our partner ecosystem: https://www.mongodb.com/company/partners
Payments: https://www.mongodb.com/solutions/use-cases/payments
Performance Advisor: /docs/api/doc/atlas-admin-api-v2/group/endpoint-performance-advisor
Pin Feature Compatibility Version for One Cluster in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-pingroupclusterfeaturecompatibilityversion
Pin Namespaces PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-pingroupclustercollstatpinnednamespaces
Português: https://mongodb.com/pt-br
Powered by Bump.sh: https://bump.sh/?utm_campaign=powered+by&utm_content=%2Fmongodb%2Fhub%2Fapi%2Fdoc%2Fatlas-admin-api-v2&utm_medium=referral&utm_source=documentation
Prettyprint: https://en.wikipedia.org/wiki/Prettyprint
Pricing: https://www.mongodb.com/pricing
Privacy Policy: https://www.mongodb.com/legal/privacy/privacy-policy
Private Endpoint Services: /docs/api/doc/atlas-admin-api-v2/group/endpoint-private-endpoint-services
Private Endpoint for Dedicated...: https://docs.atlas.mongodb.com/security-private-endpoint/
Product Updates: https://www.mongodb.com/products/updates/
Programmatic API Keys: /docs/api/doc/atlas-admin-api-v2/group/endpoint-programmatic-api-keys
Programmatic API Keys: https://www.mongodb.com/docs/atlas/customize-storage/#extend-iops-on-azure
Project IP Access List: /docs/api/doc/atlas-admin-api-v2/group/endpoint-project-ip-access-list
Projects: /docs/api/doc/atlas-admin-api-v2/group/endpoint-projects
Public Sector: https://www.mongodb.com/solutions/industries/public-sector
Push-Based Log Export: /docs/api/doc/atlas-admin-api-v2/group/endpoint-push-based-log-export
Query Shape Insights: /docs/api/doc/atlas-admin-api-v2/group/endpoint-query-shape-insights
RAG Database: https://www.mongodb.com/resources/basics/artificial-intelligence/retrieval-augmented-generation
Rate Limiting: /docs/api/doc/atlas-admin-api-v2/group/endpoint-rate-limiting
Rate Limiting: /docs/api/doc/atlas-admin-api-v2/topic/topic-rate-limiting
Read preferences for BI Connector: https://docs.atlas.mongodb.com/cluster-config/enable-bic/#std-label-bic-read-preferences
Reconfiguring a Replica Set du...: https://dochub.mongodb.org/core/regional-outage-reconfigure-replica-set
Reduce Secondary Disk Warming ...: https://docs.atlas.mongodb.com/reference/replica-set-tags/#reduce-secondary-disk-warming-impact
Reject One Incoming VPC Peering Connection POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-rejectgroupstreamvpcpeeringconnection
Relational Migrator Migrate to MongoDB with confidence: https://www.mongodb.com/products/tools/relational-migrator
Remote MCP Configurations: /docs/api/doc/atlas-admin-api-v2/group/endpoint-remote-mcp-configurations
Remove All Cloud Backup Schedules DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclusterbackupschedule
Remove All Custom Zone Mappings from One Global Cluster DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclusterglobalwritecustomzonemapping
Remove LDAP User to DN Mapping DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupusersecurityldapusertodnmapping
Remove One Access List Entry for One Organization API Key DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgapikeyaccesslistentry
Remove One Access List Entry from One Organization Service Account DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgserviceaccountaccesslistentry
Remove One Access List Entry from One Project Service Account DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupserviceaccountaccesslistentry
Remove One Alert Configuration from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupalertconfig
Remove One Atlas Search Index DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclusterftsindex
Remove One Atlas Search Index by ID DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclustersearchindex
Remove One Atlas Search Index by Name DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclustersearchindexbyname
Remove One Cluster from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupcluster
Remove One Custom Role from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupcustomdbrolerole
Remove One Database User from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupdatabaseuser
Remove One Entry from One Project IP Access List DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupaccesslistentry
Remove One Federated Database Instance and Online Archive Private Endpoint from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupprivatenetworksettingendpointid
Remove One Federated Database Instance from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupdatafederation
Remove One Flex Cluster from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupflexcluster
Remove One Invitation from One Organization DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorginvite
Remove One Invitation from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupinvite
Remove One Legacy Backup Snapshot DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclustersnapshot
Remove One Link-Token DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorglivemigrationlinktokens
Remove One Log Integration DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegrouplogintegration
Remove One Managed Namespace from One Global Cluster DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclusterglobalwritemanagednamespaces
Remove One Metric Integration DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupmetricintegration
Remove One MongoDB Cloud User from One Organization DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-removeorguser
Remove One MongoDB Cloud User from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-removegroupuser
Remove One MongoDB Cloud User from One Team DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-removeorgteamuserfromteam
Remove One MongoDB Cloud User from One Team POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-removeorgteamuser
Remove One Network Peering Connection DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegrouppeer
Remove One Network Peering Container DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupcontainer
Remove One Online Archive DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclusteronlinearchive
Remove One Organization API Key DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgapikey
Remove One Organization Configuration from One Federation DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-removefederationsettingconnectedorgconfig
Remove One Organization DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorg
Remove One Organization Role from One MongoDB Cloud User POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-removeorguserrole
Remove One Private Endpoint Service for One Provider DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupprivateendpointendpointservice
Remove One Private Endpoint for One Provider DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupprivateendpointendpointserviceendpoint
Remove One Private Endpoint for One Serverless Instance DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupprivateendpointserverlessinstanceendpoint
Remove One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroup
Remove One Project Limit DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegrouplimit
Remove One Project Role from One MongoDB Cloud User POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-removegroupuserrole
Remove One Project Service Account DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupserviceaccount
Remove One Replica Set Cloud Backup DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclusterbackupsnapshot
Remove One Role Mapping from One Organization DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletefederationsettingconnectedorgconfigrolemapping
Remove One Sharded Cluster Cloud Backup DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupclusterbackupsnapshotshardedcluster
Remove One Team from One Organization DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deleteorgteam
Remove One Team from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-removegroupteam
Remove One Third-Party Service Integration DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-deletegroupintegration
Rename One Team PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-renameorgteam
Reset AI Model Rate Limit for One Model Group POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-resetgroupaimodelapicloudgeographymodelgroupnameratelimits
Reset AI Model Rate Limits for Group POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-resetgroupaimodelapiratelimits
Reset One Maintenance Window for One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-resetgroupmaintenancewindow
Resource Policies: /docs/api/doc/atlas-admin-api-v2/group/endpoint-resource-policies
Resource Tags: https://dochub.mongodb.org/core/add-cluster-tag-atlas
Resources Hub Get help building the next big thing with MongoDB: https://www.mongodb.com/resources
Retail: https://www.mongodb.com/solutions/industries/retail
Return AI Model API Keys for One Group GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupaimodelapikeys
Return AI Model API Keys for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgaimodelapikeys
Return AI Model Rate Limits for One Group GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupaimodelapiratelimits
Return AI Model Rate Limits for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgaimodelapiratelimits
Return Account ID and VPC ID for One Project and Region GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupstreamaccountdetails
Return Advanced Configuration Options for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterprocessargs
Return All Access List Entries for One Organization API Key GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgapikeyaccesslistentries
Return All Access List Entries for One Organization Service Account GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgserviceaccountaccesslist
Return All Access List Entries for One Project Service Account GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupserviceaccountaccesslist
Return All Active Incoming VPC Peering Connections GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupstreamactivevpcpeeringconnections
Return All Active Log Integrations GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgrouplogintegrations
Return All Active Metric Integrations GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupmetricintegrations
Return All Active Third-Party Service Integrations GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupintegrations
Return All Alert Configuration Matchers Field Names GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listalertconfigmatcherfieldnames
Return All Alert Configurations Set for One Alert GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupalertalertconfigs
Return All Alert Configurations in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupalertconfigs
Return All Alerts from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupalerts
Return All Atlas Resource Policies GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgresourcepolicies
Return All Atlas Search Index Metrics for One Namespace GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgrouphostftsmetricindexmeasurements
Return All Atlas Search Indexes for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclustersearchindexes
Return All Atlas Search Indexes for One Collection GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterftsindex
Return All Atlas Search Indexes for One Collection GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclustersearchindex
Return All Atlas Search Metric Types for One Process GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgrouphostftsmetrics
Return All Authorized Clusters in All Projects GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listclusterdetails
Return All Available MongoDB LTS Versions for Clusters in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupmongodbversions
Return All Cloud Provider Access Roles GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupcloudprovideraccess
Return All Cloud Provider Regions GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterproviderregions
Return All Clusters in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusters
Return All Collection Restore Jobs for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclustercollectionrestorejobs
Return All Collection States for One Collection Restore Job GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclustercollectionrestorejobcollections
Return All Connections of the Stream Workspaces GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupstreamconnections
Return All Control Plane IP Addresses GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listcontrolplaneipaddresses
Return All Custom Roles in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupcustomdbroleroles
Return All Database Users in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupdatabaseusers
Return All Event Types GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listeventtypes
Return All Federated Database Instance and Online Archive Private Endpoints in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprivatenetworksettingendpointids
Return All Federated Database Instances in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupdatafederation
Return All Flex Clusters from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupflexclusters
Return All IP Addresses for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupipaddresses
Return All Identity Providers in One Federation GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listfederationsettingidentityproviders
Return All Invitations in One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorginvites
Return All Invitations in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupinvites
Return All Invoice Reports for One Invoice GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorginvoicereports
Return All Invoices for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorginvoices
Return All Legacy Backup Checkpoints GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterbackupcheckpoints
Return All Legacy Backup Restore Jobs GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterrestorejobs
Return All Legacy Backup Snapshots GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclustersnapshots
Return All Limits for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgrouplimits
Return All Line Items for One Invoice by Invoice ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-searchorginvoicelineitems
Return All MCP Configurations for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgmcpconfigs
Return All MCP Configurations for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupmcpconfigs
Return All Metric Names GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupcollstatmetrics
Return All MongoDB Cloud Users Assigned to One Team GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgteamusers
Return All MongoDB Cloud Users in One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgusers
Return All MongoDB Cloud Users in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupusers
Return All MongoDB Processes in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprocesses
Return All Namespaces for One Host GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprocessperformanceadvisornamespaces
Return All Network Peering Connections in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgrouppeers
Return All Network Peering Containers in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupcontainerall
Return All Network Peering Containers in One Project for One Cloud Provider GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupcontainers
Return All Non-Compliant Resources GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgnoncompliantresources
Return All Online Archives for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusteronlinearchives
Return All Open Alerts for One Alert Configuration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupalertconfigalerts
Return All Organization API Keys Assigned to One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupapikeys
Return All Organization API Keys GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgapikeys
Return All Organization Configurations from One Federation GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listfederationsettingconnectedorgconfigs
Return All Organization Service Accounts GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgserviceaccounts
Return All Organizations GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgs
Return All Pending Invoices for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorginvoicepending
Return All Private Endpoint Services for One Provider GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprivateendpointendpointservice
Return All Private Endpoints for One Serverless Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprivateendpointserverlessinstanceendpoint
Return All Private Link Connections GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupstreamprivatelinkconnections
Return All Project IP Access List Entries GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupaccesslistentries
Return All Project Service Accounts GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupserviceaccounts
Return All Projects Available for Migration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorglivemigrationavailableprojects
Return All Projects GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroups
Return All Projects in One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorggroups
Return All Query Limits for One Federated Database Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupdatafederationlimits
Return All Query Shapes GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterqueryshapes
Return All Rate Limits GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listratelimits
Return All Replica Set Cloud Backups GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterbackupsnapshots
Return All Restore Jobs for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterbackuprestorejobs
Return All Restore Jobs for One Flex Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupflexclusterbackuprestorejobs
Return All Restore Jobs for One Serverless Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupserverlessbackuprestorejobs
Return All Role Mappings from One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listfederationsettingconnectedorgconfigrolemappings
Return All Search Nodes GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustersearchdeployment
Return All Secrets for One Organization MCP Configuration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgmcpconfigsecrets
Return All Secrets for One Project MCP Configuration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupmcpconfigsecrets
Return All Serverless Instances in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupserverlessinstances
Return All Service Account Project Assignments GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgserviceaccountgroups
Return All Sharded Cluster Cloud Backups GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterbackupsnapshotshardedclusters
Return All Snapshot Export Buckets GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupbackupexportbuckets
Return All Snapshot Export Jobs GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterbackupexports
Return All Snapshots for One Flex Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupflexclusterbackupsnapshots
Return All Snapshots of One Serverless Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupserverlessbackupsnapshots
Return All Stock Keeping Units GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listskus
Return All Stream Failover Connections GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupstreamconnectionfailoverconnections
Return All Stream Processors in One Stream Workspace GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupstreamprocessors
Return All Stream Workspaces in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupstreamworkspaces
Return All Suggested Indexes GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterperformanceadvisorsuggestedindexes
Return All Suggested Indexes GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprocessperformanceadvisorsuggestedindexes
Return All Suggested Indexes to Drop GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterperformanceadvisordropindexsuggestions
Return All Teams in One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgteams
Return All Teams in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupteams
Return All VPC Peering Connections GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupstreamvpcpeeringconnections
Return All X.509 Certificates Assigned to One Database User GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupdatabaseusercerts
Return Associated Invoices GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgassociatedinvoices
Return Atlas Search Hardware and Status Metrics GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgrouphostftsmetricmeasurements
Return Atlas Search Metrics for One Index in One Namespace GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgrouphostftsmetricindexmeasurements
Return Auditing Configuration for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupauditlog
Return Auto Scaling Configuration for One Sharded Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-autogroupclusterscalingconfiguration
Return Available Databases for One MongoDB Process GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprocessdatabases
Return Available Disks for One MongoDB Process GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprocessdisks
Return Backup Compliance Policy Settings GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupbackupcompliancepolicy
Return Cluster-Level Query Latency GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclustercollstatmeasurements
Return Collections in One Database in One Snapshot GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterbackupsnapshotdatabasecollections
Return Database Access History for One Cluster by Cluster Name GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupdbaccesshistorycluster
Return Database Access History for One Cluster by Hostname GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupdbaccesshistoryprocess
Return Databases in One Snapshot GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterbackupsnapshotdatabases
Return Delegation Settings for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgdelegationsettings
Return Events from One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listorgevents
Return Events from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupevents
Return Federation Settings for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgfederationsettings
Return Host-Level Query Latency GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprocesscollstatmeasurements
Return LDAP or X.509 Configuration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupusersecurity
Return Managed Slow Operation Threshold Status GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupmanagedslowms
Return Measurements for One Database in One MongoDB Process GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprocessdatabasemeasurements
Return Measurements for One Disk GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprocessdisk
Return Measurements for One MongoDB Process GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprocessmeasurements
Return Measurements of One Disk for One MongoDB Process GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprocessdiskmeasurements
Return Metadata of One Identity Provider GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getfederationsettingidentityprovidermetadata
Return Object Storage Private Endpoints for Cloud Backups for One Cloud Provider in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupbackupprivateendpoints
Return One Access List Entry for One Organization API Key GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgapikeyaccesslistentry
Return One Alert Configuration from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupalertconfig
Return One Alert from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupalert
Return One Atlas Resource Policy GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgresourcepolicy
Return One Atlas Search Index GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterftsindex
Return One Atlas Search Index by ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustersearchindex
Return One Atlas Search Index by Name GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustersearchindexbyname
Return One Cloud Backup Schedule GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackupschedule
Return One Cloud Provider Access Role GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupcloudprovideraccess
Return One Cluster from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupcluster
Return One Collection Restore Job for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustercollectionrestorejob
Return One Collection State for One Collection Restore Job GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustercollectionrestorejobcollection
Return One Collection in One Database in One Snapshot GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackupsnapshotdatabasecollection
Return One Configuration for Encryption at Rest Using Customer-Managed Keys for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupencryptionatrest
Return One Custom DNS Configuration for Atlas Clusters on AWS GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupawscustomdns
Return One Custom Role in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupcustomdbrolerole
Return One Database User from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupdatabaseuser
Return One Database for One MongoDB Process GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprocessdatabase
Return One Database in One Snapshot GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackupsnapshotdatabase
Return One Event from One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgevent
Return One Event from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupevent
Return One Federated Database Instance Query Limit for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupdatafederationlimit
Return One Federated Database Instance and Online Archive Private Endpoint in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprivatenetworksettingendpointid
Return One Federated Database Instance in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupdatafederation
Return One Flex Cluster from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupflexcluster
Return One Identity Provider by ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getfederationsettingidentityprovider
Return One Invitation in One Organization by Invitation ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorginvite
Return One Invitation in One Project by Invitation ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupinvite
Return One Invoice Report GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorginvoicereport
Return One Invoice as CSV for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorginvoicecsv
Return One Invoice for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorginvoice
Return One Legacy Backup Checkpoint GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackupcheckpoint
Return One Legacy Backup Restore Job GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterrestorejob
Return One Legacy Backup Snapshot GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustersnapshot
Return One Limit for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgrouplimit
Return One Log Integration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgrouplogintegration
Return One MCP Configuration for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgmcpconfig
Return One MCP Configuration for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupmcpconfig
Return One Maintenance Window for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupmaintenancewindow
Return One Managed Namespace in One Global Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterglobalwrites
Return One Metric Integration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupmetricintegration
Return One Migration Job GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgrouplivemigration
Return One Migration Validation Job GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgrouplivemigrationvalidatestatus
Return One MongoDB Cloud User by ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getuser
Return One MongoDB Cloud User by Username GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getuserbyname
Return One MongoDB Cloud User in One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorguser
Return One MongoDB Cloud User in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupuser
Return One MongoDB Process by ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprocess
Return One Network Peering Connection in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgrouppeer
Return One Network Peering Container GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupcontainer
Return One Object Storage Private Endpoint for Cloud Backups for One Cloud Provider in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupbackupprivateendpoint
Return One Online Archive GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusteronlinearchive
Return One Organization API Key GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgapikey
Return One Organization Configuration from One Federation GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getfederationsettingconnectedorgconfig
Return One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorg
Return One Organization Service Account GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgserviceaccount
Return One Outage Simulation GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusteroutagesimulation
Return One Private Endpoint Service for One Provider GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprivateendpointendpointservice
Return One Private Endpoint for Encryption at Rest Using Customer Key Management for One Cloud Provider in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupencryptionatrestprivateendpoint
Return One Private Endpoint for One Provider GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprivateendpointendpointserviceendpoint
Return One Private Endpoint for One Serverless Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprivateendpointserverlessinstanceendpoint
Return One Private Link Connection GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupstreamprivatelinkconnection
Return One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroup
Return One Project IP Access List Entry GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupaccesslistentry
Return One Project Service Account GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupserviceaccount
Return One Project by Name GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupbyname
Return One Push-Based Log Export Configuration in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgrouppushbasedlogexport
Return One Query Shape GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterqueryshape
Return One Rate Limit GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getratelimit
Return One Replica Set Cloud Backup GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackupsnapshot
Return One Restore Job for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackuprestorejob
Return One Restore Job for One Flex Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupflexclusterbackuprestorejob
Return One Restore Job for One Serverless Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupserverlessbackuprestorejob
Return One Role Mapping from One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getfederationsettingconnectedorgconfigrolemapping
Return One Secret for One Organization MCP Configuration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgmcpconfigsecret
Return One Secret for One Project MCP Configuration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupmcpconfigsecret
Return One Serverless Instance from One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupserverlessinstance
Return One Sharded Cluster Cloud Backup GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackupsnapshotshardedcluster
Return One Snapshot Export Bucket GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupbackupexportbucket
Return One Snapshot Export Job GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterbackupexport
Return One Snapshot Schedule GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustersnapshotschedule
Return One Snapshot for One Flex Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupflexclusterbackupsnapshot
Return One Snapshot of One Serverless Instance GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupserverlessbackupsnapshot
Return One Stock Keeping Unit GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getsku
Return One Stream Connection GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupstreamconnection
Return One Stream Failover Connection GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupstreamconnectionfailoverconnection
Return One Stream Processor GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupstreamprocessor
Return One Stream Workspace GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupstreamworkspace
Return One Team by ID GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgteam
Return One Team by Name GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgteambyname
Return One Team in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupteam
Return One Third-Party Service Integration GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupintegration
Return Pinned Namespaces GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclustercollstatpinnednamespaces
Return Pre-Filtered Activity Feed Link for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgactivityfeed
Return Pre-Filtered Activity Feed Link for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupactivityfeed
Return Private Endpoints for Encryption at Rest Using Customer Key Management for One Cloud Provider in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupencryptionatrestprivateendpoints
Return Project Settings GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupsettings
Return Query Shape Details GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterqueryshapeinsightdetails
Return Query Statistic Summaries GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterqueryshapeinsightsummaries
Return Ranked Namespaces from One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclustercollstatnamespaces
Return Ranked Namespaces from One Host GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprocesscollstatnamespaces
Return Regionalized Private Endpoint Status GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupprivateendpointregionalmode
Return Schema Advice GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupclusterperformanceadvisorschemaadvice
Return Serverless Auto-Indexing Status GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupserverlessperformanceadvisorautoindexing
Return Settings for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgsettings
Return Single AI Model API Key for One Group GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupaimodelapikey
Return Single AI Model API Key for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgaimodelapikey
Return Single AI Model Rate Limit for One Group GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupaimodelapicloudgeographymodelgroupnameratelimits
Return Single AI Model Rate Limit for One Organization GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgaimodelapicloudgeographymodelgroupnameratelimits
Return Slow Queries GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupprocessperformanceadvisorslowquerylogs
Return Status of All Cluster Operations GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupclusterstatus
Return Status of LDAP Configuration Verification in One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupusersecurityldapverify
Return Status of One Project IP Access List Entry GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupaccessliststatus
Return Status of Sample Dataset Load for One Cluster GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupsampledatasetload
Return Usage Details for One Cost Explorer Query GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getorgbillingcostexplorerusage
Return the Status of This MongoDB Application GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-getsystemstatus
Revoke JWKS from One OIDC Identity Provider DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-revokefederationsettingidentityproviderjwks
Revoke MongoDB Employee Cluster Access for One Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-revokegroupclustermongodbemployeeaccess
Rolling Index: /docs/api/doc/atlas-admin-api-v2/group/endpoint-rolling-index
Root: /docs/api/doc/atlas-admin-api-v2/group/endpoint-root
Search Deliver engaging search experiences: https://www.mongodb.com/products/platform/atlas-search
Security Information: https://www.mongodb.com/company/contact/mongodb-vulnerability-disclosure-policy
See stories: https://www.mongodb.com/solutions/customer-case-studies
Serverless Development: https://www.mongodb.com/solutions/use-cases/serverless
Serverless Instances: /docs/api/doc/atlas-admin-api-v2/group/endpoint-serverless-instances
Serverless Private Endpoints: /docs/api/doc/atlas-admin-api-v2/group/endpoint-serverless-private-endpoints
Service Accounts: /docs/api/doc/atlas-admin-api-v2/group/endpoint-service-accounts
Service accounts: /docs/api/doc/atlas-admin-api-v2/authentication#doc-authentication-service-accounts
Set One Project Limit PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-setgrouplimit
Set Serverless Auto-Indexing Status POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-setgroupserverlessperformanceadvisorautoindexing
Shared Cluster Backups: https://docs.atlas.mongodb.com/backup/shared-tier/overview/
Sign In: https://account.mongodb.com/account/login
Sign Up: https://www.mongodb.com/cloud/atlas/register
Skills and Certifications Develop in-demand skills and earn MongoDB certifications: https://learn.mongodb.com
Solutions Library Organized and tailored solutions to kick-start projects: https://www.mongodb.com/docs/atlas/architecture/current/solutions-library/
Start One Outage Simulation POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-startgroupclusteroutagesimulation
Start One Stream Processor POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-startgroupstreamprocessor
Start One Stream Processor With Options POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-startgroupstreamprocessorwith
Stop One Stream Processor POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-stopgroupstreamprocessor
Stream Processing Integrate MongoDB and Kafka: https://www.mongodb.com/products/platform/atlas-stream-processing
Streams: /docs/api/doc/atlas-admin-api-v2/group/endpoint-streams
Support: https://www.mongodb.com/services/support
Take One On-Demand Snapshot POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-takegroupclusterbackupsnapshots
Teams: /docs/api/doc/atlas-admin-api-v2/group/endpoint-teams
Telecommunications: https://www.mongodb.com/solutions/industries/telecommunications
Test Failover for One Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-restartgroupclusterprimaries
Third-Party Integrations: /docs/api/doc/atlas-admin-api-v2/group/endpoint-third-party-integrations
This option corresponds to the...: https://docs.mongodb.com/upcoming/reference/configuration-options/#mongodb-setting-net.ssl.disabledProtocols
Toggle Automatic Deferral of Maintenance for One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-togglegroupmaintenancewindowautodefer
Toggle Regionalized Private Endpoint Status PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-togglegroupprivateendpointregionalmode
Toggle State of One Alert Configuration in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-togglegroupalertconfig
Trust Center: https://www.mongodb.com/products/platform/trust
Unassign One Organization API Key from One Project DELETE: /docs/api/doc/atlas-admin-api-v2/operation/operation-removegroupapikey
Unpin Feature Compatibility Version for One Cluster in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-unpingroupclusterfeaturecompatibilityversion
Unpin Namespaces PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-unpingroupclustercollstatunpinnamespaces
Update AI Model Rate Limit PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupaimodelapicloudgeographymodelgroupnameratelimits
Update Advanced Configuration Options for One Cluster PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclusterprocessargs
Update Auditing Configuration for One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupauditlog
Update Backup Compliance Policy Settings PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupbackupcompliancepolicy
Update Cloud Backup Schedule for One Cluster PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclusterbackupschedule
Update Delegation Settings for One Organization PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorgdelegationsettings
Update Encryption at Rest Configuration in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupencryptionatrest
Update Existing AI Model API Key PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupaimodelapikey
Update Expiration Date for One Cloud Backup PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclusterbackupsnapshot
Update Expiration Date for One Legacy Backup Snapshot PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclustersnapshot
Update LDAP or X.509 Configuration PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupusersecurity
Update One Alert Configuration in One Project PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupalertconfig
Update One Atlas Resource Policy PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorgresourcepolicy
Update One Atlas Search Index PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclusterftsindex
Update One Atlas Search Index by ID PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclustersearchindex
Update One Atlas Search Index by Name PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclustersearchindexbyname
Update One Cluster in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupcluster
Update One Custom Role in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupcustomdbrolerole
Update One Database User in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupdatabaseuser
Update One Export Bucket Private Networking Settings PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupbackupexportbucket
Update One Federated Database Instance in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupdatafederation
Update One Flex Cluster in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupflexcluster
Update One Identity Provider PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updatefederationsettingidentityprovider
Update One Invitation in One Organization PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorginvites
Update One Invitation in One Organization by Invitation ID PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorginvitebyid
Update One Invitation in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupinvites
Update One Invitation in One Project by Invitation ID PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupinvitebyid
Update One Log Integration PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategrouplogintegration
Update One MCP Configuration for One Organization PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorgmcpconfig
Update One MCP Configuration for One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupmcpconfig
Update One Maintenance Window for One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupmaintenancewindow
Update One Metric Integration PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupmetricintegration
Update One MongoDB Cloud User in One Organization PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorguser
Update One Network Peering Connection PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategrouppeer
Update One Network Peering Container PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupcontainer
Update One Online Archive PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclusteronlinearchive
Update One Organization API Key PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorgapikey
Update One Organization Configuration in One Federation PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updatefederationsettingconnectedorgconfig
Update One Organization PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorg
Update One Organization Service Account PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorgserviceaccount
Update One Private Endpoint Service for One Provider PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupprivateendpointendpointservice
Update One Private Endpoint for One Serverless Instance PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupprivateendpointserverlessinstanceendpoint
Update One Private Link Connection PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupstreamprivatelinkconnection
Update One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroup
Update One Project Service Account PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupserviceaccount
Update One Push-Based Log Export Configuration in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategrouppushbasedlogexport
Update One Role Mapping in One Organization PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updatefederationsettingconnectedorgconfigrolemapping
Update One Stream Connection PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupstreamconnection
Update One Stream Failover Connection PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupstreamconnectionfailoverconnection
Update One Stream Processor PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupstreamprocessor
Update One Stream Workspace PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupstreamworkspace
Update One Third-Party Service Integration PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupintegration
Update Organization API Key Roles for One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupapikeyroles
Update Organization Roles for One MongoDB Cloud User PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorguserroles
Update Project Roles for One MongoDB Cloud User PUT: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupuserroles
Update Project Settings PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupsettings
Update Query Shape Rejection Status PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclusterqueryshape
Update Search Nodes PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclustersearchdeployment
Update Settings for One Organization PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updateorgsettings
Update Snapshot Schedule for One Cluster PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclustersnapshotschedule
Update State of One Custom DNS Configuration for Atlas Clusters on AWS PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-togglegroupawscustomdns
Update Team Roles in One Project PATCH: /docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupteam
Upgrade One Flex Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-tenantgroupflexclusterupgrade
Upgrade One Shared-Tier Cluster POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-upgradegroupclustertenantupgrade
Upgrade One Shared-Tier Cluster to One Serverless Instance POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-upgradegroupclustertenantupgradetoserverless
Validate One Atlas Resource Policy POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-validateorgresourcepolicies
Validate One Cluster Configuration POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-validategroupclusterconfigurations
Validate One Migration Request POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-validategrouplivemigrations
Vector Databases: https://www.mongodb.com/resources/basics/databases/vector-databases
Vector Search Design intelligent apps with gen AI: https://www.mongodb.com/products/platform/atlas-vector-search
Verify Connect via Peering-Only Mode for One Project GET: /docs/api/doc/atlas-admin-api-v2/operation/operation-verifygroupprivateipmode
Verify LDAP Configuration in One Project POST: /docs/api/doc/atlas-admin-api-v2/operation/operation-verifygroupusersecurityldap
View All Products Explore our full developer suite: https://www.mongodb.com/products
View as Markdown: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster.md
Web Linking Specification (RFC...: https://datatracker.ietf.org/doc/html/rfc5988
X.509 Authentication: /docs/api/doc/atlas-admin-api-v2/group/endpoint-x-509-authentication
YAML OpenAPI specification: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2.yaml
enable custom DNS: https://docs.atlas.mongodb.com/reference/api/aws-custom-dns-update/
https://www.mongodb.com
latest default: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2
preview: https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/preview
日本語: https://mongodb.com/ja-jp
简体中文: https://mongodb.com/zh-cn
한국어: https://mongodb.com/ko-kr

[content]
Create One Cluster in One Project | Atlas Admin API v2 documentation
Documentation
General Information
Documentation
Community Forums
Blog
University
Products
Platform
Atlas
Build and scale with an AI-ready platform
Platform Services
Database
Deploy a multi-cloud database
Search
Deliver engaging search experiences
Vector Search
Design intelligent apps with gen AI
Stream Processing
Integrate MongoDB and Kafka
Self Managed
Enterprise Advanced
Run and manage MongoDB yourself
Community Edition
Develop locally with MongoDB
Tools
Compass
Work with MongoDB data in a GUI
Integrations
Integrations with third-party services
Relational Migrator
Migrate to MongoDB with confidence
View All Products
Explore our full developer suite
MongoDB 8.0
Our fastest version ever
Build with MongoDB Atlas
Get started for free in minutes
Sign Up
Test Enterprise Advanced
Develop with MongoDB on-premises
Download
Try Community Edition
Explore the latest version of MongoDB
Download
Resources
Documentation
Learn how to build with MongoDB and get started today
Skills and Certifications
Develop in-demand skills and earn MongoDB certifications
Books
Read books and e-books about MongoDB
MongoDB for Educators
Take advantage of educator resources
MongoDB for Students
Take advantage of student benefits
Community
Join a community of developers
Events and Webinars
Find an event or webinar near you
Resources Hub
Get help building the next big thing with MongoDB
Solutions
Use cases
Artificial Intelligence
Modernization
Payments
Serverless Development
Gaming
Intelligent Search
Edge and Mobile
Industries
Financial Services
Telecommunications
Healthcare
Retail
Public Sector
Manufacturing
Solutions Library
Organized and tailored solutions to kick-start projects
MongoDB AMP
Modernize applications up to 3x faster
Learn more
Startups and AI Innovators
For world-changing ideas and AI pioneers
Learn more
Customer Case Studies
Hear directly from our users
See stories
Company
Careers
Start your next adventure
Blog
Read articles and announcements
Newsroom
Read press releases and news stories
Partners
Learn about our partner ecosystem
Leadership
Meet our executive team
Company
Learn more about who we are
Contact Us
Reach out to MongoDB
Connect with an expert
Investors
Visit our investor portal
Learn more
Pricing
Eng
Support
Sign In
Get Started
Documentation
General Information
Documentation
Community Forums
Blog
University
Products
Platform
Atlas
Build and scale with an AI-ready platform
Platform Services
Database
Deploy a multi-cloud database
Search
Deliver engaging search experiences
Vector Search
Design intelligent apps with gen AI
Stream Processing
Integrate MongoDB and Kafka
Self Managed
Enterprise Advanced
Run and manage MongoDB yourself
Community Edition
Develop locally with MongoDB
Tools
Compass
Work with MongoDB data in a GUI
Integrations
Integrations with third-party services
Relational Migrator
Migrate to MongoDB with confidence
View All Products
Explore our full developer suite
MongoDB 8.0
Our fastest version ever
Build with MongoDB Atlas
Get started for free in minutes
Sign Up
Test Enterprise Advanced
Develop with MongoDB on-premises
Download
Try Community Edition
Explore the latest version of MongoDB
Download
Resources
Documentation
Learn how to build with MongoDB and get started today
Skills and Certifications
Develop in-demand skills and earn MongoDB certifications
Books
Read books and e-books about MongoDB
MongoDB for Educators
Take advantage of educator resources
MongoDB for Students
Take advantage of student benefits
Community
Join a community of developers
Events and Webinars
Find an event or webinar near you
Resources Hub
Get help building the next big thing with MongoDB
Solutions
Use cases
Artificial Intelligence
Modernization
Payments
Serverless Development
Gaming
Intelligent Search
Edge and Mobile
Industries
Financial Services
Telecommunications
Healthcare
Retail
Public Sector
Manufacturing
Solutions Library
Organized and tailored solutions to kick-start projects
MongoDB AMP
Modernize applications up to 3x faster
Learn more
Startups and AI Innovators
For world-changing ideas and AI pioneers
Learn more
Customer Case Studies
Hear directly from our users
See stories
Company
Careers
Start your next adventure
Blog
Read articles and announcements
Newsroom
Read press releases and news stories
Partners
Learn about our partner ecosystem
Leadership
Meet our executive team
Company
Learn more about who we are
Contact Us
Reach out to MongoDB
Connect with an expert
Investors
Visit our investor portal
Learn more
Pricing
Eng
Support
Sign In
Get Started
Search in all APIs
ESC
Show more
Use
to navigate results,
ENTER
to select one,
ESC
to close
Type in any word to easily find the endpoint, property or group of operations you are looking for.
Search API documentation…
Ctrl+K
⌘K
MongoDB REST APIs hub
Atlas Admin API v2
Atlas Embedding and Reranking API
(Deprecated) Atlas Admin API v1
(Deprecated) MongoDB Atlas Data API v1
MongoDB Atlas App Services Admin API 3.0
MongoDB Atlas Status API
MongoDB Relational Migrator REST API
Back to hub page
Download source
JSON OpenAPI specification
YAML OpenAPI specification
Back to Atlas Docs
API Changelog
Toggle dark mode
latest
latest
default
2023-01-01
2023-02-01
2023-10-01
2023-11-15
2024-05-30
2024-08-05
2024-10-23
2024-11-13
2025-02-19
2025-03-12
preview
Topics
Introduction
Authentications
Rate Limiting
Endpoints
Access Tracking
Return Database Access History for One Cluster by Cluster Name
GET
Return Database Access History for One Cluster by Hostname
GET
Activity Feed
Return Pre-Filtered Activity Feed Link for One Project
GET
Return Pre-Filtered Activity Feed Link for One Organization
GET
AI Model API Keys
Return AI Model API Keys for One Group
GET
Create New AI Model API Key
POST
Return Single AI Model API Key for One Group
GET
Delete Existing AI Model API Key
DELETE
Update Existing AI Model API Key
PATCH
Return AI Model API Keys for One Organization
GET
Return Single AI Model API Key for One Organization
GET
AI Model Rate Limits
Return Single AI Model Rate Limit for One Group
GET
Update AI Model Rate Limit
PATCH
Reset AI Model Rate Limit for One Model Group
POST
Return AI Model Rate Limits for One Group
GET
Reset AI Model Rate Limits for Group
POST
Return Single AI Model Rate Limit for One Organization
GET
Return AI Model Rate Limits for One Organization
GET
Alert Configurations
Return All Alert Configuration Matchers Field Names
GET
Return All Alert Configurations in One Project
GET
Create One Alert Configuration in One Project
POST
Return One Alert Configuration from One Project
GET
Update One Alert Configuration in One Project
PUT
Remove One Alert Configuration from One Project
DELETE
Toggle State of One Alert Configuration in One Project
PATCH
Return All Alert Configurations Set for One Alert
GET
Alerts
Return All Open Alerts for One Alert Configuration
GET
Return All Alerts from One Project
GET
Return One Alert from One Project
GET
Acknowledge One Alert from One Project
PATCH
Atlas Search
Create One Atlas Search Index
POST
Return All Atlas Search Indexes for One Collection
GET
Return One Atlas Search Index
GET
Remove One Atlas Search Index
DELETE
Update One Atlas Search Index
PATCH
Return All Search Nodes
GET
Create Search Nodes
POST
Delete Search Nodes
DELETE
Update Search Nodes
PATCH
Return All Atlas Search Indexes for One Cluster
GET
Create One Atlas Search Index
POST
Return All Atlas Search Indexes for One Collection
GET
Return One Atlas Search Index by Name
GET
Remove One Atlas Search Index by Name
DELETE
Update One Atlas Search Index by Name
PATCH
Return One Atlas Search Index by ID
GET
Remove One Atlas Search Index by ID
DELETE
Update One Atlas Search Index by ID
PATCH
Auditing
Return Auditing Configuration for One Project
GET
Update Auditing Configuration for One Project
PATCH
AWS Clusters DNS
Return One Custom DNS Configuration for Atlas Clusters on AWS
GET
Update State of One Custom DNS Configuration for Atlas Clusters on AWS
PATCH
Cloud Backups
Return All Snapshot Export Buckets
GET
Create One Snapshot Export Bucket
POST
Return One Snapshot Export Bucket
GET
Delete One Snapshot Export Bucket
DELETE
Update One Export Bucket Private Networking Settings
PATCH
Return Object Storage Private Endpoints for Cloud Backups for One Cloud Provider in One Project
GET
Create One Object Storage Private Endpoint for Cloud Backups for One Cloud Provider in One Project
POST
Return One Object Storage Private Endpoint for Cloud Backups for One Cloud Provider in One Project
GET
Delete One Object Storage Private Endpoint for Cloud Backups for One Cloud Provider from One Project
DELETE
Return Backup Compliance Policy Settings
GET
Update Backup Compliance Policy Settings
PUT
Disable Backup Compliance Policy Settings
DELETE
Return All Snapshot Export Jobs
GET
Create One Snapshot Export Job
POST
Return One Snapshot Export Job
GET
Return All Restore Jobs for One Cluster
GET
Create One Restore Job of One Cluster
POST
Return One Restore Job for One Cluster
GET
Cancel One Restore Job for One Cluster
DELETE
Return One Cloud Backup Schedule
GET
Remove All Cloud Backup Schedules
DELETE
Update Cloud Backup Schedule for One Cluster
PATCH
Return All Replica Set Cloud Backups
GET
Take One On-Demand Snapshot
POST
Return One Sharded Cluster Cloud Backup
GET
Remove One Sharded Cluster Cloud Backup
DELETE
Return All Sharded Cluster Cloud Backups
GET
Return One Replica Set Cloud Backup
GET
Remove One Replica Set Cloud Backup
DELETE
Update Expiration Date for One Cloud Backup
PATCH
Return Databases in One Snapshot
GET
Return One Database in One Snapshot
GET
Return Collections in One Database in One Snapshot
GET
Return One Collection in One Database in One Snapshot
GET
Return All Collection Restore Jobs for One Cluster
GET
Create One Collection Restore Job
POST
Return One Collection Restore Job for One Cluster
GET
Return All Collection States for One Collection Restore Job
GET
Return One Collection State for One Collection Restore Job
GET
Return All Restore Jobs for One Serverless Instance
GET
Create One Restore Job for One Serverless Instance
POST
Return One Restore Job for One Serverless Instance
GET
Return All Snapshots of One Serverless Instance
GET
Return One Snapshot of One Serverless Instance
GET
Cloud Migration Service
Create One Migration for One Local Managed Cluster to MongoDB Atlas
POST
Validate One Migration Request
POST
Return One Migration Validation Job
GET
Return One Migration Job
GET
Cut Over One Migrated Cluster
PUT
Return All Projects Available for Migration
GET
Create One Link-Token
POST
Remove One Link-Token
DELETE
Cloud Provider Access
Return All Cloud Provider Access Roles
GET
Create One Cloud Provider Access Role
POST
Deauthorize One Cloud Provider Access Role
DELETE
Return One Cloud Provider Access Role
GET
Authorize One Cloud Provider Access Role
PATCH
Cluster Outage Simulation
Return One Outage Simulation
GET
Start One Outage Simulation
POST
End One Outage Simulation
DELETE
Clusters
Return All Authorized Clusters in All Projects
GET
Validate One Cluster Configuration
POST
Return All Clusters in One Project
GET
Create One Cluster in One Project
POST
Return All Cloud Provider Regions
GET
Upgrade One Shared-Tier Cluster
POST
Upgrade One Shared-Tier Cluster to One Serverless Instance
POST
Return One Cluster from One Project
GET
Remove One Cluster from One Project
DELETE
Update One Cluster in One Project
PATCH
Return Auto Scaling Configuration for One Sharded Cluster
GET
Return Advanced Configuration Options for One Cluster
GET
Update Advanced Configuration Options for One Cluster
PATCH
Test Failover for One Cluster
POST
Return Status of All Cluster Operations
GET
Grant MongoDB Employee Cluster Access for One Cluster
POST
Pin Feature Compatibility Version for One Cluster in One Project
POST
Revoke MongoDB Employee Cluster Access for One Cluster
POST
Unpin Feature Compatibility Version for One Cluster in One Project
POST
Load Sample Dataset into One Cluster
POST
Return Status of Sample Dataset Load for One Cluster
GET
Collection Level Metrics
Return Pinned Namespaces
GET
Pin Namespaces
PUT
Add Pinned Namespaces
PATCH
Unpin Namespaces
PATCH
Return Ranked Namespaces from One Cluster
GET
Return Cluster-Level Query Latency
GET
Return All Metric Names
GET
Return Ranked Namespaces from One Host
GET
Return Host-Level Query Latency
GET
Custom Database Roles
Return All Custom Roles in One Project
GET
Create One Custom Role
POST
Return One Custom Role in One Project
GET
Remove One Custom Role from One Project
DELETE
Update One Custom Role in One Project
PATCH
Data Federation
Return All Federated Database Instances in One Project
GET
Create One Federated Database Instance in One Project
POST
Return One Federated Database Instance in One Project
GET
Remove One Federated Database Instance from One Project
DELETE
Update One Federated Database Instance in One Project
PATCH
Return All Query Limits for One Federated Database Instance
GET
Return One Federated Database Instance Query Limit for One Project
GET
Delete One Query Limit for One Federated Database Instance
DELETE
Configure One Query Limit for One Federated Database Instance
PATCH
Download Query Logs for One Federated Database Instance
GET
Return All Federated Database Instance and Online Archive Private Endpoints in One Project
GET
Create One Federated Database Instance and Online Archive Private Endpoint for One Project
POST
Return One Federated Database Instance and Online Archive Private Endpoint in One Project
GET
Remove One Federated Database Instance and Online Archive Private Endpoint from One Project
DELETE
Database Users
Return All Database Users in One Project
GET
Create One Database User in One Project
POST
Return One Database User from One Project
GET
Remove One Database User from One Project
DELETE
Update One Database User in One Project
PATCH
Encryption at Rest using Customer Key Management
Return One Configuration for Encryption at Rest Using Customer-Managed Keys for One Project
GET
Update Encryption at Rest Configuration in One Project
PATCH
Return Private Endpoints for Encryption at Rest Using Customer Key Management for One Cloud Provider in One Project
GET
Create One Private Endpoint for Encryption at Rest Using Customer Key Management for One Cloud Provider in One Project
POST
Return One Private Endpoint for Encryption at Rest Using Customer Key Management for One Cloud Provider in One Project
GET
Delete One Private Endpoint for Encryption at Rest Using Customer Key Management for One Cloud Provider from One Project
DELETE
Events
Return All Event Types
GET
Return Events from One Project
GET
Return One Event from One Project
GET
Return Events from One Organization
GET
Return One Event from One Organization
GET
Federated Authentication
Delete One Federation Settings Instance
DELETE
Return All Organization Configurations from One Federation
GET
Return One Organization Configuration from One Federation
GET
Remove One Organization Configuration from One Federation
DELETE
Update One Organization Configuration in One Federation
PATCH
Return All Role Mappings from One Organization
GET
Create One Role Mapping in One Organization Configuration
POST
Return One Role Mapping from One Organization
GET
Update One Role Mapping in One Organization
PUT
Remove One Role Mapping from One Organization
DELETE
Return All Identity Providers in One Federation
GET
Create One Identity Provider
POST
Return One Identity Provider by ID
GET
Delete One Identity Provider
DELETE
Update One Identity Provider
PATCH
Revoke JWKS from One OIDC Identity Provider
DELETE
Return Metadata of One Identity Provider
GET
Return Federation Settings for One Organization
GET
Flex Clusters
Return All Flex Clusters from One Project
GET
Create One Flex Cluster in One Project
POST
Return One Flex Cluster from One Project
GET
Remove One Flex Cluster from One Project
DELETE
Update One Flex Cluster in One Project
PATCH
Upgrade One Flex Cluster
POST
Flex Restore Jobs
Return All Restore Jobs for One Flex Cluster
GET
Create One Restore Job for One Flex Cluster
POST
Return One Restore Job for One Flex Cluster
GET
Flex Snapshots
Download One Flex Cluster Snapshot
POST
Return All Snapshots for One Flex Cluster
GET
Return One Snapshot for One Flex Cluster
GET
Global Clusters
Return One Managed Namespace in One Global Cluster
GET
Add One Custom Zone Mapping to One Global Cluster
POST
Remove All Custom Zone Mappings from One Global Cluster
DELETE
Create One Managed Namespace in One Global Cluster
POST
Remove One Managed Namespace from One Global Cluster
DELETE
Invoices
Return Associated Invoices
GET
Create One Cost Explorer Query Process
POST
Return Usage Details for One Cost Explorer Query
GET
Return All Invoices for One Organization
GET
Return All Pending Invoices for One Organization
GET
Return One Invoice for One Organization
GET
Return One Invoice as CSV for One Organization
GET
Return All Line Items for One Invoice by Invoice ID
GET
Return All Invoice Reports for One Invoice
GET
Create One Invoice Report
POST
Return One Invoice Report
GET
Return All Stock Keeping Units
GET
Return One Stock Keeping Unit
GET
LDAP Configuration
Return LDAP or X.509 Configuration
GET
Update LDAP or X.509 Configuration
PATCH
Remove LDAP User to DN Mapping
DELETE
Verify LDAP Configuration in One Project
POST
Return Status of LDAP Configuration Verification in One Project
GET
Legacy Backup
Return All Legacy Backup Checkpoints
GET
Return One Legacy Backup Checkpoint
GET
Return All Legacy Backup Restore Jobs
GET
Create One Legacy Backup Restore Job
POST
Return One Legacy Backup Restore Job
GET
Return One Snapshot Schedule
GET
Update Snapshot Schedule for One Cluster
PATCH
Return All Legacy Backup Snapshots
GET
Return One Legacy Backup Snapshot
GET
Remove One Legacy Backup Snapshot
DELETE
Update Expiration Date for One Legacy Backup Snapshot
PATCH
Maintenance Windows
Return One Maintenance Window for One Project
GET
Reset One Maintenance Window for One Project
DELETE
Update One Maintenance Window for One Project
PATCH
Toggle Automatic Deferral of Maintenance for One Project
POST
Defer One Maintenance Window for One Project
POST
Metric Integrations
Return All Active Metric Integrations
GET
Create One Metric Integration
POST
Return One Metric Integration
GET
Update One Metric Integration
PUT
Remove One Metric Integration
DELETE
MongoDB Cloud Users
Return All MongoDB Cloud Users in One Project
GET
Add One MongoDB Cloud User to One Project
POST
Return One MongoDB Cloud User in One Project
GET
Remove One MongoDB Cloud User from One Project
DELETE
Add One Project Role to One MongoDB Cloud User
POST
Remove One Project Role from One MongoDB Cloud User
POST
Return All MongoDB Cloud Users Assigned to One Team
GET
Add One MongoDB Cloud User to One Team
POST
Remove One MongoDB Cloud User from One Team
POST
Return All MongoDB Cloud Users in One Organization
GET
Add One MongoDB Cloud User to One Organization
POST
Return One MongoDB Cloud User in One Organization
GET
Remove One MongoDB Cloud User from One Organization
DELETE
Update One MongoDB Cloud User in One Organization
PATCH
Add One Organization Role to One MongoDB Cloud User
POST
Remove One Organization Role from One MongoDB Cloud User
POST
Create One MongoDB Cloud User
POST
Return One MongoDB Cloud User by Username
GET
Return One MongoDB Cloud User by ID
GET
Monitoring and Logs
Download Logs for One Cluster Host in One Project
GET
Return All Atlas Search Metric Types for One Process
GET
Return All Atlas Search Index Metrics for One Namespace
GET
Return Atlas Search Metrics for One Index in One Namespace
GET
Return Atlas Search Hardware and Status Metrics
GET
Return All MongoDB Processes in One Project
GET
Return One MongoDB Process by ID
GET
Return Available Databases for One MongoDB Process
GET
Return One Database for One MongoDB Process
GET
Return Measurements for One Database in One MongoDB Process
GET
Return Available Disks for One MongoDB Process
GET
Return Measurements for One Disk
GET
Return Measurements of One Disk for One MongoDB Process
GET
Return Measurements for One MongoDB Process
GET
Network Peering
Return All Network Peering Containers in One Project for One Cloud Provider
GET
Create One Network Peering Container
POST
Return All Network Peering Containers in One Project
GET
Return One Network Peering Container
GET
Remove One Network Peering Container
DELETE
Update One Network Peering Container
PATCH
Return All Network Peering Connections in One Project
GET
Create One Network Peering Connection
POST
Return One Network Peering Connection in One Project
GET
Remove One Network Peering Connection
DELETE
Update One Network Peering Connection
PATCH
Verify Connect via Peering-Only Mode for One Project
GET
Disable Connect via Peering-Only Mode for One Project
PATCH
Online Archive
Return All Online Archives for One Cluster
GET
Create One Online Archive
POST
Download Online Archive Query Logs
GET
Return One Online Archive
GET
Remove One Online Archive
DELETE
Update One Online Archive
PATCH
Organizations
Return All Organizations
GET
Create One Organization
POST
Return One Organization
GET
Remove One Organization
DELETE
Update One Organization
PATCH
Return Delegation Settings for One Organization
GET
Update Delegation Settings for One Organization
PATCH
Return All Projects in One Organization
GET
Return All Invitations in One Organization
GET
Create Invitation for One MongoDB Cloud User in One Organization
POST
Update One Invitation in One Organization
PATCH
Return One Invitation in One Organization by Invitation ID
GET
Remove One Invitation from One Organization
DELETE
Update One Invitation in One Organization by Invitation ID
PATCH
Return Settings for One Organization
GET
Update Settings for One Organization
PATCH
Update Organization Roles for One MongoDB Cloud User
PUT
Performance Advisor
Return All Suggested Indexes to Drop
GET
Return Schema Advice
GET
Return All Suggested Indexes
GET
Return Managed Slow Operation Threshold Status
GET
Disable Managed Slow Operation Threshold
DELETE
Enable Managed Slow Operation Threshold
POST
Return All Namespaces for One Host
GET
Return Slow Queries
GET
Return All Suggested Indexes
GET
Return Serverless Auto-Indexing Status
GET
Set Serverless Auto-Indexing Status
POST
Private Endpoint Services
Create One Private Endpoint Service for One Provider
POST
Update One Private Endpoint Service for One Provider
PATCH
Return Regionalized Private Endpoint Status
GET
Toggle Regionalized Private Endpoint Status
PATCH
Return All Private Endpoint Services for One Provider
GET
Return One Private Endpoint Service for One Provider
GET
Remove One Private Endpoint Service for One Provider
DELETE
Create One Private Endpoint for One Provider
POST
Return One Private Endpoint for One Provider
GET
Remove One Private Endpoint for One Provider
DELETE
Programmatic API Keys
Return All Organization API Keys Assigned to One Project
GET
Create and Assign One Organization API Key to One Project
POST
Assign One Organization API Key to One Project
POST
Unassign One Organization API Key from One Project
DELETE
Update Organization API Key Roles for One Project
PATCH
Return All Organization API Keys
GET
Create One Organization API Key
POST
Return One Organization API Key
GET
Remove One Organization API Key
DELETE
Update One Organization API Key
PATCH
Return All Access List Entries for One Organization API Key
GET
Create One Access List Entry for One Organization API Key
POST
Return One Access List Entry for One Organization API Key
GET
Remove One Access List Entry for One Organization API Key
DELETE
Project IP Access List
Return All Project IP Access List Entries
GET
Add Entries to Project IP Access List
POST
Return One Project IP Access List Entry
GET
Remove One Entry from One Project IP Access List
DELETE
Return Status of One Project IP Access List Entry
GET
Projects
Return All Projects
GET
Create One Project
POST
Return One Project by Name
GET
Return One Project
GET
Remove One Project
DELETE
Update One Project
PATCH
Add One MongoDB Cloud User to One Project
POST
Return All Invitations in One Project
GET
Create Invitation for One MongoDB Cloud User in One Project
POST
Update One Invitation in One Project
PATCH
Return One Invitation in One Project by Invitation ID
GET
Remove One Invitation from One Project
DELETE
Update One Invitation in One Project by Invitation ID
PATCH
Return All IP Addresses for One Project
GET
Return All Limits for One Project
GET
Return One Limit for One Project
GET
Remove One Project Limit
DELETE
Set One Project Limit
PATCH
Return All Available MongoDB LTS Versions for Clusters in One Project
GET
Return Project Settings
GET
Update Project Settings
PATCH
Update Project Roles for One MongoDB Cloud User
PUT
Migrate One Project to Another Organization
POST
Push-Based Log Export
Return All Active Log Integrations
GET
Create One Log Integration
POST
Return One Log Integration
GET
Update One Log Integration
PUT
Remove One Log Integration
DELETE
Return One Push-Based Log Export Configuration in One Project
GET
Create One Push-Based Log Export Configuration in One Project
POST
Disable Push-Based Log Export for One Project
DELETE
Update One Push-Based Log Export Configuration in One Project
PATCH
Rate Limiting
Return All Rate Limits
GET
Return One Rate Limit
GET
Remote MCP Configurations
Return All MCP Configurations for One Project
GET
Create One MCP Configuration for One Project
POST
Return One MCP Configuration for One Project
GET
Delete One MCP Configuration for One Project
DELETE
Update One MCP Configuration for One Project
PATCH
Return All Secrets for One Project MCP Configuration
GET
Create One Secret for One Project MCP Configuration
POST
Return One Secret for One Project MCP Configuration
GET
Delete One Secret for One Project MCP Configuration
DELETE
Return All MCP Configurations for One Organization
GET
Create One MCP Configuration for One Organization
POST
Return One MCP Configuration for One Organization
GET
Delete One MCP Configuration for One Organization
DELETE
Update One MCP Configuration for One Organization
PATCH
Return All Secrets for One Organization MCP Configuration
GET
Create One Secret for One Organization MCP Configuration
POST
Return One Secret for One Organization MCP Configuration
GET
Delete One Secret for One Organization MCP Configuration
DELETE
Resource Policies
Return All Non-Compliant Resources
GET
Return All Atlas Resource Policies
GET
Create One Atlas Resource Policy
POST
Return One Atlas Resource Policy
GET
Delete One Atlas Resource Policy
DELETE
Update One Atlas Resource Policy
PATCH
Validate One Atlas Resource Policy
POST
Rolling Index
Create One Rolling Index
POST
Root
Return the Status of This MongoDB Application
GET
Return All Control Plane IP Addresses
GET
Serverless Instances
Return All Serverless Instances in One Project
GET
Return One Serverless Instance from One Project
GET
Serverless Private Endpoints
Return All Private Endpoints for One Serverless Instance
GET
Create One Private Endpoint for One Serverless Instance
POST
Return One Private Endpoint for One Serverless Instance
GET
Remove One Private Endpoint for One Serverless Instance
DELETE
Update One Private Endpoint for One Serverless Instance
PATCH
Service Accounts
Return All Project Service Accounts
GET
Create One Project Service Account
POST
Return One Project Service Account
GET
Remove One Project Service Account
DELETE
Update One Project Service Account
PATCH
Return All Access List Entries for One Project Service Account
GET
Add Access List Entries for One Project Service Account
POST
Remove One Access List Entry from One Project Service Account
DELETE
Create One Project Service Account Secret
POST
Delete One Project Service Account Secret
DELETE
Assign One Service Account to One Project
POST
Return All Organization Service Accounts
GET
Create One Organization Service Account
POST
Return One Organization Service Account
GET
Delete One Organization Service Account
DELETE
Update One Organization Service Account
PATCH
Return All Access List Entries for One Organization Service Account
GET
Add Access List Entries for One Organization Service Account
POST
Remove One Access List Entry from One Organization Service Account
DELETE
Return All Service Account Project Assignments
GET
Create One Organization Service Account Secret
POST
Delete One Organization Service Account Secret
DELETE
Streams
Return All Stream Workspaces in One Project
GET
Create One Stream Workspace
POST
Return Account ID and VPC ID for One Project and Region
GET
Return All Active Incoming VPC Peering Connections
GET
Return All Private Link Connections
GET
Create One Private Link Connection
POST
Return One Private Link Connection
GET
Delete One Private Link Connection
DELETE
Update One Private Link Connection
PATCH
Return All VPC Peering Connections
GET
Delete One VPC Peering Connection
DELETE
Accept One Incoming VPC Peering Connection
POST
Reject One Incoming VPC Peering Connection
POST
Return One Stream Workspace
GET
Delete One Stream Workspace
DELETE
Update One Stream Workspace
PATCH
Download Audit Logs for One Atlas Stream Processing Workspace
GET
Return All Connections of the Stream Workspaces
GET
Create One Stream Connection
POST
Return One Stream Connection
GET
Delete One Stream Connection
DELETE
Update One Stream Connection
PATCH
Return All Stream Failover Connections
GET
Create One Failover Stream Connection
POST
Return One Stream Failover Connection
GET
Delete One Stream Failover Connection
DELETE
Update One Stream Failover Connection
PATCH
Create One Stream Processor
POST
Return One Stream Processor
GET
Delete One Stream Processor
DELETE
Update One Stream Processor
PATCH
Start One Stream Processor
POST
Start One Stream Processor With Options
POST
Stop One Stream Processor
POST
Return All Stream Processors in One Stream Workspace
GET
Download Operational Logs for One Atlas Stream Processing Workspace
GET
Create One Stream Workspace with Sample Connections
POST
Teams
Return All Teams in One Project
GET
Add Multiple Teams to One Project
POST
Return One Team in One Project
GET
Remove One Team from One Project
DELETE
Update Team Roles in One Project
PATCH
Return All Teams in One Organization
GET
Create One Team in One Organization
POST
Return One Team by Name
GET
Return One Team by ID
GET
Remove One Team from One Organization
DELETE
Rename One Team
PATCH
Assign MongoDB Cloud Users in One Organization to One Team
POST
Remove One MongoDB Cloud User from One Team
DELETE
Third-Party Integrations
Return All Active Third-Party Service Integrations
GET
Return One Third-Party Service Integration
GET
Update One Third-Party Service Integration
PUT
Create One Third-Party Service Integration
POST
Remove One Third-Party Service Integration
DELETE
X.509 Authentication
Return All X.509 Certificates Assigned to One Database User
GET
Create One X.509 Certificate for One Database User
POST
Disable Customer-Managed X.509
DELETE
Query Shape Insights
Return Query Statistic Summaries
GET
Return Query Shape Details
GET
Return All Query Shapes
GET
Return One Query Shape
GET
Update Query Shape Rejection Status
PATCH
Powered by Bump.sh
Search API documentation…
Ctrl+K
⌘K
MongoDB REST APIs hub
Atlas Admin API v2
Atlas Embedding and Reranking API
(Deprecated) Atlas Admin API v1
(Deprecated) MongoDB Atlas Data API v1
MongoDB Atlas App Services Admin API 3.0
MongoDB Atlas Status API
MongoDB Relational Migrator REST API
Back to hub page
Download source
JSON OpenAPI specification
YAML OpenAPI specification
Back to Atlas Docs
API Changelog
Toggle dark mode
Create One Cluster in One Project
Ask AI
View as Markdown
Copy as Markdown
POST
/api/atlas/v2/groups/{groupId}/clusters
Service accounts
Digest auth
Creates one cluster in the specified project. Clusters contain a group of hosts that maintain the same data set. This resource can create clusters with asymmetrically-sized shards. Each project supports up to 25 database deployments. This feature is not available for serverless clusters.
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. Deprecated versions: v2-{2024-08-05}, v2-{2023-02-01}, v2-{2023-01-01}
Role requirements
Project Cluster Creator
Create Flex Cluster
Headers
Use-Effective-Instance-Fields
boolean
Controls how hardware specification fields are returned in the response after cluster creation. When set to true, returns the original client-specified values and provides separate effective fields showing current operational values. When false (default), hardware specification fields show current operational values directly. Primarily used for autoscaling compatibility.
Default value is
false
.
Use-Effective-Fields-Replication-Specs
boolean
Controls how
replicationSpecs
fields are returned in the response. When set to
true
, stores the client's view of
replicationSpecs
and returns it in
replicationSpecs
, while the actual cluster state (including auto-scaled hardware and auto-added shards) is returned in
effectiveReplicationSpecs
. When
false
(default),
replicationSpecs
contains the actual cluster state.
Default value is
false
.
Path parameters
groupId
string
Required
Unique 24-hexadecimal digit string that identifies your project. Use the
/groups
endpoint to retrieve all projects to which the authenticated user has access.
NOTE
: Groups and projects are synonymous terms. Your group id is the same as your project id. For existing groups, your group/project id remains the same. The resource and corresponding endpoints use the term groups.
Format should match the following pattern:
^([a-f0-9]{24})$
.
Query parameters
envelope
boolean
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
.
pretty
boolean
Flag that indicates whether the response body should be in the prettyprint format.
Default value is
false
.
Prettyprint
application/vnd.atlas.2024-10-23+json
Body
Required
Cluster to create in this project.
acceptDataRisksAndForceReplicaSetReconfig
string(date-time)
If reconfiguration is necessary to regain a primary due to a regional outage, submit this field alongside your topology reconfiguration to request a new regional outage resistant topology. Forced reconfigurations during an outage of the majority of electable nodes carry a risk of data loss if replicated writes (even majority committed writes) have not been replicated to the new primary node. MongoDB Atlas docs contain more information. To proceed with an operation which carries that risk, set
acceptDataRisksAndForceReplicaSetReconfig
to the current date. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
Reconfiguring a Replica Set du...
adaptiveCapacity
string | null
Governs adaptive capacity behavior of Azure nodes in single-cloud Azure clusters or multi-cloud clusters that include Azure nodes. Adaptive capacity enables fallback hardware selection when the primary instance family is unavailable.
ENABLED
means the cluster explicitly opts in to adaptive capacity.
DISABLED
means the cluster explicitly opts out; the cluster receives capacity errors instead of being placed on fallback hardware.
null
means the field is unset; Azure clusters use adaptive capacity by default when the feature is enabled at the group level. Setting this field for single-cloud AWS or GCP clusters is a no-op.
Values are
ENABLED
or
DISABLED
.
advancedConfiguration
object
Group of settings that configures a subset of the advanced configuration details.
Hide advancedConfiguration attributes
Show advancedConfiguration attributes
object
customOpensslCipherConfigTls12
array[string]
The custom OpenSSL cipher suite list for TLS 1.2. Requires
tlsCipherConfigMode
=
CUSTOM
; when
tlsCipherConfigMode
is omitted, supplying a non-empty list infers
CUSTOM
.
Values are
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
or
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
.
customOpensslCipherConfigTls13
array[string]
The custom OpenSSL cipher suite list for TLS 1.3. Requires
tlsCipherConfigMode
=
CUSTOM
; when
tlsCipherConfigMode
is omitted, supplying a non-empty list infers
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
.
minimumEnabledTlsProtocol
string
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
.
This option corresponds to the...
tlsCipherConfigMode
string
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
.
backupEnabled
boolean
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
.
Cloud Backups
biConnector
object
Settings needed to configure the MongoDB Connector for Business Intelligence for this cluster.
MongoDB Connector for Business...
Hide biConnector attributes
Show biConnector attributes
object
enabled
boolean
Flag that indicates whether MongoDB Connector for Business Intelligence is enabled on the specified cluster.
readPreference
string
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
.
Read preferences for BI Connector
clusterType
string
Configuration of nodes that comprise the cluster.
Values are
REPLICASET
,
SHARDED
, or
GEOSHARDED
.
configServerManagementMode
string
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
.
MongoDB Sharded Cluster Config...
diskWarmingMode
string
Disk warming mode selection.
Values are
FULLY_WARMED
,
VISIBLE_EARLIER
, or
ENHANCED_FULLY_WARMED
. Default value is
FULLY_WARMED
.
Reduce Secondary Disk Warming ...
encryptionAtRestProvider
string
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
.
Encryption at Rest using Custo...
globalClusterSelfManagedSharding
boolean
Set this field to configure the Sharding Management Mode when creating a new Global Cluster.
When set to false, the management mode is set to Atlas-Managed Sharding. This mode fully manages the sharding of your Global Cluster and is built to provide a seamless deployment experience.
When set to true, the management mode is set to Self-Managed Sharding. This mode leaves the management of shards in your hands and is built to provide an advanced and flexible deployment experience.
This setting cannot be changed once the cluster is deployed.
Creating a Global Cluster
labels
array[object]
Deprecated
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.
Resource Tags
Hide labels attributes
Show labels attributes
object
Human-readable labels applied to this MongoDB Cloud component.
key
string
Key applied to tag and categorize this component.
Minimum length is
1
, maximum length is
255
.
value
string
Value set to the Key applied to tag and categorize this component.
Minimum length is
1
, maximum length is
255
.
mongoDBMajorVersion
string
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.
Available MongoDB Versions in ...
name
string
Human-readable label that identifies the cluster.
Format should match the following pattern:
^[a-zA-Z0-9][a-zA-Z0-9-]*$
.
paused
boolean
Flag that indicates whether the cluster is paused.
pitEnabled
boolean
Flag that indicates whether the cluster uses continuous cloud backups.
Continuous Cloud Backups
redactClientLogData
boolean
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.
Log Redaction
replicaSetScalingStrategy
string
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
.
Modify the Replica Set Scaling...
replicationSpecs
array[object]
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.
Hide replicationSpecs attributes
Show replicationSpecs attributes
object
Details that explain how MongoDB Cloud replicates data on the specified MongoDB database.
regionConfigs
array[object]
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.
One of:
AWS
object
AZURE
object
GCP
object
TENANT
object
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
AWS
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
AZURE
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
GCP
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
TENANT
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
backingProviderName
string
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
.
Create Flex Cluster API
zoneName
string
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
.
retainBackups
boolean
Flag that indicates whether the cluster retains backups.
Default value is
false
.
rootCertType
string
Root Certificate Authority that MongoDB Atlas cluster uses. MongoDB Cloud supports Internet Security Research Group.
Value is
ISRGROOTX1
. Default value is
ISRGROOTX1
.
tags
array[object]
List that contains key-value pairs between 1 to 255 characters in length for tagging and categorizing the cluster.
Resource Tags
Hide tags attributes
Show tags attributes
object
Key-value pair that tags and categorizes a MongoDB Cloud organization, project, or cluster. For example,
environment : production
.
key
string
Required
Constant that defines the set of the tag. For example,
environment
in the
environment : production
tag.
Minimum length is
1
, maximum length is
255
.
value
string
Required
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
.
terminationProtectionEnabled
boolean
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
.
useAwsTimeBasedSnapshotCopyForFastInitialSync
boolean
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
.
versionReleaseSystem
string
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
.
Responses
201
application/vnd.atlas.2024-10-23+json
Created
Hide headers attributes
Show headers attributes
RateLimit-Limit
The maximum number of requests that a user can make within a specific time window.
RateLimit-Remaining
The number of requests remaining in the current rate limit window before the limit is reached.
Hide response attributes
Show response attributes
object
acceptDataRisksAndForceReplicaSetReconfig
string(date-time)
If reconfiguration is necessary to regain a primary due to a regional outage, submit this field alongside your topology reconfiguration to request a new regional outage resistant topology. Forced reconfigurations during an outage of the majority of electable nodes carry a risk of data loss if replicated writes (even majority committed writes) have not been replicated to the new primary node. MongoDB Atlas docs contain more information. To proceed with an operation which carries that risk, set
acceptDataRisksAndForceReplicaSetReconfig
to the current date. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
Reconfiguring a Replica Set du...
adaptiveCapacity
string | null
Governs adaptive capacity behavior of Azure nodes in single-cloud Azure clusters or multi-cloud clusters that include Azure nodes. Adaptive capacity enables fallback hardware selection when the primary instance family is unavailable.
ENABLED
means the cluster explicitly opts in to adaptive capacity.
DISABLED
means the cluster explicitly opts out; the cluster receives capacity errors instead of being placed on fallback hardware.
null
means the field is unset; Azure clusters use adaptive capacity by default when the feature is enabled at the group level. Setting this field for single-cloud AWS or GCP clusters is a no-op.
Values are
ENABLED
or
DISABLED
.
advancedConfiguration
object
Group of settings that configures a subset of the advanced configuration details.
Hide advancedConfiguration attributes
Show advancedConfiguration attributes
object
customOpensslCipherConfigTls12
array[string]
The custom OpenSSL cipher suite list for TLS 1.2. Requires
tlsCipherConfigMode
=
CUSTOM
; when
tlsCipherConfigMode
is omitted, supplying a non-empty list infers
CUSTOM
.
Values are
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
or
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
.
customOpensslCipherConfigTls13
array[string]
The custom OpenSSL cipher suite list for TLS 1.3. Requires
tlsCipherConfigMode
=
CUSTOM
; when
tlsCipherConfigMode
is omitted, supplying a non-empty list infers
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
.
minimumEnabledTlsProtocol
string
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
.
This option corresponds to the...
tlsCipherConfigMode
string
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
.
backupEnabled
boolean
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
.
Cloud Backups
biConnector
object
Settings needed to configure the MongoDB Connector for Business Intelligence for this cluster.
MongoDB Connector for Business...
Hide biConnector attributes
Show biConnector attributes
object
enabled
boolean
Flag that indicates whether MongoDB Connector for Business Intelligence is enabled on the specified cluster.
readPreference
string
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
.
Read preferences for BI Connector
clusterType
string
Configuration of nodes that comprise the cluster.
Values are
REPLICASET
,
SHARDED
, or
GEOSHARDED
.
configServerManagementMode
string
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
.
MongoDB Sharded Cluster Config...
configServerType
string
Describes a sharded cluster's config server type.
Values are
DEDICATED
or
EMBEDDED
.
MongoDB Sharded Cluster Config...
connectionStrings
object
Collection of Uniform Resource Locators that point to the MongoDB database.
Connection string URI format.
Hide connectionStrings attributes
Show connectionStrings attributes
object
awsPrivateLink
object
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to MongoDB Cloud through the interface endpoint that the key names.
Network Peering Connection
Hide awsPrivateLink attribute
Show awsPrivateLink attribute
object
*
string
Additional properties
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to MongoDB Cloud through the interface endpoint that the key names.
Network Peering Connection
awsPrivateLinkSrv
object
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to Atlas through the interface endpoint that the key names. If the cluster uses an optimized connection string,
awsPrivateLinkSrv
contains the optimized connection string. If the cluster has the non-optimized (legacy) connection string,
awsPrivateLinkSrv
contains the non-optimized connection string even if an optimized connection string is also present.
Network Peering Connection
Hide awsPrivateLinkSrv attribute
Show awsPrivateLinkSrv attribute
object
*
string
Additional properties
Private endpoint-aware connection strings that use AWS-hosted clusters with Amazon Web Services (AWS) PrivateLink. Each key identifies an Amazon Web Services (AWS) interface endpoint. Each value identifies the related
mongodb://
connection string that you use to connect to Atlas through the interface endpoint that the key names. If the cluster uses an optimized connection string,
awsPrivateLinkSrv
contains the optimized connection string. If the cluster has the non-optimized (legacy) connection string,
awsPrivateLinkSrv
contains the non-optimized connection string even if an optimized connection string is also present.
Network Peering Connection
private
string
Network peering connection strings for each interface Virtual Private Cloud (VPC) endpoint that you configured to connect to this cluster. This connection string uses the
mongodb+srv://
protocol. The resource returns this parameter once someone creates a network peering connection to this cluster. This protocol tells the application to look up the host seed list in the Domain Name System (DNS). This list synchronizes with the nodes in a cluster. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to append the seed list or change the URI if the nodes change. Use this URI format if your driver supports it. If it doesn't, use
connectionStrings.private
. For Amazon Web Services (AWS) clusters, this resource returns this parameter only if you enable custom DNS.
Network Peering Connection
privateEndpoint
array[object]
List of private endpoint-aware connection strings that you can use to connect to this cluster through a private endpoint. This parameter returns only if you deployed a private endpoint to all regions to which you deployed this clusters' nodes.
Hide privateEndpoint attributes
Show privateEndpoint attributes
object
Private endpoint-aware connection string that you can use to connect to this cluster through a private endpoint.
Private Endpoint for Dedicated...
connectionString
string
Private endpoint-aware connection string that uses the
mongodb://
protocol to connect to MongoDB Cloud through a private endpoint.
endpoints
array[object]
List that contains the private endpoints through which you connect to MongoDB Cloud when you use
connectionStrings.privateEndpoint[n].connectionString
or
connectionStrings.privateEndpoint[n].srvConnectionString
.
Hide endpoints attributes
Show endpoints attributes
object
Details of a private endpoint deployed for this cluster.
endpointId
string
Unique string that the cloud provider uses to identify the private endpoint.
providerName
string
Cloud provider in which MongoDB Cloud deploys the private endpoint.
Values are
AWS
,
AZURE
, or
GCP
.
region
string
Region where the private endpoint is deployed.
srvConnectionString
string
Private endpoint-aware connection string that uses the
mongodb+srv://
protocol to connect to MongoDB Cloud through a private endpoint. The
mongodb+srv
protocol tells the driver to look up the seed list of hosts in the Domain Name System (DNS). This list synchronizes with the nodes in a cluster. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to append the seed list or change the Uniform Resource Identifier (URI) if the nodes change. Use this Uniform Resource Identifier (URI) format if your application supports it. If it doesn't, use
connectionStrings.privateEndpoint[n].connectionString
.
srvShardOptimizedConnectionString
string
Private endpoint-aware connection string optimized for sharded clusters that uses the
mongodb+srv://
protocol to connect to MongoDB Cloud through a private endpoint. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to change the Uniform Resource Identifier (URI) if the nodes change. Use this Uniform Resource Identifier (URI) format if your application and Atlas cluster supports it. If it doesn't, use and consult the documentation for
connectionStrings.privateEndpoint[n].srvConnectionString
.
type
string
MongoDB process type to which your application connects. Use
MONGOD
for replica sets and
MONGOS
for sharded clusters.
Values are
MONGOD
or
MONGOS
.
privateSrv
string
Network peering connection strings for each interface Virtual Private Cloud (VPC) endpoint that you configured to connect to this cluster. This connection string uses the
mongodb+srv://
protocol. The resource returns this parameter when someone creates a network peering connection to this cluster. This protocol tells the application to look up the host seed list in the Domain Name System (DNS). This list synchronizes with the nodes in a cluster. If the connection string uses this Uniform Resource Identifier (URI) format, you don't need to append the seed list or change the Uniform Resource Identifier (URI) if the nodes change. Use this Uniform Resource Identifier (URI) format if your driver supports it. If it doesn't, use
connectionStrings.private
. For Amazon Web Services (AWS) clusters, this parameter returns only if you
enable custom DNS
.
Network Peering Connection
standard
string
Public connection string that you can use to connect to this cluster. This connection string uses the
mongodb://
protocol.
Connection String URI Format
standardSrv
string
Public connection string that you can use to connect to this cluster. This connection string uses the
mongodb+srv://
protocol.
Connection String URI Format
createDate
string(date-time)
Date and time when MongoDB Cloud created this cluster. This parameter expresses its value in ISO 8601 format in UTC.
diskWarmingMode
string
Disk warming mode selection.
Values are
FULLY_WARMED
,
VISIBLE_EARLIER
, or
ENHANCED_FULLY_WARMED
. Default value is
FULLY_WARMED
.
Reduce Secondary Disk Warming ...
effectiveReplicationSpecs
array[object]
List of settings that represent the actual cluster state. This is read-only and always returned in the response. It reflects the current cluster configuration, which may differ from
replicationSpecs
due to system-managed changes.
Hide effectiveReplicationSpecs attributes
Show effectiveReplicationSpecs attributes
object
Details that explain how MongoDB Cloud replicates data on the specified MongoDB database.
id
string
Unique 24-hexadecimal digit string that identifies the replication object for a shard in a Cluster. If you include existing shard replication configurations in the request, you must specify this parameter. If you add a new shard to an existing Cluster, you may specify this parameter. The request deletes any existing shards in the Cluster that you exclude from the request. This corresponds to Shard ID displayed in the UI.
Format should match the following pattern:
^([a-f0-9]{24})$
.
regionConfigs
array[object]
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.
One of:
AWS
object
AZURE
object
GCP
object
TENANT
object
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
AWS
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
analyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
effectiveAnalyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveElectableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveReadOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
readOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
AZURE
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
analyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
effectiveAnalyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveElectableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveReadOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
readOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
GCP
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
analyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
effectiveAnalyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveElectableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveReadOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
readOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
TENANT
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
backingProviderName
string
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
.
Create Flex Cluster API
zoneId
string
Unique 24-hexadecimal digit string that identifies the zone in a Global Cluster. This value can be used to configure Global Cluster backup policies.
Format should match the following pattern:
^([a-f0-9]{24})$
.
zoneName
string
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
.
encryptionAtRestProvider
string
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
.
Encryption at Rest using Custo...
featureCompatibilityVersion
string
Feature compatibility version of the cluster. This will always appear regardless of whether FCV is pinned.
featureCompatibilityVersionExpirationDate
string(date-time)
Feature compatibility version expiration date. Will only appear if FCV is pinned. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
globalClusterSelfManagedSharding
boolean
Set this field to configure the Sharding Management Mode when creating a new Global Cluster.
When set to false, the management mode is set to Atlas-Managed Sharding. This mode fully manages the sharding of your Global Cluster and is built to provide a seamless deployment experience.
When set to true, the management mode is set to Self-Managed Sharding. This mode leaves the management of shards in your hands and is built to provide an advanced and flexible deployment experience.
This setting cannot be changed once the cluster is deployed.
Creating a Global Cluster
groupId
string
Unique 24-hexadecimal character string that identifies the project.
Format should match the following pattern:
^([a-f0-9]{24})$
.
id
string
Unique 24-hexadecimal digit string that identifies the cluster.
Format should match the following pattern:
^([a-f0-9]{24})$
.
internalClusterRole
string
Internal classification of the cluster's role. Possible values:
NONE
(regular user cluster),
SYSTEM_CLUSTER
(system cluster for backup),
INTERNAL_SHADOW_CLUSTER
(internal use shadow cluster for testing).
Values are
NONE
,
SYSTEM_CLUSTER
, or
INTERNAL_SHADOW_CLUSTER
.
labels
array[object]
Deprecated
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.
Resource Tags
Hide labels attributes
Show labels attributes
object
Human-readable labels applied to this MongoDB Cloud component.
key
string
Key applied to tag and categorize this component.
Minimum length is
1
, maximum length is
255
.
value
string
Value set to the Key applied to tag and categorize this component.
Minimum length is
1
, maximum length is
255
.
links
array[object]
List of one or more Uniform Resource Locators (URLs) that point to API sub-resources, related API resources, or both. RFC 5988 outlines these relationships.
Web Linking Specification (RFC...
Hide links attributes
Show links attributes
object
href
string
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
.
rel
string
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
.
mongoDBEmployeeAccessGrant
object
MongoDB employee granted access level and expiration for a cluster.
Hide mongoDBEmployeeAccessGrant attributes
Show mongoDBEmployeeAccessGrant attributes
object
expirationTime
string(date-time)
Required
Expiration date for the employee access grant. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
grantType
string
Required
Level of access to grant to MongoDB Employees.
Values are
CLUSTER_DATABASE_LOGS
,
CLUSTER_INFRASTRUCTURE
, or
CLUSTER_INFRASTRUCTURE_AND_APP_SERVICES_SYNC_DATA
.
links
array[object]
List of one or more Uniform Resource Locators (URLs) that point to API sub-resources, related API resources, or both. RFC 5988 outlines these relationships.
Web Linking Specification (RFC...
Hide links attributes
Show links attributes
object
href
string
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
.
rel
string
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
.
mongoDBMajorVersion
string
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.
Available MongoDB Versions in ...
mongoDBVersion
string
Version of MongoDB that the cluster runs.
Format should match the following pattern:
([\d]+\.[\d]+\.[\d]+)
.
name
string
Human-readable label that identifies the cluster.
Format should match the following pattern:
^[a-zA-Z0-9][a-zA-Z0-9-]*$
.
paused
boolean
Flag that indicates whether the cluster is paused.
pitEnabled
boolean
Flag that indicates whether the cluster uses continuous cloud backups.
Continuous Cloud Backups
redactClientLogData
boolean
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.
Log Redaction
replicaSetScalingStrategy
string
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
.
Modify the Replica Set Scaling...
replicationSpecs
array[object]
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.
Hide replicationSpecs attributes
Show replicationSpecs attributes
object
Details that explain how MongoDB Cloud replicates data on the specified MongoDB database.
id
string
Unique 24-hexadecimal digit string that identifies the replication object for a shard in a Cluster. If you include existing shard replication configurations in the request, you must specify this parameter. If you add a new shard to an existing Cluster, you may specify this parameter. The request deletes any existing shards in the Cluster that you exclude from the request. This corresponds to Shard ID displayed in the UI.
Format should match the following pattern:
^([a-f0-9]{24})$
.
regionConfigs
array[object]
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.
One of:
AWS
object
AZURE
object
GCP
object
TENANT
object
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
AWS
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
analyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
effectiveAnalyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveElectableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveReadOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
readOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
AZURE
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
analyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
effectiveAnalyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveElectableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveReadOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
readOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
GCP
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
analyticsAutoScaling
object
Options that determine how this cluster handles resource scaling.
Hide analyticsAutoScaling attributes
Show analyticsAutoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
analyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
autoScaling
object
Options that determine how this cluster handles resource scaling.
Hide autoScaling attributes
Show autoScaling attributes
object
compute
object
Options that determine how this cluster handles CPU scaling.
Hide compute attributes
Show compute attributes
object
enabled
boolean
Flag that indicates whether instance size reactive auto-scaling is enabled.
Set to
true
to enable instance size reactive auto-scaling. If enabled, you must specify a value for
replicationSpecs[n].regionConfigs[m].autoScaling.compute.maxInstanceSize
.
Set to
false
to disable instance size reactive auto-scaling.
maxInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
minInstanceSize
string
Instance size boundary to which your cluster can automatically scale.
One of:
AWS Instance Sizes
string
Azure Instance Sizes
string
GCP Instance Sizes
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
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
.
Values are
M10
,
M20
,
M30
,
M40
,
M50
,
M60
,
M80
,
M140
,
M200
,
M250
,
M300
,
M400
,
R40
,
R50
,
R60
,
R80
,
R200
,
R300
,
R400
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
scaleDownEnabled
boolean
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
.
diskGB
object
Setting that enables disk auto-scaling.
Hide diskGB attribute
Show diskGB attribute
object
enabled
boolean
Flag that indicates whether this cluster enables disk auto-scaling. The maximum memory allowed for the selected cluster tier and the oplog size can limit storage auto-scaling.
effectiveAnalyticsSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveElectableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
effectiveReadOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
readOnlySpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
The current hardware specifications for read only nodes in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
nodeCount
integer(int32)
Number of nodes of the given type for MongoDB Cloud to deploy to the region.
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
Details that explain how MongoDB Cloud replicates data in one region on the specified MongoDB database.
Hide attributes
Show attributes
electableSpecs
object
One of:
AWS Cluster Hardware Settings
object
AzureHardwareSpec20240805
object
GCPHardwareSpec20240805
object
TenantHardwareSpec20240805
object
Hardware specifications for nodes deployed in the region.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
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:
set
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.
Instance sizes
M10
to
M40
have a ratio of disk capacity to system memory of 60:1.
Instance sizes greater than
M40
have a ratio of 120:1.
diskThroughput
integer(int32)
Target throughput desired for storage attached to this hardware. Only returned for Gen 2 instance sizes with Standard (GP3) volume type.
ebsVolumeType
string
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.
HIGH_PERFORMANCE
volume types use IO2 EBS volumes and must fall within the allowable IOPS range for the selected volume size.
NVMe clusters require either
PROVISIONED
or
HIGH_PERFORMANCE
.
Values are
STANDARD
,
PROVISIONED
, or
HIGH_PERFORMANCE
. Default value is
STANDARD
.
instanceSize
string
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
,
M400_NVME
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
M300_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
,
R400_GEN_2
,
R700_GEN_2
,
M40_NVME_GEN_2
,
M50_NVME_GEN_2
,
M60_NVME_GEN_2
,
M80_NVME_GEN_2
,
M200_NVME_GEN_2
, or
M400_NVME_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
diskIOPS
integer(int32)
Target throughput desired for storage attached to your Azure-provisioned cluster. Change this parameter if you:
set
replicationSpecs[n].regionConfigs[m].providerName
:
Azure
.
set
replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize
:
M40
or greater not 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.
Programmatic API Keys
instanceSize
string
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
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
instanceSize
string
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
,
R600
,
M30_GEN_2
,
M40_GEN_2
,
M50_GEN_2
,
M60_GEN_2
,
M80_GEN_2
,
M140_GEN_2
,
M200_GEN_2
,
R40_GEN_2
,
R50_GEN_2
,
R60_GEN_2
,
R80_GEN_2
,
R200_GEN_2
,
R300_GEN_2
, or
R400_GEN_2
.
nodeCount
integer(int32)
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.
Hide attributes
Show attributes
diskSizeGB
number(double)
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.
Customize Storage
effectiveInstanceSize
string
The true tenant instance size. This is present to support backwards compatibility for deprecated provider types and/or instance sizes.
Values are
FLEX
,
M2
,
M5
, or
M0
.
instanceSize
string
Hardware specification for the instances in this M0/M2/M5 tier cluster.
Values are
M0
,
M2
, or
M5
.
priority
integer(int32)
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
.
providerName
string
Discriminator
Cloud service provider on which MongoDB Cloud provisions the hosts. Set dedicated clusters to
AWS
,
GCP
,
AZURE
or
TENANT
.
Value is
TENANT
.
regionName
string
Physical location of your MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. The region name is only returned in the response for single-region clusters. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. It assigns the VPC a Classless Inter-Domain Routing (CIDR) block. To limit a new VPC peering connection to one Classless Inter-Domain Routing (CIDR) block and region, create the connection first. Deploy the cluster after the connection starts. GCP Clusters and Multi-region clusters require one VPC peering connection for each region. MongoDB nodes can use only the peering connection that resides in the same region as the nodes to communicate with the peered VPC.
One of:
AWS Regions
string
Azure Regions
string
GCP Regions
string
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
.
backingProviderName
string
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
.
Create Flex Cluster API
zoneId
string
Unique 24-hexadecimal digit string that identifies the zone in a Global Cluster. This value can be used to configure Global Cluster backup policies.
Format should match the following pattern:
^([a-f0-9]{24})$
.
zoneName
string
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
.
retainBackups
boolean
Flag that indicates whether the cluster retains backups.
Default value is
false
.
rootCertType
string
Root Certificate Authority that MongoDB Atlas cluster uses. MongoDB Cloud supports Internet Security Research Group.
Value is
ISRGROOTX1
. Default value is
ISRGROOTX1
.
stateName
string
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
.
tags
array[object]
List that contains key-value pairs between 1 to 255 characters in length for tagging and categorizing the cluster.
Resource Tags
Hide tags attributes
Show tags attributes
object
Key-value pair that tags and categorizes a MongoDB Cloud organization, project, or cluster. For example,
environment : production
.
key
string
Required
Constant that defines the set of the tag. For example,
environment
in the
environment : production
tag.
Minimum length is
1
, maximum length is
255
.
value
string
Required
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
.
terminationProtectionEnabled
boolean
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
.
useAwsTimeBasedSnapshotCopyForFastInitialSync
boolean
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
.
versionReleaseSystem
string
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
.
400
application/json
Bad Request.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
401
application/json
Unauthorized.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
402
application/json
Payment Required.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
403
application/json
Forbidden.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
404
application/json
Not Found.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
409
application/json
Conflict.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
429
application/json
Too Many Requests.
Hide headers attributes
Show headers attributes
RateLimit-Limit
The maximum number of requests that a user can make within a specific time window.
RateLimit-Remaining
The number of requests remaining in the current rate limit window before the limit is reached.
Retry-After
The minimum time you should wait, in seconds, before retrying the API request. This header might be returned for 429 or 503 error responses.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
500
application/json
Internal Server Error.
Hide response attributes
Show response attributes
object
badRequestDetail
object | null
Bad request detail.
Hide badRequestDetail attribute
Show badRequestDetail attribute
object | null
fields
array[object]
Describes all violations in a client request.
Hide fields attributes
Show fields attributes
object
description
string
Required
A description of why the request element is bad.
field
string
Required
A path that leads to a field in the request body.
detail
string | null
Describes the specific conditions or reasons that cause each type of error.
error
integer(int32)
Required
HTTP status code returned with this error.
External documentation
errorCode
string
Required
Application error code returned with this error.
parameters
array[object]
Parameters used to give more information about the error.
reason
string | null
Application error message returned with this error.
POST
/api/atlas/v2/groups/{groupId}/clusters
Atlas CLI
Atlas CLI
Go
curl (Service Accounts)
curl (Digest)
atlas api clusters createCluster --help
import ( "os" "context" "log" sdk "go.mongodb.org/atlas-sdk/v20250312001/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.CreateGroupClusterApiParams{} sdkResp, httpResp, err := client.ClustersApi. CreateGroupClusterWithParams(ctx, params). Execute() }
curl --include --header "Authorization: Bearer ${ACCESS_TOKEN}" \ --header "Accept: application/vnd.atlas.2025-03-12+json" \ --header "Content-Type: application/json" \ -X POST "https://cloud.mongodb.com/api/atlas/v2/groups/{groupId}/clusters" \ -d '{ <Payload> }'
curl --user "${PUBLIC_KEY}:${PRIVATE_KEY}" \ --digest --include \ --header "Accept: application/vnd.atlas.2025-03-12+json" \ --header "Content-Type: application/json" \ -X POST "https://cloud.mongodb.com/api/atlas/v2/groups/{groupId}/clusters" \ -d '{ <Payload> }'
Request example
Cluster
{ "clusterType": "SHARDED", "name": "myCluster", "replicationSpecs": [ { "regionConfigs": [ { "analyticsAutoScaling": { "autoIndexing": { "enabled": false }, "compute": { "enabled": true, "maxInstanceSize": "M40", "minInstanceSize": "M30", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "analyticsSpecs": { "diskSizeGB": 10, "instanceSize": "M40", "nodeCount": 0 }, "autoScaling": { "autoIndexing": { "enabled": false }, "compute": { "enabled": true, "maxInstanceSize": "M60", "minInstanceSize": "M30", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "electableSpecs": { "diskSizeGB": 10, "instanceSize": "M60", "nodeCount": 3 }, "priority": 7, "providerName": "AWS", "readOnlySpecs": { "diskSizeGB": 10, "instanceSize": "M60", "nodeCount": 0 }, "regionName": "US_EAST_1" } ], "zoneName": "Zone 1" }, { "regionConfigs": [ { "analyticsAutoScaling": { "autoIndexing": { "enabled": false }, "compute": { "enabled": true, "maxInstanceSize": "M40", "minInstanceSize": "M30", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "analyticsSpecs": { "diskSizeGB": 10, "instanceSize": "M30", "nodeCount": 0 }, "autoScaling": { "autoIndexing": { "enabled": false }, "compute": { "enabled": true, "maxInstanceSize": "M60", "minInstanceSize": "M30", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "electableSpecs": { "diskSizeGB": 10, "instanceSize": "M40", "nodeCount": 3 }, "priority": 7, "providerName": "AWS", "readOnlySpecs": { "diskSizeGB": 10, "instanceSize": "M40", "nodeCount": 0 }, "regionName": "US_EAST_1" } ], "zoneName": "Zone 1" } ] }
Response examples (201)
# Headers # Payload { "acceptDataRisksAndForceReplicaSetReconfig": "2026-05-04T09:42:00Z", "adaptiveCapacity": "ENABLED", "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", "configServerType": "DEDICATED", "connectionStrings": { "awsPrivateLink": { "additionalProperty1": "string", "additionalProperty2": "string" }, "awsPrivateLinkSrv": { "additionalProperty1": "string", "additionalProperty2": "string" }, "private": "string", "privateEndpoint": [ { "connectionString": "string", "endpoints": [ { "endpointId": "string", "providerName": "AWS", "region": "string" } ], "srvConnectionString": "string", "srvShardOptimizedConnectionString": "string", "type": "MONGOD" } ], "privateSrv": "string", "standard": "string", "standardSrv": "string" }, "createDate": "2026-05-04T09:42:00Z", "diskWarmingMode": "FULLY_WARMED", "effectiveReplicationSpecs": [ { "id": "32b6e34b3d91647abb20e7b8", "regionConfigs": [ { "electableSpecs": { "diskSizeGB": 42.0, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10", "nodeCount": 3 }, "priority": 7, "providerName": "AWS", "regionName": "US_GOV_WEST_1", "analyticsAutoScaling": { "compute": { "enabled": true, "maxInstanceSize": "M10", "minInstanceSize": "M10", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "analyticsSpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "autoScaling": { "compute": { "enabled": true, "maxInstanceSize": "M10", "minInstanceSize": "M10", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "effectiveAnalyticsSpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "effectiveElectableSpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "effectiveReadOnlySpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "readOnlySpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" } } ], "zoneId": "32b6e34b3d91647abb20e7b8", "zoneName": "string" } ], "encryptionAtRestProvider": "NONE", "featureCompatibilityVersion": "string", "featureCompatibilityVersionExpirationDate": "2026-05-04T09:42:00Z", "globalClusterSelfManagedSharding": true, "groupId": "32b6e34b3d91647abb20e7b8", "id": "32b6e34b3d91647abb20e7b8", "internalClusterRole": "NONE", "labels": [ { "key": "string", "value": "string" } ], "links": [ { "href": "https://cloud.mongodb.com/api/atlas", "rel": "self" } ], "mongoDBEmployeeAccessGrant": { "expirationTime": "2026-05-04T09:42:00Z", "grantType": "CLUSTER_DATABASE_LOGS", "links": [ { "href": "https://cloud.mongodb.com/api/atlas", "rel": "self" } ] }, "mongoDBMajorVersion": "string", "mongoDBVersion": "string", "name": "string", "paused": true, "pitEnabled": true, "redactClientLogData": true, "replicaSetScalingStrategy": "WORKLOAD_TYPE", "replicationSpecs": [ { "id": "32b6e34b3d91647abb20e7b8", "regionConfigs": [ { "electableSpecs": { "diskSizeGB": 42.0, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10", "nodeCount": 3 }, "priority": 7, "providerName": "AWS", "regionName": "US_GOV_WEST_1", "analyticsAutoScaling": { "compute": { "enabled": true, "maxInstanceSize": "M10", "minInstanceSize": "M10", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "analyticsSpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "autoScaling": { "compute": { "enabled": true, "maxInstanceSize": "M10", "minInstanceSize": "M10", "scaleDownEnabled": true }, "diskGB": { "enabled": true } }, "effectiveAnalyticsSpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "effectiveElectableSpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "effectiveReadOnlySpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" }, "readOnlySpecs": { "diskSizeGB": 42.0, "nodeCount": 3, "diskIOPS": 42, "diskThroughput": 42, "ebsVolumeType": "STANDARD", "instanceSize": "M10" } } ], "zoneId": "32b6e34b3d91647abb20e7b8", "zoneName": "string" } ], "retainBackups": false, "rootCertType": "ISRGROOTX1", "stateName": "IDLE", "tags": [ { "key": "string", "value": "string" } ], "terminationProtectionEnabled": false, "useAwsTimeBasedSnapshotCopyForFastInitialSync": false, "versionReleaseSystem": "LTS" }
Response examples (400)
{ "detail": "(This is just an example, the exception may not be related to this endpoint) No provider AWS exists.", "error": 400, "errorCode": "VALIDATION_ERROR", "reason": "Bad Request" }
Response examples (401)
{ "detail": "(This is just an example, the exception may not be related to this endpoint)", "error": 401, "errorCode": "NOT_ORG_GROUP_CREATOR", "reason": "Unauthorized" }
Response examples (402)
{ "detail": "(This is just an example, the exception may not be related to this endpoint)", "error": 402, "errorCode": "NO_PAYMENT_INFORMATION_FOUND", "reason": "Payment Required" }
Response examples (403)
{ "detail": "(This is just an example, the exception may not be related to this endpoint)", "error": 403, "errorCode": "CANNOT_CHANGE_GROUP_NAME", "reason": "Forbidden" }
Response examples (404)
{ "detail": "(This is just an example, the exception may not be related to this endpoint) Cannot find resource AWS", "error": 404, "errorCode": "RESOURCE_NOT_FOUND", "reason": "Not Found" }
Response examples (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", "error": 409, "errorCode": "CANNOT_DELETE_ORG_ACTIVE_LIVE_MIGRATION_ATLAS_ORG_LINK", "reason": "Conflict" }
Response examples (429)
{ "detail": "(This is just an example, the exception may not be related to this endpoint)", "error": 429, "errorCode": "RATE_LIMITED", "reason": "Too Many Requests" }
Response examples (500)
{ "detail": "(This is just an example, the exception may not be related to this endpoint)", "error": 500, "errorCode": "UNEXPECTED_ERROR", "reason": "Internal Server Error" }
English
English
Português
Español
한국어
日本語
简体中文
© 2026 MongoDB, Inc.
About
Careers
Investor Relations
Legal
Privacy Policy
GitHub
Security Information
Trust Center
Follow Us
Support
Contact Us
Customer Portal
Atlas Status
Product Updates
Customer Support
Manage Cookies
Your Privacy Choices
Deployment Options
MongoDB Atlas
Enterprise Advanced
Community Edition
Data Basics
Vector Databases
NoSQL Databases
Document Databases
RAG Database
ACID Transactions
MERN Stack
Agent Memory
MEAN Stack
© 2026 MongoDB, Inc.
