Skip to content
Database ⇄ Accounting and finance

Amazon DynamoDB to Pigment integration — real-time, two-way sync

Keep Amazon DynamoDB 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 Amazon DynamoDB and Pigment

Work with Pigment's financial data straight from Amazon DynamoDB: 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 Global secondary indexes (GSIs), Local secondary indexes (LSIs), DynamoDB Streams, Global Tables in Amazon DynamoDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Amazon DynamoDB, 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 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • 02 Sync headcount and compensation data from an HRIS into workforce planning models.
  • 03 Use DynamoDB Streams as a change-data-capture source to push item INSERT, MODIFY, and REMOVE events into a CRM, search index, or operational database in near-real-time.
  • 04 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.

Common sync patterns

Write back safely

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

React to financial events

Changes in Pigment appear in Amazon DynamoDB 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 Amazon DynamoDB as regular tables or collections your team can join, index, and query.

What you can sync between Amazon DynamoDB 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.

Amazon DynamoDB objects Pigment objects How this pairing syncs
Tables Top-level containers, each with a partition key and optional sort key; Stacksync syncs a table as a stream of items with full read and write via PutItem, UpdateItem, and DeleteItem. 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.
Global secondary indexes (GSIs) Alternate key projections that let you Query by non-key attributes without a full table Scan; read-only views maintained automatically by DynamoDB. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Global secondary indexes (GSIs) is specific to Amazon DynamoDB and Scenarios to Pigment — each maps to any object or custom field on the other side.
Local secondary indexes (LSIs) Extra sort keys within the same partition key, defined at table creation; queried like the base table for alternate access patterns. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Data imports to Pigment — each maps to any object or custom field on the other side.
DynamoDB Streams Ordered item-level change records (INSERT, MODIFY, REMOVE) with old/new image views and 24-hour retention; the native change-data-capture source Stacksync reads for near-real-time sync. Users and permissions Access controls governing which model areas a sync can touch DynamoDB Streams is specific to Amazon DynamoDB and Users and permissions to Pigment — each maps to any object or custom field on the other side.
Global Tables Multi-region, active-active replicas of a table kept in sync by DynamoDB; each region is read and written locally with last-writer-wins conflict resolution. Applications Planning models organized by domain such as finance, sales, or workforce Global Tables is specific to Amazon DynamoDB and Applications to Pigment — each maps to any object or custom field on the other side.
Time to Live (TTL) Per-item expiry timestamps; DynamoDB deletes expired items in the background and emits a Streams REMOVE record for each deletion. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Time to Live (TTL) is specific to Amazon DynamoDB and Metrics to Pigment — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB 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.

Amazon DynamoDB Pigment Sub-second propagation

DetectionChanges in Amazon DynamoDB are captured at the source via change data capture — no polling loop against its API. DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views.

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

Pigment Amazon DynamoDB 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 Amazon DynamoDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Amazon DynamoDB: Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.
  • Pigment: Subject to the platform's API rate limits.
What ships with Amazon DynamoDB ⇄ Pigment

Connect Amazon DynamoDB and Pigment for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon DynamoDB–Pigment connection.

Real-time

Two-way sync

Changes in Amazon DynamoDB or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon DynamoDB 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 Amazon DynamoDB or Pigment record.

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Pigment sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon DynamoDB and Pigment.

How the Amazon DynamoDB and Pigment connectors work

Amazon DynamoDB

Integration surface
AWS SDK / low-level HTTPS JSON API at dynamodb.<region>.amazonaws.com (PutItem, GetItem, UpdateItem, DeleteItem, Query, Scan, BatchWriteItem, TransactWriteItems), plus PartiQL (ExecuteStatement) for SQL-style access and DynamoDB Streams for change capture.
Authentication
AWS Signature Version 4 (SigV4) signed requests using an IAM access key ID and secret key, or temporary STS credentials from an assumed IAM role; IAM policies scope access down to table and item level.
Change detection
DynamoDB Streams emit ordered item-level change records (INSERT, MODIFY, REMOVE) with KEYS_ONLY, NEW_IMAGE, OLD_IMAGE, or NEW_AND_OLD_IMAGES views and 24-hour retention, read via shard iterators (or Kinesis Data Streams for longer retention). No native HTTP webhooks.
Capabilities
read · write · CDC
Rate limits
Throughput is metered in read/write capacity units (provisioned or on-demand): 1 WCU = one 1 KB write per second, 1 RCU = one strongly-consistent 4 KB read per second. Exceeding capacity or the ~3,000 RCU / 1,000 WCU per-partition ceiling returns ProvisionedThroughputExceededException with throttling.

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 Amazon DynamoDB 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 Amazon DynamoDB 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
    Amazon DynamoDB connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon DynamoDB 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 · Amazon DynamoDB ⇄ 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
    Amazon DynamoDB Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon DynamoDB 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
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:

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 443 integrations available for Amazon DynamoDB and Pigment.

Popular · 5 of 443
All Amazon DynamoDB 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