You can choose the storage configuration when creating a new cluster via the AWS Management Console or the AWS CLI.
Amazon DocumentDB (with MongoDB compatibility) offers two storage configurations: and IO-Optimized . The IO-Optimized configuration is designed for applications with high input/output (I/O) demands. It provides predictable performance by decoupling I/O charges from storage usage, making it cost-effective for I/O-intensive workloads. This report explains the architecture, benefits, use cases, and cost implications of the IO-Optimized setting. documentdb io optimized
Introduced in late 2022, the configuration changes the pricing model: You can choose the storage configuration when creating
| Database | IO-Optimized Equivalent? | Notes | |----------|--------------------------|-------| | MongoDB Atlas | M-series with provisioned IOPS | Atlas charges separate I/O unless using higher tiers. | | Amazon RDS (Aurora) | Aurora I/O-Optimized | Similar model for Aurora MySQL/PostgreSQL. | | DynamoDB | On-demand vs. provisioned | Different abstraction, but predictable cost theme. | provisioned | Different abstraction
IO-Optimized is recommended for:
This mode offers increased write throughput and reduced latency, tailored for the most demanding workloads.