Docs Menu
Docs Home
/
MongoDB Atlas
/

Manage Serverless Instances (Deprecated)

On this page

  • Required Access
  • View Your Serverless Instances
  • Update Your 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. Atlas will automatically migrate all existing M2 and M5 clusters to Flex clusters. For Serverless instances, 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.

Use the following resources to configure and manage your Serverless instances.

To view or update your Serverless instances, you must have Project Read Only access or higher to the project.

To view all Serverless instances in the Atlas UI, see View All Cloud Clusters. To view the details for a Serverless instance, see View Cluster Details.

You can manage Serverless instances in the following ways:

Action
Description

Configure backup for your Serverless instance.

Add tags, view existing tags, and manage tags.

IMPORTANT: Don't include sensitive information such as Personally Identifiable Information (PII) or Protected Health Information (PHI) in your resource tags. Other MongoDB services, such as Billing, can access resource tags. Resource tags are not intended for private and sensitive data. To learn more, see Sensitive Information.

Terminate an existing Serverless instance.

Back

Pre-Defined Tags