Skip to content
Database ⇄ Human resources

Amazon Lightsail to Lever integration — real-time, two-way sync

Keep Amazon Lightsail and Lever 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 Lightsail and Lever

Put your workforce data where your apps can reach it: Amazon Lightsail and Lever share the same people, positions, and org structure in real time.

Lever is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Amazon Lightsail is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Feedback, Interviews, Notes and Contacts, Opportunities in Lever need to exist as queryable Views, Users and Grants, Managed Databases, Databases in Amazon Lightsail before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Views, Users and Grants, Managed Databases, Databases in Amazon Lightsail with Feedback, Interviews, Notes and Contacts, Opportunities in Lever field by field, in real time. You decide which system owns which fields — Lever typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Migrate data continuously from a Lightsail database to a larger managed database as an application outgrows the VPS tier.
  • 02 Sync a Lightsail-hosted application database with a CRM so customer records match what the app stores.
  • 03 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.
  • 04 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.

Common sync patterns

Mirror people records into the database

Records maintained in Lever land as queryable Views, Users and Grants, Managed Databases, Databases in Amazon Lightsail, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

Reporting and analytics on current data

Feedback, Interviews, Notes and Contacts, Opportunities replicate into Amazon Lightsail where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

What you can sync between Amazon Lightsail and Lever

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 Lever objects How this pairing syncs
Managed Databases Lightsail-hosted MySQL or PostgreSQL instances that a sync connects to as standard databases. Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. Managed Databases is specific to Amazon Lightsail and Offers to Lever — each maps to any object or custom field on the other side.
Databases Logical databases on the instance that scope a connection. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Databases is specific to Amazon Lightsail and Users to Lever — each maps to any object or custom field on the other side.
Schemas Namespaces used when selecting tables to sync. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Schemas is specific to Amazon Lightsail and Stages to Lever — each maps to any object or custom field on the other side.
Tables Relational tables read from and written to at row level. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Tables is specific to Amazon Lightsail and Feedback to Lever — each maps to any object or custom field on the other side.
Views Query-backed read-only sources. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Views is specific to Amazon Lightsail and Interviews to Lever — 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. Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. Users and Grants is specific to Amazon Lightsail and Notes and Contacts to Lever — each maps to any object or custom field on the other side.

How changes propagate between Amazon Lightsail and Lever

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 Lightsail Lever Interval-based propagation

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

Lever Amazon Lightsail Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is applied to Amazon Lightsail as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Amazon Lightsail: No API-style rate limits; capacity is fixed by the chosen Lightsail bundle.
  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
What ships with Amazon Lightsail ⇄ Lever

Connect Amazon Lightsail and Lever for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon Lightsail and Lever.

How the Amazon Lightsail and Lever connectors work

Amazon Lightsail

Integration surface
MySQL or PostgreSQL wire protocol (SQL) to the managed database endpoint
Authentication
Database credentials; public endpoint access must be enabled or a tunnel used
Change detection
Polling on timestamp or key columns; log-based CDC depends on engine parameter access, which is more limited than on full RDS
Capabilities
read · write
Rate limits
No API-style rate limits; capacity is fixed by the chosen Lightsail bundle

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide
How it works

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

    Choose tables

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

Amazon Lightsail and Lever 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 437 integrations available for Amazon Lightsail and Lever.

Popular · 7 of 437
All Amazon Lightsail integrations All Lever 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