Aurora zero-ETL integrations with Amazon Redshift

Help you derive holistic insights from multiple data sources.

Eliminate the need to build and maintain complex data pipelines that perform extract, transform, and load (ETL) operations. Zero-ETL integrations remove the challenges that come with building and managing pipelines by provisioning and managing them for you.

Reduce operational burden and cost, and let you focus on improving your applications.

Let you leverage Amazon Redshift's analytics and ML capabilities to derive insights from transactional and other data, to respond effectively to critical, time-sensitive events.

The source DB cluster must be in the same Region as the target Amazon Redshift data warehouse.

You can't rename a DB cluster or any of its instances if it has existing integrations.

You can't create multiple integrations between the same source and target databases.

You can't delete a DB cluster that has existing integrations. You must delete all associated integrations first.

If you stop the source DB cluster, the last few transactions might not be replicated to the target data warehouse until you resume the cluster.

If your cluster is the source of a blue/green deployment, the blue and green environments can't have existing zero-ETL integrations during switchover. You must delete the integration first and switch over, then recreate it.

A DB cluster must contain at least one DB instance in order to be the source of an integration.

You can't create an integration for a source DB cluster that is a cross-account clone, such as those shared using AWS Resource Access Manager (AWS RAM).

If your source cluster is the primary DB cluster in an Aurora global database and it fails over to one of its secondary clusters, the integration becomes inactive. You must delete and recreate the integration.

You can't create an integration for a source database that has another integration being actively created.

When you initially create an integration, or when a table is being resynchronized, data seeding from the source to the target can take 20-25 minutes or more depending on the size of the source database. This delay can lead to increased replica lag.

Some data types aren't supported. For more information, see Data type differences between Aurora and Amazon Redshift databases.

Object identifiers (including database name, table name, column names, and others) can contain only alphanumeric characters, numbers, $, and _ (underscore).

System tables, temporary tables, and views aren't replicated to Amazon Redshift.

ALTER TABLE partition operations cause your table to resynchronize in order to reload data from Aurora to Amazon Redshift. The table will be unavailable for querying while it's resynchronizing. For more information, see One or more of my Amazon Redshift tables requires a resync.

Your source DB cluster must be running a supported version of Aurora MySQL. For a list of supported versions, see Supported Regions and Aurora DB engines for zero-ETL integrations with Amazon Redshift.

Zero-ETL integrations rely on MySQL binary logging (binlog) to capture ongoing data changes. Don't use binlog-based data filtering, as it can cause data inconsistencies between the source and target databases.

Zero-ETL integrations are supported only for databases configured to use the InnoDB storage engine.

Foreign key references with predefined table updates aren't supported. Specifically, ON DELETE and ON UPDATE rules aren't supported with CASCADE, SET NULL, and SET DEFAULT actions. Attempting to create or update a table with such references to another table will put the table into a failed state.

XA transactions performed on the source DB cluster cause the integration to enter a state of Syncing.

Your source DB cluster must be running a supported version of Aurora PostgreSQL. For a list of supported versions, see Supported Regions and Aurora DB engines for zero-ETL integrations with Amazon Redshift.

If you select an Aurora PostgreSQL source DB cluster, you must specify at least one data filter pattern. At minimum, the pattern must include a single database (database-name.*.*) for replication to Amazon Redshift. For more information, see Data filtering for Aurora zero-ETL integrations with Amazon Redshift.

All databases created within the source Aurora PostgreSQL DB cluster must use UTF-8 encoding.

If you perform declarative partitioning transactions on the source DB cluster, all affected tables enter a failed state and are no longer accessible in Amazon Redshift.

Two-phase transactions aren't supported.

If you delete all DB instances from a DB cluster that is the source of an integration and then re-add a DB instance, replication breaks between the source and the target clusters.

The source DB cluster can't use use Aurora Limitless Database.