Skip to content
Database ⇄ Accounting and finance

AWS Aurora MySQL to Rillet integration — real-time, two-way sync

Keep AWS Aurora MySQL 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.

  • 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 AWS Aurora MySQL and Rillet

Work with Rillet's financial data straight from AWS Aurora MySQL: 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 Customer, Vendor, Invoice, Credit Memo from Rillet into Databases (schemas), Tables, Rows, Columns in AWS Aurora MySQL and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against AWS Aurora MySQL, and rows your code writes or updates flow back into Rillet with validation, so the finance system stays the system of record.

Common use cases

  • Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
  • Push billing events from a product or usage-metering system into Rillet for revenue recognition.
  • Give backend services read and write access to ERP or billing data by syncing it into Aurora tables the application already queries.
  • Stream row changes from Aurora into SaaS tools via binlog CDC instead of scheduled batch exports.

Query finance data like any other data

Customers, invoices, and payments from Rillet live in AWS Aurora MySQL as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on AWS Aurora MySQL; Stacksync handles the API calls, rate limits, and retries against Rillet.

Write back safely

Updates written to the synced tables in AWS Aurora MySQL propagate into Rillet, so automations can create or correct finance records without custom integration code.

What you can sync between AWS Aurora MySQL and Rillet

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.

AWS Aurora MySQL objects Rillet objects
Primary keys and indexes Used to match rows across systems and keep incremental syncs efficient. Customer Synced with incremental and full sync per the Stacksync docs.
Views Can serve as read-only sync sources for derived or filtered datasets. Vendor Synced with incremental and full sync per the Stacksync docs.
Foreign keys Express relationships that syncs preserve when mapping to related objects elsewhere. Invoice Synced with incremental and full sync per the Stacksync docs.
Stored procedures and triggers Existing database logic keeps firing on rows written by a sync. Credit Memo Synced with incremental and full sync per the Stacksync docs.
Databases (schemas) Logical namespaces that scope which tables a sync connection can see. Bill Synced with incremental and full sync per the Stacksync docs.
Tables The primary sync unit; each table maps one-to-one to a table or object in the paired system. Journal Entry Synced with incremental and full sync per the Stacksync docs.
What ships with AWS Aurora MySQL ⇄ Rillet

Connect AWS Aurora MySQL and Rillet for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS Aurora MySQL–Rillet connection.

Real-time

Two-way sync

Changes in AWS Aurora MySQL or Rillet instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever AWS Aurora MySQL or Rillet 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 AWS Aurora MySQL or Rillet record.

Observability

Monitoring

Track your AWS Aurora MySQL ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between AWS Aurora MySQL and Rillet.

How the AWS Aurora MySQL and Rillet connectors work

AWS Aurora MySQL

Integration surface
SQL wire protocol (MySQL-compatible), standard MySQL drivers and JDBC
Authentication
Database credentials, optionally AWS IAM database authentication, over TLS
Change detection
Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback
Capabilities
read · write · CDC

Rillet

Integration surface
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
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

How to connect AWS Aurora MySQL to Rillet — 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 AWS Aurora MySQL 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    AWS Aurora MySQL connected
    Rillet connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the AWS Aurora MySQL 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · AWS Aurora MySQL ⇄ Rillet
    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
    AWS Aurora MySQL Rillet
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

AWS Aurora MySQL and Rillet integration FAQ

SECURITY

Security teams love 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 386 integrations available for AWS Aurora MySQL and Rillet.

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

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