Source connector

Amazon DynamoDB connector

Amazon DynamoDB integration for databases, warehouses and BI tools

Serverless key-value and document store on AWS. Datrise captures Amazon DynamoDB entities such as tables, items, partition keys, sort keys, attributes and stream records, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Amazon DynamoDB API (Scan / Query, DynamoDB Streams, Export to S3) authenticates with API key, and Amazon DynamoDB caps calls at No requests-per-second API cap; throughput is bounded by provisioned or on-demand read capacity, and a single Scan or Query page is hard-capped at 1 MB.

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `source_dynamodb_tables`) with a schema derived from the Amazon DynamoDB API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Amazon DynamoDB pipeline page, and join the waitlist to get the Amazon DynamoDB connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Amazon DynamoDB data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
tables	source_dynamodb_tables	Upsert by primary key, incremental on updated-at
items	source_dynamodb_items	Upsert by primary key, incremental on updated-at
partition keys	source_dynamodb_partition_keys	Upsert by primary key, incremental on updated-at
sort keys	source_dynamodb_sort_keys	Upsert by primary key, incremental on updated-at
attributes	source_dynamodb_attributes	Upsert by primary key, incremental on updated-at
stream records	source_dynamodb_stream_records	Upsert by primary key, incremental on updated-at

Amazon DynamoDB API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

API	Amazon DynamoDB API (Scan / Query, DynamoDB Streams, Export to S3)
Authentication	API key — AWS IAM credentials (access key ID and secret, or an assumed role) signing each request with SigV4; there is no separate DynamoDB credential.
Pagination	keyset — `LastEvaluatedKey` from a Scan or Query response is sent back as `ExclusiveStartKey` on the next call; a page stops at 1 MB of data or the `Limit` value, whichever comes first.
Rate limit	No requests-per-second API cap; throughput is bounded by provisioned or on-demand read capacity, and a single Scan or Query page is hard-capped at 1 MB
Incremental cursor	Not published
Webhooks	No
Bulk export	Yes — Export to S3 from the point-in-time recovery window (consumes no read capacity units)
Deletes detectable	Yes — DynamoDB Streams emits REMOVE records for deleted items; a Scan-based sync only ever sees absence, never the deletion.

Official API reference

What bites when replicating Amazon DynamoDB

A Scan page is capped at 1 MB read *before* any `FilterExpression` is applied, so a selective scan can return an empty `Items` array and still hand back a `LastEvaluatedKey` that must be followed.
Export to S3 requires point-in-time recovery to be enabled on the table first; without PITR the export simply is not available, and PITR only covers the retention window it has been on for.
A full Scan consumes read capacity in proportion to table size and competes with production traffic, whereas the S3 export consumes no RCUs — which makes the export the safer backfill path on a live table.
Items have no schema beyond the key attributes, so two rows in the same table can carry different fields and a destination table has to be built from observed attributes rather than a declared schema.

Compare this against every other documented API

Popular destinations for Amazon DynamoDB

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Amazon DynamoDB connector FAQ

What Amazon DynamoDB data does the connector extract?: 6 objects: tables, items, partition keys, sort keys, attributes and stream records. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Amazon DynamoDB integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Amazon DynamoDB data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Amazon DynamoDB → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Amazon DynamoDB pipeline with guided onboarding

Join the waitlist to get priority access for Amazon DynamoDB integrations with guided setup, schema-aware mapping, and production-grade incremental sync.