Connect Jedify to Snowflake using key-pair authentication with a dedicated service user, role, and warehouse. The steps below walk through every command you need to run in Snowflake and in your terminal.Documentation Index
Fetch the complete documentation index at: https://docs.jedify.com/llms.txt
Use this file to discover all available pages before exploring further.
Setup steps
1. Get your Snowflake account identifier
Run this query in Snowflake. You’ll paste the result into the Jedify connector form at the end.2. Generate a private and public key pair
Run the following commands in your terminal. They write two files to your current directory:rsa_key.p8 (private) and rsa_key.pub (public).
3. Create a service user, role, and dedicated warehouse
Start the warehouse at size XS — Jedify uses it for lightweight metadata queries, and you can resize later if needed.4. Set the public key on the user
Snowflake expects the public key as a single line, with the-----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- lines removed and all newlines stripped. Run this in your terminal to print the key in the right format:
Using
ALTER USER (rather than setting rsa_public_key inside CREATE USER) makes this step safe to re-run and ensures the key is updated even when JEDIFY_USER already exists.5. Grant the role to the user
6. Grant warehouse and query monitor privileges
7. Grant access to your data
Replace<DB> and <SCHEMA> with the database and schema you want Jedify to read from.
8. Verify permissions
9. Whitelist Jedify’s IP addresses (if applicable)
If your Snowflake account uses network policies, add Jedify’s IPs to your allowlist. See Pro Tips below for the current list.10. Configure the connector in Jedify
In the Jedify Snowflake connector form, provide:- Account identifier — the value from step 1.
- User —
JEDIFY_USER. - Role —
JEDIFY_ROLE. - Warehouse —
JEDIFY_WH. - Private key — paste the contents of
rsa_key.p8as-is, including the-----BEGIN PRIVATE KEY-----and-----END PRIVATE KEY-----lines and all line breaks. To copy it, run:
Next steps
- To restrict which rows each Jedify end-user can see, see Snowflake Row-Level Security.
Pro Tips
- If you see errors like “JWT token is invalid”, the
JEDIFY_USERpublic key is not set correctly. Re-run step 4 and make sure the header, trailer, and newlines are stripped. - If you use IP allowlisting, whitelist the following Jedify IPs:
52.204.197.134,18.214.105.237,3.221.71.32,54.146.39.101,44.223.227.241,34.232.100.157,18.205.143.126,3.225.6.155,3.93.123.244,44.209.198.167,54.209.19.14,52.6.210.170. - Use
type = SERVICEwhen creating the Jedify user to ensure programmatic-only access. - Use
CREATE IF NOT EXISTSin setup scripts to make them safe to re-run. - Grant
SELECT ON FUTURE TABLES(orVIEWS) so Jedify keeps access as new objects are added.