Skip to main content

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 the role column.)
  • 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.
1

Create role, user, warehouse, and database in the data warehouse

  1. Review and make any changes to the following setup script.
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
set role_name = 'TRANSFER_ROLE';
set database_name = 'TRANSFER_DATABASE';
set schema_name = 'PRECREATED_SCHEMA';

use database identifier($database_name);
grant ALL PRIVILEGES on schema identifier($schema_name) to role identifier($role_name);
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.
  1. 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 successfully in the query results.
2

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.
  1. Review current network policies to check for existing IP safelists.
Show network policies
SHOW NETWORK POLICIES;
  1. If there is no existing Snowflake Network Policies (the SHOW query returns no results), you can skip to Step 3.
  2. 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 POLICY command to specify the IP addresses that can access your Snowflake warehouse.
Create network policy
CREATE NETWORK POLICY <transfer_service_policy_name> ALLOWED_IP_LIST = ('<static_ip>');
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.
Creating your first network policyIf you have no existing network policies and you create your first as part of this step, all other IPs outside of the ALLOWED_IP_LIST will be blocked. Snowflake does not allow setting a network policy that blocks your current IP address. (An error message results while trying to create a network policy that blocks the current IP address.) But be careful when setting your first network policy.
3

Add your destination

Use the following details to complete the connection setup: host name, database name, your chosen schema name, username, and password.

Permissions checklist

  • Role grants:
    • USAGE on the target warehouse
    • If the destination schema will be created by the service:
      • USAGE and CREATE SCHEMA on the target database (the setup script also includes MONITOR)
    • If using a pre-created schema:
      • USAGE on the target database
      • ALL PRIVILEGES on the target schema
  • User defaults set (optional but recommended): DEFAULT_ROLE, DEFAULT_WAREHOUSE
  • If using key auth: user has the PKCS#8 RSA_PUBLIC_KEY set
  • If network policies are enforced: our egress IP is allowlisted

FAQ

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.
Minimum grants:
  • USAGE on the warehouse
  • If the destination schema will be created by the service: USAGE and CREATE SCHEMA on the database
  • If using a pre-created schema: USAGE on the database and ALL PRIVILEGES on the schema
Yes. Grant USAGE on that warehouse to the transfer role. You may also size the warehouse to control performance/cost.
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.