Skip to content
Security and identity ⇄ Database

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

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

Close the gap between your application data and your directory: Dynamo DB and Active Directory share users, groups, and access in real time, in both directions.

Active Directory is the system of record for who people are and what they can reach: users, the groups they belong to, and the applications assigned to them. Dynamo DB holds the operational data those same people show up in, whether an employee or member table that decides who should have an account at all, a customers list, or the rows an application checks before it authorizes an action. The two describe overlapping users and groups, and when a nightly export or a hand-run script is all that connects them, accounts lag joiners and leavers and the application authorizes against a stale picture of who has access.

Stacksync syncs Attributes, Partition and Sort Keys, Global Secondary Indexes, DynamoDB Streams in Dynamo DB with Service principals & applications, Organizational units, Organizational contacts, Users in Active Directory field by field, in real time, and in both directions. You decide which system owns which fields, with the directory holding credentials and group membership and the database holding the source list of people who should exist at all, and Stacksync keeps every copy consistent, resolving conflicts by rules you set. A person added to a table becomes an account within seconds, a departure disables one just as fast, and the directory's users and groups are always present in your tables as ordinary rows.

Common use cases

  • 01 Mirror SaaS objects into DynamoDB items to serve low-latency lookups from production services.
  • 02 Consolidate multi-region Global Tables data into a single reporting store.
  • 03 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.
  • 04 Read Devices and service principals into a database for identity, asset, and license inventory across the tenant.

Common sync patterns

One profile, kept current

A name, department, email, or manager corrected in either system updates the other, so the profile the directory shows and the data the application reads stop drifting apart.

Provision accounts from the source of truth

When a person is added to the employee, member, or customer table in Dynamo DB, Stacksync creates the matching user in Active Directory with the right attributes, so access starts from live data instead of a manual ticket.

Deprovision the moment the record changes

When someone is marked inactive or removed in Dynamo DB, the matching account in Active Directory is disabled within seconds, closing the window between a departure and a login that still works.

What you can sync between Active Directory and Dynamo DB

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.

Active Directory objects Dynamo DB objects How this pairing syncs
Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. Organizational contacts is specific to Active Directory and Items to Dynamo DB — each maps to any object or custom field on the other side.
Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. Users is specific to Active Directory and Attributes to Dynamo DB — each maps to any object or custom field on the other side.
Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. Groups is specific to Active Directory and Partition and Sort Keys to Dynamo DB — each maps to any object or custom field on the other side.
Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. Group memberships is specific to Active Directory and Global Secondary Indexes to Dynamo DB — each maps to any object or custom field on the other side.
Devices Registered and joined device objects; typically read into a database for inventory and compliance reporting. DynamoDB Streams Ordered item-level change records consumed for incremental sync. Devices is specific to Active Directory and DynamoDB Streams to Dynamo DB — each maps to any object or custom field on the other side.
Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. Global Tables Multi-region replicas relevant when syncs must read from a specific region. Directory roles is specific to Active Directory and Global Tables to Dynamo DB — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Dynamo DB

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.

Active Directory Dynamo DB Sub-second propagation

DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.

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

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

Rate-limit considerations

  • Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
  • Dynamo DB: Throughput is governed by the table's provisioned or on-demand capacity mode.
What ships with Active Directory ⇄ Dynamo DB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Active Directory and Dynamo DB connectors work

Active Directory

Integration surface
Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
Authentication
OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
Change detection
Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
Capabilities
read · write · webhooks
Rate limits
Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.

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
How it works

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

    Choose tables

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

Active Directory and Dynamo DB 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 448 integrations available for Active Directory and Dynamo DB.

Popular · 8 of 448
All Active Directory integrations All Dynamo DB 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