Two-way sync
Changes in Amazon DynamoDB or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon DynamoDB and Starburst Enterprise in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Amazon DynamoDB's rows in Starburst Enterprise, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Amazon DynamoDB where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Amazon DynamoDB sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into Amazon DynamoDB, with schema and type mapping between the two systems handled for you.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Starburst Enterprise and keep Amazon DynamoDB focused on its operational workload.
Rows from Amazon DynamoDB land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
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.
| Amazon DynamoDB objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Tables Top-level containers, each with a partition key and optional sort key; Stacksync syncs a table as a stream of items with full read and write via PutItem, UpdateItem, and DeleteItem. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Time to Live (TTL) is specific to Amazon DynamoDB and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Items Individual schemaless records (attributes up to 400 KB each); read with GetItem, Query, and Scan and written with PutItem or BatchWriteItem, so write is supported here. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Items is specific to Amazon DynamoDB and Schemas to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Global secondary indexes (GSIs) Alternate key projections that let you Query by non-key attributes without a full table Scan; read-only views maintained automatically by DynamoDB. | Views Engine-level SQL views used to shape federated data before syncing it out. | Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Local secondary indexes (LSIs) Extra sort keys within the same partition key, defined at table creation; queried like the base table for alternate access patterns. | Materialized views Precomputed results that make repeated sync reads cheaper. | Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| DynamoDB Streams Ordered item-level change records (INSERT, MODIFY, REMOVE) with old/new image views and 24-hour retention; the native change-data-capture source Stacksync reads for near-real-time sync. | Columns Typed per the Trino type system, mapped from each source's native types. | DynamoDB Streams is specific to Amazon DynamoDB and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionChanges in Amazon DynamoDB are captured at the source via change data capture — no polling loop against its API. DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views.
DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
DeliveryEach detected change is applied to Amazon DynamoDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon DynamoDB–Starburst Enterprise connection.
Changes in Amazon DynamoDB or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon DynamoDB or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Amazon DynamoDB or Starburst Enterprise record.
Track your Amazon DynamoDB ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Starburst Enterprise.
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.
Authenticate Amazon DynamoDB and Starburst Enterprise with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Amazon DynamoDB and Starburst Enterprise 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Amazon DynamoDB and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Amazon DynamoDB's Tables and Time to Live (TTL)), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Amazon DynamoDB and Starburst Enterprise: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Amazon DynamoDB: AWS SDK / low-level HTTPS JSON API at dynamodb.<region>.amazonaws.com (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan, BatchWriteItem, TransactWriteItems), plus PartiQL (ExecuteStatement) for SQL-style access and DynamoDB Streams for change capture. Authentication: AWS Signature Version 4 (SigV4) signed requests using an IAM access key ID and secret key, or temporary STS credentials from an assumed IAM role; IAM policies scope access down to table and item level. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
Starburst Enterprise: The engine stores no data itself; reads and writes pass through to the underlying sources, and write support depends on each connector. Amazon DynamoDB: Throughput is metered in capacity units (provisioned or on-demand): 1 WCU = one 1 KB write/second and 1 RCU = one strongly-consistent 4 KB read/second; breaching capacity returns ProvisionedThroughputExceededException and the request is throttled. Stacksync's field mapping accounts for these differences between Amazon DynamoDB and Starburst Enterprise 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 Amazon DynamoDB and Starburst Enterprise records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon DynamoDB and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon DynamoDB–Starburst Enterprise integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 468 integrations available for Amazon DynamoDB and Starburst Enterprise.