Serverless Instance Limits

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.

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

Serverless instances support the following authentication methods only:

• Password (SCRAM-SHA-1)

• X.509 Certificates

• AWS IAM

Serverless instances don't support building indexes with a rolling build.

Serverless instances don't provide access to the Real-Time Performance Panel.

Serverless instances don't routinely cap operation throughput. Atlas may throttle operations for your Serverless instance temporarily while the system scales.

Serverless instances can support up to 500 simultaneous connections.

Serverless instances can't use the noTimeout cursor option.

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.

Atlas limits Serverless instance database names to 38 characters. In addition, namespace names (<database>.<collection>) cannot exceed 95 characters.

Serverless instances have a maximum of 50 databases and 500 collections total.

Changes to custom roles may take up to 30 seconds to deploy in Serverless instances.

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.

Serverless instances can't store documents with more than 50 nested levels.

Serverless instances support multi-document transactions that are up to 700 MB in size. Atlas aborts any Serverless instance transactions that exceed 700 MB.

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.

1.19.0

3.7.0beta1

2.13.0

1.6.0

4.3.0

4.10.0

2.5.0

4.1.0

3.12.0

2.16.0

2.1.0

4.3.0

1.2.0