Opportunity Name: EBS io1/io2 to gp3 migration
AWS Resource Type: AWS EBS (Elastic Block Store) io1/io2 provisioned solid state drives
Opportunity Description: AWS application workloads requiring high-throughput IOPS and/or low-latency often leverage io1/io2 EBS volumes. Similar to the benefits realized from migrating general purpose EBS volumes, you can also upgrade provisioned volumes to gp3 and reduce your cloud spend in the majority of use cases.
In 2020, AWS introduced the next-generation general purpose SSD volumes for EBS called gp3. These volumes deliver a better value without sacrificing performance. They support provisioned up to 16,000 provisioned IOPS. The gp3 peak throughput also rose to match that of io1/io2 at 1,000 MiB/s.
At CloudFix, we thoroughly tested this opportunity and strongly recommend migrating io1/io2 volumes with less than 16,000 provisioned IOPS to gp3. No downtime is required in the vast majority of cases.
Criteria for identifying the opportunity: CloudFix monitors EBS volume usage and analyzes metrics to identify EBS io1/io2 volumes that are candidates for migration to the gp3 volume type. Factors considered are:
- Select only io1/io2 volumes. Leave io2 block express volumes in place.
- Select volumes that are NOT short-lived (<2 weeks of existence = short-lived) because short-lived volumes are not worth optimizing
- Select volumes for which provisioned IOPS is less than 16K and peak throughput is less than 1000 MB/s. CloudFix fetches peak metrics for Nitro based instances and estimates peak metrics for other instances using the sum metric.
- Select only elastic volumes, where no downtime is expected. All volumes attached since 4th November 2016 are elastic, meaning that they support migration to gp3 without requiring downtime and the majority of volumes are elastic.
Can CloudFix implement the fix automatically once I accept the recommendation?
Yes. EBS io1/io2 to gp3 migration is automatic – once you accept the recommendation and schedule the fix, execution is automatic. As an extra precaution, CloudFix takes a snapshot of the EBS gp2 volume before migrating it to gp3.
Is it possible to rollback once CloudFix implements the fixer?
Manual rollback on your AWS account is possible. One-click rollback via CloudFix for this opportunity is currently not available.
Does this fix require downtime?
No. EBS io1/io2 to gp3 migration via CloudFix does not require any downtime. It is executed as a zero downtime fix.