Data integration

Snowflake

Ingest Snowflake warehouse and cloud-services cost from ACCOUNT_USAGE / ORGANIZATION_USAGE so data platform spend sits next to your cloud bill.

Available on request. We're prioritizing AWS, Azure, GCP, and Oracle Cloud billing first. Snowflake usage ingestion is available for design partners on request — talk to us to prioritize your account.

Connection

Read-only Snowflake user + usage views

Access model

Read-only

Time to value

Usually within an hour of granting usage view access

How OptCloud connects with Snowflake

Snowflake exposes rich cost and usage metadata in ACCOUNT_USAGE (and ORGANIZATION_USAGE for orgs). OptCloud connects with a dedicated read-only role that can query those views — warehouse metering, storage, serverless features, and query history aggregates — then attributes spend to warehouses, databases, and teams.

Required permissions

USAGE on the SNOWFLAKE database and ACCOUNT_USAGE schema (or ORGANIZATION_USAGE)
SELECT on metering and query history views OptCloud documents
No need for ACCOUNTADMIN on an ongoing basis (bootstrap may use a privileged role to grant)

OptCloud does not need access to your customer tables — only Snowflake’s metadata/usage views.

Create a connection

1
Create a dedicated OptCloud role and user
Create a role such as OPTCLOUD_READER and a service user keyed with key-pair auth (preferred) or a rotated password.
2
Grant ACCOUNT_USAGE access
Grant imported privileges on SNOWFLAKE.ACCOUNT_USAGE (or org-level equivalents) so the role can read metering history.
3
Connect in OptCloud
Add account → Snowflake. Enter account identifier, user, role, warehouse for metadata queries (X-Small is enough), and auth material.
4
Optional: map warehouses to teams
Use tags or a mapping file so warehouse spend lands in the right FinOps dimension.
5
Validate warehouse trends
Confirm Cost Explorer shows Snowflake as a provider and that warehouse-level breakdown matches Snowsight billing roughly.