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
- Review the recommended storage type, IOPS and throughput against your peaks, including backups and batch jobs.
- 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). - Watch read and write latency and queue depth for a few days after the change.
- 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
Can I shrink the storage size?
Can I shrink the storage size?
Not in place. RDS storage can only grow. Shrinking means creating a new instance and moving the data.