Skip to content
Database ⇄ Security and identity

Amazon DynamoDB to Okta integration — real-time, two-way sync

Keep Amazon DynamoDB and Okta 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 Okta

Close the gap between your application data and your directory: Amazon DynamoDB and Okta share users, groups, and access in real time, in both directions.

Okta 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 DynamoDB 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 DynamoDB Streams, Global Tables, Time to Live (TTL), Tables in Amazon DynamoDB with Factors (Authenticators), Policies, System Log, Devices in Okta 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 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.
  • 02 Mirror a high-write DynamoDB table into a relational database so teams can join NoSQL application data against relational tables for reporting.
  • 03 Sync Groups and their memberships two-way between Okta and a database or IdP so downstream app access stays aligned with source-of-truth org data.
  • 04 Mirror the System Log into Postgres or a warehouse for security analytics, access reviews, and audit retention beyond Okta's log window.

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 Amazon DynamoDB, Stacksync creates the matching user in Okta with the right attributes, so access starts from live data instead of a manual ticket.

What you can sync between Amazon DynamoDB and Okta

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 Okta objects How this pairing syncs
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. Group Rules Dynamic rules that add users to groups from profile attributes; read and written to automate access based on department, title, or location. DynamoDB Streams is specific to Amazon DynamoDB and Group Rules to Okta — 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. Factors (Authenticators) MFA enrollments per user (Okta Verify, WebAuthn, SMS, email); read for security-posture reporting and reset when a device is lost or rotated. Global Tables is specific to Amazon DynamoDB and Factors (Authenticators) to Okta — each maps to any object or custom field on the other side.
Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. Policies Sign-on, password, and authenticator-enrollment policies with their rules; read to audit access controls or updated to manage them centrally. Time to Live (TTL) is specific to Amazon DynamoDB and Policies to Okta — each maps to any object or custom field on the other side.
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. System Log Immutable audit event stream of logins, admin changes, and lifecycle events; read-only, polled by timestamp and used as the change feed and SIEM source. Tables is specific to Amazon DynamoDB and System Log to Okta — 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. Devices Registered and managed device records tied to users; read to correlate access with device posture and to feed inventory or conditional-access reporting. Items is specific to Amazon DynamoDB and Devices to Okta — 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. Users Universal Directory user records with profile attributes, credentials, and lifecycle status (staged, active, suspended, deprovisioned); full CRUD, so users are created, updated, activated, and deactivated to match an HR or identity source. Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Users to Okta — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB and Okta

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

Okta Amazon DynamoDB Sub-second propagation

DetectionOkta notifies Stacksync of record changes through webhook events. Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time.

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.
  • Okta: Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.
What ships with Amazon DynamoDB ⇄ Okta

Connect Amazon DynamoDB and Okta for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Okta 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 Okta.

How the Amazon DynamoDB and Okta 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.

Okta

Integration surface
REST API (Okta Management API, /api/v1) with Event Hooks for outbound events and the System Log API as the change feed
Authentication
SSWS API tokens (Authorization: SSWS {token}) scoped to the creating admin's permissions, or OAuth 2.0 for Okta service apps using a private-key-JWT client-credentials grant with granular scopes (DPoP supported)
Change detection
Event Hooks send an HTTPS POST to a subscribed endpoint on events such as user.lifecycle.create and group.user_membership.add (after a one-time verification handshake); the System Log API (/api/v1/logs) is polled by the since parameter and the next Link header for a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per org, per endpoint group, per minute and vary by Okta edition; responses carry X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers and exceeding one returns HTTP 429. The System Log is more tightly limited (about 120 requests/minute) and a separate concurrent-request cap (default 75 in-flight transactions) also applies.
How it works

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

    Choose tables

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

Amazon DynamoDB and Okta 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 536 integrations available for Amazon DynamoDB and Okta.

Popular · 8 of 536
All Amazon DynamoDB integrations All Okta 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