Prerequisites
- Locate your Public Key generated on your behalf. The Public Key will be a long string of text, loosely resembling the format:
'MIIBI...<SHORTENED>...Xrw2nwIDAQAB' - In order to complete the following setup steps, you or a Snowflake admin on your team must have the securityadmin and sysadmin roles. (To check your account for these roles, run
SHOW GRANTS TO USER <your_username>;and review therolecolumn.) - If your Snowflake data warehouse is using Snowflake Access Policies, you will need to have our static IP available to complete Step 2.
Recommendation: Key-pair authentication with service userSnowflake is deprecating single-factor passwords and will disallow passwords for service users (TYPE=SERVICE) by October 2026. For that reason, we strongly recommend configuring the transfer user as a service user with key-pair authentication.
Create role, user, warehouse, and database in the data warehouse
- Review and make any changes to the following setup script.
- Key-pair authentication (recommended)
- Username & password
Setup script (key-pair auth)
Using an existing
schemaBy default, a new schema (with a name you provide) will be created in the target Snowflake database upon the initial connection. If instead you create the schema ahead of time, you may remove the CREATE SCHEMA permission, and instead grant ALL PRIVILEGES on the target schema for the designated role.The script below can be used to complete this step:Grant on existing schema
Using an existing
warehouse or databaseBy default, this script creates a new warehouse and a new database. If you’d prefer to use an existing warehouse/database, change the warehouse_name variable from TRANSFER_WAREHOUSE to the name of the warehouse to be shared/database_name variable from TRANSFER_DATABASE to the name of the database to be shared.- In the Snowflake interface, select the dropdown next to the “Run” button, and click Run All. This will run every query in the script at once. If successful, you will see
Statement executed successfullyin the query results.
Configure the Snowflake access policy
If your Snowflake data warehouse is using Snowflake Access Policies, a new policy must be added to allow our static IP to write to the warehouse.
- Review current network policies to check for existing IP safelists.
Show network policies
- If there is no existing Snowflake Network Policies (the
SHOWquery returns no results), you can skip to Step 3. - If there is an existing Snowflake Network Policy, you must alter the existing policy or create a new one to safelist our static IP address. Use the
CREATE NETWORK POLICYcommand to specify the IP addresses that can access your Snowflake warehouse.
Create network policy
Network allowlistingCloud Hosted (US):
35.192.85.117/32Cloud Hosted (EU): 104.199.49.149/32If private-cloud or self-hosted, contact support for the static egress IP.Permissions checklist
- Role grants:
USAGEon the target warehouse- If the destination schema will be created by the service:
USAGEandCREATE SCHEMAon the target database (the setup script also includesMONITOR)
- If using a pre-created schema:
USAGEon the target databaseALL PRIVILEGESon the target schema
- User defaults set (optional but recommended):
DEFAULT_ROLE,DEFAULT_WAREHOUSE - If using key auth: user has the PKCS#8
RSA_PUBLIC_KEYset - If network policies are enforced: our egress IP is allowlisted
FAQ
How is the Snowflake connection secured?
How is the Snowflake connection secured?
We recommend key-based authentication. You register a public key on a Snowflake user and we authenticate using the corresponding private key, so no password is shared or stored. You can also enforce Snowflake Network Policies to allowlist our egress IP.
What permissions does the data transfer role need?
What permissions does the data transfer role need?
Minimum grants:
USAGEon the warehouse- If the destination schema will be created by the service:
USAGEandCREATE SCHEMAon the database - If using a pre-created schema:
USAGEon the database andALL PRIVILEGESon the schema
Can I use an existing warehouse?
Can I use an existing warehouse?
Yes. Grant
USAGE on that warehouse to the transfer role. You may also size the warehouse to control performance/cost.Can I use the same transfer role for multiple destinations?
Can I use the same transfer role for multiple destinations?
If you have multiple Snowflake destinations, you can use the same transfer role for up to 2 destinations. You will be issued a unique public key for each destination and can use the
RSA_PUBLIC_KEY and RSA_PUBLIC_KEY_2 to store up to two public keys.