Snowflake Warehouse Over-Provisioned Max Clusters
The warehouse may scale further than the workload needs, so a burst can multiply spend without anyone approving it.
Free to start. No card. The playground just needs your work email.
Snowflake
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Snowflake, with read-only access to the account.
Explain
Every finding says exactly what to change: Lower the warehouse's maximum cluster count.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Snowflake Warehouse on Snowflake
- The fix, by hand
- Check the 14-day peak cluster count for the resource via WAREHOUSE_LOAD_HISTORY.
- Lower MAX_CLUSTER_COUNT toward (observed_peak + 1 cluster of headroom): ALTER WAREHOUSE the resource SET MAX_CLUSTER_COUNT = ‹n›;.
- Re-evaluate quarterly. A max set far above real demand is just an accident waiting to surprise you.
These are the steps the finding carries in the product.
- Category
- Governance. Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-2105- Full reference
Related checks
See the governance findings 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.