Skip to main content

RDS: Migrate RDS instances from gp2 to gp3

Updated this week

Difficulty: Easy

Description

We identified RDS instances in your account still using gp2 storage. Migrating to gp3 provides better baseline IOPS (3,000 regardless of volume size vs 3 IOPS/GB on gp2) and configurable throughput at the same price per GB. Customers who over-provisioned gp2 storage solely to achieve higher IOPS can right-size their volumes after migrating to gp3.


Selection Criteria

  • RDS instance uses gp2 storage type.

  • Instance has been running for at least 7 days.

  • Expected annualized savings exceed $10.


Expected Saving

gp2 and gp3 cost the same per GB ($0.115/GB/month) for RDS. The savings opportunity lies in reducing over-provisioned storage: customers who inflated gp2 volume size to get more IOPS (3 IOPS/GB) no longer need to do so with gp3's fixed 3,000 IOPS baseline.


Operational Impact

  • Storage type changes are applied online — no instance restart or downtime required. The modification runs in the background.

  • ⚠️ Warning — One modification at a time: RDS only allows one storage modification at a time per instance. If another modification is already in progress, the gp3 migration must wait.

  • ⚠️ Warning — 6-hour cooldown: After a storage modification completes, a 6-hour cooldown applies before another storage change can be initiated on the same instance.


References

Did this answer your question?