Authenticate to Snowflake Using Key Pair or PAT in Data Fusion
A Snowflake connector enables ingestion of structured data from a Snowflake data warehouse into Data Fusion. Snowflake connectors are categorized under SQL/JDBC connectors and are commonly used for batch-oriented ingestion workflows.
Use this connector to access tables and views stored in Snowflake and ingest the data into target types for downstream processing, transformation, and analytics workflows.
When to Use a Snowflake Connector
Use a Snowflake connector when:
- Your data resides in Snowflake
- You need to ingest structured, table-based data
- Your data can be queried using SQL
Typical use cases include:
- Batch ingestion from warehouse tables
- Analytics and reporting pipelines
- Data synchronization workflows
- Enterprise data warehouse integrations
Connector Configuration Model
Snowflake connectors are configured using the Configure Snowflake Connector wizard, which organizes connector setup into separate stages.
| Stage | Purpose |
|---|---|
| Connector | Select the connector type |
| Destination | Configure the connector identity |
| Authentication | Configure connection and authentication settings |
| Review & Test | Validate and save the connector |
Snowflake uses separate Destination and Authentication configuration sections in the connector wizard.
Connection endpoint and session configuration fields are configured on the Destination page. These fields include:
- serverEndpoint
- port
- database
- warehouse
Identity and secret-based authentication fields are configured on the Authentication page.
Authentication Model
Supported authentication methods include:
- KeyPair — Uses a private key for authentication
- ProgrammaticAccessToken (PAT) — Uses a token for authentication
The Authentication page always includes the following identity fields:
- username
- password
Selecting an authentication method reveals additional credential fields specific to that method.
Authentication Method Comparison
| Method | Description | Best Suited For | Security Profile | Notes |
|---|---|---|---|---|
| KeyPair | Uses a private key (PEM format) with a passphrase | Production workloads, automation, and service accounts | High | Recommended for secure non-interactive access. Eliminates password-only dependency. Simplifies authentication without requiring private key management. Token lifecycle management is still required. |
| ProgrammaticAccessToken (PAT) | Uses a token for authentication | Service integrations and automated workflows | High | Token lifecycle management is still required. |
KeyPair Authentication Fields
When KeyPair is selected, the following additional fields appear:
| Field | Description | Required |
|---|---|---|
| privateKey | PEM content including -----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY----- | Yes |
| passphrase | Passphrase for the key if encrypted. Leave blank if the key is not encrypted. | No |
ProgrammaticAccessToken Authentication Fields
When ProgrammaticAccessToken is selected, the following additional field appears:
| Field | Description | Required |
|---|---|---|
| programmaticAccessToken | Programmatic access token | Yes |
Connect to Snowflake
Before You Begin
Before configuring the connector, ensure that:
- You have the Snowflake server hostname (
serverEndpoint) - You have valid Snowflake credentials
- You have the Snowflake warehouse and database names
- Your Snowflake account is accessible from the platform environment
Ensure that:
- The corresponding public key is registered for the Snowflake user
- Your user has access to the specified warehouse and database
- If using an encrypted private key, the passphrase is available
Step 1: Select the Connector Type
- On the Data Fusion canvas, click + Add Data Source.
- In the connector list, locate Snowflake under the Database & Data Warehouse section, or search for snowflake.
- Click Snowflake.
The wizard advances to the Destination step.
Note: Connector names must be unique, alphanumeric, and must not begin with a number. If you enter a duplicate or invalid name, the wizard displays a validation error.
Step 2: Configure Destination Settings
On the Destination page, configure the connector identity.
| Field | Description | Required |
|---|---|---|
| name | Unique name for the connector | Yes |
| description | Optional description for the connector | No |
Also configure the following connection endpoint fields on the Destination page:
| Field | Description | Required |
|---|---|---|
| serverEndpoint | Snowflake server hostname (for example, account.snowflakecomputing.com) | Yes |
| port | Port number for the Snowflake connection | No |
| database | Name of the Snowflake database to connect to | Yes |
| warehouse | Name of the Snowflake virtual warehouse to use for query execution | Yes |
Automatically Populate Fields
To automatically populate Authentication and Advanced fields:
- Click the Auto-populate panel on the left side of the wizard.
- Select JSON or JDBC URL as the input format.
- Paste the configuration.
- Click Extract & Suggest Mapping.
- Review the suggested mappings.
- Click Apply Mapping & Fill Fields.
Click Continue.
Step 3: Configure Authentication
On the Authentication page, configure the connection details and authentication method.
Base Connection Fields
The following fields are always displayed:
| Field | Description |
|---|---|
| username | Snowflake username |
| password | Snowflake password |
Select an Authentication Method
From the Authentication Method dropdown, select one of the following:
- KeyPair
- ProgrammaticAccessToken
KeyPair Authentication
If KeyPair is selected, complete the following fields:
| Field | Description | Required |
|---|---|---|
| privateKey | Paste PEM content including -----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY----- | Yes |
| passphrase | Passphrase for the key if encrypted. Leave blank if the key is not encrypted. | No |
ProgrammaticAccessToken Authentication
If ProgrammaticAccessToken is selected, complete the following field:
| Field | Description | Required |
|---|---|---|
| programmaticAccessToken | Programmatic access token | Yes |
Click Continue.
Step 4: Review and Test the Configuration
On the Review & Test page:
- Review the connector configuration summary.
- Verify the Destination and Authentication sections.
- Review any validation issues displayed by the wizard.
To save and validate the connection:
- Click Save & Test
To save without validating the connection:
- Click Save & Close
If Save & Test is used, the wizard validates:
- Authentication
- Network connectivity
- Access to the Snowflake account
A success or failure status is displayed after validation completes.
If the test fails:
- Return to the relevant step.
- Update the configuration.
- Run the test again.
[!NOTE] If validation fails during Save & Test, the connector is still saved and the wizard remains open so you can correct the configuration.
After saving, the connector appears on the Connectors page.
Next Steps
After creating the connector:
Create a Source Collection for Snowflake data
Configure transformations and mappings
Run and monitor ingestion jobs