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

# Rightsize RDS Storage

> Lower the provisioned IOPS, throughput or storage type of RDS storage that is bigger than the workload needs.

RDS bills provisioned storage performance (IOPS and throughput) whether or not the database uses it. AWS Compute Optimizer compares what each instance's storage is provisioned for with what it actually uses, and recommends a cheaper storage configuration. nOps imports these recommendations daily through AWS Cost Optimization Hub with the estimated monthly saving.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Database |
| **Service** | Amazon RDS |
| **Action** | Rightsize |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 14 days |
| **Source** | AWS Compute Optimizer |

## Why it matters

Provisioned IOPS are often set for a migration or load test and never lowered again.

## How nOps finds it

This recommendation comes from AWS Compute Optimizer through Cost Optimization Hub, not from an nOps rule. AWS looks at the storage's IOPS and throughput over its lookback period (14 days by default) and recommends a configuration that still covers it. The saving is AWS's estimate.

## Before you start

AWS Compute Optimizer and Cost Optimization Hub enabled. Permission to modify the instance (`rds:ModifyDBInstance`).

## How to implement

1. Review the recommended storage type, IOPS and throughput against your peaks, including backups and batch jobs.
2. Modify the storage (**RDS console → Modify → Storage**, or `aws rds modify-db-instance --db-instance-identifier DB_ID --storage-type gp3 --iops IOPS --storage-throughput MBPS`).
3. Watch read and write latency and queue depth for a few days after the change.
4. Update Terraform or CloudFormation so a later deployment does not change it back.

## Risks and considerations

* Allocated storage size cannot be reduced in place; this recommendation changes performance settings or storage type, not size.
* After a storage change, RDS may not allow another storage change for about 6 hours, and the instance can be in a storage-optimization state for a while.
* To roll back, modify the storage back to its previous settings.

## FAQs

> [accordion] Can I shrink the storage size?
>
> Not in place. RDS storage can only grow. Shrinking means creating a new instance and moving the data.

## Related

* [Upgrade DB Instance Storage](https://help.nops.io/inform/supported-recommendations/upgrade-db-instance-storage)
* [Rightsize RDS Instance](https://help.nops.io/inform/supported-recommendations/rightsize-rds-instance)
* [Change EBS Volume to gp3](https://help.nops.io/inform/supported-recommendations/change-ebs-volume-to-gp3)
* [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.