Docs Playbook
Storage Orphan Disks and Volumes
Remove orphan block storage that no longer serves workloads.
Detached volumes often survive instance lifecycle operations and continue billing silently.
Detection Signals
- Unattached or detached block storage without active mounts.
- No write activity in recent observation windows.
- Missing owner, service, or retention tags.
Execution Steps
- Validate attachment state and owner metadata.
- Take final snapshot where required by policy.
- Delete or archive with approval record.
- Document savings and retention outcome in report exports.
Provider Differences
| Provider Group | Operational Notes |
|---|---|
| AWS | Unattached EBS volumes and stale storage classes. |
| Azure | Unattached managed disks with no compute linkage. |
| GCP | Orphan persistent disks outside active instance groups. |
| Oracle/IBM/Tencent | Detached block disks across regional projects. |
Share
Pass the cleanup path to the next reviewer
Send the same remediation steps to engineering, finance, or the owner who needs to sign off.
Next Step
Run a focused scan, validate owners, then export evidence for approval and execution.
Save your first $1,000 before the next billing cycle.