Skip to content
Database ⇄ Developer tools

Dynamo DB to Newrelic integration — real-time, two-way sync

Keep Dynamo DB and Newrelic 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 Dynamo DB and Newrelic

Keep Dynamo DB and Newrelic in step: the rows in your database and the Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) your engineering tools track stay consistent in real time, in both directions.

Dynamo DB is where your application's durable data lives; Newrelic 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 Global Tables, Tables, Items, Attributes in Dynamo DB with Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) in Newrelic 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 Stream item changes from DynamoDB application tables into a Postgres or warehouse copy for SQL analytics.
  • 02 Sync customer records between DynamoDB-backed services and a CRM so support and sales see live application state.
  • 03 Record deployment and change markers from CI/CD through NerdGraph change tracking to correlate releases with performance and error-rate shifts.
  • 04 Sync the Entity catalog into a CMDB or warehouse for asset inventory, and add or replace entity Tags to keep ownership and environment metadata current.

Common sync patterns

Where Newrelic manages users or groups: keep identity aligned

Directory and identity records in Newrelic stay matched to the users or owners table in Dynamo DB, so provisioning and de-provisioning flow from one source.

Turn rows into the records your tools track

A new or changed row in Dynamo DB creates or updates the matching record in Newrelic, 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 Newrelic arrive in Dynamo DB as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

What you can sync between Dynamo DB and Newrelic

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.

Dynamo DB objects Newrelic objects How this pairing syncs
Tables The top-level containers a sync targets; each table is addressed independently. Workloads Workload groupings of related entities via NerdGraph workloadCreate/workloadUpdate/workloadDelete with full CRUD; read for status rollups or provisioned from a service catalog to keep team-level views current. Tables is specific to Dynamo DB and Workloads to Newrelic — each maps to any object or custom field on the other side.
Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. Synthetics Monitors Synthetic uptime and scripted browser checks managed through NerdGraph synthetics mutations (create, update, delete); monitor results are read via NRQL for availability and latency reporting. Items is specific to Dynamo DB and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side.
Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. Custom Events Custom events posted write-only to the Event API on insights-collector with a License/Ingest key; business or pipeline events pushed into New Relic to enrich dashboards, then queried back out with NRQL. Attributes is specific to Dynamo DB and Custom Events to Newrelic — each maps to any object or custom field on the other side.
Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. Change Tracking (Deployments) Deployment and change markers recorded through NerdGraph changeTrackingCreateDeployment; written from CI/CD to annotate charts, and read back via NRQL on the Deployment event for release correlation. Partition and Sort Keys is specific to Dynamo DB and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side.
Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. Dashboards Dashboard definitions and widgets via NerdGraph dashboardCreate/dashboardUpdate/dashboardDelete mutations and entity queries, with full CRUD; exported for backup and audit or provisioned and updated programmatically from a source of truth. Global Secondary Indexes is specific to Dynamo DB and Dashboards to Newrelic — each maps to any object or custom field on the other side.
DynamoDB Streams Ordered item-level change records consumed for incremental sync. Alert Policies & Conditions Alert policies and NRQL alert conditions managed through NerdGraph alertsPolicy and alertsNrqlCondition mutations with full create, update, and delete; read out for audit or provisioned from a config source so alerting stays consistent across accounts. DynamoDB Streams is specific to Dynamo DB and Alert Policies & Conditions to Newrelic — each maps to any object or custom field on the other side.

How changes propagate between Dynamo DB and Newrelic

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.

Dynamo DB Newrelic Sub-second propagation

DetectionChanges in Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.

DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.

Newrelic Dynamo DB Sub-second propagation

DetectionNewrelic notifies Stacksync of record changes through webhook events. NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans).

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

Rate-limit considerations

  • Dynamo DB: Throughput is governed by the table's provisioned or on-demand capacity mode.
  • Newrelic: NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
What ships with Dynamo DB ⇄ Newrelic

Connect Dynamo DB and Newrelic for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamo DB–Newrelic connection.

Real-time

Two-way sync

Changes in Dynamo DB or Newrelic instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamo DB or Newrelic 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 Dynamo DB or Newrelic record.

Observability

Monitoring

Track your Dynamo DB ⇄ Newrelic sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamo DB and Newrelic.

How the Dynamo DB and Newrelic connectors work

Dynamo DB

Integration surface
Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries
Authentication
AWS IAM credentials with SigV4 request signing
Change detection
Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration
Capabilities
read · write · CDC
Rate limits
Throughput is governed by the table's provisioned or on-demand capacity mode

Newrelic

Integration surface
NerdGraph (GraphQL) plus REST data-ingest APIs (Event, Metric, Log, Trace) and the legacy REST API v2
Authentication
User API key (prefixed NRAK-) sent in the API-Key header for NerdGraph queries and mutations; the data-ingest APIs (Event, Metric, Log) use a License/Ingest key in the Api-Key header. Keys, endpoints, and data are region-scoped (US, EU, JP).
Change detection
NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans); config objects such as dashboards, alert policies, and workloads carry no modified-date and are diffed on each run. Alert workflows can push outbound webhook notifications for near-real-time alerting. No CDC feed.
Capabilities
read · write · webhooks
Rate limits
NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
How it works

How to connect Dynamo DB to Newrelic — 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 Dynamo DB and Newrelic 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
    Dynamo DB connected
    Newrelic connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamo DB and Newrelic 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 · Dynamo DB ⇄ Newrelic
    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
    Dynamo DB Newrelic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Dynamo DB and Newrelic 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 329 integrations available for Dynamo DB and Newrelic.

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

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