Pause, Resume, or Terminate a Cluster
On this page
You can pause, resume, or terminate your clusters. For serverless instances, see Terminate a Serverless Instance.
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
$searchqueries.Note
When you pause a cluster, Atlas deletes all data from the search nodes. Atlas automatically rebuilds the Atlas Search indexes when you resume the Atlas cluster.
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.
If a paused cluster doesn't have Encryption at Rest 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.
Required Access
To pause, resume, or delete a cluster, you must have Project Cluster Manager
access or higher to the project.
Pause One Cluster
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.
M0, M2, and M5 Clusters
Atlas automatically pauses all inactive M0, M2, and M5
clusters after 60 days.
M10+ 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.
M0 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't initiate a pause for M0 clusters.
Local Deployments
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
See: Related Links
Resume One Cluster
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.
Resume a Cloud Deployment
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.
Resume a Local Deployment with the Atlas CLI
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.
Tip
See: Related Links
Terminate One Deployment
Use the following resources to terminate a deployment.
Terminate a Cloud 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.
Terminate a Local Deployment with the Atlas CLI
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.