Create a user for Elementary cloud
- Please create a Snowflake key-pair (private and public key) using this guide.
- Using the public key generated in the previous step, please run the following in your dbt project folder:
Permissions and security
Elementary cloud doesn’t require read permissions to your tables and schemas, but only the following:- Read-only access to the elementary schema.
- Access to read metadata in information schema and query history, related to the tables in your dbt project.
Fill the connection form
Provide the following fields:- Account: Find your account by using the Snowflake account URL and removing
snowflakecomputing.com. e.g.example.us-east-1. For more information, see Account Identifiers in the Snowflake docs. - Database name: The name of the database where your Elementary schema exist. e.g.
analytics. - Warehouse: e.g.
ELEMENTARY_WAREHOUSE. - Elementary schema: The name of your Elementary schema. Usually
[schema name]_elementary. - Role (optional): e.g.
ELEMENTARY_ROLE.
- Key pair (Recommended):
- User: The user created for Elementary.
- Private key: The private key you generated for Elementary. For more information, see Generate Private Key in the Snowflake docs.
- Private key passphrase (optional)
- User password (Deprecated, not recommended):
- User: The user created for Elementary.
- Password: The password you set when creating your Snowflake account.
Snowflake are in the process of deprecating single-factor username & password authentication for all human users. As a result, while still supported,
we recommend configuring the user in advance using key-pair authentication rather than username & password, and configuring the user as TYPE=SERVICE
(this is automatically handled in the user creation macro above).See here for more information regarding this change.