Skip to content

Commit b05753e

Browse files
committed
edits to snowflake key pair only authentication
1 parent e7ad160 commit b05753e

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

src/connections/reverse-etl/reverse-etl-source-setup-guides/snowflake-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ At a high level, when you set up Snowflake for Reverse ETL, the configured user/
1414
> If you have an existing dbt account with a Git repository, you can use [Segment's dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes.
1515
1616
## Set up guide
17-
Follow the instructions below to set up the Segment Snowflake connector. Segment recommends you use the `ACCOUNTADMIN` role to execute all the commands below, and that you create a user that authenticates with an encrypted key pair. Snowflake plans to deprecate password-only authentication starting August 2026. Learn more in the [Snowflake docs](https://docs.snowflake.com/en/user-guide/security-mfa-rollout){:target="_blank"}.
17+
Follow the instructions below to set up the Segment Snowflake connector. Segment recommends you use the `ACCOUNTADMIN` role to execute all the commands below, and that you create a user that authenticates with an encrypted key pair. Snowflake only supports authentication using a key pair as Snowflake plans to deprecate password-only authentication starting August 2026. Learn more in the [Snowflake docs](https://docs.snowflake.com/en/user-guide/security-mfa-rollout){:target="_blank"}.
1818

1919
> info ""
2020
> Segment has a Terraform provider, powered by the Public API, that you can use to create a Snowflake Reverse ETL source. See the [segment_source (Resource)](https://registry.terraform.io/providers/segmentio/segment/latest/docs/resources/source){:target="_blank”} documentation for more information.

src/connections/storage/catalog/snowflake/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -142,8 +142,8 @@ To connect Snowflake to Segment:
142142
* Database name: The database that Segment uses in order to sync data
143143
* Warehouse: The warehouse in your Snowflake account that Segment uses to run SQL
144144
* Username: The Snowflake user that Segment uses to run in your warehouse
145-
* Authentication
146-
* Private key: View Snowflake’s key pair set up doc. You can upload in .p8 file format. Key length must be at least 2048-bit. An encrypted key is recommended but not required.
145+
* Authentication: Snowflake only supports authentication using a key pair.
146+
* Private key: View [Snowflake’s key pair set up doc](https://docs.snowflake.com/en/user-guide/key-pair-auth){:target="_blank"}. You can upload in .p8 file format. Key length must be at least 2048-bit. An encrypted key is recommended but not required. You need to first create the user and assign it a key pair following the instructions in the Snowflake docs. Then, set the `segment_connections_username` variable in the SQL script to the user you just created.
147147
4. Test your connection.
148148
5. Click **Save**.
149149

src/unify/data-graph/setup-guides/snowflake-setup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -154,7 +154,7 @@ To connect your warehouse to the Data Graph:
154154
- **Database**: The only database that Segment requires write access to in order to create tables for internal bookkeeping. This database is referred to as `segment_connection_db` in the script below.
155155
- **Warehouse**: The [warehouse](https://docs.snowflake.com/en/user-guide/warehouses){:target="_blank”} in your Snowflake account that you want to use for Segment to run the SQL queries. This warehouse is referred to as `segment_connection_warehouse` in the script below.
156156
- **Username**: The Snowflake user that Segment uses to run SQL in your warehouse. This user is referred to as `segment_connection_username` in the script below.
157-
- **Authentication**: Snowflake only supports authentication using a key pair:
157+
- **Authentication**: Snowflake only supports authentication using a key pair as Snowflake plans to deprecate password-only authentication starting August 2026. Learn more in the [Snowflake docs](https://docs.snowflake.com/en/user-guide/security-mfa-rollout){:target="_blank"}.
158158
- **Key Pair**: You need to first create the user and assign it a key pair following the instructions in the [Snowflake docs](https://docs.snowflake.com/en/user-guide/key-pair-auth){:target="_blank"}. Then, set the `segment_connections_username` variable in the SQL script to the user you just created.
159159

160160

0 commit comments

Comments
 (0)