Atlas limits how many of each kind of component you can create, and the number of connections allowed to a cluster based on cluster tier. These tables outline component and connection limits.
If any of these limits present a problem for your organization, please contact Atlas support.
Connection Limits and Cluster Tier¶
Atlas reserves a small portion of connections to each Atlas cluster for supporting Atlas services. Contact Atlas support for more information on Atlas reserved connections.
Collection and Index Limits¶
While there is no hard limit on the number of collections in a single cluster, the performance of a cluster might degrade if it serves a large number of collections and indexes. Larger collections have a greater impact on performance.
The recommended maximum combined number of collections and indexes by Atlas cluster tier are as follows:
5,000 collections and indexes
M20 / M30
10,000 collections and indexes
100,000 collections and indexes
Organization and Project Limits¶
Database Users per Atlas Project
Atlas Users per Atlas Project
Atlas Users per Atlas Organization
API Keys per Atlas Organization
Access List Entries per Atlas Project
Users per Atlas Team
Teams per Atlas Project
Teams per Atlas Organization
Teams per Atlas User
Organizations per Atlas User
Clusters per Atlas Project
Projects per Atlas Organization
Custom MongoDB roles per Atlas Project
Assigned Roles per Database User
Hourly Billing per Atlas Project
A Technical Account Manager or Billing Admin can raise this limit.
Data Lake Tenants per Atlas User
Total Network Peering Connections per Atlas Project
Pending Network Peering Connections per Atlas Project
AWS PrivateLink Addressable Targets per Region
Azure Private Link Addressable Targets per Region
Atlas also limits how long particular labels of components can be.
Character Length Limit
Atlas truncates the cluster name to 23 characters in its internal interactions. In practice, this means:
Latin alphanumeric characters only.
API Key Description