Explanation
Why the waste happens and who it affects.
Failing to adopt io2 where appropriate results in unnecessary spend on IOPS-heavy volumes.
Billing model
The pricing dimensions that drive this cost.
Provisioned IOPS volumes are billed based on the amount of storage (per GB) and the number of provisioned IOPS. While io1 and io2 share the same baseline pricing, io2 introduces tiered IOPS pricing-offering a lower per-IOPS rate once volumes exceed thresholds such as 32,000 IOPS. For high-throughput workloads, this tiering makes io2 significantly more cost-effective.
How to detect
5 checks to find it in your estate.
- Review provisioned EBS volumes with the io1 volume type
- Identify volumes provisioned with more than 32,000 IOPS
- Confirm the workload requires sustained high IOPS
- Estimate cost differences between io1 and io2 for similar configurations
- Check for infrastructure-as-code templates still defaulting to io1
How to fix
4 ways to remove the waste.
- Convert high-IOPS io1 volumes to io2 where supported
- Update provisioning templates to default to io2 for performance-critical workloads
- Validate application compatibility (typically no changes required)
- Monitor cost and performance post-migration to confirm impact
Documentation
Vendor references for pricing and configuration.