Skip to content
Database ⇄ Security and identity

AWS Aurora MySQL to Onelogin integration — real-time, two-way sync

Keep AWS Aurora MySQL 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 AWS Aurora MySQL and Onelogin

Close the gap between your application data and your directory: AWS Aurora MySQL 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. AWS Aurora MySQL 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 Rows, Columns, Primary keys and indexes, Views in AWS Aurora MySQL with Authentication factors (MFA), Custom user fields, Users, Roles 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 Stream row changes from Aurora into SaaS tools via binlog CDC instead of scheduled batch exports.
  • 02 Sync a production Aurora cluster with an analytics database while filtering out sensitive columns.
  • 03 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.
  • 04 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.

Common sync patterns

Read users and groups as ordinary tables

Users, groups, and their memberships from Onelogin land in AWS Aurora MySQL as rows your application and queries can join, so authorization checks and access reporting run against the database instead of the directory API.

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.

What you can sync between AWS Aurora MySQL 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.

AWS Aurora MySQL objects Onelogin objects How this pairing syncs
Columns MySQL data types are mapped to the paired system's field types during schema setup. Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Columns is specific to AWS Aurora MySQL and Roles to Onelogin — each maps to any object or custom field on the other side.
Primary keys and indexes Used to match rows across systems and keep incremental syncs efficient. Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Primary keys and indexes is specific to AWS Aurora MySQL and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side.
Views Can serve as read-only sync sources for derived or filtered datasets. Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. Views is specific to AWS Aurora MySQL and Groups to Onelogin — each maps to any object or custom field on the other side.
Foreign keys Express relationships that syncs preserve when mapping to related objects elsewhere. Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. Foreign keys is specific to AWS Aurora MySQL and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side.
Stored procedures and triggers Existing database logic keeps firing on rows written by a sync. Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. Stored procedures and triggers is specific to AWS Aurora MySQL and Events to Onelogin — each maps to any object or custom field on the other side.
Databases (schemas) Logical namespaces that scope which tables a sync connection can see. Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Databases (schemas) is specific to AWS Aurora MySQL and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.

How changes propagate between AWS Aurora MySQL 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.

AWS Aurora MySQL Onelogin Sub-second propagation

DetectionChanges in AWS Aurora MySQL are captured at the source via change data capture — no polling loop against its API. Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback.

DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.

Onelogin AWS Aurora MySQL 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 AWS Aurora MySQL as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • 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 AWS Aurora MySQL ⇄ Onelogin

Connect AWS Aurora MySQL and Onelogin for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS Aurora MySQL–Onelogin connection.

Real-time

Two-way sync

Changes in AWS Aurora MySQL or Onelogin instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever AWS Aurora MySQL 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 AWS Aurora MySQL or Onelogin record.

Observability

Monitoring

Track your AWS Aurora MySQL ⇄ Onelogin sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between AWS Aurora MySQL and Onelogin.

How the AWS Aurora MySQL and Onelogin connectors work

AWS Aurora MySQL

Integration surface
SQL wire protocol (MySQL-compatible), standard MySQL drivers and JDBC
Authentication
Database credentials, optionally AWS IAM database authentication, over TLS
Change detection
Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback
Capabilities
read · write · CDC

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 AWS Aurora MySQL 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.

  1. 01

    Connect your apps

    Authenticate AWS Aurora MySQL 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    AWS Aurora MySQL connected
    Onelogin connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the AWS Aurora MySQL 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · AWS Aurora MySQL ⇄ Onelogin
    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
    AWS Aurora MySQL Onelogin
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

AWS Aurora MySQL and Onelogin 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 AWS Aurora MySQL and Onelogin.

Popular · 8 of 448
All AWS Aurora MySQL integrations All Onelogin 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