Skip to main content
The features described in this article are in public preview and may change. The Transformations external data sources API is beta.
Register a Snowflake integration in Cognite Data Fusion (CDF) as an external data source, from Integrations or with the Transformations API.

Before you start

On Snowflake

CDF uses the account identifier, service user, service role, and warehouse to open a session in your Snowflake account. Create the service user and role. This is an example. Replace the names to match your account:
Example service user and role
Do not grant INSERT, UPDATE, DELETE, CREATE, OWNERSHIP, ACCOUNTADMIN, ALL PRIVILEGES, or broad future grants. For a dynamic table or a Snowflake-managed Iceberg table, grant SELECT on that table type instead. If the account uses a network policy, contact Cognite Support for the CDF egress IP addresses. Your Snowflake admin allowlists those addresses so CDF can reach the account.

On CDF

These capabilities control who can register the source and who can run queries that use it. See Transform data. Use a CDF token for API calls. That identity is separate from the Snowflake service user. Example scope for all sources in the project:
To limit access, set dataSetId on the source and use datasetScope on the capability.

Register in Integrations

1

Open Integrations

Navigate to Data fusion > Integrate > Integrations, select Zero-copy, then select Set up.
2

Select a source system

Select Snowflake, then Snowflake Connector.
3

Enter the integration details

External ID is permanent.
4

Enter the connection details

Use the account identifier, service user, role, and warehouse from On Snowflake. The account identifier is not a URL.
5

Create the connection

Select Create connection. The integration is listed on the Zero-copy tab.
6

Copy the public key

Open the integration and copy the public key from the details page.
7

Send the key to your Snowflake admin

The admin registers it on the Snowflake service user. See Register the public key.
To register the same source with the API, continue with Register with the API.

Register with the API

Set base values (replace placeholders):
1

Collect the Snowflake values

Collect the account identifier, service user, service role, and warehouse. A Snowflake admin creates them in On Snowflake.
2

Grant CDF capabilities

Add the capabilities above to the group used by the identity that calls the API and runs transformations.
3

Register the source

format must be "snowflake". See Transformation external data sources. Success returns 201 and the generated publicKey. The private key is never returned.If the externalId already exists in the project, the request returns 409 and creates no items. A connection is not edited in place. To change settings, delete the source and register a replacement.

Register the public key

Copy the public key from the integration details page, or from the publicKey field in the API response. Send it to your Snowflake admin. The admin sets the key on the service user. Paste the key without the BEGIN and END lines and without line breaks.
Run DESC USER COGNITE_TRANSFORMATIONS_SVC; and confirm RSA_PUBLIC_KEY_FP is set. Until this command runs, a preview that uses the external ID fails with an invalid JWT token. See Read Snowflake data in transformations.

Rotate the public key

The public key expires. Set the new expiry in the future and at most one year ahead. Rotate when no critical job is scheduled. Open the integration on the Zero-copy tab in Integrations and select Edit. You can change the expiry and generate a new public key. Connection settings stay read-only. Select Save, then copy the new public key from the details page and send it to your Snowflake admin. The admin registers the new key on the service user before the next run. The external ID stays the same, so existing SQL does not change. With the API:

Delete the connection

On the integration, select Delete integration. With the API:
Transformations that reference the deleted external ID fail on the next run. Deleting the connection in CDF does not change Snowflake. Remove the key there as well:

Manage sources

Full schemas: Transformation external data sources and the beta OpenAPI tag.

Next steps

Last modified on November 17, 2026