Before you start

  • Your data plane must be able to reach the cluster over TCP — a public endpoint, a peered network (VPC peering / PrivateLink), or an SSH tunnel to a private one. Redshift’s default port is 5439.
  • A Redshift user Dippr can log in as with a password. It needs at least SELECT on the schemas you want to expose (schema discovery reads information_schema.columns, excluding pg_catalog and information_schema).

Register the integration

From Integrations, choose Register integration and select Amazon Redshift.
Redshift’s SSL modes are the Amazon driver’s, not Postgres’s. verify-ca (the default) encrypts and checks the server certificate’s chain; verify-full additionally checks the hostname; disable turns TLS off. There is no require mode — a Redshift cluster terminates TLS by default, so the secure verify-ca default is the one you want unless you have a reason to change it.
Capabilities available for this kind: driver (required) and federation. Federation is what makes the cluster a catalog on your query engines. (This kind is not exposed as MCP tools.)

Test connection

Runs SELECT 1 followed by SELECT version() against the stored (or, before saving, the drafted) credentials and reports the server’s version string on success. A failure reports the driver’s own error — a wrong password, an unreachable host, or a database that doesn’t exist.

In Explore

Once a query engine applies this integration, it appears as a catalog named after the integration’s display name (lowercased, non-alphanumeric characters collapsed to underscores; a name that collides with another catalog gets a short suffix; see How catalogs are named). Every schema and table your Redshift user can read from information_schema appears under it, with column names, types and nullability.

Limitations

  • Discovery reports schemas and tables only — no row counts, indexes or constraints.
  • Federation is over JDBC. IAM authentication and the S3 UNLOAD parallel-read path are not supported in this version — connect with a database user and password.
  • The integration does not itself make the cluster read-only. What the engine can read or write in Redshift is bounded by the grants of the database user you connect as (and by your own Dippr roles), not by this record — so connect as a user with only the access you intend to expose.

Equivalent dip command

Register a Redshift source

Troubleshooting

SSH tunnels

Reach a cluster sitting behind a bastion, in a private network.

Test connection and secrets

How Test connection works, and how your credentials are stored.