Submit feedback on
Outdated Provisioned IOPS Volume Type for High-I/O Workloads
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Outdated Provisioned IOPS Volume Type for High-I/O Workloads
Adam Richter
Service Category
Storage
Cloud Provider
AWS
Service Name
AWS EBS
Inefficiency Type
Outdated Resource Selection
Explanation

Many environments continue using io1 volumes for high-performance workloads due to legacy provisioning or lack of awareness of io2 benefits. io2 volumes provide equivalent or better performance and durability with reduced cost at scale. Failing to adopt io2 where appropriate results in unnecessary spend on IOPS-heavy volumes.

Relevant Billing Model

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.

Detection
  • 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
Remediation
  • 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
Submit Feedback