.avif)
Overview
- Connect to Snowflake with key-pair (JWT) authentication
- Reference a table directly by
database.schema.table - Refresh on a schedule with standard cron expressions
What you'll need
A few connection details link Ridge to your account. Collect these before you start.
Set up the connection
1 Create a Connection
On the Data page, click New Connection and choose Snowflake as the type. Enter the credentials you gathered, then save.
- Account identifier and Username
- Private key (PEM) and its password
2 Create a Dataset
Back on the Data page, click New, select source Connection, and pick the Snowflake connection you just created. A Data Set points at a specific table and carries its own refresh schedule.
3 Select a table
Pick the table Ridge reads from Snowflake, referenced as database.schema.table.
4 Schedule ingestion
Set an ingestion schedule with standard cron syntax, then save. Ridge reads the table from Snowflake and stores the results, ready for analysis.
Best practices
A few habits keep ingestion secure and predictable.
Supported features & limitations
- Connects with key-pair (JWT) authentication — no password stored
- Reads any table your role has read access to
- IP allowlisting — Ridge reads Snowflake from a single static IP,
44.252.226.28, so you can add it to a Snowflake network policy and keep your account closed to everything else - Tests the connection when you save it, so credential problems surface immediately
- Refreshes on the schedule you set, with no infrastructure to manage
- Key-pair (JWT) auth only — username/password authentication is not supported.
Troubleshooting
Most connection issues fall into four buckets. Expand the one that matches your error.
Invalid credentials
"marshaling private key failed", "could not parse PEM", "incorrect username or password", "JWT token is invalid", 401
Your PEM key or password is bad, or the JWT was rejected. Re-paste the PEM key (keep the newlines) and password, and confirm key-pair auth is registered on the user.
Insufficient permissions
"insufficient privileges", "access control", "not allowed from this IP", 403
The role lacks rights. Grant it read access to the object. If your account uses a network policy, confirm 44.252.226.28 is on its allowed list.
Resource not found
"does not exist or not authorized", "object does not exist", "account name", 404
The account identifier or object name is wrong. Fix the identifier.
Network unreachable
"could not resolve host", "timed out", "connection refused"
The host is unreachable or timed out. Check your egress allowlist and account host.