Can I bring an existing MongoDB deployment into MongoDB Atlas for management?

No. However, you can upload data from existing MongoDB deployment into MongoDB Atlas.

  • You can use the Live Migrate feature in Atlas to migrate from a source replica set to an Atlas replica set cluster.
  • You can use the Live Migrate feature in Atlas to migrate from a source sharded cluster to an Atlas sharded cluster.
  • You can use mongomirror to migrate data from an existing MongoDB replica set into MongoDB Atlas.
  • You can use mongodump and mongorestore to seed MongoDB Atlas clusters from an existing standalone, replica set, and sharded cluster .

For information, see Import Data into Cluster.

You can also write scripts using official MongoDB supported drivers to upload data.

Which versions of MongoDB does Atlas use for the clusters?

Atlas supports creating M10+ paid tier clusters with the following MongoDB versions:

  • MongoDB 3.4
  • MongoDB 3.6
  • MongoDB 4.0

MongoDB Server 3.2 is planned for End of Life on September 2018. Atlas deprecated support for deploying clusters with MongoDB 3.2 in March, 2018.

M0 Free Tier and M2/M5 shared tier clusters built after April 23, 2018 only support MongoDB 3.6.

As new maintenance releases become available, Atlas automatically upgrades to these releases via a rolling process to maintain cluster availability.

Can I migrate between regions?

Yes. You can change one or more regions for a given cluster within the original cloud service provider for that cluster. Using a rolling-migration strategy for moving nodes from the original region to a new region, MongoDB Atlas preserves cluster availability.

AWS Only

Amazon Web Services (AWS) Virtual Private Cloud (VPC) peering connections are region-specific. Clusters utilizing an existing VPC peering connections to an AWS VPC in a given AWS region lose access to that peering connection if moved to a different AWS region. AWS does not support VPC peering connections between different regions. See Set up VPC Peering Connection for complete documentation.

If you need to migrate data between regions on different cloud service providers, you can:

Do you support cross-region deployments?

Yes. You can specify additional regions for high availability or local reads when creating or scaling a deployment.

Atlas does not support cross-cloud service provider deployments.

What AWS Regions does Atlas support?

Atlas supports all AWS regions other than those in China and US GovCloud. For more information, see Amazon Web Services.

How does MongoDB Atlas deliver high availability?

Atlas clusters use MongoDB’s replication capability to deliver high availability. All Atlas clusters are either replica sets or sharded clusters where each shard is a replica set. For complete documentation on MongoDB replica sets and replication, see Replication.

Atlas uses a rolling upgrade strategy for executing maintenance or infrastructure operations, such as applying security patches or scaling up a Atlas cluster. The rolling upgrade strategy ensures that the cluster can process reads and writes for the majority of the maintenance or infrastructure operation. During the rolling upgrade procedure:

  • Atlas applies the changes to each secondary node in the cluster.
  • Atlas directs the primary node to step down to the secondary state and trigger an election of a new primary.
  • Once the cluster has a new primary, Atlas applies the changes to the former primary node.

Applications must hold write operations while the cluster elects a new primary. The cluster can continue to process secondary read operations during this period. Elections on Atlas clusters typically complete within a few seconds. Factors such as network latency may extend the time required for replica set elections to complete, which in turn affects the amount of time your cluster may operate without a primary. These factors are dependent on your particular cluster architecture.

Retryable Writes with MongoDB 3.6

MongoDB 3.6+ drivers can automatically retry certain write operations a single time. Retryable writes provide built-in handling of automatic failovers and elections. The cluster must run MongoDB 3.6 or greater to support retryable writes. See retryable writes for complete documentation and requirements.

To enable this feature, add retryWrites=true to your Atlas URI connection string. See Connect via Driver for details on connecting to a Atlas cluster using a URI connection string.

For M10+ clusters, Atlas provides a Test Failover feature for application developers to check that their applications are designed to detect and react appropriately to a replica set election. By designing applications that can seamlessly handle a replica set election, developers no longer have to worry about the underlying maintenance occurring on their clusters.

Atlas maintenance operations include OS patches and maintenance patches for the MongoDB database itself (e.g. v3.6.3 to v3.6.4). Infrastructure operations include repair operations required to replace faulty infrastructure, and scheduled infrastructure replacements such as changing the cluster size.

Please contact MongoDB support if you would like help architecting your application to use MongoDB Atlas with optimal availability.

How can I pay for MongoDB Atlas without a credit card?

For alternative ways of purchasing Atlas, please contact MongoDB Inc..

Can I specify my own VPC for my MongoDB Atlas project?

No. An Atlas project, and its clusters, are associated with a region-specific Virtual Private Cloud (VPC).

Atlas creates a VPC when you deploy the first M10+ dedicated paid cluster to a given provider and region. For multi-region clusters, Atlas creates one VPC per region if there is not already a VPC for that region.

