RDS instance using gp2 storage (migrate to gp3 for 20% savings)
- Severity
- Low
- Service
- RDS
- Check ID
- RDS_GP2_STORAGE
What this check finds
This RDS instance uses gp2 EBS storage. AWS recommends gp3, which is 20% cheaper and offers independently configurable IOPS and throughput without provisioning extra capacity.
Passing looks like: RDS uses gp3 storage.
How to fix it
Modify the instance to use gp3 storage.
AWS CLI
aws rds modify-db-instance --db-instance-identifier DB_ID --storage-type gp3 --apply-immediately
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
RDS → Modify → Storage type → gp3.
Compliance
This is a cost check. It flags spend that buys nothing, which no compliance framework asks about, so it is not mapped to a control.
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More RDS checks
- HighAurora/RDS cluster storage is not encrypted at rest
- HighRDS automated backups are disabled
- HighRDS instance does not have automatic minor version upgrades enabled
- HighRDS instance has zero database connections for 7 days
- HighRDS instance storage is not encrypted at rest
- HighRDS security group allows broad CIDR ingress (broader than /16)
- HighRDS snapshot is public
- MediumAurora/RDS cluster has automated backups disabled