Snowflake Warehouse Over-Provisioned Min Clusters
A minimum number of clusters is held ready at all times, so that capacity is paid for whether or not queries arrive.
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 minimum 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
- Open Snowsight → Admin → Warehouses → the resource → check MIN_CLUSTER_COUNT and MAX_CLUSTER_COUNT.
- Review WAREHOUSE_LOAD_HISTORY for the last 14 days. Confirm load rarely required over 1 cluster.
- Lower the floor: ALTER WAREHOUSE the resource SET MIN_CLUSTER_COUNT = 1;.
- Keep MAX_CLUSTER_COUNT for burst headroom. Auto-scaling adds clusters on demand without an always-on floor.
- Re-evaluate after 2 weeks.
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-2102- 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.