Real-time
Two-way sync
Changes in AWS Aurora PostgreSQL or Rillet instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Accounting and finance
AWS Aurora PostgreSQL to Rillet integration — real-time, two-way sync
Keep AWS Aurora PostgreSQL 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 PostgreSQL and Rillet
Work with Rillet's financial data straight from AWS Aurora PostgreSQL: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.
Teams connect Rillet to AWS Aurora PostgreSQL to expose accounting records — Accounts, Invoices, Bills — as relational tables their own systems can query. Rillet records become Aurora rows, so billing pipelines and finance reporting run in SQL and write back to the accounting system.
Stacksync mirrors Account, Customer, Vendor, Invoice from Rillet into Primary keys and constraints, Views and materialized views, Foreign keys, Replication slots and publications in AWS Aurora PostgreSQL and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against AWS Aurora PostgreSQL, 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
- 01 Reconcile Credit Memos and Bills against application data with Postgres joins instead of exports.
- 02 Feed a usage-based billing pipeline that writes Aurora rows and produces Rillet Invoices.
- 03 Build finance dashboards on Aurora views over live Rillet Account data.
- 04 Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
Common sync patterns
Accounting mirror
Rillet Account, Invoice, and Bill records sync into Aurora tables for SQL-based financial reporting.
Automated invoicing
invoice rows generated in Aurora from usage data flow into Rillet as Invoices against the right Customer.
Vendor and customer master sync
Rillet Customers and Vendors stay consistent with entity records in Aurora schemas.
What you can sync between AWS Aurora PostgreSQL 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 PostgreSQL objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Columns Rich Postgres types including JSONB and arrays are mapped to the paired system's fields. | Account Synced with incremental and full sync per the Stacksync docs. | Columns is specific to AWS Aurora PostgreSQL and Account to Rillet — each maps to any object or custom field on the other side. | |
| Primary keys and constraints Identify rows for upserts and enforce integrity on sync writes. | Customer Synced with incremental and full sync per the Stacksync docs. | Primary keys and constraints is specific to AWS Aurora PostgreSQL and Customer to Rillet — each maps to any object or custom field on the other side. | |
| Views and materialized views Usable as read-only sources for filtered or precomputed sync datasets. | Vendor Synced with incremental and full sync per the Stacksync docs. | Views and materialized views is specific to AWS Aurora PostgreSQL and Vendor to Rillet — each maps to any object or custom field on the other side. | |
| Foreign keys Relationship metadata that syncs can translate into object references elsewhere. | Invoice Synced with incremental and full sync per the Stacksync docs. | Foreign keys is specific to AWS Aurora PostgreSQL and Invoice to Rillet — each maps to any object or custom field on the other side. | |
| Replication slots and publications The logical replication objects that power log-based CDC. | Credit Memo Synced with incremental and full sync per the Stacksync docs. | Replication slots and publications is specific to AWS Aurora PostgreSQL and Credit Memo to Rillet — each maps to any object or custom field on the other side. | |
| Databases and schemas PostgreSQL's two-level namespace scopes which tables a sync connection targets. | Bill Synced with incremental and full sync per the Stacksync docs. | Databases and schemas is specific to AWS Aurora PostgreSQL and Bill to Rillet — each maps to any object or custom field on the other side. |
How changes propagate between AWS Aurora PostgreSQL and Rillet
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.
AWS Aurora PostgreSQL Rillet Sub-second propagation
DetectionChanges in AWS Aurora PostgreSQL are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication (WAL decoding through replication slots), with timestamp polling as a fallback.
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
Rillet AWS Aurora PostgreSQL Sub-second propagation
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 AWS Aurora PostgreSQL as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Rillet: Subject to the platform's API rate limits.
What ships with AWS Aurora PostgreSQL ⇄ Rillet
Connect AWS Aurora PostgreSQL and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS Aurora PostgreSQL–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever AWS Aurora PostgreSQL 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 PostgreSQL or Rillet record.
Observability
Monitoring
Track your AWS Aurora PostgreSQL ⇄ 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 PostgreSQL and Rillet.
How the AWS Aurora PostgreSQL and Rillet connectors work
AWS Aurora PostgreSQL
- Integration surface
- SQL wire protocol (PostgreSQL-compatible), standard Postgres drivers and JDBC
- Authentication
- Database credentials, optionally AWS IAM database authentication, over TLS
- Change detection
- Log-based CDC via PostgreSQL logical replication (WAL decoding through replication slots), with timestamp polling 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.
How it works
How to connect AWS Aurora PostgreSQL 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.
- 01
Connect your apps
Authenticate AWS Aurora PostgreSQL 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.
AWS Aurora PostgreSQL
connected
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the AWS Aurora PostgreSQL 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.
objects · AWS Aurora PostgreSQL ⇄ RilletCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
AWS Aurora PostgreSQL RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
AWS Aurora PostgreSQL and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between AWS Aurora PostgreSQL and Rillet: authenticate both systems, choose the objects to sync (such as AWS Aurora PostgreSQL's Columns and Primary keys and constraints), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both AWS Aurora PostgreSQL and Rillet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on AWS Aurora PostgreSQL: Log-based CDC via PostgreSQL logical replication (WAL decoding through replication slots), with timestamp polling as a fallback. On Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Rillet side: Account, Customer, Vendor, Invoice, plus custom fields where Rillet exposes them. On the AWS Aurora PostgreSQL side: Primary keys and constraints, Views and materialized views, Foreign keys, Replication slots and publications. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for AWS Aurora PostgreSQL and Rillet: Accounting mirror; Automated invoicing; Vendor and customer master sync. Rillet Account, Invoice, and Bill records sync into Aurora tables for SQL-based financial reporting.
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
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 373 integrations available for AWS Aurora PostgreSQL and Rillet.
Popular · 7 of 373
-
AWS Aurora PostgreSQL ⇄ Anaplan -
AWS Aurora PostgreSQL ⇄ Chargebee -
AWS Aurora PostgreSQL ⇄ Hyperline -
AWS Aurora PostgreSQL ⇄ Pigment -
Rillet ⇄ MongoDB -
Rillet ⇄ Google AlloyDB -
Rillet ⇄ Dynamo DB
No integrations match .
