Explanation
Why the waste happens and who it affects.
Gp3 allows users to configure IOPS and throughput independently of volume size, while io2 provides higher durability and more predictable performance than io1. These newer volumes are generally more cost-effective and can be adopted without re-architecting workloads. Many teams continue using outdated types due to default AMIs, automation templates, or simple oversight.
Billing model
The pricing dimensions that drive this cost.
EBS volumes are billed per GB-month based on the provisioned size and the selected volume type. Additional charges may apply for provisioned IOPS or throughput beyond the default baseline, depending on the volume type.
How to detect
5 checks to find it in your estate.
- Identify volumes using gp2, io1, or other legacy types
- Compare current performance needs (IOPS, throughput) with the default capabilities of newer alternatives
- Evaluate whether the volume type was chosen intentionally or inherited from legacy infrastructure
- Check whether Elastic Volumes is supported for live migration on the attached instance
- Consult with infrastructure owners or automation templates to confirm ongoing default behavior
How to fix
How to remove the waste.
Modify the EBS volume type in place - such as changing from gp2 to gp3, or io1 to io2-using the AWS Console, CLI, or API. The change is typically non-disruptive and completes without downtime. In rare cases where in-place modification isn't supported (e.g., older instance types), create a snapshot and restore it to a new volume with the desired configuration. Update AMIs, launch templates, and automation tools to ensure future volumes use cost-effective, modern types by default.
Documentation
Vendor references for pricing and configuration.