(AWS deployments only) Atlas also creates a VPC when you create a VPC peering connection to an AWS VPC. Atlas creates the VPC in the same region as the peered VPC.

To use a different VPC (e.g. on the customer’s own cloud infrastructure accounts), you would need to use MongoDB Cloud Manager or Ops Manager.

MongoDB Atlas or MongoDB Cloud Manager?

Atlas offers a managed and simplified experience. Atlas users have access to a curated selection of configuration and infrastructure options. The available Atlas configuration and infrastructure options may not provide the flexibility that some users require. For example, Atlas requires TLS for cluster connectivity and does not surface options for disabling TLS. Atlas is best suited for users who want fewer moving parts to manage, enabling developers and database administrators to be more productive.

MongoDB Cloud Manager offers more control by exposing more configuration options on the infrastructure of your choice. Cloud Manager users have access to advanced operations and a higher level of control, but must manage the full lifecycle of their infrastructure. Cloud Manager is best suited for users who require a higher level of control over their MongoDB clusters.

Please contact MongoDB support for guidance on which MongoDB service best suits the needs of your organization.

As an existing MongoDB Cloud Manager account holder, how do I create a new MongoDB Atlas project?

In the Context drop down in Cloud Manager, select New Project.

The Create a New Project screen provides you the choice to create either an Atlas project or a Cloud Manager project. Select MongoDB Atlas and continue with the creating the project.

As an existing Atlas account holder, how do I create a new Atlas project?

In the Context drop down in Cloud Manager, select New Project.

The Create a New Project screen provides you the choice to create either an Atlas project or a Cloud Manager project. Select MongoDB Atlas and continue with the creating the project.

Can I disable SSL/TLS on my deployment?


How do I remove my project?

You can remove a project if:

  • You have the Project Owner role for the project.
  • The project has no outstanding invoices.
  • The project has no active clusters.

To delete a project for an organization, you can delete from the organization’s Projects view or the project’s Project Setting view. For details, see Delete a Project.

Can I pause or stop my Atlas clusters?

You can pause an M10+ paid cluster for up to 7 days at a time. Atlas automatically resumes the cluster after 7 days. For complete documentation, see Pause a Cluster.

How do I modify alerts?

To modify an existing alert settings, go to Alerts and select Alert Settings. Click the ellipsis ... to modify (edit, clone, disable, delete) the setting for an active Alerts.

Does MongoDB Atlas expose the oplog?

Yes. To access the oplog, a database user must have read access on the local database. To create a user with read access on local:

  1. Click Clusters, then Security.
  2. Click Add New User and enter a user name. For example, “oploguser”.
  3. Click Show Advanced Options and select the read role and the local database. This restricts the user to read operations on the local database.
  4. Enter a password and click Add User.


To increase the size of an oplog for a cluster, click Support in the Atlas navigation pane and file a help ticket with the following information:

  • The name of and URL for the Atlas cluster,
  • The desired oplog size, and
  • The use case that requires a larger oplog.

Can MongoDB Atlas deploy clusters with more than 24 shards?

While MongoDB Atlas out of the box allows selection of up to 24 shards, customers interested in more than 24 shards should inquire with MongoDB. Contact us at

How does Atlas encrypt my data?

Atlas uses whole volume (disk) encryption for any data at rest, including your cluster data and backups of that data.

Atlas also requires TLS encryption for client data and intra-cluster network communications.

If your organization requires more specific information regarding Atlas encryption, please contact Atlas support. From the Atlas project or cluster view, click Support in the left-hand navigation bar.

Can I pre-split chunks in a Atlas sharded cluster?

The Atlas admin MongoDB user role has the necessary privileges to pre-split chunks in an empty sharded collection.

See Create Chunks in a Sharded Cluster for complete documentation on sharded cluster chunk creation and management.

Where can I view the system status of the MongoDB Cloud?

Visit for the status of the MongoDB Cloud, including Atlas and Cloud Manager.

You can also subscribe to an RSS feed of the MongoDB Cloud Status page using your preferred RSS reader.

I have a cluster running MongoDB 3.2. How does the upcoming End of Life affect me?

MongoDB Server 3.2 is planned for End of Life on September 2018. Atlas deprecated support for deploying clusters with MongoDB 3.2 in March, 2018.

Atlas will automatically upgrade any clusters running MongoDB 3.2 to MongoDB 3.4 in September 2018. Project Owners can upgrade their MongoDB 3.2 clusters at any time before then.

To prepare for upgrading your cluster from MongoDB 3.2 to MongoDB 3.4 or greater, do the following:

  • Read the Release Notes for MongoDB Server 3.4.
  • Read the Compatibility Changes for MongoDB Server 3.4.
  • Check that your application’s MongoDB driver version is compatible with MongoDB 3.4.
  • Upgrade your application’s MongoDB driver to the latest version that supports MongoDB 3.4.
  • Use the Test Failover feature to test application resilience to elections. Atlas uses a rolling strategy to support high cluster availability when performing the major MongoDB version change. The rolling upgrade procedure requires at least one election per replica set.

