Skip to content
Database ⇄ Developer tools

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

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

Keep Amazon DynamoDB and Datadog in step: the rows in your database and the Metrics, Incidents, Service Level Objectives, Hosts your engineering tools track stay consistent in real time, in both directions.

Amazon DynamoDB is where your application's durable data lives; Datadog is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs Items, Global secondary indexes (GSIs), Local secondary indexes (LSIs), DynamoDB Streams in Amazon DynamoDB with Metrics, Incidents, Service Level Objectives, Hosts in Datadog field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.
  • 02 Mirror a high-write DynamoDB table into a relational database so teams can join NoSQL application data against relational tables for reporting.
  • 03 Provision and update Datadog Monitors from a config database or Git so alert definitions stay consistent across teams and environments.
  • 04 Publish deploy and pipeline Events, and submit custom Metrics, into Datadog from CI/CD or a data pipeline to enrich dashboards and correlation.

Common sync patterns

Turn rows into the records your tools track

A new or changed row in Amazon DynamoDB creates or updates the matching record in Datadog, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.

Land tool activity as queryable rows

Records and events from Datadog arrive in Amazon DynamoDB as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

One integration pattern instead of per-tool API code

Read and write the synced tables in Amazon DynamoDB and Stacksync keeps Datadog current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.

What you can sync between Amazon DynamoDB and Datadog

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 Datadog 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. Metrics Time-series metrics queried in aggregate windows through the query API and submitted via POST /api/v1/series; individual raw points cannot be extracted beyond retention. Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Metrics to Datadog — 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. Incidents Incident records from the v2 Incidents API with full CRUD, including status and timeline fields; landed in a database for MTTR reporting or created and updated from an external incident workflow. Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Incidents to Datadog — 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. Service Level Objectives SLO definitions and status history via the v1 SLO API with full CRUD; read out for reliability and error-budget reporting, or provisioned and updated from a reliability config. DynamoDB Streams is specific to Amazon DynamoDB and Service Level Objectives to Datadog — 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. Hosts Infrastructure host inventory with tags and metadata from the v1 host list API; loaded into a CMDB or warehouse for asset tracking, and hosts can be muted or unmuted via the API. Global Tables is specific to Amazon DynamoDB and Hosts to Datadog — 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. Monitors Alert definitions with query, thresholds, and current state via the v1 Monitors API, which supports full create, update, and delete; Stacksync reads alert state into a warehouse or provisions and updates monitors from a config source. Time to Live (TTL) is specific to Amazon DynamoDB and Monitors to Datadog — 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. Logs Log events searched via the v2 Logs search endpoint by time window and submittable through the log intake API; commonly streamed to a warehouse for retention beyond Datadog's storage period. Tables is specific to Amazon DynamoDB and Logs to Datadog — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB and Datadog

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

Datadog Amazon DynamoDB Sub-second propagation

DetectionDatadog notifies Stacksync of record changes through webhook events. Polling with time-windowed search queries on Logs and Events (timestamp cursor).

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.
  • Datadog: Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.
What ships with Amazon DynamoDB ⇄ Datadog

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Datadog 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 Datadog.

How the Amazon DynamoDB and Datadog 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.

Datadog

Integration surface
REST API (v1 and v2)
Authentication
API key (DD-API-KEY) plus an Application key (DD-APPLICATION-KEY) sent as request headers; application keys are tied to the creating user and inherit that user's permissions and authorization scopes.
Change detection
Polling with time-windowed search queries on Logs and Events (timestamp cursor); monitor alerts can also push via the Webhooks notification integration. No modified-date CDC on mutable objects.
Capabilities
read · write · webhooks
Rate limits
Per-endpoint limits return HTTP 429 with X-RateLimit-Limit/-Remaining/-Period/-Reset headers. Log ingestion and metric submission are not rate limited; search endpoints such as Logs and Events queries carry quotas that Datadog Support can raise.
How it works

How to connect Amazon DynamoDB to Datadog — 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 Datadog 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
    Datadog connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon DynamoDB and Datadog 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 ⇄ Datadog
    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 Datadog
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Amazon DynamoDB and Datadog 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.

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:

Related integrations

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

Popular · 8 of 417
Coworkers laughing in front of a laptop in a casual office setting

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