Two-way sync
Changes in Active Directory or Amazon RDS instantly reflect in both systems. No stale data, no manual imports.
Keep Active Directory and Amazon RDS in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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. Amazon RDS 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 Columns, Primary and Unique Keys, Read Replicas, Stored Procedures in Amazon RDS with Groups, Group memberships, Devices, Directory roles 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.
When a person is added to the employee, member, or customer table in Amazon RDS, Stacksync creates the matching user in Active Directory with the right attributes, so access starts from live data instead of a manual ticket.
When someone is marked inactive or removed in Amazon RDS, the matching account in Active Directory is disabled within seconds, closing the window between a departure and a login that still works.
Users, groups, and their memberships from Active Directory land in Amazon RDS as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.
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 | Amazon RDS objects | How this pairing syncs | |
|---|---|---|---|
| Group memberships Member and owner links between users and groups; membership add/remove changes are surfaced by delta query. | Schemas Namespaces within a database used to isolate synced tables. | Group memberships is specific to Active Directory and Schemas to Amazon RDS — 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. | Tables The core sync target; rows map to records in connected SaaS systems. | Devices is specific to Active Directory and Tables to Amazon RDS — 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. | Views Read-side projections exposed to outbound syncs. | Directory roles is specific to Active Directory and Views to Amazon RDS — each maps to any object or custom field on the other side. | |
| Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. | Columns Field-level mapping targets, typed per the underlying engine. | Service principals & applications is specific to Active Directory and Columns to Amazon RDS — each maps to any object or custom field on the other side. | |
| Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. | Primary and Unique Keys Match keys for idempotent upserts. | Organizational units is specific to Active Directory and Primary and Unique Keys to Amazon RDS — each maps to any object or custom field on the other side. | |
| Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. | Read Replicas Low-impact read endpoints often used as the source side of a sync. | Organizational contacts is specific to Active Directory and Read Replicas to Amazon RDS — each maps to any object or custom field on the other side. |
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.
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 Amazon RDS as a row-level write, with types converted between the two schemas.
DetectionChanges in Amazon RDS are captured at the source via change data capture — no polling loop against its API. Engine-native log-based CDC: MySQL/MariaDB binlog, PostgreSQL logical replication, SQL Server CDC.
DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Amazon RDS connection.
Changes in Active Directory or Amazon RDS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Active Directory or Amazon RDS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Active Directory or Amazon RDS record.
Track your Active Directory ⇄ Amazon RDS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Active Directory and Amazon RDS.
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.
Authenticate Active Directory and Amazon RDS with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Active Directory and Amazon RDS 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Active Directory and Amazon RDS: authenticate both systems, choose the objects to sync (such as Active Directory's Group memberships and Devices), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Active Directory and Amazon RDS connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Active Directory–Amazon RDS integration in-house.
Yes — Stacksync ships production-grade connectors for both Active Directory and Amazon RDS. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Active Directory: 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. On Amazon RDS: Engine-native log-based CDC: MySQL/MariaDB binlog, PostgreSQL logical replication, SQL Server CDC; enabled through RDS parameter groups, with polling as a fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Amazon RDS side: Columns, Primary and Unique Keys, Read Replicas, Stored Procedures, plus custom fields where Amazon RDS exposes them. On the Active Directory side: Groups, Group memberships, Devices, Directory roles. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 452 integrations available for Active Directory and Amazon RDS.