Skip to content
Storage ⇄ Database

Amazon S3 to Google Cloud Spanner integration — real-time, two-way sync

Keep Amazon S3 and Google Cloud Spanner 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 S3 and Google Cloud Spanner

Keep Google Cloud Spanner and Amazon S3 in step: a row in Google Cloud Spanner for every file in Amazon S3, with names, paths, metadata, and status staying consistent in real time, in both directions.

A database holds structured records; a storage system holds the files those records depend on, such as contracts, images, exports, uploads, and documents. The two describe the same things from opposite sides: a row in Google Cloud Spanner says a file exists and carries its name, location, and status, while Amazon S3 holds the bytes. Linked only by a hand-kept path or a one-off script, the two drift the moment a file is renamed, moved, or deleted and the record still points at where it used to be.

Stacksync syncs Databases, Tables, Rows, Interleaved tables in Google Cloud Spanner with Buckets, Objects, Object metadata, Object tags in Amazon S3 bi-directionally and in real time. File attributes, including name, path or object key, size, type, modified time, owner, and tags or custom properties, map field by field to columns on the matching row, and a change on either side shows up on the other within seconds. New files appear as rows, metadata edits travel in the direction you choose, and deletes stay consistent, with conflict rules you set in place of nightly reconciliation scripts.

Common use cases

  • 01 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.
  • 02 Run a two-way sync between Spanner and a SaaS tool so edits made by ops teams land back in the application database.
  • 03 Reconcile Object versions and delete markers into an audit table so teams track when files under a compliance prefix were added, replaced, or removed.
  • 04 Index every new Object's key, size, LastModified, and user metadata into a Postgres catalog table so applications query S3 contents in SQL instead of paging ListObjectsV2.

Common sync patterns

File metadata kept in step

Tags, custom properties, owner, or status columns edited on a row in Google Cloud Spanner write back to the matching file's metadata in Amazon S3, and metadata changed in Amazon S3 updates the row, so the two never disagree about a file.

Records that point at documents

Where a record in Google Cloud Spanner references a file in Amazon S3, such as a contract, an image, an export, or an upload, the reference, path, and status stay consistent as files are renamed, moved, or replaced, so stored links keep resolving.

A landing zone for incoming files

Files that arrive in a folder or bucket in Amazon S3 become rows in Google Cloud Spanner as they land, so a database-driven process can pick them up without polling the storage system's API.

What you can sync between Amazon S3 and Google Cloud Spanner

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 S3 objects Google Cloud Spanner objects How this pairing syncs
Object tags Up to 10 key-value tags per object, mutable in place via the tagging API independent of content, so classification and retention labels sync two-way without rewriting files. Change streams Capture inserts, updates, and deletes for log-style change data capture. Object tags is specific to Amazon S3 and Change streams to Google Cloud Spanner — each maps to any object or custom field on the other side.
Object versions When bucket versioning is enabled every write creates a new version ID; prior versions and delete markers are readable for history and audit syncs. Views Read-only projections useful for shaping data before it leaves Spanner. Object versions is specific to Amazon S3 and Views to Google Cloud Spanner — each maps to any object or custom field on the other side.
Prefixes (folders) Logical path segments in object keys used to scope a sync and to parallelize throughput, since S3 rate limits partition by prefix. Databases Top-level containers that scope schema and sync configuration. Prefixes (folders) is specific to Amazon S3 and Databases to Google Cloud Spanner — each maps to any object or custom field on the other side.
Multipart uploads In-progress large-object uploads assembled from parts; objects above ~100 MB (required above 5 GB) are written this way, and incomplete uploads persist until completed or aborted. Tables Relational tables mapped one-to-one to sync targets. Multipart uploads is specific to Amazon S3 and Tables to Google Cloud Spanner — each maps to any object or custom field on the other side.
Buckets Top-level, region-scoped containers that hold objects; enumerated to discover the namespaces and prefixes a sync should cover. Rows The unit of read and write in each sync cycle, keyed by primary key. Buckets is specific to Amazon S3 and Rows to Google Cloud Spanner — each maps to any object or custom field on the other side.
Objects Files stored under a key; content is read with GET and written with PUT, and each object's key/size/ETag/LastModified is the unit indexed into a database. Interleaved tables Child rows physically co-located with parents; synced as related records. Objects is specific to Amazon S3 and Interleaved tables to Google Cloud Spanner — each maps to any object or custom field on the other side.

How changes propagate between Amazon S3 and Google Cloud Spanner

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 S3 Google Cloud Spanner Sub-second propagation

DetectionAmazon S3 notifies Stacksync of record changes through webhook events. S3 Event Notifications push object-created, object-removed, and object-tagging events to SNS, SQS, Lambda, or EventBridge.

DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.

Google Cloud Spanner Amazon S3 Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

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

Rate-limit considerations

  • Amazon S3: S3 sustains at least 3,500 PUT/COPY/POST/DELETE and 5,500 GET/HEAD requests per second per partitioned prefix and scales higher automatically; bursts can return HTTP 503 SlowDown while it repartitions.
  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
What ships with Amazon S3 ⇄ Google Cloud Spanner

Connect Amazon S3 and Google Cloud Spanner for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon S3–Google Cloud Spanner connection.

Real-time

Two-way sync

Changes in Amazon S3 or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon S3 or Google Cloud Spanner 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 S3 or Google Cloud Spanner record.

Observability

Monitoring

Track your Amazon S3 ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon S3 and Google Cloud Spanner.

How the Amazon S3 and Google Cloud Spanner connectors work

Amazon S3

Integration surface
S3 REST API (also via AWS SDKs and the S3-compatible endpoint)
Authentication
AWS IAM credentials — an access key ID and secret access key signed with AWS Signature Version 4; supports temporary STS credentials and cross-account IAM roles
Change detection
S3 Event Notifications push object-created, object-removed, and object-tagging events to SNS, SQS, Lambda, or EventBridge; there is no modified-since query, so polling relies on each object's LastModified from ListObjectsV2
Capabilities
read · write · webhooks
Rate limits
S3 sustains at least 3,500 PUT/COPY/POST/DELETE and 5,500 GET/HEAD requests per second per partitioned prefix and scales higher automatically; bursts can return HTTP 503 SlowDown while it repartitions.

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
How it works

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

    Choose tables

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

Amazon S3 and Google Cloud Spanner 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 418 integrations available for Amazon S3 and Google Cloud Spanner.

Popular · 7 of 418
All Amazon S3 integrations All Google Cloud Spanner 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