Skip to main content
EBS volumes are billed for the storage, IOPS and throughput they are provisioned with, not what they use. AWS Compute Optimizer compares each volume’s provisioned performance with its observed use and recommends a cheaper configuration that still fits. nOps imports these recommendations daily through AWS Cost Optimization Hub and shows AWS’s estimated saving.

Why it matters

Provisioned IOPS and throughput are often set for a peak that never comes, and on io1, io2 and gp3 volumes they can cost more than the storage itself.

How nOps finds it

This recommendation comes from AWS Compute Optimizer, not from nOps. Compute Optimizer looks at the volume’s IOPS and throughput over its lookback period and recommends a lower provisioned configuration or a cheaper type, with an estimated 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. Review the recommended type, IOPS and throughput against the volume’s peak use in CloudWatch (VolumeReadOps, VolumeWriteOps, VolumeReadBytes, VolumeWriteBytes).
  2. Modify the volume: EC2 → Volumes → Modify volume, or aws ec2 modify-volume --volume-id ID --volume-type TYPE --iops N --throughput N.
  3. Wait for the modification to complete. The volume stays attached and in use.
  4. Update Terraform or CloudFormation so a later deployment does not change it back.

Risks and considerations

  • Less provisioned performance means less headroom. Check peaks outside the lookback window, such as month-end jobs or restores.
  • EBS volume size cannot be reduced in place. A smaller size needs a new volume and a data copy.
  • 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 settings.