Two-way sync
Changes in Amazon Aurora or Amazon Lightsail instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon Aurora and Amazon Lightsail in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Amazon Aurora and Amazon Lightsail continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both Amazon Aurora and Amazon Lightsail, so each workload runs on the engine that suits it.
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 Aurora objects | Amazon Lightsail objects | How this pairing syncs | |
|---|---|---|---|
| Databases Logical databases within a cluster that scope a sync connection. | Databases Logical databases on the instance that scope a connection. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Schemas Namespaces (PostgreSQL) or database-level grouping (MySQL) used in table selection. | Schemas Namespaces used when selecting tables to sync. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tables Relational tables synced bi-directionally at row level. | Tables Relational tables read from and written to at row level. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Read-only query-backed sources for downstream syncs. | Views Query-backed read-only sources. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Read Replicas Reader endpoints that syncs can target to keep load off the writer. | Users and Grants Database accounts used to give the sync connection scoped access. | Read Replicas is specific to Amazon Aurora and Users and Grants to Amazon Lightsail — each maps to any object or custom field on the other side. | |
| Materialized Views Precomputed result sets (PostgreSQL-compatible clusters) readable as sources. | Managed Databases Lightsail-hosted MySQL or PostgreSQL instances that a sync connects to as standard databases. | Materialized Views is specific to Amazon Aurora and Managed Databases to Amazon Lightsail — 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.
DetectionChanges in Amazon Aurora are captured at the source via change data capture — no polling loop against its API. Log-based CDC: binlog on MySQL-compatible clusters, logical replication/decoding on PostgreSQL-compatible clusters.
DeliveryEach detected change is applied to Amazon Lightsail as a row-level write, with types converted between the two schemas.
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 applied to Amazon Aurora 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 Aurora–Amazon Lightsail connection.
Changes in Amazon Aurora or Amazon Lightsail instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon Aurora or Amazon Lightsail 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 Aurora or Amazon Lightsail record.
Track your Amazon Aurora ⇄ Amazon Lightsail sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon Aurora and Amazon Lightsail.
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 Aurora and Amazon Lightsail 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 Aurora and Amazon Lightsail 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 Aurora and Amazon Lightsail: authenticate both systems, choose the objects to sync (such as Amazon Aurora's Databases and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Amazon Aurora: Aurora is wire-compatible with MySQL and PostgreSQL, so any tooling built for those engines connects without modification. Amazon Lightsail: Lightsail managed databases run standard MySQL or PostgreSQL engines, so integrations use ordinary database drivers and SQL rather than a proprietary API. Stacksync's field mapping accounts for these differences between Amazon Aurora and Amazon Lightsail without custom code.
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 Aurora and Amazon Lightsail records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon Aurora and Amazon Lightsail connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon Aurora–Amazon Lightsail integration in-house.
Yes — Stacksync ships production-grade connectors for both Amazon Aurora and Amazon Lightsail. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Amazon Aurora: Log-based CDC: binlog on MySQL-compatible clusters, logical replication/decoding on PostgreSQL-compatible clusters; polling as a fallback. 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 367 integrations available for Amazon Aurora and Amazon Lightsail.