This inefficiency occurs when legacy volume types such as gp2 or io1 remain in use, even though AWS has released newer types—like gp3 and io2—that offer better performance at lower cost. 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.
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.
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.
