Skip to content
Database ⇄ Accounting and finance

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

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

Work with Pigment'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 Dimension lists, Tables, Scenarios, Data imports from Pigment into Views, Foreign keys, Stored procedures and triggers, Databases (schemas) 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 Pigment with validation, so the finance system stays the system of record.

Common use cases

  • 01 Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • 02 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • 03 Sync a production Aurora cluster with an analytics database while filtering out sensitive columns.
  • 04 Let operations teams edit records in a spreadsheet-style tool with changes written back to Aurora safely.

Common sync patterns

Write back safely

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

React to financial events

Changes in Pigment appear in AWS Aurora MySQL as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

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

What you can sync between AWS Aurora MySQL and Pigment

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 Pigment objects How this pairing syncs
Tables The primary sync unit; each table maps one-to-one to a table or object in the paired system. Tables Row-based transactional data loaded into models from source systems Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Primary keys and indexes Used to match rows across systems and keep incremental syncs efficient. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Primary keys and indexes is specific to AWS Aurora MySQL and Metrics to Pigment — each maps to any object or custom field on the other side.
Views Can serve as read-only sync sources for derived or filtered datasets. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Views is specific to AWS Aurora MySQL and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Foreign keys Express relationships that syncs preserve when mapping to related objects elsewhere. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Foreign keys is specific to AWS Aurora MySQL and Scenarios to Pigment — each maps to any object or custom field on the other side.
Stored procedures and triggers Existing database logic keeps firing on rows written by a sync. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Stored procedures and triggers is specific to AWS Aurora MySQL and Data imports to Pigment — each maps to any object or custom field on the other side.
Databases (schemas) Logical namespaces that scope which tables a sync connection can see. Users and permissions Access controls governing which model areas a sync can touch Databases (schemas) is specific to AWS Aurora MySQL and Users and permissions to Pigment — each maps to any object or custom field on the other side.

How changes propagate between AWS Aurora MySQL and Pigment

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 MySQL Pigment Sub-second propagation

DetectionChanges in AWS Aurora MySQL are captured at the source via change data capture — no polling loop against its API. Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback.

DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.

Pigment AWS Aurora MySQL Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

DeliveryEach detected change is applied to AWS Aurora MySQL as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Pigment: Subject to the platform's API rate limits.
What ships with AWS Aurora MySQL ⇄ Pigment

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

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

Real-time

Two-way sync

Changes in AWS Aurora MySQL or Pigment 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 Pigment 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 Pigment record.

Observability

Monitoring

Track your AWS Aurora MySQL ⇄ Pigment 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 Pigment.

How the AWS Aurora MySQL and Pigment 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

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

How to connect AWS Aurora MySQL to Pigment — 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 Pigment 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
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the AWS Aurora MySQL and Pigment 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 ⇄ Pigment
    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 Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

AWS Aurora MySQL and Pigment integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 357 integrations available for AWS Aurora MySQL and Pigment.

Popular · 6 of 357
All AWS Aurora MySQL integrations All Pigment integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own