AWS guide
Unattached EBS volumes: stop paying for disks nobody is using
When an EC2 instance is terminated or rebuilt, EBS volumes are sometimes left behind. Those disks keep charging. Cleaning them up is one of the fastest AWS cost savings wins—if someone owns the cleanup.
Why unattached EBS is silent waste
EBS pricing is tied to provisioned storage and type (gp3, io1, …), not whether an instance is attached. Orphaned volumes from failed launches and decommissioned apps pile up across regions.
Safe cleanup steps
Snapshot first if you need a recovery option, confirm no future attach plan, then delete. Tag-based ownership (team/project) makes reviews faster next time.
- Filter volumes with state = available (unattached)
- Check create date and last attach time
- Snapshot critical data if unsure
- Delete only with owner approval
SpendPilot workflow
Waste scans flag unattached EBS as actions. Assign an owner, approve, delete in AWS, then verify spend drop on the EBS line in Cost Explorer via SpendPilot verification.
Checklist
- Scan all regions you actually use
- List available (unattached) volumes
- Exclude volumes reserved for known restore drills
- Approve deletion with an owner
- Verify EBS cost drop after sync
FAQ
- Do unattached EBS volumes still cost money?
- Yes. You pay for provisioned storage whether or not a volume is attached to an instance.
- Can SpendPilot delete EBS for me?
- No. Deletion stays in your AWS account after human approval. SpendPilot finds, tracks, and verifies.