Cluster Missing/Weak Auto-Termination
Without auto-termination a cluster keeps its workers running after the last job finishes, so the bill is set by when someone remembers to stop it.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudDatabricks
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Tighten auto-termination on the Databricks cluster. 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
- Databricks Cluster on AWS, Databricks Cluster on Azure, Databricks Cluster on Google Cloud
- The fix, by hand on AWS
- Set 'Terminate after' to 10-120 minutes of inactivity.
- Enforce auto-termination defaults via a cluster policy.
These are the steps the finding carries in the product.
- Category
- Scheduling. Resources running 24x7 with a clear off-hours usage pattern, ready for start and stop scheduling.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-2201RC-2301RC-2401- Full reference
Related checks
See the always-on 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.