Skip to main content
The Redshift connector uses the Redshift Data API, so Danube needs no driver and no network path to your cluster: every call is an authenticated AWS API request. It works with provisioned clusters and Redshift Serverless. Setup and the IAM policy are on the AWS page.

​
Connection fields

Besides the AWS fields (role or keys, region), store:
  • Cluster identifier for a provisioned cluster, or Serverless workgroup for Redshift Serverless (one of the two);
  • Database;
  • Database user (provisioned clusters: Danube connects as this user with temporary IAM credentials) or Secret ARN (a Secrets Manager secret holding a user name and password).

​
Tools

​
Read-only at the source

The Data API has no read-only switch, so the database user decides what a statement can do. Run Query refuses comments, several statements and write keywords before anything is sent, but connect as a user that can only read:
Repeat the grants for every schema agents should read. For a secret, create the user with a password instead and store the name and password in Secrets Manager.

​
Limits

  • Calls time out after 15 s by default (up to 55 s). A statement that times out keeps running in Redshift; its result stays available for 24 hours through statement_id.
  • The row cap cuts what is returned, not what Redshift computes. Add a LIMIT to large queries.

​
Example prompts

  • “Which tables are in the sales schema?”
  • “How many orders failed payment per day over the last two weeks?”
  • “Top ten merchants by declined card volume this month.”