For guidance on performing the major version change upgrade yourself, see Atlas Major Version Change Procedure for a MongoDB-recommended procedure. This procedure includes creating a staging cluster for the purpose of testing and validating application and cluster performance and functionality on the new MongoDB version.

To contact Atlas support with questions, comments, or concerns regarding the 3.2 End of Life and planned upgrade, select Support in the left-hand navigation of the Atlas UI.

What versions of TLS does Atlas support?

Atlas deployments created after July 2018 support only Transport Layer Security (TLS) protocol versions 1.1 and 1.2 by default. Atlas deployments created before July 2018 support TLS protocol version 1.0, 1.1, and 1.2 by default. After August 2018, Atlas will support only TLS 1.1 and 1.2 by default for all Atlas clusters.

Deprecating TLS 1.0 improves your security of data-in-transit and aligns with industry best practices. This is why MongoDB 4.0 requires TLS 1.1 or later when TLS is enabled. As Atlas requires TLS connections for all Atlas clusters, Atlas clusters running MongoDB 4.0 always use TLS 1.1 or later by default.

You can read more about timing and reasons for the change from the Payment Card Industry (PCI) as well as the National Institute of Standards and Technology (NIST).

If you have questions about TLS support or cannot update your applications to support TLS 1.1 or later by late August 2018, please contact Atlas support.

To open a Atlas support ticket, log into the your Atlas account. Click the Support link in the Atlas UI and fill in the requested details.

How do I know if my applications support TLS 1.1 or later?

TLS 1.1 was defined in April 2006. Applications whose underlying programming languages or security libraries predate TLS 1.1 may require updating to a more recent version to support TLS 1.1 or later. You may also need to update the application host operating system to support TLS 1.1 or later.

MongoDB and Atlas do not provide services to audit external applications for which versions of TLS support they support. Third party services such as may provide the appropriate tooling. MongoDB does not endorse the aforementioned service, and its reference is intended only as informational. Defer to your organization’s procedures in selecting the appropriate vendor or service for auditing your applications to ensure TLS 1.0 is disabled.

What do I have to do to update my clusters for TLS 1.1 or later?

Atlas will automatically update your existing clusters to only support TLS 1.1 or later in late August 2018. The only thing you should consider doing is auditing your applications for support of TLS 1.1 or later and updating any components of your technology stack that do not support TLS 1.1 or later.

Can I force enable TLS 1.0?

Atlas allows users to manually enable TLS 1.0 during cluster creation and cluster modification.

Enabling TLS 1.0 for any Atlas cluster carries significant risks. Consider enabling TLS 1.0 only for as long as required to update your application stack to support TLS 1.1 or later.

What happens when I reach my Atlas storage limit?

The result of reaching your Atlas storage limit depends on the Atlas tier you are using.

  • For shared clusters (M0, M2, M5), the maximum storage is a hard limit and cannot be exceeded. You can add additional storage by upgrading to a dedicated cluster (M10+). For details on how Atlas calculates storage limits for shared clusters, see this section of the FAQ.
  • By default, M10+ clusters auto-expand storage based on disk usage thresholds. To modify this setting to a fixed storage limit, refer to the Modify a Cluster page.

If you attempt to write to a shared cluster that does not have space for the desired write operation, Atlas displays an error message similar to the following:

  "writeError": {
    "code": 8000,
    "errmsg": "you are over your space quota, using 513 MB of 512 MB"

For more information on the differences between shared and dedicated clusters, see Atlas M0 (Free Tier), M2, and M5 Limitations.


You can configure alerts which trigger once your allocated storage reaches a specified threshold. Atlas calculates allocated storage using metrics returned by the dbStats() command. For information on storage alerts, see DB Storage alert conditions.

How does Atlas calculate storage limits for shared clusters (M0, M2, M5)

Atlas calculates the storage limit for shared clusters based on data usage, as opposed to the storageSize metric used by non-shared clusters (which includes compression). Atlas determines data usage by summing a cluster’s dataSize and indexSize. You can issue the db.stats() method to view the values of these fields.

How do I get support for my Atlas clusters?

Atlas provides support for the use of the service itself. Support for development and performance of the database itself requires a MongoDB subscription. For details, contact MongoDB Inc..

You can open support tickets from the Atlas UI. Log in to your Atlas account and navigate to the organization or project for which you have a question, comment, or concern. From the navigation bar, click Support to open the support ticket form. Fill in the information as requested, and an Atlas technical support engineer will reach out to you.

How do I delete my user account?

Open an Atlas support ticket to delete your Atlas account.

←   Billing API  →