Amazon DynamoDB Agent for Gluesync: Key Features
Core principles
Gluesync uses the SDK provided by AWS for DynamoDB to connect and consume the DynamoDB APIs.
Change data capture
CDC is implemented using the native APIs called DynamoDB Streams. To read more about DynamoDB Streams please refer to the official AWS documentation available here at this link.
Platform supported features
| Feature | Support | Notes |
|---|---|---|
Target role |
✅ |
Writes to DynamoDB through the official AWS SDK with TLS enforced by default. |
Source role |
✅ |
Consumes DynamoDB Streams to capture real-time changes from tables in any region. |
Snapshots |
✅ |
Supports Core Hub snapshot tasks that scan DynamoDB tables for initial loads. |
CDC |
✅ |
Continuous replication based on Streams shards for near real-time forwarding. |
CDC type |
DynamoDB Streams |
Relies on AWS’s native change stream API (Streams docs). |
Bulk load |
N/A |
Bulk staging tables only apply to relational stores; DynamoDB snapshots + Streams handle throughput needs. |
Source persisted internal cache |
N/A |
State tracking lives in Core Hub metadata; agent does not maintain its own disk cache. |
Target persisted internal cache |
N/A |
Writes go straight to DynamoDB via the AWS SDK. |
Driver / connector |
AWS SDK for Java/Kotlin |
Gluesync embeds the official AWS DynamoDB SDK. |
Chains |
N/A |
Not supported being it a NoSQL database. |
Truncate operation support (reading) |
N/A |
DynamoDB has no TRUNCATE primitive; deletions must be explicit. |
Truncate operation support (writing) |
N/A |
Targets cannot issue TRUNCATE-equivalent operations on DynamoDB tables. |