Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Field Name

Field Type

Field Dependency

Description

Label*

Default value: None
Example: Snowflake_S3_Databas e_Account

String

N/A

Specify a unique label for the account.

Account properties*

JDBC JARs

Use this field set to add a list of JDBC JAR files to be loaded. The Snowflake account has been tested with the JDBC driver version 3.14.0.


Click  to add a new row for each JDBC JAR file. Add each JAR file in a separate row. See Downloading the JDBC Driver for more information about JDBC drivers and downloading the appropriate driver for your account.

JDBC Driver*

Default value: None
Example: snowflake-jdbc-3.14.0.jar

String

N/A

Specify the fully-qualified name of the JDBC driver class to be used for connecting to the server.

The Snowflake Snap Pack is bundled with the default Snowflake JDBC JAR v3.14 file. Therefore, even if you do not provide a JDBC Driver, the account does not fail.

Hostname*

Default value: None
Example: demo.snowflake.net

String

N/A

Specify the hostname of the Snowflake server to which you want to connect the new account.

Port Number*

Default value: 443 
Example: 332

Integer

N/A

Specify the port number associated with the Snowflake database server that you must use for this account.

Authentication Type*

Default Value: Password
Example: Key Pair

Dropdown list

N/A

Choose an authentication type to connect to the database. The available options are:

  • Password: Authenticates with the Username and Password credentials.

  • Key Pair: Authenticates using the Private Key and Encrypted Private Key Passphrase.

Username*

Default Value: N/A
ExampleSW_User

String

N/A

Specify the username to connect to the Snowflake database server.

Password*

Default Value: N/A
Examplell@98#*00w

String

Appears when you select Password for Authentication Type.

Specify the password associated with the username specified above. This will be used as the default password while retrieving connections.

Encrypted Private Key*

Default Value: N/A
Example: -----BEGIN PRIVATE KEY-----MIIE6TAbBgkqhkiG9w0BBQMwDgQILYPyennlX2bd8yX8
xOxGSGfvB+99+PmSlex0FmY9ov1J8H1H9Y3lJXXb

-----END PRIVATE KEY-----

String

Appears when you select Key Pair for Authentication Type.

Specify the key that you have generated for authentication. The key must include the generated header and footer.

The Private Key is read, decrypted if necessary, and included with properties to connect to Snowflake, where it is validated with its paired Public Key to authenticate the connection.

Learn more about configuring and generating a valid key pair.

Encrypted Private Key Passphrase*

Default Value: N/A
Example: Nki62lmWfFO75Xg04W+Fnlt9ejiMn4zPbkf/me Aq1R3X7CM/ORLuLms4vU70NjzNYo09SO
UXhQmoqpEkQBvrrYuzdaQt5hvwh7vZQh WZ5L8+lTRoA
neFtmd6LZ94AssA==

String

Appears when you select Key Pair for Authentication Type.

Specify the passphrase for the Encrypted Private Key. Leave this field blank if the specified Private Key is not encrypted. However, we recommend that you use Encrypted Private Key.

Database name*

Default value: None
Example: TestDB

String

N/A

Specify the name of the database to which you want to connect.

Warehouse name*

Default value: None
Example: SW_WH

String

N/A

Specify the name of the warehouse to which you want to connect.

JDBC Driver Class

Default Valuenet.snowflake.client.jdbc.SnowflakeDriver
Examplenet.snowflake.client.jdbc.SnowflakeDriver

String

N/A

Specify the JDBC driver class to use.

S3 Bucket

Default Value: N/A
Example: sl-bucket-ca

String

N/A

Specify the name of the S3 bucket that you want to use for staging data to Snowflake. 

  • If you want to delete the temporary files from the S3 Bucket, we recommend you assign the delete object permission policy to delete the files. Learn how to assign delete object permission to an S3 user in AWS S3.

  • If you do not want to delete the temporary files, you can add an error view to the Snap and run the Pipeline

S3 Folder

Default Value: N/A
Example: sl-bucket-cas3/test

String/Expression

N/A

Specify the relative path to a folder in the S3 bucket listed in the S3 Bucket field. This is used as a root folder for staging data to Snowflake.

