Every index as a table
Indices are discovered automatically and each becomes its own schema.
AWS OpenSearch
Polytomic connects AWS OpenSearch to your data warehouse, databases, and SaaS tools for search index ETL in both directions. Replicate documents from your indices into your data warehouse for analysis, and keep OpenSearch indices loaded from PostgreSQL, Snowflake, and other sources, without writing code.
Read and write indices
Replicate indices out, or load tables in with automatic index creation.
Incremental on any sortable field
Track on a timestamp, a sequence, or any sortable field you choose.
Example workflows
Replicate OpenSearch indices into your data warehouse
What you can sync
Move data between AWS OpenSearch and your data warehouse, databases, and SaaS tools, in both directions. Read documents out of your indices, and replicate tables from your databases and data warehouse into OpenSearch indices with bulk sync.
From AWS OpenSearch
Concrete indices, each exposed as its own table
Top level fields from each index mapping
Object and nested fields kept as object values
Point in time snapshot reads with search after paging
Incremental reads on any sortable field
To AWS OpenSearch
Indices created automatically with a strict mapping
Upserts keyed on your source's unique key
New fields added to existing index mappings
Soft deletes by default, with optional hard deletes
How it works
Connect your OpenSearch domain with AWS credentials and Polytomic works in both directions. Indices are discovered and read as tables into your data warehouse, databases, or SaaS tools, and bulk sync replicates tables from your databases and data warehouse into OpenSearch indices, creating and extending mappings as your schema changes.
Reads use a point in time snapshot with search after paging rather than the older scroll approach, which keeps a long running read consistent even while the index continues receiving writes.
- Connect with AWS access keys signed for your OpenSearch domain
- Discover concrete indices and expose each as a table
- Read with point in time snapshots and search after paging
- Sync incrementally by nominating any sortable field
- Replicate tables into OpenSearch indices with bulk sync, upserting by unique key
- Monitor sync health, record volume, and failures from one interface
How to set up
Polytomic authenticates with AWS access key and secret credentials, signing requests with SigV4 against your OpenSearch domain endpoint and region. For reads, the IAM principal needs read access to the indices you want to sync, plus permission to create and delete point in time contexts. For destination use, it also needs write access to create indices, update mappings, and run bulk writes and deletes.
How to get connected
- 1In AWS, create an IAM user or principal with OpenSearch read access, plus write access if OpenSearch will be a destination
- 2Ensure it can also create and delete point in time contexts
- 3In Polytomic, navigate to Connections, then Add Connection, then AWS OpenSearch
- 4Enter the access key, secret, region, and domain endpoint
- 5Test the connection
- 6Select the indices you want to sync and click Save
See the documentation for full setup details.
Frequently asked questions
Why teams choose Polytomic
No engineering required
Set up and manage syncs without writing code.
Flexible data modeling
Use SQL to define exactly what data gets synced.
Handles scale automatically
Supports large datasets with incremental syncs and bulk APIs.
Start syncing your data with AWS OpenSearch in minutes
No credit card required. Free trial available.