Browse every Redshift database in the Data Catalog, and connect over PrivateLink

Two Redshift gaps. The Data Catalog only showed the database named in the connector's endpoint, so on a multi-database cluster most of it was invisible. And Redshift was left out of the PrivateLink option, because Artie derived the connection host from the cluster endpoint and so testing a connection dialed the public endpoint instead of the private one, even when you had a PrivateLink ready.

The Data Catalog now enumerates every database your connection can reach on a Redshift destination and runs each database's queries against that database, so the schema tree and search cover the whole cluster. A database the connection user cannot open is skipped and logged rather than failing the catalog. Redshift is also now offered as a PrivateLink connection in connector settings and in the guided setup's network step; you still enter the cluster endpoint for the port and database, and Artie routes save, test, and pipeline traffic through the PrivateLink host. Pipelines continue to write to the endpoint's database.

This is for teams running multi-database Redshift clusters, or ones that keep Redshift off the public internet.

Why this matters

• See and search every Redshift database from one connection
• Reach Redshift privately with the same PrivateLink flow as your other connectors
• No change to where pipelines write