(Preview) EBS Volume Cost Optimizations (io1, io2 to gp3)

Opportunity Name:

EBS IO1/IO2 to GP3

AWS Resource Type:

Amazon Elastic Block Store (EBS)

Opportunity Description:

Applications that have extremely high performance and/or throughput requirements (greater than 16,000 IOPS) generally use provisioned EBS volumes (io1 or io2).

In 2020, AWS announced the next-generation general purpose SSD volumes called gp3. These volumes deliver a better value without sacrificing performance. Notably, gp3 peak throughput rose to match that of io1/io2 at 1,000 MiB/s. The best part about all of this is that you can upgrade these volumes in place to immediately begin realizing the cost savings. No downtime is required in the vast majority of cases.

At CloudFix, we thoroughly tested this upgrade opportunity and strongly recommend migrating the majority of io1/io2 volumes with less than 16,000 provisioned IOPS to gp3. The performance numbers for all volume types can be found in the AWS documentation.

Criteria for identifying the opportunity:

CloudFix monitors EBS volume usage and analyzes metrics to identify EBS io1/io2 volumes that are apt for migration to the gp3 volume type. Factors considered are:

  • Select io1/io2 volumes that require 16K or less in provisioned IOPS because 16K is the maximum IOPS supported by gp3. Skip volumes with insufficient data to prove that volumes requires 16K of provisioned IOPS or less.
  • Select volumes that costs more than $100.
  • Do not select non-elastic volumes = volumes launched before November 2016 because these volumes require some downtime.
  • Finally, do not select short-lived volumes that are only around for a week or two because it may not be worth the effort.

Potential savings (range in % on annual basis):

For io1/2 volumes requiring less than 16K IOPS, gp3 volumes are 60%+ cheaper with no loss of performance

What happens when the Fixer is executed?

The fixer will first create a snapshot of the volume. After the snapshot is ready, it will retype the volume to gp3. After successful migration, the snapshot will be deleted.

Risks

This change has no risk. CloudFix takes a snapshot of the EBS io1/io2 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.

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.

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.

Do it yourself (DIY) Instructions:

If you have CloudFix subscription, CloudFix will execute these automatic cost savings for you. However, if you'd like to do it yourself - please follow these instructions:

Finding cost saving recommendations with CloudFix is FREE! You'll need a paid subscription only if you'd like CloudFix to execute those recommendations.

 

AWS Console:

  • Use CloudFix recommendations to identify the EBS volumes you want to migrate to Gp3.
  • For each volume, select the volume and click on Actions and then "Modify volume

Screen_Shot_2022-07-06_at_11.30.42_AM.png

  • Change the Volume type to General Purpose SSD (gp3) and set the IOPS and Throughput.

Screen_Shot_2022-07-06_at_11.32.29_AM.png

  • Click on Modify button.

AWS CLI:

  • Use CloudFix recommendations to identify the EBS volumes you want to migrate to Gp3.
  • For each volume execute following command
aws ec2 modify-volume --volume-id <Volume ID> --volume-type gp3 --iops <IOPS> --throughput <Througput>
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request