MySQL to Redshift
real-time replication
TwinCommit replicates MySQL to Amazon Redshift in real time by reading the MySQL transaction log and applying every committed change exactly once and in commit order. Use it to feed Redshift with live MySQL data for analytics, AI and reporting, with no triggers or capture tables on the source.
MySQL
log reader
commit-ordered · exactly-once
Redshift
native writer
How capture works on MySQL
TwinCommit connects as a replica, reads the row-based binary log and tracks position by GTID, so failovers and replica promotions are seamless.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓GTID mode recommended
- ✓REPLICATION SLAVE and REPLICATION CLIENT grants
How apply works on Redshift
Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Requirements
- ✓An S3 staging bucket and IAM role for COPY
- ✓A database user with CREATE on the target schema
- ✓Network path to the cluster or workgroup endpoint
Setup
Set up MySQL → Redshift in four steps
- 1
Prepare MySQL
Run twincommit check. It verifies binlog_format = row and binlog_row_image = full and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Redshift
Add a target block for Redshift. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: mysql
dsn: ${SOURCE_DSN}
server_id: 4201
target:
type: redshift
host: analytics.123456789.us-east-1.redshift-serverless.amazonaws.com
database: dev
staging_bucket: s3://acme-twincommit-staging
iam_role: arn:aws:iam::123456789012:role/twincommit-copy
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MySQL to Redshift replication FAQ
How does TwinCommit replicate MySQL to Redshift?
+
TwinCommit reads changes from the MySQL transaction log, buffers them per transaction, and applies each committed transaction to Redshift in commit order. Micro-batches are written to S3 as Parquet, loaded with COPY into staging tables, and applied with MERGE in one transaction together with the checkpoint.
Does MySQL to Redshift replication need triggers or capture tables?
+
No. TwinCommit reads the MySQL log directly and creates no objects in the source database.
Is MySQL to Redshift replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Redshift transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MySQL versions are supported?
+
MySQL 5.7, 8.0, 8.4, 9.x · Amazon RDS & Aurora MySQL · Azure Database for MySQL · Cloud SQL.
Stream MySQL to Redshift today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.