Docs Menu
Docs Home
/
MongoDB Atlas
/
Reference
/
Limits

Serverless Instance Limits

On this page

  • Unsupported Configurations
  • Unsupported Actions
  • Operational Limitations and Considerations
  • Minimum Driver Versions for Serverless Instances
  • Minimum mongosh Version for Serverless instances
  • Minimum MongoDB Compass Version for Serverless instances
  • Minimum MongoDB Tools Version for Serverless instances
  • Private Endpoints for Serverless Instances

Serverless instances don't currently support the Atlas features listed below. If you require these capabilities, please use a dedicated cluster.

Serverless instances don't support some features even though they are a part of the Stable API v1. We note unsupported features that are a part of the Stable API v1 inline.

MongoDB plans to add support for more configurations and actions on Serverless instances over time. Footnotes indicate that MongoDB plans to support the feature for Serverless instances in the future.

Unsupported Configurations

Currently, Serverless instances don't support the following configurations:

Unsupported Actions

Currently, Serverless instances don't support the following actions:

  • Convert Atlas Serverless instances into clusters. [1]

  • Convert Atlas dedicated clusters into Atlas Serverless instances

    You can convert a shared cluster to a Serverless instance.

  • Live migrate into Atlas Serverless instances.

  • Store more than 1 TB of data.

    This value includes the number of bytes of all uncompressed BSON documents stored in all collections, plus the bytes stored in their associated indexes.

  • Perform automated restores from backup snapshots.

  • Use Atlas Search.

  • Use Online Archive.

  • Use Atlas Device Sync.

  • Use triggers.

  • Use predefined replica set tags.

  • Test primary failover.

  • Simulate a regional outage.

  • Encryption at Rest using key management.

  • Track database access.

  • Use server-side JavaScript, such as $where, $function, $accumulator and map-reduce.

    Serverless instances don't support these features even though they're a part of the Stable API v1.

  • Download database logs.

  • Use wire compression between clients and Atlas Serverless instances.

  • Use BI Connector.

[1] Coming soon.

Operational Limitations and Considerations

Additionally, Serverless instances have the following operational limitations and considerations:

Operation
Limitation

Serverless instances don't support the allowDiskUse option for the aggregation command, its helper method, or the cursor.allowDiskUse() query cursor method.

Serverless instances don't support the $out stage. Use $merge instead.

Aggregation fields on Serverless instances that represent database and collection names (such as $merge values) can't be expressions.

Serverless instances don't support these features even though they're a part of the Stable API v1.

Aggregation pipelines for Serverless instances don't support the $currentOp, $listLocalSessions, $listSessions, and $planCacheStats stages.

Aggregation pipelines for Serverless instances can have a maximum of 50 stages.

Sort
The $sort stage has a limit of 32 megabytes of RAM.
Authentication

Serverless instances support the following authentication methods only:

  • Password (SCRAM-SHA-1)

  • X.509 Certificates

  • AWS IAM

Build Index with Rolling Build
Serverless instances don't support building indexes with a rolling build.
Real-Time Performance Panel
Serverless instances don't provide access to the Real-Time Performance Panel.
Throughput
Serverless instances don't routinely cap operation throughput. Atlas may throttle operations for your Serverless instance temporarily while the system scales.
Connections
Serverless instances can support up to 500 simultaneous connections.
Cursors
Serverless instances can't use the noTimeout cursor option.
Database Commands

Some database commands have limitations for Serverless instances. To learn more, see Unsupported Commands in Serverless Instances.

You cannot create a capped collection or convert an existing collection to a capped collection.

Namespaces and Database Names
Atlas limits Serverless instance database names to 38 characters. In addition, namespace names (<database>.<collection>) cannot exceed 95 characters.
Database and Collections
Serverless instances have a maximum of 50 databases and 500 collections total.
Custom Roles
Changes to custom roles may take up to 30 seconds to deploy in Serverless instances.
Access to Collections in local, admin, and config Databases

Serverless instances don't allow:

  • Read access to the oplog or any other collection in the local database.

  • Write access to any collection in the local and config databases.

  • Read or write access to any collection in the admin database.

Atlas issues an error similar to the following if you attempt to read or write to collections in these databases:

command <cmd name> is not allowed in this Atlas tier
(Unauthorized) not authorized on <db name> to execute command
<cmd name>

Serverless instances don't support change streams.

Serverless instances don't support this feature even though it's a part of the Stable API v1.

Serverless instances don't support collation on collections, indexes, or queries.

Serverless instances don't support these features even though they're a part of the Stable API v1.

BSON Nested Object Depth
Serverless instances can't store documents with more than 50 nested levels.
Transaction Size
Serverless instances support multi-document transactions that are up to 700 MB in size. Atlas aborts any Serverless instance transactions that exceed 700 MB.
Write Concern

Serverless instances don't support a numeric write concern level greater than 1, or custom write concerns. Operations that use a write concern level greater than 1, or custom write concerns, might return an UnsatisfiableWriteConcern error. This behavior also applies to operations sent over a connection created with a write concern option.

For clusters other than M0, M2, or M5 clusters, you can verify whether you're using a write concern mode that Serverless instances don't support with the serverStatus command's opWriteConcernCounters field.

Minimum Driver Versions for Serverless Instances

To connect to your Serverless instance using a driver, you must use at least one of the following versions:

Driver
Version
1.19.0
3.7.0beta1
2.13.0
1.6.0
4.3.0
4.10.0
2.5.0
4.1.0
1.11.0 (Extension)
1.10.0 (Library)
3.12.0
2.16.0
2.1.0
4.3.0
1.2.0

Minimum mongosh Version for Serverless instances

To connect to Serverless instances using mongosh, you must use version 1.0.0 or later.

Important

You can't connect to Serverless instances using the legacy mongo shell.

Minimum MongoDB Compass Version for Serverless instances

To connect to Serverless instances using MongoDB Compass, you must use version 1.28 or later.

Minimum MongoDB Tools Version for Serverless instances

To import data using the MongoDB Tools, including mongodump, mongorestore, mongoexport, and mongoimport, you must have MongoDB Tools version 100.10.0 or later.

Private Endpoints for Serverless Instances

You can connect up to two private endpoints per Serverless instance. To learn more about private endpoints, see Learn About Private Endpoints in Atlas.

Back

Atlas Flex Limits

Next

M0, M2, and M5 Limits