S3 Access-key ID

Default Value: N/A
Example: NAVRGGRV7EDCFVLKJH

String/Expression

N/A

Specify the S3 access key ID that you want to use for AWS authentication.

S3 Secret key

Default Value: N/A
Example: 2RGiLmL/6bCujkKLaRuUJHY9uSDEjNYr+ozHRtg

String/Expression

N/A

Specify the S3 secret key associated with the S3 Access-ID key. listed in the S3 Access-key ID field.

S3 AWS Token

Default Value: None
Example: AQoDYXdzEJr

String/Expression

N/A

Specify the S3 AWS Token to connect to private and protected Amazon S3 buckets. Note that only global Security Token Service (STS) regions are supported.

S3 Storage Integration

Default Value: N/A
Example: S3_Storage_Integration

String/Expression

N/A

Specify the S3 Storage Integration for Snowflake to be used for staging data instead of using AWS Acces-key ID and S3 Secret key. This value is necessary for validating data after a bulk load or bulk insert operation.

Advanced properties

URL Properties

Use this field set to define additional URL properties to use if any.

Granting roles

You can grant roles to the SnapLogic Snowflake account by using the role parameter in the URL Properties field set. Ensure that the roles are predefined in your Snowflake account before configuring the SnapLogic Snowflake account.

See Roles and Grant Roles for details.

URL property name

Default value: None
Example : queryTimeout

String

N/A

Specify the name of the URL property.

URL property value

Default value: None
Example: 4

String

N/A

Specify the URL property value associated with the URL property name.

Batch size*

Default value: 50
Example: 3

Integer

N/A

Specify the number of Snowflake queries that you want to execute at a time.

  • Select queries are not batched.

  • Using a large batch size could use up the JDBC placeholder limit of 2100.

Fetch size*

Default value: 100
Example12

Integer

N/A

Specify the number of rows a query must fetch for each execution.

Large values could cause the server to run out of memory.

Min pool size*

Default value: 3
Example: 0

Integer

N/A

Specify the minimum number of idle connections that you want the pool to maintain at a time.

Minimum value: 0
Maximum value: No limit

Max pool size*

Default value: 15
Example: 0

Integer

N/A

Specify the maximum number of connections that you want the pool to maintain at a time.

Minimum value: 0
Maximum value: No limit

Max life time*

Default value: 60
Example: 50

Integer

N/A

Specify the maximum lifetime of a connection in the pool.

  • Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit.

  • 0 indicates an infinite lifetime, subject to the Idle Timeout value. 

  • An in-use connection is never retired. Connections are removed only after they are closed.

Idle Timeout*

Default value: 5
Example: 4

Integer

N/A

Specify the maximum amount of time a connection is allowed to sit idle in the pool.

0 indicates that idle connections are never removed from the pool.

Checkout timeout*

Default value: 10000
Example: 9000

Integer

N/A

Specify the number of milliseconds you want the system to wait for a connection to become available when the pool is exhausted. 

If you provide 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout.

For any other value other than 0, the Snap displays an exception after the wait time has expired.

Generating a Valid Key Pair

Generating a Valid Key Pair
Multiexcerpt macro
nameGenerating a valid key pair
  1. In a Linux terminal, run the following command to generate a Private Key stored in PKCS8 format:

    • Encrypted (recommended): openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -out rsa_key.p8

  2. Generate a public key by referencing the previously generated private key rsa_key.p8: openssl rsa -in rsa_key.p8 -pubout -out rsa_key.pub

  3. Store the generated private key (rsa_key.p8) and public key (rsa_key.pub) in a safe location.

  4. In the Snowflake console, assign the public key to the required Snowflake user. Exclude the header and footer from the public key. ALTER USER jsmith SET RSA_PUBLIC_KEY='MIIBIjANBgkqh...';

  5. In the Snowflake console, verify the assignment of the public key to the required Snowflake user: DESC USER jsmith;

  6. Specify the entire Private Key and include the header and footer in the Private Key field of the Snowflake account.

    Snowflake supports multiple active keys for uninterrupted rotation. Learn more: Key Pair Authentication & Key Pair Rotation — Snowflake Documentation.

...