> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Switch I/O-Heavy DocumentDB Clusters to I/O-Optimized

> Switch I/O-heavy DocumentDB clusters to I/O-Optimized storage so I/O is no longer billed per request.

DocumentDB standard storage bills every I/O request. The I/O-Optimized configuration has no I/O charge, but storage costs three times as much and instances up to about 10% more. nOps finds clusters whose I/O costs more than twice their storage and estimates the saving from switching them, per account and region.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Database |
| **Service** | Amazon DocumentDB |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## 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

1. Open the recommendation to see which clusters to switch.
2. 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`).
3. The change is made without downtime. Check the next weeks' bill for the lower total.
4. 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

> [accordion] 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.

## Related

* [Switch Aurora Cluster to I/O-Optimized](https://help.nops.io/inform/supported-recommendations/switch-aurora-cluster-to-i-o-optimized)
* [Delete Inactive DocumentDB Clusters](https://help.nops.io/inform/supported-recommendations/delete-inactive-documentdb-clusters)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.