Redshift speaks the Postgres wire protocol on a different port. The setup mirrors Postgres with a few Redshift-specific notes.
Step 1: Create a read-only user
CREATE USER klairr_reader PASSWORD '...';
GRANT USAGE ON SCHEMA public TO klairr_reader;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO klairr_reader;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO klairr_reader;UNLOAD, COPY, VACUUM, and ANALYZE are explicitly blocked at the SQL guardrail layer regardless of the user’s role.
Step 2: Add the connector
| Field | Example |
|---|---|
| Cluster endpoint | my-cluster.cabcdef.us-east-1.redshift.amazonaws.com |
| Port | 5439 |
| Database | analytics |
| Schema | public |
| Username | klairr_reader |
| Password | … |
| SSL mode | Require (recommended) |
Notes
- For IAM-based auth, contact support — username/password is the v1 path.
- DISTKEY/SORTKEY hints are surfaced in the schema DDL passed to the LLM.
- Cost-per-query is not metered by Klairr; Redshift bills on cluster compute.