Skip to content
Database ⇄ Data warehouse

OpenSearch to Starburst Enterprise integration — real-time, two-way sync

Keep OpenSearch and Starburst Enterprise 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 OpenSearch and Starburst Enterprise

Connect OpenSearch and Starburst Enterprise with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want OpenSearch's rows in Starburst Enterprise, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in OpenSearch where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in OpenSearch sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into OpenSearch, with schema and type mapping between the two systems handled for you.

Common use cases

  • Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
  • Consolidate reads from multiple databases behind a single connection instead of maintaining one integration per source
  • Stream CRM records such as accounts, contacts, and tickets into OpenSearch to power internal search across customer data.
  • Sync product catalogs from an ERP or database into the indexes that back storefront search.

Offload heavy reads

Point analytical queries at the synced copy in Starburst Enterprise and keep OpenSearch focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from OpenSearch land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.

Serve warehouse results at database speed

Aggregates or model outputs computed in Starburst Enterprise sync into OpenSearch, where whatever reads from that database gets them without querying the warehouse.

What you can sync between OpenSearch and Starburst Enterprise

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.

OpenSearch objects Starburst Enterprise objects
Data streams Append-oriented time-series storage for logs and events pushed from source systems Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas.
Snapshots Backup artifacts, relevant when reseeding an index from a repository Tables Queryable relations; writes pass through to sources whose connectors support them.
Indexes The core container; synced records land in indexes with defined mappings Views Engine-level SQL views used to shape federated data before syncing it out.
Documents JSON records written via the index and bulk APIs and read via search queries Materialized views Precomputed results that make repeated sync reads cheaper.
Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills Columns Typed per the Trino type system, mapped from each source's native types.
Index templates Mapping and settings presets applied to new indexes a sync creates Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source.
What ships with OpenSearch ⇄ Starburst Enterprise

Connect OpenSearch and Starburst Enterprise for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your OpenSearch ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between OpenSearch and Starburst Enterprise.

How the OpenSearch and Starburst Enterprise connectors work

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

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works

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

    Choose tables

    Pick the OpenSearch and Starburst Enterprise 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 · OpenSearch ⇄ Starburst Enterprise
    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
    OpenSearch Starburst Enterprise
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

OpenSearch and Starburst Enterprise integration FAQ

SECURITY

Security teams love 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for OpenSearch and Starburst Enterprise.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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