GCP Vertex AI Notebook Stopped
A stopped notebook stops charging for compute and keeps charging for its boot and data disks, which persist until the instance is deleted.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, fixed.
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 stopped Workbench notebook. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
In one click, ZopNight deletes the resource, then checks the change took. When someone other than an admin starts a pause or a delete, an admin approves it first.
- Applies to
- Vertex AI Workbench Notebooks on Google Cloud
- 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-1213- 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.