Two-way sync
Changes in Amazon Lightsail or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon Lightsail and Iterable in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Iterable holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in Amazon Lightsail, hard to get into campaigns without manual exports.
Stacksync mirrors Events, Campaigns, Templates, Lists from Iterable into Managed Databases, Databases, Schemas, Tables in Amazon Lightsail field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in Amazon Lightsail, from usage, orders, or account status, sync back into Iterable to drive campaigns and ads, with Iterable kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.
A new lead, form fill, or list change in Iterable arrives as a row change in Amazon Lightsail, so scoring, jobs, and notifications run in the tooling your team already uses.
Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.
Contacts, leads, audiences, and campaign metrics from Iterable live in Amazon Lightsail as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.
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 | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces used when selecting tables to sync. | Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. | Schemas is specific to Amazon Lightsail and Templates to Iterable — each maps to any object or custom field on the other side. | |
| Tables Relational tables read from and written to at row level. | Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. | Tables is specific to Amazon Lightsail and Lists to Iterable — each maps to any object or custom field on the other side. | |
| Views Query-backed read-only sources. | Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. | Views is specific to Amazon Lightsail and Catalogs to Iterable — 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. | Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Users and Grants is specific to Amazon Lightsail and Commerce / Purchases to Iterable — 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. | Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. | Managed Databases is specific to Amazon Lightsail and Export data to Iterable — each maps to any object or custom field on the other side. | |
| Databases Logical databases on the instance that scope a connection. | Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. | Databases is specific to Amazon Lightsail and Users to Iterable — 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 Iterable through its API, with automatic retries and rate-limit backoff.
DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs 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–Iterable connection.
Changes in Amazon Lightsail or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon Lightsail or Iterable 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 Iterable record.
Track your Amazon Lightsail ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon Lightsail and Iterable.
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 Iterable 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 Iterable 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 Iterable: 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.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Amazon Lightsail and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon Lightsail and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon Lightsail–Iterable integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon Lightsail and Iterable. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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 Iterable: System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range. 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: Managed Databases, Databases, Schemas, Tables, plus custom fields where Amazon Lightsail exposes them. On the Iterable side: Events, Campaigns, Templates, Lists. Stacksync auto-detects both schemas and converts types between the two systems.
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 397 integrations available for Amazon Lightsail and Iterable.