Two-way sync
Changes in Amazon Lightsail or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon Lightsail 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.
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 Lightsail 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 Users and Grants, Managed Databases, Databases, Schemas in Amazon Lightsail with Users, Roles, Apps (app instances), Groups 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.
A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
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.
When a person is added to the employee, member, or customer table in Amazon Lightsail, Stacksync creates the matching user in Onelogin with the right attributes, so access starts from live data instead of a manual ticket.
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 Lightsail objects | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces used when selecting tables to sync. | 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. | Schemas is specific to Amazon Lightsail and Groups to Onelogin — each maps to any object or custom field on the other side. | |
| Tables Relational tables read from and written to at row level. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Tables is specific to Amazon Lightsail and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side. | |
| Views Query-backed read-only sources. | Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Views is specific to Amazon Lightsail and Events to Onelogin — each maps to any object or custom field on the other side. | |
| Users and Grants Database accounts used to give the sync connection scoped access. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Users and Grants is specific to Amazon Lightsail and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| Managed Databases Lightsail-hosted MySQL or PostgreSQL instances that a sync connects to as standard databases. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | Managed Databases is specific to Amazon Lightsail and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Databases Logical databases on the instance that scope a connection. | 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. | Databases is specific to Amazon Lightsail and Users to Onelogin — 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.
DetectionStacksync polls Amazon Lightsail for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or key columns.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
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 Lightsail as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon Lightsail–Onelogin connection.
Changes in Amazon Lightsail or Onelogin instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon Lightsail or Onelogin data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Amazon Lightsail or Onelogin record.
Track your Amazon Lightsail ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon Lightsail and Onelogin.
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 Amazon Lightsail 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.
Pick the Amazon Lightsail 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.
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 Amazon Lightsail and Onelogin: authenticate both systems, choose the objects to sync (such as Amazon Lightsail's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Amazon Lightsail: Polling on timestamp or key columns; log-based CDC depends on engine parameter access, which is more limited than on full RDS. 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.
On the Amazon Lightsail side: Users and Grants, Managed Databases, Databases, Schemas, plus custom fields where Amazon Lightsail exposes them. On the Onelogin side: Users, Roles, Apps (app instances), Groups. 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.
Common patterns for Amazon Lightsail and Onelogin: Keep group and role membership aligned; One profile, kept current; Provision accounts from the source of truth. A group or role change made in either system updates the other, so the entitlements an application enforces match what the directory grants.
Amazon Lightsail: MySQL or PostgreSQL wire protocol (SQL) to the managed database endpoint. Authentication: Database credentials; public endpoint access must be enabled or a tunnel used. Onelogin: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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 435 integrations available for Amazon Lightsail and Onelogin.