> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/setting-up-your-database/snowflake/connecting-to-snowflake.md).

# Configuring Snowflake workspace data connections

{% hint style="info" %}
Snowflake is phasing out support for using a simple username and password for authentication. For more information, go to the [Snowflake documentation](https://docs.snowflake.com/en/user-guide/security-mfa-rollout#deprecation-timeline).

We strongly recommend that you use key pair authentication for all database connections. This is currently the default option for workspace connections.
{% endhint %}

{% hint style="info" %}
Structural supports Snowflake on AWS and Azure Blob Storage. If you use Snowflake on Google Cloud Platform (GCP), contact Tonic.ai.
{% endhint %}

In the workspace configuration:

1. From the **Connection Type** dropdown list, select **Snowflake.**
2. In the **Source Settings** section, under **Snowflake Type:**
   * To connect to a Snowflake database on AWS, click **AWS**.
   * To connect to a Snowflake database on Azure, click **Azure**.

The database connection configuration for AWS and Azure is mostly the same. The configuration for temporary file storage is slightly different.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Connect to the source database</strong><br><br>Configure the connection to the Snowflake source database.</td><td><a href="/app/setting-up-your-database/snowflake/connecting-to-snowflake/snowflake-source-connection.md">Connecting to the Snowflake source database</a></td></tr><tr><td><strong>Connect to the destination database</strong><br><br>Configure the connection to the Snowflake destination database.</td><td><a href="/app/setting-up-your-database/snowflake/connecting-to-snowflake/snowflake-destination-connection.md">Connecting to the Snowflake destination database</a></td></tr><tr><td><strong>Configure the temporary storage on AWS</strong><br><br>For AWS set the location and credentials to store temporary files.</td><td><a href="/app/setting-up-your-database/snowflake/connecting-to-snowflake/snowflake-temp-storage-aws.md">AWS - Setting the storage location for temporary files</a></td></tr><tr><td><strong>Configure the temporary storage on Azure</strong><br><br>For Azure, set the location and credentials to store temporary files.</td><td><a href="/app/setting-up-your-database/snowflake/connecting-to-snowflake/snowflake-temp-storage-azure.md">Azure - Setting the storage location for temporary files</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/app/setting-up-your-database/snowflake/connecting-to-snowflake.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.