Skip to Content
DestinationsRedshiftOverview

Amazon Redshift

Source + Destination — Vendo connects to your Redshift cluster or Serverless workgroup via the Redshift Data API. No VPC setup, no JDBC drivers, no firewall changes. Your data stays in your warehouse.

Key Benefits

  • Zero-Copy Access — Query your Redshift tables directly. Data never leaves your cluster.
  • No VPC Required — The Redshift Data API works over the public AWS API, not through your VPC.
  • Provisioned & Serverless — Works with both classic provisioned clusters and Redshift Serverless.
  • PostgreSQL Compatible — Standard SQL queries using familiar PostgreSQL syntax.

How It Works

Vendo connects via the AWS Redshift Data API, which executes SQL statements against your cluster without requiring a direct network connection. Queries are submitted asynchronously, and results are retrieved once complete.

No data is stored by Vendo. Query results are used in-flight and discarded after processing.

Authentication

Vendo uses AWS IAM credentials (access key + secret key) to authenticate with the Redshift Data API. The IAM user needs permissions to execute statements and retrieve results.

MethodDescription
IAM CredentialsAWS access key ID + secret access key with Redshift Data API permissions
Database UserOptional — for provisioned clusters using GetClusterCredentials

What You Need

  • An Amazon Redshift provisioned cluster or Serverless workgroup
  • AWS IAM credentials with Redshift Data API permissions
  • The cluster identifier (provisioned) or workgroup name (Serverless)
  • The database name and AWS region

Platform Details

SettingValue
Connection MethodAWS Redshift Data API
Query ExecutionAsync (execute + poll + get results)
AuthenticationAWS IAM credentials
Data StorageNone — zero-copy
VPC/FirewallNot required

What to Expect After Setup

  1. Connection Verified — Vendo tests connectivity via the Data API
  2. Schema Browser — Browse schemas and tables in the Vendo UI
  3. Query Ready — Run SQL queries, build models, and create audiences
  4. No Sync Needed — Queries execute directly against your cluster
Last updated on