Snowflake Connection
For instructions on configuring and running the Snowflake Connection, see the main Snowflake Connection page.
Setting up the Snowflake Connection
In the connection's Set up and run page, you need to enter your Snowflake and Amazon S3 or Google Cloud Storage credentials to authenticate your connection with those two systems. This section contains tips for authenticating with both systems.
Tips for Snowflake authentication
You’ll need your Snowflake account name, username, and password.
You can select a storage provider, either Google Cloud Storage or Amazon Web Services (S3).
Snowflake users can be normal business users with sufficient access. But you may want to consider creating an authorization for external integrations with Snowflake so if the specific user account is removed, the connection does not need to be reconfigured.
These authentication details are used to get metadata on database, schema, and tables, and to run import and export SQL commands to get and send data.
For all databases that will be accessed via the BlueConic Snowflake Connection, the Snowflake account must have the following grants:
SELECT
INSERT
UPDATE
DELETE
CREATE STAGE
CREATE FILE FORMAT
CREATE OR REPLACE FILE FORMAT
Google Cloud Storage authentication
If you choose Google Cloud Storage as storage provider for the data exchange, the Snowflake Connection requires your Google Cloud Storage credentials: Client ID, client secret, project ID, and bucket to be used to retrieve and store files.
You must be connected to your Google Cloud Storage account first.
Amazon Web Services (S3) authentication
The Snowflake Connection requires your S3 key, secret key, and bucket name.
AWS IAM user can be regular business users with sufficient access. But it is also common to create an authorization for external integrations with AWS, so if the specific user account is removed the connection does not need to be reconfigured.
These credentials are used for the staging of data for import and export into S3 via CSV staging files.
IAM access should allow the following actions for the bucket where the files are staged:
s3:PutObject
s3:GetObject
s3:GetObjectVersion
s3:DeleteObject
s3:DeleteObjectVersion