Terminate Serverless Instances (Deprecated)
Terminate One Serverless Instance
Important
As of February 2025, you can create Flex clusters, and can no longer
create M2 and M5 clusters or Serverless instances in the
Atlas UI, Atlas CLI, Atlas Administration API, Atlas Kubernetes Operator, HashiCorp Terraform,
or Atlas CloudFormation Resources.
You can still use existing M2 and M5 clusters and Serverless instances.
Atlas deprecated M2 and M5 clusters and Serverless instances.
Beginning April 2, 2025, Atlas will automatically migrate all existing
M2 and M5 clusters to Flex clusters.
For Serverless instances, beginning May 5 2025, Atlas will determine whether to migrate instances to Free clusters, Flex clusters, or Dedicated clusters according to your usage. To see which tiers Atlas will migrate your instances to, consult the All Clusters page in the Atlas UI.
To terminate an Atlas Serverless instance using the Atlas UI:
In Atlas, go to the Clusters page for your project.
Warning
Navigation Improvements In Progress
We're currently rolling out a new and improved navigation experience. If the following steps don't match your view in the Atlas UI, see the preview documentation.
If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
If it's not already displayed, click Clusters in the sidebar.
The Clusters page displays.
Warning
If you terminate a Serverless instance with associated tags that don't apply to any other cluster, Atlas deletes the tags. You can't restore these deleted tags.
Atlas terminates the Serverless instance after completing any in-progress deployment changes.
Atlas bills for the operations performed while the Serverless instance is active. To learn more about Atlas billing, see Manage Billing.