Integrations / Amazon Redshift
Amazon Redshift
Amazon Redshift data warehouse service
Basic auth
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
An Amazon Redshift cluster or workgroup Telara can reach (publicly, via peering, or through a path your admin set up).
A database user that can connect. Do not use the master password of a human DBA login if you can avoid it.
Vendor setup
Get the credential
1
Create a database user
In the Redshift query editor (or SQL), CREATE USER for Telara and GRANT the schemas you want read. Copy the username and password.
2
Copy connection fields
In the AWS console, open the cluster or workgroup → Properties. Copy endpoint host, port, database name, and the cluster/workgroup identifier if the form asks.
3
Paste in Telara
Settings → Integrations → Amazon Redshift. Enter host, port, database, username, and password. Enable TLS if the form offers it.
In Telara
Connect in Telara
Basic auth
In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.
Fields Telara asks for
- Username
- Password
- Host
- Port
- Database
- Cluster
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Schema | Partial — not every record the vendor holds is synced |
| Table | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Schema | Up to 1 day | Removed records disappear on the next full sync |
| Table | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Schema, Table.
After connect
Verify it worked
This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.
Honesty
Known limitations
Security groups and NACLs that block Telara produce timeouts, not SQL errors.
Serverless workgroups and provisioned clusters have different endpoints — copy from the resource you mean.