Skip to content
Storage ⇄ Database

Amazon S3 to OpenSearch integration — real-time, two-way sync

Keep Amazon S3 and OpenSearch 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 OpenSearch

Keep OpenSearch and Amazon S3 in step: a row in OpenSearch 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 OpenSearch 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 Index templates, Ingest pipelines, Data streams, Snapshots in OpenSearch 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 Stream CRM records such as accounts, contacts, and tickets into OpenSearch to power internal search across customer data.
  • 02 Sync product catalogs from an ERP or database into the indexes that back storefront search.
  • 03 Mirror Objects under a given Bucket and prefix into another bucket, region, or a warehouse external stage for backup or downstream processing.
  • 04 Trigger a database or ERP record update the moment an S3 Event Notification fires an object-created event, for example when a partner drops an EDI or invoice file into an inbound prefix.

Common sync patterns

A landing zone for incoming files

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

Continuous archival to file storage

Rows from OpenSearch are written out to Amazon S3 as files on a schedule or as they change, giving a durable, low-cost copy for backup, compliance, or a data lake, without a custom export job to maintain.

A queryable index of the file store

Every file or object in Amazon S3 shows up as a row in OpenSearch, with its name, folder or key, size, type, and modified date as columns, so the contents of the store can be listed, filtered, and joined like any other table.

What you can sync between Amazon S3 and OpenSearch

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 OpenSearch 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. Documents JSON records written via the index and bulk APIs and read via search queries Object tags is specific to Amazon S3 and Documents to OpenSearch — 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. Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills Object versions is specific to Amazon S3 and Index aliases to OpenSearch — 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. Index templates Mapping and settings presets applied to new indexes a sync creates Prefixes (folders) is specific to Amazon S3 and Index templates to OpenSearch — 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. Ingest pipelines Server-side processors that transform documents as they are written Multipart uploads is specific to Amazon S3 and Ingest pipelines to OpenSearch — 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. Data streams Append-oriented time-series storage for logs and events pushed from source systems Buckets is specific to Amazon S3 and Data streams to OpenSearch — 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. Snapshots Backup artifacts, relevant when reseeding an index from a repository Objects is specific to Amazon S3 and Snapshots to OpenSearch — each maps to any object or custom field on the other side.

How changes propagate between Amazon S3 and OpenSearch

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

OpenSearch Amazon S3 Interval-based propagation

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

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.
  • OpenSearch: Throughput bounded by cluster sizing rather than fixed API quotas.
What ships with Amazon S3 ⇄ OpenSearch

Connect Amazon S3 and OpenSearch for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Amazon S3 ⇄ OpenSearch 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 OpenSearch.

How the Amazon S3 and OpenSearch 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.

OpenSearch

Integration surface
REST API over HTTP(S) with JSON payloads
Authentication
basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service
Change detection
no native change feed; reads rely on queries with scroll or point-in-time polling
Capabilities
read · write
Rate limits
throughput bounded by cluster sizing rather than fixed API quotas
How it works

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

    Choose tables

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

Amazon S3 and OpenSearch 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 415 integrations available for Amazon S3 and OpenSearch.

Popular · 7 of 415
All Amazon S3 integrations All OpenSearch 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