Skip to content
Database ⇄ Developer tools

Amazon DynamoDB to Azure Service Bus integration — real-time, two-way sync

Keep Amazon DynamoDB and Azure Service Bus 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 Azure Service Bus

Keep Amazon DynamoDB and Azure Service Bus in step: the rows in your database and the Topics, Subscriptions, Messages, Rules / Filters your engineering tools track stay consistent in real time, in both directions.

Amazon DynamoDB is where your application's durable data lives; Azure Service Bus 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 Topics, Subscriptions, Messages, Rules / Filters in Azure Service Bus 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 Use DynamoDB Streams as a change-data-capture source to push item INSERT, MODIFY, and REMOVE events into a CRM, search index, or operational database in near-real-time.
  • 02 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.
  • 03 Receive messages from a queue or subscription with an AMQP receiver and write them into a Postgres or warehouse table for durable, SQL-queryable storage.
  • 04 Fan out CRM or ERP record changes to a topic and let billing, analytics, and notification subscriptions each filter with SQL rules and react without coupling to the source.

Common sync patterns

One integration pattern instead of per-tool API code

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

React to changes on either side in near real time

Updates in Azure Service Bus arrive as row changes in Amazon DynamoDB, and writes to Amazon DynamoDB propagate to Azure Service Bus within seconds, so triggers, jobs, and alerts fire without polling.

Where Azure Service Bus manages users or groups: keep identity aligned

Directory and identity records in Azure Service Bus stay matched to the users or owners table in Amazon DynamoDB, so provisioning and de-provisioning flow from one source.

What you can sync between Amazon DynamoDB and Azure Service Bus

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 Azure Service Bus objects How this pairing syncs
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. Scheduled / deferred messages Messages enqueued for future delivery at a set time, or deferred and set aside by sequence number for retrieval later, out of the normal receive order. Tables is specific to Amazon DynamoDB and Scheduled / deferred messages to Azure Service Bus — each maps to any object or custom field on the other side.
Items Individual schemaless records (attributes up to 400 KB each); read with GetItem, Query, and Scan and written with PutItem or BatchWriteItem, so write is supported here. Queues Point-to-point entity: a sender writes messages and one competing consumer at a time receives them under PeekLock, then completes or abandons each message. Items is specific to Amazon DynamoDB and Queues to Azure Service Bus — each maps to any object or custom field on the other side.
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. Topics Publish/subscribe entity a publisher sends to; each message is fanned out to every subscription whose filter rules match, so many consumers get their own copy. Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Topics to Azure Service Bus — 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. Subscriptions A virtual queue attached to a topic; a consumer receives its own stream of matching messages here, independent of other subscriptions on the same topic. Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Subscriptions to Azure Service Bus — 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. Messages The synced unit: a body plus system and user properties, MessageId, SessionId, and TTL; capped at 256 KB on Standard and up to 100 MB on Premium over AMQP. DynamoDB Streams is specific to Amazon DynamoDB and Messages to Azure Service Bus — 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. Rules / Filters SQL or correlation filters on a subscription that decide which topic messages it receives; a rule can also add or modify properties via a filter action. Global Tables is specific to Amazon DynamoDB and Rules / Filters to Azure Service Bus — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB and Azure Service Bus

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

Azure Service Bus Amazon DynamoDB Interval-based propagation

DetectionStacksync polls Azure Service Bus for changes on an incremental schedule, reading only records changed since the previous pass. Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or.

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.
  • Azure Service Bus: Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity.
What ships with Amazon DynamoDB ⇄ Azure Service Bus

Connect Amazon DynamoDB and Azure Service Bus for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Azure Service Bus 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 Azure Service Bus.

How the Amazon DynamoDB and Azure Service Bus 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.

Azure Service Bus

Integration surface
AMQP 1.0 messaging protocol plus an HTTP/REST API; entities live under a namespace at <namespace>.servicebus.windows.net (legacy SBMP also supported)
Authentication
Microsoft Entra ID (Azure AD) RBAC with managed identities - roles Azure Service Bus Data Owner, Data Sender, and Data Receiver - or Shared Access Signature (SAS) policies scoped with Manage, Send, and Listen claims
Change detection
Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or ReceiveAndDelete. No modified-date polling and no native HTTP push; Azure Event Grid can separately raise an 'active messages available' event for intermittent receivers
Capabilities
read · write
Rate limits
Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity
How it works

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

    Choose tables

    Pick the Amazon DynamoDB and Azure Service Bus 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 ⇄ Azure Service Bus
    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 Azure Service Bus
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon DynamoDB and Azure Service Bus 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 417 integrations available for Amazon DynamoDB and Azure Service Bus.

Popular · 8 of 417
All Amazon DynamoDB integrations All Azure Service Bus 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