Loading

Content connectors

Stack Serverless

Note

This page is about Content connectors that synchronize third-party data into Elasticsearch. If you’re looking for Kibana connectors to integrate with services like generative AI model providers, refer to Kibana Connectors.

A connector is an Elastic integration that syncs data from an original data source to Elasticsearch. Use connectors to create searchable, read-only replicas of your data in Elasticsearch.

Each connector extracts the original files, records, or objects; and transforms them into documents within Elasticsearch.

These connectors are written in Python and the source code is available in the elastic/connectors repo.

Important

As of Elastic 9.0, managed connectors on Elastic Cloud Hosted are no longer available. All connectors must be self-managed.

This table provides an overview of our available connectors, their current support status, and the features they support.

The columns provide specific information about each connector:

  • Status: Indicates whether the connector is in General Availability (GA), Technical Preview, Beta, or is an Example connector.
  • Advanced sync rules: Specifies the versions in which advanced sync rules are supported, if applicable.
  • Local binary extraction service: Specifies the versions in which the local binary extraction service is supported, if applicable.
  • Incremental syncs: Specifies the version in which incremental syncs are supported, if applicable.
  • Document level security: Specifies the version in which document level security is supported, if applicable.
Connector Status Advanced sync rules Local binary extraction service Incremental syncs Document level security Source code
Azure Blob GA - 8.11+ 8.13+ - View code
Box Preview - - 8.13+ - View code
Confluence Cloud GA 8.9+ 8.11+ 8.13+ 8.10 View code
Confluence Data Center Preview 8.13+ 8.13+ 8.13+ 8.14+ View code
Confluence Server GA 8.9+ 8.11+ 8.13+ 8.14+ View code
Dropbox GA - 8.11+ 8.13+ 8.12+ View code
GitHub GA 8.10+ 8.11+ 8.13+ 8.12+ View code
Gmail GA - - 8.13+ 8.10+ View code
Google Cloud Storage GA - 8.11+ 8.13+ - View code
Google Drive GA - 8.11+ 8.13+ 8.10+ View code
GraphQL Preview - - - - View code
Jira Cloud GA 8.9+ 8.11+ 8.13+ 8.10+ View code
Jira Data Center Preview 8.13+ 8.13+ 8.13+ 8.13+* View code
Jira Server GA 8.9+ 8.11+ 8.13+ - View code
Microsoft SQL Server GA 8.11+ - - - View code
MongoDB GA 8.8 native/ 8.12 self-managed - - - View code
MySQL GA 8.8+ - - - View code
Network drive GA 8.10+ 8.14+ 8.13+ 8.11+ View code
Notion GA 8.14+ - - - View code
OneDrive GA 8.11+ 8.11+ 8.13+ 8.11+ View code
Opentext Documentum Example n/a n/a n/a - View code
Oracle GA - - - - View code
Outlook GA - 8.11+ 8.13+ 8.14+ View code
PostgreSQL GA 8.11+ - - - View code
Redis Preview - - - - View code
Amazon S3 GA 8.12+ 8.11+ - - View code
Salesforce GA 8.12+ 8.11+ 8.13+ 8.13+ View code
ServiceNow GA 8.10+ 8.11+ 8.13+ 8.13+ View code
Sharepoint Online GA 8.9+ 8.9+ 8.9+ 8.9+ View code
Sharepoint Server Beta - 8.11+ 8.13+ 8.15+ View code
Slack Preview - - - - View code
Teams Preview - - 8.13+ - View code
Zoom Preview - 8.11+ 8.13+ - View code
Tip

Because prerequisites and configuration details vary by data source, you’ll need to refer to the individual connector references for specific details.

Because connectors are self-managed on your own infrastructure, they run outside of your Elastic deployment.

You can run them from source or in a Docker container.

In order to set up, configure, and run a connector you’ll be moving between your third-party service, the Elastic UI, and your terminal. At a high-level, the workflow looks like this:

  1. Satisfy any data source prerequisites (e.g., create an OAuth application).
  2. Create a connector in the UI (or via the API).
  3. Deploy the connector service:
  4. Enter data source configuration details in the UI.

The first decision you need to make before deploying a connector is which third party service (data source) you want to sync to Elasticsearch. See the list of available connectors.

Note that each data source will have specific prerequisites you’ll need to meet to authorize the connector to access its data. For example, certain data sources may require you to create an OAuth application, or create a service account. You’ll need to check the individual connector documentation for these details.