On this page
Use the following resources to configure and manage Atlas clusters. These settings don't apply to serverless instances.
View Your Clusters
Select Cluster Tier
Select your preferred cluster tier. The cluster tier dictates the memory, storage, and IOPS specification for each data-bearing server  in the cluster.
You might see different values depending on your selected cloud provider and region.
Use Shared clusters as economical clusters for getting started with MongoDB and for low-throughput applications. These clusters deploy to a shared environment with access to a subset of Atlas features. To learn more about shared cluster limitations, see Atlas M0 (Free Cluster), M2, and M5 Limitations.
You can deploy one
M0 cluster (free sandbox replica set
cluster) per Atlas project. You can upgrade
M0 free cluster to an
M2+ shared cluster at any time.
M5 clusters (low-cost shared clusters) provide the
following added features compared to
Backups for your cluster data
Atlas deploys MongoDB 5.0 for all shared clusters (
M5). However, Shared Clusters don't support all functionality in MongoDB version 5.0 and later. To learn more, see Atlas M0 (Free Cluster), M2, and M5 Limitations.
Atlas supports shared cluster deployment in a subset of cloud providers and regions. Atlas grays out any shared cluster tiers that the selected cloud service provider and region doesn't support. To learn more about the regions that support shared cluster deployments, see:
Dedicated Clusters for Low-Traffic Applications
M20 cluster tiers support development environments
and low-traffic applications.
These clusters support replica set deployments only, but otherwise provide full access to Atlas features.
M20 cluster tiers run on a burstable performance
Dedicated Clusters for High-Traffic Applications
M30+ cluster tiers support production environments with
high-traffic applications and large datasets.
These clusters support replica set and sharded cluster deployments with full access to Atlas features.
Some clusters have variants, denoted by the ❯ character. When you select these clusters, Atlas lists the variants and tags each cluster to distinguish their key characteristics.
For applications hosted on AWS or Azure that require low-latency and high-throughput I/O, Atlas offers storage options using locally attached ephemeral NVMe SSDs.
Atlas doesn't support NVMe clusters on Google Cloud.
The following cluster tiers support NVMe clusters on AWS:
The following cluster tiers support NVMe clusters on Azure:
Atlas supports NVMe clusters in the following Azure regions:
The fixed-value storage space and RAM for an NVMe cluster corresponds to its cluster tier. To learn more, see Amazon Cluster Configuration Options and Azure Cluster Configuration Options.
Clusters with NVMe storage use Cloud Backups. You can't disable backup on NVMe clusters. If you want to use hourly backups, Atlas limits backups on NVMe clusters to once every 12 hours.
NVMe clusters use a hidden secondary node that consists of a provisioned volume with high throughput and IOPS to facilitate backup.
You can't pause an NVMe cluster.
NVMe clusters auto-scale to the next higher tier when 90% of the available storage space is consumed, and the migration requires an initial sync.
NVMe Availability Zones
NVMe clusters in the following Azure regions have two Availability Zones:
NVMe clusters in all other Azure regions that indicate Availability Zones have three Availability Zones.
Free, Shared, and Dedicated Cluster Comparison
The following table highlights key differences between an
Tier cluster, an
M5 shared cluster, and an
M10+ dedicated cluster.
Free Cluster (
Shared Cluster (
Dedicated Cluster (
Storage (Data Size + Index Size)
10 - 4000 GB
MongoDB Version Support
4.2, 4.4, 5.0, Latest Release
Metrics and Alerts
Full metrics, including the Real Time Performance Tab, and full alert configuration options.
Global Region Selection
Atlas supports deploying
Atlas supports deploying
Atlas supports deploying clusters globally on Amazon Web Services, Google Cloud Platform, and Microsoft Azure
Yes, including queryable backups
Yes, for clusters using an
BI Connector for Atlas
For a complete list of M0 free cluster, M2, and M5 limitations, see Atlas M0 (Free Cluster), M2, and M5 Limitations.
|||For replica sets, the data-bearing servers are the servers hosting the replica set nodes. For sharded clusters, the data-bearing servers are the servers hosting the shards. For sharded clusters, Atlas also deploys servers for the config servers; these are charged at a rate separate from the cluster costs.|
Take the Next Steps
You can manage clusters in the following ways:
Customize the storage capacity of your cluster. Each cluster tier comes with a default set of resources.
Configure the cluster tier ranges that Atlas uses to automatically scale your cluster tier, storage capacity, or both in response to cluster usage.
Configure additional cluster settings such as MongoDB version, backup, and encryption options.
Reconfigure an existing cluster. Modify any of the available Atlas configuration options.
Manage major version upgrades for your cluster. Atlas enables you to upgrade the major version of an Atlas cluster at any time.
Configure maintenance windows for your cluster. You can set the hour of the day that Atlas should start weekly maintenance on your cluster.
Pause, resume, or terminate an existing cluster. You can't change the configuration of a paused cluster. Also, you can't read data from or write data to a paused cluster.
Configure multi-cloud distribution for increased availability. Atlas offers options to improve the availability and workload balancing of your cluster.
Use replica set tags to direct queries from specific applications to desired node types and regions. To use replica set tags in your connection string and direct queries to desired nodes, set the tag in the