> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt # Pause, Resume, or Terminate a Cluster You can pause, resume, or terminate your clusters, including Atlas Infinite clusters. See also [Terminate a Flex Cluster.](https://www.mongodb.com/docs/atlas/terminate-flex-clusters.md#std-label-terminate-flex-cluster) ## Considerations for Paused Clusters - You can't: - Change the configuration of a paused cluster. - Read data from or write data to a paused cluster. - Add or remove Search Nodes to a paused cluster. - For paused clusters, Atlas: - Stops triggering configured alerts. - Stops all backups. Your existing snapshots remain until they expire. - Stops all [`$search`](https://www.mongodb.com/docs/search/query/aggregation-stages/search.md#mongodb-pipeline-pipe.-search) queries. **Note:** This note applies to Atlas Core clusters. Search Nodes aren't supported on Atlas Infinite clusters in public preview. When you pause a cluster, Atlas deletes all data from the Search Nodes. Atlas creates new search nodes and automatically rebuilds the MongoDB Search indexes when you resume the Atlas cluster. While Atlas rebuilds the MongoDB Search indexes, the [`$search`](https://www.mongodb.com/docs/search/query/aggregation-stages/search.md#mongodb-pipeline-pipe.-search) and [`$vectorSearch`](https://www.mongodb.com/docs/vector-search/query/aggregation-stages/vector-search-stage.md#mongodb-pipeline-pipe.-vectorSearch) pipeline stages are unavailable. When you resume the cluster, Atlas only has metrics from the new search nodes as Atlas doesn't retain any MongoDB Search metrics from before you paused the cluster. - If you have a [Backup Compliance Policy enabled](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy), when you resume a cluster, Atlas automatically enables Cloud Backup. If the Backup Compliance Policy has the Require Point in Time Restore to all clusters option set to On, Atlas automatically enables Continuous Cloud Backup and adjusts the restore window according to the Backup Compliance Policy. Atlas automatically modifies the backup to meet the minimum requirements of the Backup Compliance Policy. On Atlas Core clusters, if you deploy Search Nodes separately, Atlas rebuilds the MongoDB Search indexes to restore the data on the Search Nodes that it deleted when you paused the Atlas cluster. - If a paused cluster doesn't have [Encryption at Rest](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption) enabled, you can't toggle the Require Encryption at Rest using Customer Key Management for all clusters option to On in a Backup Compliance Policy. - In certain scenarios, pausing a cluster pauses its required maintenance tasks. When you unpause the cluster, these maintenance tasks may start immediately, which could delay cluster availability. ## Required Access To pause or resume a cluster, you must have [`Project Cluster Manager`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Cluster-Manager) access or higher to the project. To terminate a cluster, you must have [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) or [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) access. ## Pause One Cluster ### Considerations - You can pause a cluster only if it's healthy. You can see an indication of a cluster's health in the Clusters view in the Atlas UI, and learn more about how cluster health is monitored by reviewing [important cluster metrics](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-important_cluster_metrics). You can retry pausing an unhealthy cluster after it returns to a healthy state. - You can pause a cluster only if its disk space usage is lower than 95%. To monitor disk space usage, see [Review Cluster Metrics.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics) Depending on your cluster tier, Atlas either pauses clusters automatically or when you manually initiate it. ### Free Clusters Atlas automatically pauses all inactive Free clusters (formerly known as `M0`) after 30 days. ### Flex Clusters You can't pause Flex clusters. Atlas doesn't automatically pause inactive Flex clusters. ### M10+ Clusters You can pause `M10` or larger clusters: - If they do not use [NVMe storage.](https://www.mongodb.com/docs/atlas/nvme-storage.md#std-label-nvme-storage) - For up to 30 days. If you don't resume the cluster within 30 days, Atlas resumes the cluster. **Note:** You must allow a recently [resumed](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-resume-cluster) cluster to run for at least 60 minutes before pausing the cluster again. This allows the cluster to process all the maintenance jobs that were queued while it was paused. Atlas only charges paused clusters for storage. Atlas does not charge for any other services or data transfer on paused clusters. ### Atlas CLI To pause a running Atlas cluster using the Atlas CLI, run the following command: ```sh atlas clusters pause [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas clusters pause.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-clusters-pause/) ### Free Clusters Atlas automatically stops collecting monitoring information for a Free cluster after a few days of inactivity. If there is no activity for 30 days, then Atlas automatically pauses the cluster completely, disallowing any connections to it until you resume the cluster. Atlas sends an email seven days before pausing the cluster. Atlas sends another email after pausing the cluster. You can [resume](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-resume-cluster) the cluster at any time *unless* the paused cluster was running on an old version that Atlas can't restore to the current version. You should export a copy of your data if you don't plan to use your Free cluster for an extended period of time. To learn more, see [Restore Data From Paused Free Cluster.](https://www.mongodb.com/docs/atlas/backup/restore-free-tier-cluster.md#std-label-restore-free-tier-cluster) You can't initiate a pause for Free clusters. ### Local Deployments To pause the specified Atlas deployment using the Atlas CLI, run the following command: ```sh atlas deployments pause [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas deployments pause.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-deployments-pause/) ## Resume One Cluster **Important: Feature unavailable in Flex Clusters** Flex clusters don't support this feature at this time. To learn more, see [Atlas Flex Limitations.](https://www.mongodb.com/docs/atlas/reference/flex-limitations.md#std-label-flex-cluster-limitations) **Note:** If you have a [Backup Compliance Policy enabled](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy), when you resume a cluster, Atlas automatically enables Cloud Backup. If the Backup Compliance Policy has the Require Point in Time Restore to all clusters option set to On, Atlas automatically enables Continuous Cloud Backup and adjusts the restore window according to the Backup Compliance Policy. Atlas automatically modifies the backup to meet the minimum requirements of the Backup Compliance Policy. On Atlas Core clusters, if you deploy Search Nodes separately, Atlas rebuilds the MongoDB Search indexes to restore the data on the Search Nodes that it deleted when you paused the Atlas cluster. To resume collection of monitoring information for an Atlas Free cluster paused for monitoring, connect to that cluster using a [MongoDB Driver](https://www.mongodb.com/docs/atlas/driver-connection.md#std-label-connect-via-driver), [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh), or [Data Explorer.](https://www.mongodb.com/docs/atlas/atlas-ui.md#std-label-atlas-ui) ### Resume a Cloud Deployment To resume an Atlas `M10+` cluster that you paused previously: ### Atlas CLI To start a paused Atlas cluster using the Atlas CLI, run the following command: ```sh atlas clusters start [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas clusters start.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-clusters-start/) **Note:** If you don't resume an `M10+` cluster within 30 days, Atlas resumes the cluster. ### Resume a Local Deployment with the Atlas CLI To start an Atlas deployment using the Atlas CLI, run the following command: ```sh atlas deployments start [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas deployments start.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-deployments-start/) ## Terminate One Deployment Use the following resources to terminate a deployment. ### Terminate a Cloud Deployment To terminate an Atlas cloud cluster: ### Atlas CLI **Note:** If you enabled Termination Protection on your cluster, you must first disable it. To delete one cluster in the specified project using the Atlas CLI, run the following command: ```sh atlas clusters delete [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas clusters delete.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-clusters-delete/) Atlas terminates the cluster after completing any in-progress deployment changes. On Atlas Core clusters, Atlas also terminates all Search Nodes configured for the cluster. Atlas bills for the hours that the cluster was active. To learn more about Atlas billing, see [Manage Billing.](https://www.mongodb.com/docs/atlas/billing.md#std-label-atlas-billing) **Warning: Deleting Search Indexes and Clusters Is Irreversible** Terminating a cluster also deletes any backup snapshots for that cluster. See [Backup Scheduling, Retention, and On-Demand Snapshots](https://www.mongodb.com/docs/atlas/backup/cloud-backup/scheduling.md#std-label-cloud-provider-retention-policy). If you terminate a cluster with associated [tags](https://www.mongodb.com/docs/atlas/tags.md#std-label-configure-resource-tags) that don't apply to any other cluster, Atlas deletes the tags. You can't restore these deleted tags. Deleting Search indexes and associated clusters is a permanent action. MongoDB doesn't provide support for recovering deleted Search indexes or data. Ensure that you have taken appropriate measures, such as creating backups, to avoid data loss before proceeding. MongoDB doesn't support requests to recover deleted Search indexes or data. You are responsible for data integrity and configurations. ### M10+ **Note: Public IP Address Retention** When you terminate a cluster with a lifetime of 12 hours or more, Atlas reserves the cluster's public IP (Internet Protocol) address, bound to its original cluster name. The following time frames apply from the moment you terminate the cluster: | Cluster Lifetime | IP Address Retention | | --- | --- | | Less than 12 hours | Not retained | | 12 to 35 hours | 12 to 35 hours (equal to the cluster lifetime) | | 36 hours or more | 36 hours | If, in the applicable time frame, you create a new cluster with the same name, Atlas reassigns the reserved public IP (Internet Protocol) address to that cluster. cluster IP (Internet Protocol) addresses don't change when you or Atlas pause or resume clusters. ### Terminate a Local Deployment with the Atlas CLI To delete the specified Atlas deployment using the Atlas CLI, run the following command: ```sh atlas deployments delete [deploymentName] [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas deployments delete.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-deployments-delete/)