Docs Menu

Docs HomeLaunch & Manage MongoDBMongoDB Atlas

Pause, Resume, or Terminate a Cluster

On this page

  • Considerations for Paused Clusters
  • Required Access
  • Pause One Cluster
  • Resume One Cluster
  • Terminate One Deployment

You can pause, resume, or terminate your clusters. For serverless instances, see Terminate a Serverless Instance.

To pause, resume, or delete a cluster, you must have Project Cluster Manager access or higher to the project.

Important

Feature unavailable in Serverless Instances

Serverless instances don't support this feature at this time. To learn more, see Serverless Instance Limitations.

Depending on your cluster tier, Atlas either pauses clusters automatically or when you manually initiate it.

Atlas automatically pauses all inactive M0 clusters after 60 days.

You can't pause M2 and M5 clusters. Atlas doesn't automatically pauses inactive M2 or M5 clusters.

You can pause M10 or larger clusters:

  • If they do not use NVMe storage.

  • For up to 30 days. If you don't resume the cluster within 30 days, Atlas resumes the cluster.

Atlas only charges paused clusters for storage. Atlas does not charge for any other services or data transfer on paused clusters.

Atlas automatically stops collecting monitoring information for an M0 cluster after a few days of inactivity.

If there is no activity for 60 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 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.

You can't initiate a pause for M0 clusters.

To pause the specified Atlas deployment using the Atlas CLI, run the following command:

atlas deployments pause <deploymentName> [options]

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas deployments pause.

Tip

Important

Feature unavailable in Serverless Instances

Serverless instances don't support this feature at this time. To learn more, see Serverless Instance Limitations.

Note

If you have a Backup Compliance Policy enabled, 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.

If you deployed search nodes separately, Atlas rebuilds the Atlas 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 M0 cluster paused for monitoring, connect to that cluster using a MongoDB Driver, mongosh, or Data Explorer.

To resume an Atlas M0 cluster that Atlas paused due to inactivity, or an Atlas M10+ cluster that you paused previously:

Note

If you don't resume an M10+ cluster within 30 days, Atlas resumes the cluster.

To start an Atlas deployment using the Atlas CLI, run the following command:

atlas deployments start <deploymentName> [options]

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas deployments start.

Use the following resources to terminate a deployment.

To terminate an Atlas cloud cluster:

Atlas terminates the cluster after completing any in-progress deployment changes. 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.

Warning

Terminating a cluster also deletes any backup snapshots for that cluster. See Snapshot Schedule. If you terminate a cluster with associated tags that don't apply to any other database deployment, Atlas deletes the tags. You can't restore these deleted tags.

To delete the specified Atlas deployment using the Atlas CLI, run the following command:

atlas deployments delete [deploymentName] [options]

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas deployments delete.

←  Configure Maintenance WindowConfigure High Availability and Workload Isolation →