Snowflake billing ingestion uses a Snowflake integration you create once on the Integrations page, then attach to a billing datasource. Authentication is key-pair (RSA): Costory shows a public key for your Snowflake user; the private key is stored securely and is never returned after you save.
Not supported yet.
1. Create the Snowflake integration
- Open Costory and go to Integrations.
- Start the flow to add a Snowflake integration.
- When Costory displays setup SQL and a generated public RSA key, copy them.
- In the Snowflake console (or worksheet), run the setup SQL as a user who can alter the login for the Snowflake user Costory will use. This registers the public key for key-pair authentication.
- Enter the Snowflake connection details Costory asks for (for example account identifier, user, role, and warehouse as shown in the stepper).
- Complete validation. Costory checks access through the Snowflake SQL API before any sync is enabled.
2. Enable Snowflake billing
- Go to Billing > Import new billing datasource > Snowflake.
- Select the Snowflake integration you created above.
- Finish the stepper. Costory provisions the billing sync and starts ingesting data.
First sync timing is similar to other SaaS billing sources (on the order of minutes). See Data refresh for ongoing cadence.
What Costory includes
- Usage-based cost data from Snowflake account usage (including views such as USAGE_IN_CURRENCY_DAILY), with warehouse and query history where the connector exposes them for allocation and analysis. Query tags are included when Snowflake provides them, so query-level costs appear with tag dimensions you can use to filter and group in Explorer.
What Costory does not include
- Terraform automation for this datasource (use the UI only until Terraform support ships).
To remove access, delete or rotate credentials from the Costory UI and adjust Snowflake users and keys on your side. You cannot archive a Snowflake integration while an active billing datasource still references it.