On this page
Atlas offers the following resources to manage your Atlas clusters and serverless instances.
The Database Deployments view displays all clusters and serverless instances to which the user belongs.
The All Clusters page groups clusters and serverless instances under their Atlas project.
To filter the returned list of database deployments:
Use the search box. Enter the organization name, project name, or cluster/serverless instance name to limit returned database deployments to specific organizations, projects, or clusters/serverless instances.
Use the dropdown menus to limit the returned list using one or more of the following filters:MenuFilter PurposeMenu OptionsAvailabilityStatus of the nodes within the database deployment.
TypeDeployment type of database deployment.
Some Nodes Available
Has Warnings & Alerts
Version of MongoDB that the database deployments are running.
If the FCV of your cluster is set and if the FCV is below the MongoDB version of your cluster, the cluster in the Atlas UI Database Deployments page shows the
FCVof your cluster to reflect the features that are currently available on your cluster during the upgrade. After Atlas upgrades your cluster to the new version, the cluster in the Atlas UI Database Deployments page shows the new MongoDB version of your cluster.ConfigurationAdditional configuration options for the database deployment including authentication, backup, and TLS.
To display clusters that have not contacted Atlas in the last 6 months, click Show Inactive Clusters.
Atlas returns the following information for each database deployment:
Name of the database deployment.
MongoDB Version of the database deployment.
Size of the database deployment data.
Backup enabled status.
Number of nodes in the database deployment. This only displays for clusters.
SSL enabled status. This displays only for clusters.
Authentication required status. This displays only for clusters.
Number of open alerts. This displays only for clusters.
To return all Atlas deployments using the Atlas CLI, run the following command:
atlas deployments list [options]
To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas deployments list.
Through the Database Deployment Detail view, Atlas displays clusters and serverless instances grouped into their Project.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
If the Database Deployments page is not already displayed, click Database in the sidebar.
The Atlas consoles displays the following for database deployments in the selected project:
Metadata:FieldDescriptionDatabase Deployment NameName of the database deployment.VersionVersion of MongoDB that the database deployment runs.Cluster TierCluster tiers such as
M30, or the like (clusters only).RegionCloud region where Atlas hosts the database deployment.TypeType of structure for the cluster (i.e., Replica Set or Sharded Cluster), and number of nodes in the cluster (clusters only).Linked App Services AppName of the Atlas App Services application linked to this cluster, if appropriate (clusters only).
Read / write operations per second.
Number of open connections to the database deployment.
Logical size of database deployment data.
Database deployment disk IOPS (Available on M10+ clusters).
Atlas pauses monitoring for these metrics on
clusters without connection activity for seven days. Atlas
indicates which clusters fell into this state in the
Database Deployment Detail view. Atlas limits details
displayed for these clusters.
To resume monitoring, make a successful connection to the cluster using:
After you view your database deployments, you can:
Manage your Atlas clusters with cluster-specific options.
Manage your Atlas serverless instances with serverless-specific options.
Manage your Atlas Global Clusters. Atlas Global Clusters require that you define single or multi-region Zones. You can also shard global collections for global writes.