Skip to content
Database ⇄ Human resources

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

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

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

Greenhouse 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: Offers, Scorecards, Scheduled Interviews, Users in Greenhouse need to exist as queryable Tables, Views, Users and Grants, Managed 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 Tables, Views, Users and Grants, Managed Databases in Amazon Lightsail with Offers, Scorecards, Scheduled Interviews, Users in Greenhouse field by field, in real time. You decide which system owns which fields — Greenhouse 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 Push cleaned or enriched records from central systems back into the Lightsail database behind a small web app.
  • 02 Migrate data continuously from a Lightsail database to a larger managed database as an application outgrows the VPS tier.
  • 03 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
  • 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.

Common sync patterns

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Greenhouse stay consistent in Amazon Lightsail, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

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

Mirror people records into the database

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

What you can sync between Amazon Lightsail and Greenhouse

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 Greenhouse objects How this pairing syncs
Managed Databases Lightsail-hosted MySQL or PostgreSQL instances that a sync connects to as standard databases. Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Managed Databases is specific to Amazon Lightsail and Departments and Offices to Greenhouse — each maps to any object or custom field on the other side.
Databases Logical databases on the instance that scope a connection. Candidates Person records with contact details, tags, and custom fields; read and written via Harvest, often created from sourcing or enrichment pipelines. Databases is specific to Amazon Lightsail and Candidates to Greenhouse — each maps to any object or custom field on the other side.
Schemas Namespaces used when selecting tables to sync. Applications Links a Candidate to a Job; carries current stage, status, and source. Movable, rejectable, and hireable through Harvest write calls. Schemas is specific to Amazon Lightsail and Applications to Greenhouse — each maps to any object or custom field on the other side.
Tables Relational tables read from and written to at row level. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Tables is specific to Amazon Lightsail and Jobs to Greenhouse — each maps to any object or custom field on the other side.
Views Query-backed read-only sources. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Views is specific to Amazon Lightsail and Offers to Greenhouse — 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. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Users and Grants is specific to Amazon Lightsail and Scorecards to Greenhouse — each maps to any object or custom field on the other side.

How changes propagate between Amazon Lightsail and Greenhouse

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

Greenhouse Amazon Lightsail Sub-second propagation

DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.

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.
  • Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
What ships with Amazon Lightsail ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon Lightsail ⇄ Greenhouse 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 Greenhouse.

How the Amazon Lightsail and Greenhouse 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

Greenhouse

Integration surface
Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
Authentication
HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
Change detection
HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
Capabilities
read · write · webhooks
Rate limits
Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
Greenhouse setup guide
How it works

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

    Choose tables

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

Amazon Lightsail and Greenhouse 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 Greenhouse.

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