Explanation
Why the waste happens and who it affects.
Some may be intentionally retained for reattachment or backup purposes, but many persist unintentionally due to the lack of automated cleanup. When these detached volumes are also inactive-showing no read or write activity-they represent unnecessary ongoing costs. Identifying and removing these orphaned volumes can produce meaningful savings without affecting running workloads.
Billing model
The pricing dimensions that drive this cost.
EBS volumes are billed based on the provisioned volume type, size, and performance configuration, regardless of usage or attachment
How to detect
6 checks to find it in your estate.
- Identify EBS volumes that are not attached to any EC2 instance ("available")
- Review usage data to confirm that no read or write activity has occurred over a defined lookback period
- Check whether the volume is intentionally retained for manual recovery, reattachment, or snapshot purposes, especially if it's part of a known backup or disaster recovery process managed outside of AWS
- Evaluate the cost contribution of the volume based on size, type, and provisioned IOPS
- Determine whether a recent snapshot exists or is needed before deletion
- Confirm with application or infrastructure owners whether the volume still serves a purpose
How to fix
How to remove the waste.
Delete detached and inactive EBS volumes that are no longer required. Before deletion, take a snapshot if the data must be retained for backup or compliance purposes. Consider setting up scheduled audits or automated cleanup routines to regularly identify and remove unused volumes.
Documentation
Vendor references for pricing and configuration.