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
- Check the recommended type, IOPS and throughput, and that no other modification is in progress on the volume.
- 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. - Wait for the modification to reach optimizing or completed. The volume stays attached and in use.
- 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
How is this different from nOps's own gp3 recommendation?
How is this different from nOps's own gp3 recommendation?
This one comes from AWS. nOps shows only one of the two for a volume, preferring AWS’s when both exist.
Do I need to stop the instance?
Do I need to stop the instance?
No. Volume modifications are made online.