Docs Playbook
Snapshot Retention and Cleanup
Align snapshot retention with compliance and cost control.
Snapshot growth is easy to ignore because individual objects are cheap, but aggregate spend grows quickly.
Detection Signals
- Old snapshots beyond policy retention window.
- No linked recovery drills or active dependency chains.
- Redundant image generations for deprecated environments.
Execution Steps
- Group snapshots by workload and retention class.
- Keep required recovery points and mark deletable candidates.
- Apply staged deletion by risk level.
- Track retained vs removed sets in audit-ready exports.
Provider Differences
| Provider Group | Operational Notes |
|---|---|
| AWS | Old EBS snapshots and outdated AMIs. |
| Azure | Disk snapshot backlog across subscriptions. |
| GCP | Snapshot chains with expired retention purpose. |
| Vultr/DigitalOcean | Legacy snapshot accumulation in dev stacks. |
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.