Advanced Analytica Advanced Analytica: IBOM
← All connectors
Redshift logo

Source connector

Redshift

Set up Redshift as a source and move its data into your chosen destination.

Version 0.5.5 community alpha

Redshift

You can replicate data from Amazon Redshift to your destination using JDBC. The connector supports full refresh and cursor-based incremental syncs.

Features

FeatureSupportedNotes
Full Refresh SyncYes
Incremental SyncYesCursor-based, using ORDER BY on a user-defined cursor column
Replicate Incremental DeletesNo
Logical Replication (WAL)No
SSL SupportYesEnabled by default on all connections
SSH Tunnel ConnectionNo
NamespacesYesEnabled by default
Schema SelectionYesMultiple schemas may be used at one time; leave empty to replicate all schemas

The Redshift source doesn’t alter your warehouse schema. However, the connected destination may alter it. See the destination’s documentation for details.

Incremental sync

You can run incremental syncs using a user-defined cursor field, such as an updated_at column. The connector uses this column to track rows changed since the previous sync.

You must also configure a primary key for the stream to run incremental + dedupe syncs.

Prerequisites

  1. An active Amazon Redshift cluster.
  2. A database user with SELECT permission for the tables you want to replicate. A dedicated read-only user is recommended.
  3. Network access from Airbyte to your Redshift cluster, if they’re in separate VPCs. See Authorizing access to your cluster in the AWS docs.

Setup guide

1. Verify cluster access

Use the Test Connection button in the Airbyte UI to confirm Airbyte can reach your Redshift cluster. If the connection fails, review your VPC security groups and subnet routing.

2. Configure the source

Enter these connection details in the Airbyte UI:

FieldDescription
HostThe endpoint of your Redshift cluster, without the port or database name. This typically includes the cluster ID, region, and ends with .redshift.amazonaws.com. Find it on the cluster details page under Connection string.
PortThe port your cluster listens on. The default is 5439.
DatabaseThe name of the database to connect to.
UsernameThe database user to authenticate as.
PasswordThe password for the database user.
Schemas(Optional) A list of schemas to replicate. Schema names are case-sensitive. Leave empty to replicate all schemas the user has access to.
JDBC URL Params(Optional) Additional JDBC connection properties, formatted as key=value pairs separated by & (for example, loginTimeout=30&tcpKeepAlive=true).

Encryption

All connections use SSL by default. You don’t need any additional configuration.

Data type handling

The connector automatically maps Redshift data types to Airbyte types. Be aware of these behaviours:

  • The connector reads timestamp and timestamptz columns as raw server-rendered strings, then parses them. This bypasses the JDBC driver’s timezone conversion. It avoids a known JDBC driver behaviour that can shift timestamps by an hour during daylight saving time transitions.
  • Redshift stores timestamptz values as UTC. The connector preserves the UTC instant when serialising these values.
  • When using a timestamptz column as an incremental sync cursor, the connector handles timezone-aware and timezone-naive cursor formats.

Limitations

  • Change Data Capture (CDC) isn’t supported. Only cursor-based incremental replication is available.
  • SSH tunnel connections aren’t supported.
  • IAM-based authentication isn’t supported. You must authenticate with a database username and password.

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

Changelog

Expand to review
VersionDatePull RequestSubject
0.5.52026-06-0474769Handle timezone-aware timestamps in cursor parsing and fix DST offset in timestamptz reads
0.5.42025-07-1662922Convert to new gradle build flow
0.5.32024-12-1849893Use a base image: airbyte/java-connector-base:1.0.0
0.5.22024-02-1335223Adopt CDK 0.20.4
0.5.12024-01-2434453bump CDK version
0.5.02023-12-1833484Remove LEGACY state
(none)2023-11-1732616Improve timestamptz handling
0.4.02023-06-2627737License Update: Elv2
0.3.172023-06-2027212Fix silent exception swallowing in StreamingJdbcDatabase
0.3.162022-12-1420346Consolidate date/time values mapping for JDBC sources
0.3.152022-10-1316238Update incremental query to avoid data missing when new data is inserted at the same time as a sync starts under non-CDC incremental mode
0.3.142022-09-0116258Emit state messages more frequently
0.3.132022-05-25Added JDBC URL params
0.3.122022-08-1814356DB Sources: only show a table can sync incrementally if at least one column can be used as a cursor field
0.3.112022-07-1414574Removed additionalProperties:false from JDBC source connectors
0.3.102022-04-2912480Query tables with adaptive fetch size to optimize JDBC memory consumption
0.3.92022-02-219744List only the tables on which the user has SELECT permissions.
0.3.82022-02-1410256Add -XX:+ExitOnOutOfMemoryError JVM option
0.3.72022-01-269721Added schema selection
0.3.62022-01-208617Update connector fields title/description
0.3.52021-12-248958Add support for JdbcType.ARRAY
0.3.42021-10-217234Allow SSL traffic only
0.3.32021-10-126965Added SSL Support
0.3.22021-08-134699Added json config validator
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.