Skip to content
Database ⇄ Human resources

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

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

Put your workforce data where your apps can reach it: Amazon RDS 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 RDS is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Notes and Contacts, Opportunities, Postings, Requisitions in Lever need to exist as queryable Columns, Primary and Unique Keys, Read Replicas, Stored Procedures in Amazon RDS 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 Columns, Primary and Unique Keys, Read Replicas, Stored Procedures in Amazon RDS with Notes and Contacts, Opportunities, Postings, Requisitions 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 Sync master data (customers, products, pricing) from an ERP into the RDS databases that power customer-facing apps
  • 02 Use a read replica as the sync source to keep change capture load off the primary instance
  • 03 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.
  • 04 Two-way sync Opportunities and their Stages between Lever and a Postgres database so recruiting ops and analysts query the pipeline in SQL while recruiters keep working in Lever.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in Amazon RDS write onto the matching record in Lever where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Lever land as queryable Columns, Primary and Unique Keys, Read Replicas, Stored Procedures in Amazon RDS, 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.

What you can sync between Amazon RDS 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 RDS objects Lever objects How this pairing syncs
Stored Procedures Engine-specific logic that can react to synced rows. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Stored Procedures is specific to Amazon RDS and Feedback to Lever — 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. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Databases is specific to Amazon RDS and Interviews to Lever — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to isolate synced tables. 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. Schemas is specific to Amazon RDS and Notes and Contacts to Lever — 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. Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. Tables is specific to Amazon RDS and Opportunities to Lever — each maps to any object or custom field on the other side.
Views Read-side projections exposed to outbound syncs. Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. Views is specific to Amazon RDS and Postings to Lever — each maps to any object or custom field on the other side.
Columns Field-level mapping targets, typed per the underlying engine. Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Columns is specific to Amazon RDS and Requisitions to Lever — each maps to any object or custom field on the other side.

How changes propagate between Amazon RDS 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 RDS Lever 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 Lever through its API, with automatic retries and rate-limit backoff.

Lever Amazon RDS 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 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.
  • 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 RDS ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon RDS ⇄ 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 RDS and Lever.

How the Amazon RDS and Lever 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

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

    Choose tables

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

Amazon RDS 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 454 integrations available for Amazon RDS and Lever.

Popular · 7 of 454
All Amazon RDS 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