Why it matters
Unused volumes are pure cost, and provisioned IOPS or io2 volumes left behind can be expensive.How nOps finds it
This recommendation comes from AWS Compute Optimizer, not from nOps. Compute Optimizer marks a volume unused when it is not attached, or when it is attached but had almost no read or write activity over its lookback period. The saving is AWS’s estimate of the volume’s monthly charge. nOps imports the highest-saving recommendation AWS gives for each volume.Before you start
AWS Compute Optimizer enabled for the account, and permission to create snapshots and delete volumes (ec2:CreateSnapshot, ec2:DeleteVolume). Confirm the volume is not needed with its owner.
How to implement
- Check the volume’s state and attachments:
aws ec2 describe-volumes --volume-ids ID. - Take a snapshot so the data can be recovered:
aws ec2 create-snapshot --volume-id ID, and wait until it completes. - If the volume is attached, confirm with the owner, unmount it inside the instance, and detach it. Never detach a root volume.
- Delete the volume: EC2 → Volumes → Actions → Delete volume, or
aws ec2 delete-volume --volume-id ID. - Delete the snapshot later if you are sure the data is not needed.
Risks and considerations
- Detaching an attached volume can break an application that expects it, even if it is rarely used.
- Deleting a volume is permanent. The snapshot is the only way to get the data back, and it is billed separately at the snapshot rate.
- To roll back, create a new volume from the snapshot and attach it.
FAQs
Why does an attached volume show up?
Why does an attached volume show up?
Compute Optimizer also flags attached volumes with almost no reads or writes. Check with the owner before detaching them.