Docs Menu

Pause, Resume, or Terminate a Cluster

On this page

  • Considerations for Paused Clusters
  • Pause One Cluster
  • Resume One Cluster
  • Terminate One Cluster

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

  • You can't:

    • Modify the configuration of a paused cluster.
    • Read data from or write data to a paused cluster.
  • For paused clusters, Atlas:

    • Doesn't trigger configured alerts.
    • Stops all backups. Your existing snapshots remain until they expire.
Important
Serverless Instances are in Preview

Serverless instances are in preview and do not 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 initiate.

To pause a cluster with the Atlas API, see Modify a Cluster.

Important
Serverless Instances are in Preview

Serverless instances are in preview and do not support this feature at this time. To learn more, see Serverless Instance Limitations.

To resume a paused Atlas M0 cluster, connect to that cluster using the Atlas API, a Driver, mongosh, or Data Explorer.

To resume a paused Atlas M10+ cluster:

1
  1. If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
  2. If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
  3. If the Database Deployments page is not already displayed, click Databases in the sidebar.
2

For the cluster you want to pause, either:

  • Click , then click Resume, or
  • Click Resume.
Note

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

To terminate an Atlas cluster:

1
  1. If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
  2. If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
  3. If the Database Deployments page is not already displayed, click Databases in the sidebar.
2
3

Atlas terminates the cluster after completing any in-progress deployment changes.

Atlas bills for the hours that the cluster was active. To learn more about Atlas billing, see Billing.

Warning

Terminating a cluster also deletes any backup snapshots for that cluster. See Snapshot Schedule.

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 address, bound to its original cluster name.

The following time frames apply from the moment the user terminates 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 address to that cluster.

Cluster IP addresses don't change when clusters are paused then resumed.

Give Feedback
© 2021 MongoDB, Inc.

About

  • Careers
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2021 MongoDB, Inc.