Skip to content

Commit 8c3a3ab

Browse files
committed
addressing engg feedback [netlify-build]
1 parent 3434fe1 commit 8c3a3ab

File tree

2 files changed

+9
-12
lines changed

2 files changed

+9
-12
lines changed

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

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ At a high level, when you set up Snowflake for Reverse ETL, the configured user/
1313
> Segment now supports key-pair authentication for Snowflake Reverse ETL sources.
1414
1515
## Set up guide
16-
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 a key pair.
16+
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.
1717

1818
1. Log in to your Snowflake account.
1919
2. Navigate to *Worksheets*.
@@ -50,16 +50,14 @@ Follow the instructions below to set up the Segment Snowflake connector. Segment
5050
GRANT USAGE ON DATABASE segment_reverse_etl TO ROLE segment_reverse_etl;
5151
GRANT CREATE SCHEMA ON DATABASE segment_reverse_etl TO ROLE segment_reverse_etl;
5252
```
53-
6. Enter and run one of the following code snippets below to create the user Segment will use to run queries. Segment recommends creating a user that authenticates using a key pair.
54-
53+
6. Enter and run one of the following code snippets below to create the user Segment uses to run queries. For added security, Segment recommends creating a user that authenticates using a key pair.
5554

5655
To create a user that authenticates with a key pair, [create a key pair](https://docs.snowflake.com/en/user-guide/key-pair-auth#configuring-key-pair-authentication){:target="_blank”} and then execute the following SQL commands:
5756
``` sql
5857
-- create user (key-pair authentication)
5958
CREATE USER segment_reverse_etl_user
6059
DEFAULT_ROLE = segment_reverse_etl
61-
RSA_PUBLIC_KEY = 'MIIBIjANBgkqh...'
62-
RSA_PUBLIC_KEY_FP = 'enter the passphrase you created';
60+
RSA_PUBLIC_KEY = 'enter your public key';
6361

6462
-- role access
6563
GRANT ROLE segment_reverse_etl TO USER segment_reverse_etl_user;

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

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -86,17 +86,17 @@ GRANT CREATE SCHEMA ON DATABASE "SEGMENT_EVENTS" TO ROLE "SEGMENT";
8686

8787
### Step 4: Create a user for Segment
8888

89-
Create the user that Segment uses to connect to your warehouse. You can create a user that authenticates with a key pair, or you can create a user that authenticates using a password. Segment recommends creating a user that will authenticate with an encrypted key pair.
89+
Create the user that Segment uses to connect to your warehouse. You can create a user that authenticates with a key pair, or you can create a user that authenticates using a password. For enhanced security, Segment recommends creating a user that will authenticate with an encrypted key pair.
9090

9191
#### Create a user that authenticates with a key pair
9292
If you are creating a user that will use a key pair to authenticate, you first must create a public key and then can create a new user.
9393

94-
##### Generate a key
94+
##### Generate keys
9595

9696
To start, open a terminal window and generate a private key by running the following command, replacing `key_name` with the name you'd like to give the key. The command generates a private key in PEM format, and will prompt you to enter a passphrase. Write down or remember this passphrase, as you will need it when creating your Segment user and configuring your destination in the Segment app.
9797

9898
> success ""
99-
> If you want to generate an unencrypted key, append `-nocrypt` to the end of the command.
99+
> If you want to generate an unencrypted private key, append `-nocrypt` to the end of the command.
100100
101101
```
102102
openssl genrsa 2048 | openssl pkcs8 -topk8 -v2 des3 -inform PEM -out key_name.p8
@@ -114,13 +114,12 @@ After you've created the public key, save the file to a local directory.
114114

115115
##### Generate a new user and assign the key to them
116116

117-
Now, create a new user by executing the following SQL command, replacing the public key value with the key you previously generated. If you generated an unencrypted key, omit the `RSA_PUBLIC_KEY_FP` value, as it is only required for users with encrypted keys.
117+
Now, create a new user by executing the following SQL command, replacing the public key value with the key you previously generated.
118118

119119
``` sql
120120
CREATE USER SEGMENT_USER
121121
DEFAULT_ROLE = SEGMENT
122-
RSA_PUBLIC_KEY = 'MIIBIjANBgkqh...'
123-
RSA_PUBLIC_KEY_FP = 'enter the passphrase you created';
122+
RSA_PUBLIC_KEY = 'enter your public key';
124123
GRANT ROLE "SEGMENT" TO USER "SEGMENT_USER";
125124
```
126125

@@ -244,7 +243,7 @@ At this time, the Segment Snowflake destination is not compatible with Snowflake
244243

245244
### Key pair authentication
246245

247-
Segment recommends that you authenticate with your Snowflake warehouse using key-pair authentication. Key-pair authentication uses PKCS#8 private keys, which are typically exchanged in the PEM base64-encoded format.
246+
Segment recommends that you authenticate with your Snowflake warehouse using an encrypted key pair. Key-pair authentication uses PKCS#8 private keys, which are typically exchanged in the PEM base64-encoded format.
248247

249248
Although you can create up to two keys in Snowflake, Segment only supports authenticating with one key at a time. To change the key that is in Segment, return to your Snowflake destination's settings and upload a new key in the **Private Key** field.
250249

0 commit comments

Comments
 (0)