Skip to content
Database ⇄ Accounting and finance

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

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

Work with Recurly's financial data straight from Amazon Lightsail: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Accounts, Subscriptions, Plans, Invoices from Recurly into Databases, Schemas, Tables, Views in Amazon Lightsail and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Amazon Lightsail, and rows your code writes or updates flow back into Recurly with validation, so the finance system stays the system of record.

Common use cases

  • 01 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 03 Sync a Lightsail-hosted application database with a CRM so customer records match what the app stores.
  • 04 Push cleaned or enriched records from central systems back into the Lightsail database behind a small web app.

Common sync patterns

Write back safely

Updates written to the synced tables in Amazon Lightsail propagate into Recurly, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Recurly appear in Amazon Lightsail as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Recurly live in Amazon Lightsail as regular tables or collections your team can join, index, and query.

What you can sync between Amazon Lightsail and Recurly

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 Recurly objects How this pairing syncs
Tables Relational tables read from and written to at row level. Subscriptions Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting. Tables is specific to Amazon Lightsail and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Views Query-backed read-only sources. Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Views is specific to Amazon Lightsail and Plans to Recurly — 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. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Users and Grants is specific to Amazon Lightsail and Invoices to Recurly — 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. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Managed Databases is specific to Amazon Lightsail and Transactions to Recurly — each maps to any object or custom field on the other side.
Databases Logical databases on the instance that scope a connection. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Databases is specific to Amazon Lightsail and Line Items to Recurly — each maps to any object or custom field on the other side.
Schemas Namespaces used when selecting tables to sync. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Schemas is specific to Amazon Lightsail and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Amazon Lightsail and Recurly

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

Recurly Amazon Lightsail Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Amazon Lightsail ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

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

    Choose tables

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

Amazon Lightsail and Recurly 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
CSA STAR
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 432 integrations available for Amazon Lightsail and Recurly.

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

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