FAQs/Integrations & tracking/Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth
Integrations & tracking · RevSure FAQs

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth

1. Navigate to Revsure App and Click "Data Hub"

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 1)

2. Click "Data Sources"

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 2)

3. Click "Add New"

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 3)

4. Click Snowflake among the list of Integrations

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 4)

5. Set the "Connection Name *" field

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 5)

6. Fill the "Custom URL *" field

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 6)

7. Fill the "Warehouse *" field

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 7)

8. Choose the "Private Key / Pair" field

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 8)

9. Give the "User Name"

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 9)

10. From the .p8 file for Private Key of RSA, Copy paste to the "Private Key" field

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 10)

11. Set the "Private Key Passphrase" field

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 11)

12. Set the "User Role" field

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 12)

13. Click "Connect"

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 13)

The connection is created!

The Keys and Tokens Used for Authentication are stored with Revsure in a Secure Manner utilizing Google's Key Management System

  • All keys and tokens are encrypted with Google Cloud KMS before being stored, ensuring plaintext values are never persisted.
  • Multiple CryptoKeys are maintained for different services and use cases, enabling isolation, fine-grained access control, and independent rotation.
  • Only ciphertext is stored in the database, making the data unreadable without authorized access to the correct KMS key.
  • Security of Keys, Credentials and Tokens in Revsure

14. Snowflake Source Connection using RSA - Integration Architecture

Revsure Snowflake Integration Implementation Guide : RSA Private Key Auth (figure 14)

Data Security Practices

  • All Customer Data is encrypted at rest in our GCP environment (using AES256) and in transit (using HTTP over TLS)
  • RevSure Data-Hub Service that manages the connection uses Java based Snowflake Driver.
  • RevSure ETL workflows connecting to Snowflake are executed as Apache Spark batch jobs. The Spark connector relies on the Snowflake JDBC driver to handle the low-level connection details.
  • Both Data-Hub and Spark connectors establish a secure, encrypted connection using TLS1.2+. This ensures that all the data transferred between the Spark and Snowflake environments is protected.
  • All the RevSure Data-Hub Services and ETL Workflows are residing within a VPC (Virtual Private Cloud) and connected to a VPN (Virtual Private Network), thereby the services are isolated from the public internet.

Ready when your stack is

Still stuck? Bring it to the session

A RevSure engineer walks your exact setup on a 30-minute working session.