MongoDB to Redshift
real-time replication
TwinCommit replicates MongoDB to Amazon Redshift in real time by reading the MongoDB transaction log and applying every committed change exactly once and in commit order. Use it to feed Redshift with live MongoDB data for analytics, AI and reporting, with no triggers or capture tables on the source.
MongoDB
log reader
commit-ordered · exactly-once
Redshift
native writer
How capture works on MongoDB
TwinCommit opens change streams on replica sets and sharded clusters, persists resume tokens with the checkpoint, and keeps multi-document transactions intact.
Prerequisites
- ✓Replica set or sharded cluster (change streams need an oplog)
- ✓changeStream and find privileges on watched databases
- ✓Pre- and post-images enabled for full before/after values (optional)
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 MongoDB → Redshift in four steps
- 1
Prepare MongoDB
Run twincommit check. It verifies replica set or sharded cluster (change streams need an oplog) 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: mongodb
uri: ${MONGODB_URI}
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.customersMongoDB to Redshift replication FAQ
How does TwinCommit replicate MongoDB to Redshift?
+
TwinCommit reads changes from the MongoDB 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 MongoDB to Redshift replication need triggers or capture tables?
+
No. TwinCommit reads the MongoDB log directly and creates no objects in the source database.
Is MongoDB 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 MongoDB versions are supported?
+
MongoDB 5.0–8.x · MongoDB Atlas · replica sets and sharded clusters.
Stream MongoDB to Redshift today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.