Skip to content
Database ⇄ Developer tools

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

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

Keep Amazon DynamoDB and Google Pubsub in step: the rows in your database and the Message attributes, Dead-letter topics, Ordering keys, Topics your engineering tools track stay consistent in real time, in both directions.

Amazon DynamoDB is where your application's durable data lives; Google Pubsub is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.

Stacksync syncs Global Tables, Time to Live (TTL), Tables, Items in Amazon DynamoDB with Message attributes, Dead-letter topics, Ordering keys, Topics in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.

Common use cases

  • 01 Backfill or migrate records into DynamoDB from another database using BatchWriteItem, then keep the two stores in continuous sync.
  • 02 Mirror a high-write DynamoDB table into a relational database so teams can join NoSQL application data against relational tables for reporting.
  • 03 Attach an Avro or Protocol Buffer schema to a topic so every message Stacksync publishes is validated against an agreed contract.
  • 04 Publish new and changed database rows as messages to a Pub/Sub topic so multiple downstream subscriptions consume the change stream independently.

Common sync patterns

Where Google Pubsub manages users or groups: keep identity aligned

Directory and identity records in Google Pubsub stay matched to the users or owners table in Amazon DynamoDB, so provisioning and de-provisioning flow from one source.

Turn rows into the records your tools track

A new or changed row in Amazon DynamoDB creates or updates the matching record in Google Pubsub, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.

Land tool activity as queryable rows

Records and events from Google Pubsub arrive in Amazon DynamoDB as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

What you can sync between Amazon DynamoDB and Google Pubsub

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 Google Pubsub objects How this pairing syncs
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. Message attributes Up to 100 key-value pairs per message; carry routing metadata and drive subscription filter expressions. Local secondary indexes (LSIs) is specific to Amazon DynamoDB and Message attributes to Google Pubsub — 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. Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. DynamoDB Streams is specific to Amazon DynamoDB and Dead-letter topics to Google Pubsub — 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. Ordering keys Tag messages so those sharing a key deliver in publish order when message ordering is enabled; throughput capped at 1 MBps per key. Global Tables is specific to Amazon DynamoDB and Ordering keys to Google Pubsub — 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. Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. Time to Live (TTL) is specific to Amazon DynamoDB and Topics to Google Pubsub — each maps to any object or custom field on the other side.
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. Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. Tables is specific to Amazon DynamoDB and Subscriptions to Google Pubsub — each maps to any object or custom field on the other side.
Items Individual schemaless records (attributes up to 400 KB each); read with GetItem, Query, and Scan and written with PutItem or BatchWriteItem, so write is supported here. Messages The synced unit: base64-encoded data plus attributes, ordering key, messageId and publishTime; capped at 10 MB each. Items is specific to Amazon DynamoDB and Messages to Google Pubsub — each maps to any object or custom field on the other side.

How changes propagate between Amazon DynamoDB and Google Pubsub

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 Google Pubsub 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 Google Pubsub through its API, with automatic retries and rate-limit backoff.

Google Pubsub Amazon DynamoDB Sub-second propagation

DetectionGoogle Pubsub notifies Stacksync of record changes through webhook events. Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST.

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.
  • Google Pubsub: Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key.
What ships with Amazon DynamoDB ⇄ Google Pubsub

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon DynamoDB ⇄ Google Pubsub 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 Google Pubsub.

How the Amazon DynamoDB and Google Pubsub 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.

Google Pubsub

Integration surface
REST and gRPC (Cloud Pub/Sub API v1)
Authentication
Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber
Change detection
Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST; no modified-date polling
Capabilities
read · write · webhooks
Rate limits
Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key
How it works

How to connect Amazon DynamoDB to Google Pubsub — 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 Google Pubsub 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
    Google Pubsub connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Amazon DynamoDB and Google Pubsub 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 350 integrations available for Amazon DynamoDB and Google Pubsub.

Popular · 5 of 350
All Amazon DynamoDB integrations All Google Pubsub 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