Home/Data Ingestion/Data Connections/Snowflake/Secure Data Sharing

Snowflake (Secure Data Sharing)

Setting up a data connection via Snowflake Secure Data Sharing

This guide explains how Auxia reads your data in place via Snowflake Secure Data Sharing — no tables are exported, copied, or recreated, and you run no scheduled jobs on your side.

note

The recommended method for connecting Snowflake to Auxia is Direct Connection, where Auxia reads your tables in place via a read-only role on your account. Secure Data Sharing is an alternative best suited to accounts in the same cloud and region as Auxia's (cross-region/cross-cloud sharing requires replication). Confirm with your Auxia solutions engineer before choosing it.

Before proceeding, review the Source Data Requirements to ensure your tables are ready to be connected with Auxia.

1. Overview

You create a share of the tables or views you want Auxia to read and add Auxia's Snowflake account as a consumer. Auxia then reads from the share read-only, on a recurring schedule, using its own warehouse for compute — so there is no compute or scheduled task to run or maintain on your side.

Flow:

Your Snowflake account                          Auxia
      │
      │  tables / secure views
      │       │
      │       │  GRANT to a share, ADD Auxia as a consumer
      │       ▼
      │   Share ──(read-only access)──>
      │                                    │
      │                                    │  Auxia reads incrementally from the
      │                                    │  share on your schedule (Auxia's
      │                                    │  warehouse), then ingests
      │                                    ▼
      │                                Auxia platform

Time required: ~10 minutes.

Prerequisites:

• The ACCOUNTADMIN role (required to create a share and add a consumer account).
• Auxia's Snowflake account must be in the same cloud and region as yours — this is a Secure Data Sharing requirement. If it differs, Snowflake replication is required first; your Auxia solutions engineer will advise (this adds replication cost on your side).
• Each shared table/view should have a timestamp column that marks when a row was added/updated (e.g., UPDATE_DATE), so Auxia can read incrementally rather than rescanning the full table.

What Auxia provides: Auxia's Snowflake account identifier (the consumer to add to your share), and configures + schedules the connection on our side — the initial historical load and recurring incremental reads — validating row counts against the source. Your Auxia solutions engineer confirms the connection before go-live.

2. Create a Share

Run the following in a worksheet with the ACCOUNTADMIN role selected. Grant access to each database, schema, and table/view you want Auxia to read:

CREATE SHARE IF NOT EXISTS auxia_share;

GRANT USAGE  ON DATABASE <your_database>                          TO SHARE auxia_share;
GRANT USAGE  ON SCHEMA   <your_database>.<your_schema>           TO SHARE auxia_share;

-- Repeat per object you want to expose:
GRANT SELECT ON TABLE    <your_database>.<your_schema>.<table>   TO SHARE auxia_share;
-- For views, a SECURE VIEW is recommended when sharing:
GRANT SELECT ON VIEW     <your_database>.<your_schema>.<view>    TO SHARE auxia_share;

3. Add Auxia as a Consumer

Auxia will provide its Snowflake account identifier. Add it to the share:

ALTER SHARE auxia_share ADD ACCOUNTS = <auxia_account_identifier>;

note

If Auxia's account is in a different region or cloud than yours, this step requires a replicated/listing-based share instead. Your Auxia solutions engineer will provide the exact steps.

4. Send the Details to Auxia

Share the following with your Auxia solutions engineer:

• Share name (e.g., auxia_share)
• Database / schema / table (or view) names to ingest
• The timestamp/watermark column for each object (used for incremental reads)
• Desired refresh cadence (e.g., hourly or daily) and when source data typically lands

Auxia installs the share on our side, reads each object incrementally on the agreed schedule, validates row counts, and confirms before go-live.

5. Cost

• No compute on your side — Auxia reads using its own warehouse; you are not billed for the read.
• No data egress within the same cloud and region — Secure Data Sharing reads in place. Cross-region/cross-cloud sharing requires replication, which incurs storage and replication cost on your side (avoid by colocating with Auxia's account where possible).

6. Summary

Step	Action	Owner
1	Provide Snowflake account identifier	Auxia
2	Create a share and grant the objects	Client
3	Add Auxia's account as a consumer	Client
4	Send share/object names + watermark columns	Client
5	Install share, schedule reads, validate, confirm	Auxia

Need Help?

Contact support@auxia.io or your Auxia solutions engineer.