Skip to content
Database ⇄ AI

Amazon DynamoDB to Autopilot integration — real-time, two-way sync

Keep Amazon DynamoDB and Autopilot 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 Amazon DynamoDB and Autopilot

Sync the records in Amazon DynamoDB into Autopilot and land its embeddings, classifications, and generated fields back on the same rows, in real time and without a pipeline to maintain.

AI systems do not hold customers or invoices the way business apps do. What they hold is derived from your data: the vectors and metadata in a vector store, or the classifications, extracted fields, and generated text a model produces over records it was given. Amazon DynamoDB is where those source records actually live. The bridge between the two is the row itself, since an item in Autopilot and the record in Amazon DynamoDB it describes are two halves of the same thing, and they drift the moment one is updated without the other.

Stacksync syncs Local secondary indexes (LSIs), DynamoDB Streams, Global Tables, Time to Live (TTL) in Amazon DynamoDB with Journeys (Triggers), Activities, Contacts, Lists in Autopilot in real time. Rows created or changed in Amazon DynamoDB flow into Autopilot so inference and embedding run on current data, and the scores, labels, and generated fields Autopilot produces flow back onto the matching rows in Amazon DynamoDB, mapped field by field. A change on either side appears on the other within seconds, with no extraction job or webhook plumbing to keep alive.

Because matching is by a stable identifier, every row in Amazon DynamoDB stays tied to its AI-side counterpart in Autopilot. Retrieval, enrichment, and generated content always resolve back to the record they came from, so there are no orphaned vectors and no labels describing a version of a row that no longer exists.

Common use cases

  • 01 Mirror List and Smart Segment membership into a warehouse to power attribution and audience analytics alongside other sources.
  • 02 Stream Activities into a warehouse so opens, clicks, and journey steps sit next to product and revenue data for lifecycle reporting.
  • 03 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.
  • 04 Mirror a high-write DynamoDB table into a relational database so teams can join NoSQL application data against relational tables for reporting.

Common sync patterns

Write results back onto the record

Scores, labels, extracted fields, or generated text produced in Autopilot land on the matching row in Amazon DynamoDB, next to the source data your applications already query.

Keep derived data fresh as sources change

When a row in Amazon DynamoDB is updated or removed, its counterpart in Autopilot is updated or removed too, so nothing in Autopilot describes a record that has since changed or gone.

Backfill once, then stay in step

Load your existing rows from Amazon DynamoDB into Autopilot to build the index or enrichment set, then let ongoing changes sync automatically instead of re-running the whole job.

What you can sync between Amazon DynamoDB and Autopilot

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 Autopilot objects How this pairing syncs
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. Custom Fields User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns. Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Custom Fields to Autopilot — 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. Smart Segments Rule-based dynamic audiences; membership is computed by Autopilot, so it is read-only over the API. Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Smart Segments to Autopilot — 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. Journeys (Triggers) Automation journeys; a contact can be added to a journey via its trigger endpoint to start automated email or SMS sequences. DynamoDB Streams is specific to Amazon DynamoDB and Journeys (Triggers) to Autopilot — each maps to any object or custom field on the other side.
Global Tables Multi-region, active-active replicas of a table kept in sync by DynamoDB; each region is read and written locally with last-writer-wins conflict resolution. Activities Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting. Global Tables is specific to Amazon DynamoDB and Activities to Autopilot — each maps to any object or custom field on the other side.
Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. Contacts Core people records (email, name, custom fields, list and segment membership); upserted two-way as the primary sync object. Time to Live (TTL) is specific to Amazon DynamoDB and Contacts to Autopilot — each maps to any object or custom field on the other side.
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. Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. Tables is specific to Amazon DynamoDB and Lists to Autopilot — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB and Autopilot

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.

Amazon DynamoDB Autopilot Sub-second propagation

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 written to Autopilot through its API, with automatic retries and rate-limit backoff.

Autopilot Amazon DynamoDB Interval-based propagation

DetectionStacksync polls Autopilot for changes on an incremental schedule, reading only records changed since the previous pass. No CDC.

DeliveryEach detected change is applied to Amazon DynamoDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Amazon DynamoDB: Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.
  • Autopilot: The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
What ships with Amazon DynamoDB ⇄ Autopilot

Connect Amazon DynamoDB and Autopilot for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon DynamoDB–Autopilot connection.

Real-time

Two-way sync

Changes in Amazon DynamoDB or Autopilot instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon DynamoDB or Autopilot 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 Amazon DynamoDB or Autopilot record.

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Autopilot sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Autopilot.

How the Amazon DynamoDB and Autopilot connectors work

Amazon DynamoDB

Integration surface
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.
Change detection
DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views and 24-hour retention, read via shard iterators (or Kinesis Data Streams for longer retention). No native HTTP webhooks.
Capabilities
read · write · CDC
Rate limits
Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.

Autopilot

Integration surface
REST API (Autopilot v1); Autopilot rebranded to Ortto in 2021 and the newer Ortto API co-exists with the legacy Autopilot endpoints
Authentication
Per-account API key sent in the autopilotapikey request header (generated in account settings); requests use Content-Type application/json against https://api2.autopilothq.com/v1/
Change detection
No CDC; incremental sync polls the /contacts endpoint with bookmark cursor pagination and updated timestamps. Journey webhook actions can push specific contact events, but there is no general change-subscription webhook, so polling is the reliable path.
Capabilities
read · write
Rate limits
The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
Autopilot setup guide
How it works

How to connect Amazon DynamoDB to Autopilot — 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.

  1. 01

    Connect your apps

    Authenticate Amazon DynamoDB and Autopilot with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon DynamoDB connected
    Autopilot connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon DynamoDB and Autopilot 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon DynamoDB ⇄ Autopilot
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Amazon DynamoDB Autopilot
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon DynamoDB and Autopilot integration FAQ

SECURITY

Security teams trust 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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 511 integrations available for Amazon DynamoDB and Autopilot.

Popular · 8 of 511
All Amazon DynamoDB integrations All Autopilot integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own