Skip to main content
Newer RDS storage types can deliver the same or better performance at a lower price. For example, gp3 includes a baseline of IOPS and throughput that gp2 only gives on larger volumes. AWS Compute Optimizer recommends a storage upgrade where it would cost less, and nOps imports these recommendations daily through AWS Cost Optimization Hub with the estimated monthly saving.

Why it matters

gp2 is still the default in many older templates and snapshots, and the move to gp3 happens online.

How nOps finds it

This recommendation comes from AWS Compute Optimizer through Cost Optimization Hub, not from an nOps rule. AWS compares the storage’s current type and performance with newer types over its lookback period (14 days by default). 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 and performance settings.
  2. Modify the storage (RDS console → Modify → Storage type, or aws rds modify-db-instance --db-instance-identifier DB_ID --storage-type gp3), setting IOPS and throughput to at least what the database uses today.
  3. Watch latency for a few days after the change.
  4. Update Terraform or CloudFormation so a later deployment does not change it back.

Risks and considerations

  • RDS may not allow another storage change for about 6 hours after this one.
  • On small gp2 volumes, check burst behavior: gp3 gives a fixed baseline rather than burst credits.
  • To roll back, modify the storage back to its previous type.