Two-way sync
Changes in Amazon RDS or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Amazon RDS and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Connecting Rillet to Amazon RDS puts the general ledger next to operational data in SQL. Account, Invoice, and Bill records sync into RDS Tables, so finance reporting, reconciliation, and internal tools query accounting data directly, and database updates flow back into Rillet.
Stacksync mirrors Invoice, Credit Memo, Bill, Journal Entry from Rillet into Stored Procedures, Databases, Schemas, Tables in Amazon RDS and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Amazon RDS, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.
Rillet Account, Invoice, and Bill records replicate into Amazon RDS Tables for SQL-based financial reporting.
Rillet Customer and Vendor records map to RDS Schemas with Primary and Unique Keys deduplicating parties.
Credit Memos sync to RDS Views where they join against Invoices for net revenue analysis.
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 | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Stored Procedures Engine-specific logic that can react to synced rows. | Account Synced with incremental and full sync per the Stacksync docs. | Stored Procedures is specific to Amazon RDS and Account to Rillet — 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. | Customer Synced with incremental and full sync per the Stacksync docs. | Databases is specific to Amazon RDS and Customer to Rillet — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to isolate synced tables. | Vendor Synced with incremental and full sync per the Stacksync docs. | Schemas is specific to Amazon RDS and Vendor to Rillet — 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. | Invoice Synced with incremental and full sync per the Stacksync docs. | Tables is specific to Amazon RDS and Invoice to Rillet — each maps to any object or custom field on the other side. | |
| Views Read-side projections exposed to outbound syncs. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | Views is specific to Amazon RDS and Credit Memo to Rillet — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets, typed per the underlying engine. | Bill Synced with incremental and full sync per the Stacksync docs. | Columns is specific to Amazon RDS and Bill to Rillet — 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 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 Rillet through its API, with automatic retries and rate-limit backoff.
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is applied to Amazon RDS 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 RDS–Rillet connection.
Changes in Amazon RDS or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Amazon RDS or Rillet 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 RDS or Rillet record.
Track your Amazon RDS ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Amazon RDS and Rillet.
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 RDS and Rillet 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 RDS and Rillet 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 RDS and Rillet: authenticate both systems, choose the objects to sync (such as Amazon RDS's Stored Procedures and Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Amazon RDS and Rillet: Ledger mirror; Customer and vendor master sync; Credit memo tracking. Rillet Account, Invoice, and Bill records replicate into Amazon RDS Tables for SQL-based financial reporting.
Amazon RDS: 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. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: The REST API authenticates with API keys and publishes an OpenAPI specification, with separate production and sandbox environments. Amazon RDS: IAM database authentication can replace static passwords on supported engines, letting integrations authenticate with short-lived tokens. Stacksync's field mapping accounts for these differences between Amazon RDS and Rillet 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 RDS and Rillet records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Amazon RDS and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Amazon RDS–Rillet integration in-house.
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 377 integrations available for Amazon RDS and Rillet.