Atlas M0 (Free Cluster), M2, and M5 Limitations
Configuration Limitations
The following table lists the configuration limitations of Atlas
M0
free clusters and M2/M5
shared clusters:
Configuration Option | Limitation |
---|---|
Cloud Service Provider and Region | You can deploy |
MongoDB Version and Storage Engine | Atlas uses MongoDB 6.0 for M0/M2/M5 clusters. |
MongoDB Version Upgrade | You can't upgrade the MongoDB version that M0/M2/M5 clusters
run. Atlas upgrades M0 free clusters or M2/M5
shared clusters to the newest MongoDB version after several
patch versions become available for that version. To learn more,
see MongoDB Versioning. |
Cluster Tier | You must select the M0 cluster tier to deploy a free cluster. |
Cluster Memory | You can't configure memory for M0 free clusters or M2/M5
shared clusters. |
Cluster Storage | You can't configure storage size for M0 free clusters or
M2/M5 shared clusters. |
Replication Factor | Replication Factor is set to 3 Nodes and you can't modify it
for M0 free clusters or M2/M5 shared clusters. |
Replica Set Tags | M0 free clusters and M2/M5 shared clusters don't
have pre-defined replica set tags. |
Do You Want A Sharded Cluster | You can't deploy a M0 free cluster or M2/M5 shared
cluster as a Sharded Cluster. |
Do You Want To Enable Backup | You can't enable backups on TipSee also:Backup Alternative: You may use mongodump to back up your data and mongorestore to restore that data. To learn how to manually back up your data, see Command Line Tools. |
Test Primary Failovers | You can't perform primary failover testing on M0 free clusters
or M2/M5 shared clusters. |
Simulate Regional Outage | You can't perform regional outage testing on M0 free clusters
or M2/M5 shared clusters. |
Database Auditing | You can't configure database auditing
on M0 free clusters or M2/M5 shared clusters. |
Encryption at Rest using your Key Management | You can't configure encryption at Rest using Customer Key
Management on M0 free clusters
or M2/M5 shared clusters. |
Network Peering Connections | You can't configure network peering connections
on M0 free clusters or M2/M5 shared clusters. |
Access Tracking | You can't view the database access history for M0
free clusters or M2/M5 shared clusters. |
Operational Limitations
The following table lists the operational limitations of Atlas
M0
free clusters and M2/M5
shared clusters:
Operation | Limitation | ||||||
---|---|---|---|---|---|---|---|
Aggregation and Queries | Atlas On On | ||||||
API Access | While you can create an NoteYou can create an | ||||||
Atlas Alerts |
| ||||||
Atlas Monitoring | The Metrics view of an
To learn more, see Real Time Metrics. | ||||||
Authentication |
| ||||||
Auto-Expand Storage | M0 free clusters and M2/M5 shared clusters don't
provide automatically scaling storage. | ||||||
BSON Nested Object Depth | M0 free clusters and M2/M5 shared clusters
can store documents with a maximum of 50 nested levels. | ||||||
Build Index with Rolling Build | M0 free clusters and M2/M5 shared clusters don't
support building indexes with a rolling build. | ||||||
Change Streams Filtering | For M0 free clusters and M2/M5 shared clusters,
you can use only strings and regular expressions in filters on
database names (namespace ns fields) in
change streams. You can't use commands,
such as $in , in database namespace filters. This limitation
doesn't apply to filtering on collection names in change streams. | ||||||
Cluster Persistence | Atlas may deactivate idle M0 free clusters as per
the Terms of Service. | ||||||
Command Line Tools |
For | ||||||
Connections | M0 free clusters and M2/M5 shared clusters can only
have a maximum of 500 connections. | ||||||
Cursors | Free clusters and shared clusters can't use the
noTimeout cursor option. | ||||||
Custom Roles | Changes to custom roles
might take up to 30 seconds to deploy in M0 free clusters
and M2/M5 shared clusters. | ||||||
Database and Collections | M0 free clusters and M2/M5 shared clusters can have
a maximum of 100 databases and 500 collections total. | ||||||
Database Commands | Certain database commands are unsupported or behave
differently in an M0 free cluster. To learn more, see
Command Limitations in Free Clusters.
For questions or comments related to restricted commands,
contact support. | ||||||
Access to Collections in local , admin , and config Databases |
Atlas issues an error similar to the following if you attempt to read or write to collections in these databases:
| ||||||
Database Logs | M0 free clusters and M2/M5 shared clusters don't
allow you to download logs. | ||||||
Data Recovery |
| ||||||
Data Transfer Limits |
Atlas handles clusters that exceed the rate limit as follows:
| ||||||
JavaScript | M0 free clusters and M2/M5 shared clusters don't
support server-side JavaScript. For example,
$where and
map-reduce are unsupported. | ||||||
Namespaces and Database Names | M0 free cluster and M2/M5 shared cluster namespaces
are limited to 95 bytes. Database names are limited to 38 bytes. | ||||||
Number of Free Clusters | You can deploy at most one M0 free cluster per Atlas
project. | ||||||
Performance Advisor | M0 free clusters and M2/M5 shared clusters don't
provide access to the Performance Advisor. | ||||||
Query Utilization | The percentage of time that a query is running over any five
minute period must remain under 100% on M0 free clusters
and M2/M5 shared clusters. | ||||||
Real-Time Performance Panel | M0 free clusters and M2/M5 shared clusters don't
provide access to the Real-Time Performance Panel. | ||||||
Sort in Memory | M0 free clusters and M2/M5 shared clusters
sort in memory limit is 32 MB. | ||||||
Throughput |
Atlas handles clusters that exceed the operations per second rate limit as follows:
| ||||||
Automatic Pause of Idle Clusters | Atlas automatically pauses M0 free clusters after
60 days of inactivity where there are zero connections to the
cluster. You can resume the cluster at
any time. |
Driver Minimum Requirements
Driver | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Drivers that use a JRE or JDK' | Due to an issue with TLS 1.3 support in the Java JDK' (JDK-8236039), upgrade the JDK' that supports the driver you use to connect to Atlas. Minimum versions of the JDK' include:
To learn more about support for TLS 1.3 in Java-based languages, libraries, and drivers, see: |