This section describes how to integrate the with Snowflake databases.
For more information on supported versions, see Connection Types.
NOTE: This integration is supported only for deployments of |
PUBLIC
schema in the default database. PUBLIC
. Your Snowflake stage and other databases must be permitted to use S3 resources for your users.
NOTE: If users in your deployment are using IAM roles in user mode for AWS access, then the Snowflake stage must have permissions to write to the user's S3 bucket. |
For more information, see Required AWS Account Permissions.
If you are integrating with Snowflake using OAuth2, additional configuration is required:
When relational connections are enabled, this connection type is automatically available. For more information, see Enable Relational Connections.
In Snowflake terminology, a stage is a database object that points to an external location on S3. This stage must contain access credentials.
If a stage is used, it should be in the default bucket used on S3 for storage.
NOTE: For read-only connections to Snowflake, you must specify a Database for Stage. The connecting user must have write access to this database. |
Tip: You can specify a separate database to use for your stage. |
If a stage is not specified, a temporary stage is created using the current user's AWS credentials. Please verify the Pre-requisites again.
NOTE: Without a defined stage, you must have write permissions to the database from which you import. This database is used to create the temporary stage. |
For more information on stages, see https://docs.snowflake.net/manuals/sql-reference/sql/create-stage.html.
In , the stage location is specified as part of creating the Snowflake connection.
For more information, see Create Snowflake Connections.
Steps:
After you create your connection, load a small dataset based on a table in the connected Snowflake database.
NOTE: For Snowflake connections, you must have write access to the database from which you are importing. |
See Import Data Page.
For more information, see Verify Operations.