Skip to main content

Snowflake Key Pair Authentication

Coalesce supports Snowflake’s key pair authentication for connecting Development Workspaces and Environments to Snowflake instances. Both encrypted and un-encrypted private keys are supported. Encrypted keys have a corresponding passphrase that is required to use them, while un-encrypted keys can be used directly. While keys are allowed to be encrypted with an empty passphrase by Snowflake, this is not supported in Coalesce and will result in an error.

We recommend using Key pair for automated actions.

Step 1: Get Your Snowflake Account Identifier​

Obtain your Snowflake URL, by opening the account selector in Snowflake.

Add your Snowflake credentials in the build settings

Step 2: Generate Key Pair in Snowflake​

  1. Go through Snowflake’s key pair authentication steps to generate your keys.
  2. Make sure to generate a private key and save it for use in Coalesce.
  3. Generate your public key using the private key created for Coalesce.
  4. Assign the public key to your Snowflake user.

Step 3: Authenticate in Coalesce​

  1. Navigate to Build Settings > Environments or Workspaces.
  2. Select Edit, , on the Environment or Workspace that you want to connect to Snowflake using Key Pair Auth.
  3. In Edit Environment or Workspace > User Credentials, select Authentication Type as Key Pair .
  4. Enter your Snowflake Username , Private Key, Private Key Passphrase (if applicable), Role and Warehouse into their respective fields and Save. Click Test Connection to ensure this works as expected.
Workspace Settings Development page showing Snowflake connection configuration. Left sidebar lists Settings, User Credentials, Storage Mappings, Parameters, and OAuth Settings. Main panel displays connection details including Snowflake account URL (fka56740.snowflakecomputing.com), authentication fields for Key Pair login, and role set to ACCOUNTADMIN. Cancel and Save buttons at bottom.
Adding Your Private Key

When entering your private key, make sure it's formatted properly. It must include the full private key including the lines BEGIN ENCRYPTED PRIVATE KEY and END ENCRYPTED PRIVATE KEY.

-----BEGIN ENCRYPTED PRIVATE KEY-----
...
-----END ENCRYPTED PRIVATE KEY-----