Snowflake Connector Configuration and Authentication

Snowflake connector encounters authentication failures, connection timeouts, or configuration errors. This is commonly related to deprecated authentication methods, incorrect credentials, or network connectivity issues.

Common Error Messages:

• Authentication type PASSWORD is deprecated and will be removed

Note: For DataHub Cloud customers, infrastructure-level changes (Kubernetes, AWS resources, operating system configurations) are managed by DataHub Support. The solutions below focus on configuration changes that customers can implement.

1. Update authentication method:
   • Snowflake is deprecating username/password authentication
   • Switch to key-pair authentication or OAuth:

source:
  type: snowflake
  config:
    account_id: "your_account"
    warehouse: "your_warehouse"
    username: "your_username"
    authentication_type: "KEY_PAIR_AUTHENTICATOR"
    private_key_path: "/path/to/private_key.p8"
    private_key_password: "${SNOWFLAKE_PRIVATE_KEY_PASSWORD}"

2. Verify Snowflake permissions:
   • Ensure the service account has usage permissions on the warehouse
   • Grant access to ACCOUNT_USAGE schema for metadata extraction:

GRANT IMPORTED PRIVILEGES ON DATABASE snowflake TO ROLE datahub_role;

3. Check network connectivity:

   • Verify the Snowflake account URL is correct
   • Confirm firewall rules allow outbound HTTPS connections to Snowflake
   • Test connectivity using SnowSQL or another Snowflake client

4. Review connection parameters:

   • Ensure account_id includes region and cloud provider if needed (e.g., account_name.region.cloud)
   • Verify warehouse name is correct and the service account can use it
   • Check role configuration if using role-based access control

Always backup your DataHub configuration before making changes. Test solutions in a non-production environment when possible.

• Snowflake Source

• 5720, 5839, 5809, 5674, 5583, 4963, 5899, 5732