Why it matters
On read- and write-heavy clusters, I/O can be the largest part of the DocumentDB bill. I/O-Optimized removes it and makes the cost predictable.How nOps finds it
nOps reads the last 7 complete days of DocumentDB billing in each account and region. A cluster qualifies when its I/O cost is more than twice its storage cost. The saving is, for those clusters, the I/O cost minus twice the storage cost, minus 10.05% of the cost of every instance in the account and region, scaled to a month. Accounts with DocumentDB reserved instances, accounts already on I/O-Optimized, accounts mostly paid with credits and savings under $5 a month are left out.Before you start
Permission to modify the cluster (rds:ModifyDBCluster, used by DocumentDB).
How to implement
- Open the recommendation to see which clusters to switch.
- For each cluster, change the storage configuration (DocumentDB console: Clusters → your cluster → Modify → Storage configuration → I/O-Optimized, or
aws docdb modify-db-cluster --db-cluster-identifier CLUSTER --storage-type iopt1 --apply-immediately). - The change is made without downtime. Check the next weeks’ bill for the lower total.
- Update Terraform or CloudFormation so a later deployment does not switch it back.
Risks and considerations
- You can switch a cluster back to standard storage only once every 30 days.
- If the cluster’s I/O falls later, standard storage may become cheaper again.
- The estimate charges the instance uplift on every instance in the account and region, so it is on the low side.
FAQs
Why twice the storage cost?
Why twice the storage cost?
I/O-Optimized storage costs three times standard storage, so I/O must cost more than twice the storage before removing it pays for the storage increase.