Real-time
Two-way sync
Changes in Dynamo DB or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Security and identity
Dynamo DB to Onelogin integration — real-time, two-way sync
Keep Dynamo DB and Onelogin 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 Onelogin
Close the gap between your application data and your directory: Dynamo DB and Onelogin share users, groups, and access in real time, in both directions.
Onelogin 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 Roles, Apps (app instances), Groups, Mappings (mapping rules) in Onelogin 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 Consolidate multi-region Global Tables data into a single reporting store.
- 02 Replace ad-hoc export scripts with continuous sync driven by DynamoDB Streams.
- 03 Keep Role membership aligned with application or database entitlement tables so each role's assigned users match who should hold that access.
- 04 Read Users, Apps, and Groups into a database for identity, license, and app-assignment inventory across the OneLogin account.
Common sync patterns
Keep group and role membership aligned
A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
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 Onelogin with the right attributes, so access starts from live data instead of a manual ticket.
What you can sync between Dynamo DB and Onelogin
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 | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Attributes is specific to Dynamo DB and Mappings (mapping rules) to Onelogin — 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. | Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Partition and Sort Keys is specific to Dynamo DB and Events to Onelogin — 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. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Global Secondary Indexes is specific to Dynamo DB and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| DynamoDB Streams Ordered item-level change records consumed for incremental sync. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | DynamoDB Streams is specific to Dynamo DB and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Global Tables Multi-region replicas relevant when syncs must read from a specific region. | Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. | Global Tables is specific to Dynamo DB and Users to Onelogin — each maps to any object or custom field on the other side. | |
| Tables The top-level containers a sync targets; each table is addressed independently. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Tables is specific to Dynamo DB and Roles to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between Dynamo DB and Onelogin
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 Onelogin 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 Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin Dynamo DB Sub-second propagation
DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.
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.
- Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
What ships with Dynamo DB ⇄ Onelogin
Connect Dynamo DB and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamo DB–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamo DB or Onelogin 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 Onelogin record.
Observability
Monitoring
Track your Dynamo DB ⇄ Onelogin 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 Onelogin.
How the Dynamo DB and Onelogin 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
Onelogin
- Integration surface
- OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
- Authentication
- OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
- Change detection
- Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
- Capabilities
- read · write · webhooks
- Rate limits
- Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
How it works
How to connect Dynamo DB to Onelogin — 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.
- 01
Connect your apps
Authenticate Dynamo DB and Onelogin with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Dynamo DB
connected
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamo DB and Onelogin 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.
objects · Dynamo DB ⇄ OneloginCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dynamo DB OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamo DB and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dynamo DB and Onelogin: authenticate both systems, choose the objects to sync (such as Dynamo DB's Attributes and Partition and Sort Keys), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Dynamo DB: Queries are efficient only along key and index access paths; full-table scans are expensive, which makes stream-based sync preferable to polling. Onelogin: Some write calls are queued to OneLogin's job system and can take up to about five minutes to finish processing rather than completing synchronously. Stacksync's field mapping accounts for these differences between Dynamo DB and Onelogin without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Dynamo DB and Onelogin records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Dynamo DB and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Dynamo DB–Onelogin integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Dynamo DB and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Dynamo DB: Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration. On Onelogin: Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 448 integrations available for Dynamo DB and Onelogin.
Popular · 8 of 448
-
Dynamo DB ⇄ Azure Active Directory -
Dynamo DB ⇄ Okta -
Dynamo DB ⇄ Auth0 -
Dynamo DB ⇄ Jumpcloud -
Onelogin ⇄ Google Cloud Spanner - Onelogin ⇄ Google Cloud SQL
-
Onelogin ⇄ IBM AS/400 -
Onelogin ⇄ IBM Informix
No integrations match .
