Real-time
Two-way sync
Changes in Citus or Dynamo DB instantly reflect in both systems. No stale data, no manual imports.
Database
Citus to Dynamo DB integration — real-time, two-way sync
Keep Citus and Dynamo DB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Citus and Dynamo DB
Keep Citus and Dynamo DB synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Citus and Dynamo DB continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
- Consolidate multi-region Global Tables data into a single reporting store.
- Replace ad-hoc export scripts with continuous sync driven by DynamoDB Streams.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Cross-engine sync
Keep the same dataset live in both Citus and Dynamo DB, so each workload runs on the engine that suits it.
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
What you can sync between Citus and Dynamo DB
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Citus objects | Dynamo DB objects | |
|---|---|---|
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | DynamoDB Streams Ordered item-level change records consumed for incremental sync. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Global Tables Multi-region replicas relevant when syncs must read from a specific region. |
What ships with Citus ⇄ Dynamo DB
Connect Citus and Dynamo DB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Dynamo DB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Dynamo DB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Citus or Dynamo DB record.
Observability
Monitoring
Track your Citus ⇄ Dynamo DB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Dynamo DB.
How the Citus and Dynamo DB connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
Dynamo DB
- Integration surface
- Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries
- Authentication
- AWS IAM credentials with SigV4 request signing
- Change detection
- Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration
- Capabilities
- read · write · CDC
- Rate limits
- Throughput is governed by the table's provisioned or on-demand capacity mode
How it works
How to connect Citus to Dynamo DB — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Citus and Dynamo DB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
Dynamo DB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Dynamo DB objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Citus ⇄ Dynamo DBCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus Dynamo DBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Dynamo DB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Dynamo DB: authenticate both systems, choose the objects to sync (such as Citus's Reference tables and Local tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Dynamo DB: Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries. Authentication: AWS IAM credentials with SigV4 request signing. Stacksync manages authentication, retries, and rate limits on both sides.
-
Citus: Distributed tables are sharded by a declared distribution column, and reference tables are fully replicated to all nodes; the table type changes how writes and joins behave. Dynamo DB: Items are schemaless apart from the mandatory partition key (and optional sort key), so sync field mappings are defined per attribute rather than from a fixed schema. Stacksync's field mapping accounts for these differences between Citus and Dynamo DB without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Citus and Dynamo DB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Dynamo DB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Dynamo DB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and Dynamo DB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
SECURITY
Security teams love Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Citus and Dynamo DB.
Popular · 8 of 386
-
Citus ⇄ Google AlloyDB -
Citus ⇄ IBM Db2 -
Citus ⇄ Firebase -
Citus ⇄ SingleStore -
Dynamo DB ⇄ RavenDB -
Dynamo DB ⇄ Redis Enterprise -
Dynamo DB ⇄ SAP ASE (Sybase) -
Dynamo DB ⇄ Scaleway Postgres
No integrations match .
