How to govern Costs in Snowflake
A step-by-step guide to governing Costs in Snowflake with Rencore: detect, review by owner and severity, and remediate with an audit trail.
Governing Costs in Snowflake means finding where it goes wrong, reviewing the findings by owner and severity, and remediating with an audit trail. Rencore covers this concern for Snowflake with the pre-built controls below, so it becomes a repeatable check rather than a one-off cleanup. The steps that follow apply the same detect, review, remediate loop to Costs.
Steps
-
Inventory Snowflake
Connect Snowflake and let Rencore build a continuous inventory of its resources, owners, and configuration, so governance starts from what exists rather than a stale export.
-
Detect with policies
Turn on the pre-built policies that cover Costs in Snowflake to surface oversharing, sprawl, and misconfiguration on the first scan, before writing a single custom rule.
-
Review by owner and severity
Use the Snowflake reports to review findings by owner, category, and severity, and to share them with stakeholders who do not have a seat in the platform.
-
Remediate and automate
Apply automations to fix findings at scale, route sensitive changes through approvals, and keep every action reversible and logged for the audit trail.
Snowflake controls for Costs
Grounded in the Rencore catalog. See the full Snowflake catalog on the Snowflake connector page.
-
Snowflake warehouses that never auto-suspend
Detects warehouses with auto-suspend disabled (0 seconds), which keep billing while idle
Severity: Medium -
Snowflake warehouses without a resource monitor
Detects warehouses that have no resource monitor enforcing a credit cap
Severity: Medium -
Snowflake oversized warehouses that are running
Detects running warehouses sized X-Large or larger
Severity: Medium -
Snowflake databases with excessive Time Travel retention
Detects databases whose Time Travel retention exceeds 30 days
Severity: Low -
Snowflake warehouses unused in the last 30 days
Detects warehouses that consumed no compute credits over the last 30 days
Severity: Low -
Snowflake warehouses with high credit consumption
Detects warehouses that consumed more than 1,000 credits over the last 30 days
Severity: Medium -
Snowflake databases with large storage footprint
Detects databases consuming more than 1 TB of storage on average
Severity: Low -
Snowflake warehouses by size
Shows the distribution of warehouses across compute sizes to highlight cost concentration
-
Snowflake top warehouses by credits (30d)
Shows the warehouses that consumed the most compute credits over the last 30 days
-
Snowflake databases by storage (GB)
Shows the databases consuming the most storage over the last 7 days
