Connection requirements
- A cluster or Redshift Serverless endpoint reachable from the worker, with INSERT/UPDATE on the target schema
Parameterized INSERT ... ON CONFLICT
Redshift's COPY command expects data staged in S3, which NoSQLSync doesn't require you to provision — so both the bulk load and CDC use a parameterized INSERT ... ON CONFLICT DO UPDATE instead.
Setup
1
Add the connection
Provide the Redshift connection details under Connections → Add. NoSQLSync verifies it can connect before saving.
2
Pick a table name
Choose an existing table or let NoSQLSync create one from the inferred schema when the migration starts.
3
Start the migration
Bulk-load the historical data, then optionally enable CDC to keep the table current.
FAQ
Does NoSQLSync create the Redshift table for me?
Yes. If the target table doesn't exist, it's created from the inferred schema before the first batch loads.
What happens if I re-run a migration that already has data in the target?
The bulk load switches to an idempotent upsert path instead of the empty-table fast path, so re-running is safe.