Snowflake - Auxia Docs

Snowflake is a cloud data warehouse. Auxia connects to Snowflake in one of two ways: by reading your tables directly with a read-only role you create, or from files you export to an Auxia bucket on a schedule. Both are set up together with the Auxia team.

Setup: Direct connection

Recommended · about 15 minutes

Setup: GCS export

When direct access isn’t allowed

Choose a method

	Direct connection (recommended)	GCS export
How it works	Auxia reads your tables in place, on a schedule	A scheduled Snowflake task writes Parquet files to an Auxia bucket, and Auxia ingests them
What you set up	A warehouse, a key-pair service user, and a read-only role	A storage integration and a scheduled export task
Ongoing work on your side	None	Keep the export task running
Compute cost	Reads run on your warehouse, billed to your Snowflake account	Export tasks run on your warehouse
Freshness	A schedule you choose	Whenever your export task runs
Choose it when	You can grant Auxia read access to your account	Your security team won’t allow direct warehouse access

Features

Feature	Direct connection	GCS export	Notes
Setup	Assisted	Assisted	Coordinated with your Auxia solutions engineer
Nothing copied or staged on your side	✅	❌	Export writes files to Auxia’s bucket
No password exchanged	✅	✅	Direct uses key-pair authentication; export uses a storage integration
Incremental reads	✅	✅	Each table needs a timestamp column marking when a row was added or updated
Full-table snapshots	✅	—	For tables without a usable timestamp column
Instant revocation	✅	—	Drop the role or disable the service user. With export, Auxia never has access to your account
Network restriction	✅	—	Attach a Snowflake network policy to the service user
Data Health monitoring	✅	✅

How it works

Direct connection. You create a dedicated, auto-suspending warehouse, a service user that authenticates with a key pair, and a read-only role with SELECT on the tables to share. Auxia registers its public key on the user (the private key never leaves Auxia’s secret manager), then reads each table on the agreed schedule — the initial historical load first, then incremental reads scoped by each table’s timestamp column. Auxia validates row counts against the source before go-live. GCS export. Auxia gives you a destination bucket path. You create a Snowflake storage integration, send Auxia the service account Snowflake generates for it, and schedule COPY INTO tasks that export new data as Parquet. Auxia ingests from the bucket.

Limitations

Both methods are set up with the Auxia team, not in the self-serve wizard.
Setup needs a role that can create warehouses, users, roles, and storage integrations — typically ACCOUNTADMIN.
Share base tables rather than views where possible.
See Source data requirements for requirements shared by all connectors.

Setup: Direct connection

Setup: GCS export

​Choose a method

​Features

​How it works

​Limitations

Choose a method

Features

How it works

Limitations