GCP Old Disk Snapshot
Snapshot storage is billed continuously, and a snapshot old enough to predate every current restore point is paying to preserve a state nobody would roll back to.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete the aging disk snapshot. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- GCP Disk Snapshots on Google Cloud
- The fix, by hand
- Open Compute Engine Console → Snapshots.
- Review the creation date and source disk of each snapshot.
- Verify the source disk still exists and the snapshot is within your retention policy.
- Delete snapshots that are beyond retention or whose source disk has been deleted.
- Consider using snapshot schedules to automate retention management.
These are the steps the finding carries in the product.
- Category
- Orphaned resources. Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-143- Full reference
Related checks
See the orphaned resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.