Amazon Redshift Connector

Use Amazon Redshift with Supaflow to load data from your sources into a Redshift warehouse, or replicate data from Redshift to another data platform.

SourceDestinationBronze

Start for Free Source Documentation Destination Documentation

Evaluating against Fivetran? See how Supaflow handles Amazon Redshift pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Load Amazon Redshift into Snowflake

Dedicated pages for destination-specific setup, buyer questions, and Snowflake sync behavior.

Amazon Redshift to Snowflake

Migrate Amazon Redshift tables into Snowflake with native bulk export and incremental updates.

View pipeline page

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Redshift as a Destination

Load data from any supported Supaflow source into Redshift for analytics in AWS.

Redshift as a Source

Replicate selected Redshift tables into another warehouse, database, data lake, or activation destination.

Accessible Schemas and Tables

Supaflow lists tables across the schemas your Redshift user can access. Grant SELECT only where pipelines should read.

Full Refresh or Incremental

Run full refresh for small tables or use cursor-based incremental sync when a table has a reliable date or timestamp column.

Supported Objects

Source Objects

Tables across accessible schemas

All Redshift tables the configured user can access and has SELECT permission on.

Destination Objects

Tables loaded into Redshift

Data from any supported Supaflow source written to your Redshift database and schema.

How It Works

Prepare Redshift permissions

Create a Redshift user with SELECT access for source pipelines, or write permissions for destination pipelines. Allow Supaflow network access to your Redshift endpoint or use your private network path.

Configure AWS access

Follow the setup guide for the required AWS role, then associate it with your Redshift cluster or Serverless namespace.

Enter connection details

Provide the Redshift connection details, credentials, and AWS role information in Supaflow.

Test and save

Click Test & Save to verify Redshift connectivity, metadata access, destination write permissions when applicable, and AWS role access.

Use Cases

Build a Redshift warehouse

Bring product, CRM, finance, database, and file data into Redshift without custom loaders.

Move Redshift data out

Send selected Redshift tables to another data platform when teams need the data outside AWS.

Keep access scoped

Use Redshift permissions and pipeline selection to expose only the schemas, tables, and columns each workflow needs.

Frequently Asked Questions

How do I connect Supaflow to Amazon Redshift in a private VPC?

Deploy a self-hosted Docker Agent on a stable host with network access to the Redshift cluster or Serverless workgroup. The agent connects to Redshift through the private VPC path and polls Supaflow over outbound HTTPS, so the Redshift endpoint does not need to be publicly accessible. A temporary workstation tunnel is not the recommended connectivity pattern for Redshift.

Deploy a self-hosted Docker Agent

Can Redshift be both a source and a destination?

Yes. Supaflow can read Redshift tables as a source and can also load data into Redshift as a destination.

Which Redshift tables can Supaflow sync?

Supaflow supports tables across the schemas the configured Redshift user can access. Grant SELECT only on the schemas and tables you want available for source pipelines.

Does the Redshift source support CDC?

No. The Redshift source supports full refresh and cursor-based incremental sync. It does not read Redshift logs for CDC and does not detect hard deletes from source tables.

Can I use separate IAM roles for Supaflow and Redshift?

Yes. If your AWS controls require separation, configure a second Redshift IAM role in Advanced Settings.