Skip to main content


This connector materializes Flow collections into indices in an Elasticsearch cluster.

It is available for use in the Flow web application. For local development or open-source workflows, provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.


To use this connector, you'll need:

  • An Elastic cluster with a known endpoint
    • If the cluster is on the Elastic Cloud, you'll need an Elastic user with a role that grants all privileges on indices you plan to materialize to within the cluster. See Elastic's documentation on defining roles and security privileges.
  • At least one Flow collection

If you haven't yet captured your data from its external source, start at the beginning of the guide to create a dataflow. You'll be referred back to this connector-specific documentation at the appropriate steps.


To use this connector, begin with data in one or more Flow collections. Use the below properties to configure an Elasticsearch materialization, which will direct the contents of these Flow collections into Elasticsearch indices.


You can authenticate to Elasticsearch using either a username and password, or using an API key.

The connector will automatically create an Elasticsearch index for each binding of the materialization. It uses the last component of the collection name as the name of the index by default. You can customize the name of the index using the index property in the resource configuration for each binding. You can also create the indices yourself and just enter the name as the index. This allows you full control over the index creation properties.

Elasticsearch Mappings

If you let the connector create the indices automatically, it will configure it to use dynamic runtime mappings. This allows you to search based on any fields in your source documents, and avoids any issues that could be caused by the creation of too many mappings. It's recommended that you add explicit mappings as you identify the need, in order to keep your Elasticsearch queries fast.



****Elasticsearch ConnectionobjectRequired
/endpointEndpointEndpoint host or URL. If using Elastic Cloud this follows the format https://CLUSTER_ID.REGION.CLOUD_PLATFORM.DOMAIN:PORTstringRequired
/credentials/usernameUsernameUsername to use for authenticating with Elasticsearchstring
/credentials/passwordPasswordPassword to use for authenticating with Elasticsearchstring
/credentials/apiKeyAPI KeyAPI Key to use for authenticating with Elasticsearchstring


/delta_updatesDelta updatesWhether to use standard or delta updatesbooleanfalse
/indexindexName of the ElasticSearch index to store the materialization results.stringRequired
/number_of_replicasNumber of replicasThe number of replicas in ElasticSearch index. If not set, default to be 0. For single-node clusters, this must be 0. For production systems, a value of 1 or more is recommendedinteger0
/number_of_shardsNumber of shardsThe number of shards in ElasticSearch index. Must be greater than 0.integer1


# Path to the latest version of the connector, provided as a Docker image
username: flow_user
password: secret
# If you have multiple collections you need to materialize, add a binding for each one
# to ensure complete data flow-through
- resource:
index: my-elasticsearch-index
source: PREFIX/source_collection

Delta updates

This connector supports both standard and delta updates. You must choose an option for each binding.

Learn more about delta updates and the implications of using each update type.