Snowflake Warehouse Auto-Suspend Not Tuned
The warehouse keeps running after the last query finishes, so idle compute is billed until the timer expires.
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: Tighten auto-suspend on the warehouse.
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.
- Click Edit → set Auto-suspend to 60 seconds (120s for BI/result-cache-sensitive warehouses).
- Confirm Auto-resume is enabled so the warehouse wakes on the next query.
- Or run: ALTER WAREHOUSE the resource SET AUTO_SUSPEND = 60 AUTO_RESUME = TRUE;.
- Never disable AUTO_SUSPEND on production warehouses. Credits leak indefinitely after the last query.
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-2100- 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.