Skip to main content
AWS Compute Optimizer recommends moving EBS volumes to a newer volume type when it would cost less for the same or better baseline performance, most often gp2 to gp3. nOps imports these recommendations daily through AWS Cost Optimization Hub and shows AWS’s estimated saving. When AWS already has a recommendation for a volume, nOps does not show its own gp3 recommendation for it, so you see one recommendation per volume.

Why it matters

The change is online and low risk, and gp2 volumes are common in older accounts and templates.

How nOps finds it

This recommendation comes from AWS Compute Optimizer, not from nOps. Compute Optimizer compares the volume’s current type with a newer type sized for its observed performance over its lookback period, and estimates the monthly saving. nOps imports the highest-saving recommendation AWS gives for each volume.

Before you start

AWS Compute Optimizer enabled for the account, and permission to modify volumes (ec2:ModifyVolume).

How to implement

  1. Check the recommended type, IOPS and throughput, and that no other modification is in progress on the volume.
  2. Modify the volume, setting IOPS and throughput to at least what it has today: EC2 → Volumes → Modify volume, or aws ec2 modify-volume --volume-id ID --volume-type gp3 --iops N --throughput N.
  3. Wait for the modification to reach optimizing or completed. The volume stays attached and in use.
  4. Update Terraform or CloudFormation so a later deployment does not change it back.

Risks and considerations

  • EBS limits how often a volume can be modified, so wait for one change to finish before the next.
  • To roll back, modify the volume back to its original type and performance.

FAQs

This one comes from AWS. nOps shows only one of the two for a volume, preferring AWS’s when both exist.
No. Volume modifications are made online.