Atlas Infinite fixed per-tier IOPS and public-preview feature exclusions
Parent: Cluster Tier Limits and Feature Gates as Cost Drivers (Connections, IOPS Caps, Minimum Tiers) · Published reference · snapshot 2026-10-23 · skill mongodb-cohort-88cc8939dcad
↓ Facts as markdownall context files
Source-anchored research for Atlas Infinite fixed per-tier IOPS and public-preview feature exclusions. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Structure and components
- The public-preview overview excludes Atlas Kubernetes Operator, although the generated Operator API documentation contains databaseEdition=INFINITE and Infinite-specific storage fields. Schema presence alone does not establish supported Operator operation. (medium confidence) (verified as of 2026-10-23) [source]
Measurements and reference values
- The public-preview General tier table specifies M10: 625 IOPS / 10 MBps; M20: 1,250 / 20; M30: 5,000 / 80; M40: 9,375 / 150; M50: 18,750 / 300; and M60: 37,500 / 600. (low confidence) (verified as of 2026-10-23) [source]
- The public-preview Low-CPU table specifies M40: 5,000 IOPS / 80 MBps; M50: 9,375 / 150; and M60: 18,750 / 300. Class therefore matters when interpreting a tier name. (low confidence) (verified as of 2026-10-23) [source]
- The published Infinite IOPS figures assume a 16 kB I/O size and are reference baselines; maximum achieved IOPS varies with workload characteristics. They do not establish an index-build duration or throughput guarantee. (medium confidence) (verified as of 2026-10-23) [source]
- The preview reference lists General tier storage IOPS / throughput as M10: 625 / 10 MBps; M20: 1,250 / 20 MBps; M30: 5,000 / 80 MBps; M40: 9,375 / 150 MBps; M50: 18,750 / 300 MBps; M60: 37,500 / 600 MBps. Low-CPU values are M40: 5,000 / 80 MBps; M50: 9,375 / 150 MBps; M60: 18,750 / 300 MBps. (low confidence) (verified as of 2026-10-23) [source]
Problems, failure modes and limitations
- Infinite public preview excludes live migration and backup/restore between Atlas Core and Infinite, and a created cluster cannot switch database edition in either direction. (medium confidence) (verified as of 2026-10-23) [source]
- Infinite public preview excludes the database profiler and MongoDB log downloads or external log synchronization. mongostat provides incomplete metrics, and mongotop --locks returns an error. (low confidence) (verified as of 2026-10-23) [source]
- For index-build planning, increasing the amount of stored data must not be assumed to increase the storage I/O budget at a fixed Infinite tier. This is a capacity-planning inference from the documented tier-bound performance model, not a measured index-build concurrency limit. (medium confidence) (verified as of 2026-10-23) [source]
- ByteDiagram independently frames tier-bound IOPS as an architecture-review pitfall, and The Weighted Average distinguishes published throughput specifications from application measurements. Both derive product facts from MongoDB material; they are separate editorial analyses, not independent verification of vendor limits. (medium confidence) (verified as of 2026-09-30) [source]
Comparisons and alternatives
- Infinite public preview excludes Atlas Kubernetes Operator, Charts, MongoDB for VS Code, MongoDB MCP Server and MongoDB Agent Skills, and carries no uptime SLA. (low confidence) (verified as of 2026-10-23) [source]
- Other preview exclusions include Online Archive, locally attached NVMe, Charts, MongoDB for VS Code, MongoDB MCP Server, MongoDB Agent Skills, log downloads/syncs and the database profiler. Customer-managed keys support AWS KMS only, excluding Azure Key Vault and Google Cloud KMS. (low confidence) (verified as of 2026-10-23) [source]
Facts and statements
- During public preview, Atlas Infinite storage IOPS and throughput are fixed by cluster tier, remain unchanged as stored data grows, and appear as read-only values in the UI. Changing storage performance requires changing tier; capacity independence does not imply independently configurable IOPS. (high confidence) (verified as of 2026-10-23) [source]
- Infinite storage capacity is independent of tier, with up to 128 TB logical capacity per replica set. Its storage-management documentation defines logical data size as uncompressed collections plus indexes, so index storage counts toward that capacity. (high confidence) (verified as of 2026-10-20) [source]
- The public preview deploys on AWS in a single region and excludes multi-region, multi-cloud, sharded and global clusters, M80-and-larger tiers, and locally attached NVMe storage. (low confidence) (verified as of 2026-10-23) [source]
- Atlas Search, Vector Search and Online Archive are excluded from Infinite public preview. This does not exclude ordinary MongoDB indexes: the same overview explicitly supports the full query API including indexes and transactions. (low confidence) (verified as of 2026-10-23) [source]
- Infinite public preview excludes collection-level restore, cross-organization restores, copying snapshots to other regions, downloading snapshots and restoring snapshots locally. External oplog replay through mongorestore is unsupported. (low confidence) (verified as of 2026-10-23) [source]
- Infinite preview supports AWS single-region replica sets. Multi-region, multi-cloud, sharded and global clusters are excluded, so global writes are unavailable. (medium confidence) (verified as of 2026-10-23) [source]
- Atlas Search and Vector Search are excluded from Infinite public preview. Database API compatibility does not establish compatibility with these retrieval services. (medium confidence) (verified as of 2026-10-23) [source]
- Infinite public preview has no uptime SLA. Its preview status and feature exclusions should be checked before production adoption. (medium confidence) (verified as of 2026-10-23) [source]
- Preview restore restrictions exclude cross-organization restores, collection-level restores, cross-region snapshot copying, snapshot downloads/local restores and archived-snapshot imports. External oplog replay with mongorestore is unsupported; mongostat has incomplete metrics and mongotop --locks errors. (low confidence) (verified as of 2026-10-23) [source]
Children
- No children recorded.