Amazon DynamoDB to Neon Integration

How Datrise loads Amazon DynamoDB into Neon

Datrise syncs Amazon DynamoDB's tables, items, partition keys, sort keys, attributes, and stream records into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

Amazon DynamoDB: Serverless key-value and document store on AWS.

Neon: Serverless Postgres destination with branching and autoscaling.

How Amazon DynamoDB entities map to Neon

Amazon DynamoDB entity	Neon object	Notes
tables	`source_dynamodb_tables`	id PK · custom fields → jsonb columns
items	`source_dynamodb_items`	id PK · linked to source_dynamodb_tables
partition keys	`source_dynamodb_partition_keys`	id PK · linked to source_dynamodb_tables
sort keys	`source_dynamodb_sort_keys`	id PK · linked to source_dynamodb_tables

FAQ

How does Datrise handle Amazon DynamoDB's custom fields in Neon?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.

How does the Amazon DynamoDB to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Amazon DynamoDB to Neon the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.