Skip to content
Database ⇄ Security and identity

Amazon RDS to Onelogin integration — real-time, two-way sync

Keep Amazon RDS 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 Amazon RDS and Onelogin

Close the gap between your application data and your directory: Amazon RDS 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. 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 Schemas, Tables, Views, Columns in Amazon RDS with Events, Authentication factors (MFA), Custom user fields, Users 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 Use a read replica as the sync source to keep change capture load off the primary instance
  • 02 Bi-directional sync between an RDS database and a CRM so application data and sales data stay consistent without custom integration code
  • 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

Provision accounts from the source of truth

When a person is added to the employee, member, or customer table in Amazon RDS, Stacksync creates the matching user in Onelogin 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 Amazon RDS, the matching account in Onelogin is disabled within seconds, closing the window between a departure and a login that still works.

Read users and groups as ordinary tables

Users, groups, and their memberships from Onelogin 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.

What you can sync between Amazon RDS 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.

Amazon RDS objects Onelogin objects How this pairing syncs
Primary and Unique Keys Match keys for idempotent upserts. Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. Primary and Unique Keys is specific to Amazon RDS and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side.
Read Replicas Low-impact read endpoints often used as the source side of a sync. Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. Read Replicas is specific to Amazon RDS and Custom user fields to Onelogin — each maps to any object or custom field on the other side.
Stored Procedures Engine-specific logic that can react to synced rows. 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. Stored Procedures is specific to Amazon RDS and Users to Onelogin — each maps to any object or custom field on the other side.
Databases Engine-level databases on the instance that scope a sync's reads and writes. Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. Databases is specific to Amazon RDS and Roles to Onelogin — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to isolate synced tables. Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. Schemas is specific to Amazon RDS and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side.
Tables The core sync target; rows map to records in connected SaaS systems. 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. Tables is specific to Amazon RDS and Groups to Onelogin — each maps to any object or custom field on the other side.

How changes propagate between Amazon RDS 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.

Amazon RDS Onelogin Sub-second propagation

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

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

Rate-limit considerations

  • Amazon RDS: No API rate limits; throughput depends on instance class, storage IOPS, and connection limits.
  • 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 Amazon RDS ⇄ Onelogin

Connect Amazon RDS and Onelogin for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon RDS ⇄ Onelogin sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon RDS and Onelogin.

How the Amazon RDS and Onelogin connectors work

Amazon RDS

Integration surface
SQL wire protocol of the chosen engine (PostgreSQL, MySQL, MariaDB, SQL Server, Oracle)
Authentication
Database credentials over SSL/TLS, or IAM database authentication on supported engines
Change detection
Engine-native log-based CDC: MySQL/MariaDB binlog, PostgreSQL logical replication, SQL Server CDC; enabled through RDS parameter groups, with polling as a fallback
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance class, storage IOPS, and connection limits

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 Amazon RDS 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 Amazon RDS 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
    Amazon RDS connected
    Onelogin connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon RDS 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 · Amazon RDS ⇄ 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
    Amazon RDS Onelogin
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Amazon RDS 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.

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 452 integrations available for Amazon RDS and Onelogin.

Popular · 8 of 452
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.