Search connectors
This page is about Search 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 a type of Elastic integration that syncs data from an original data source to Elasticsearch. Each connector extracts the original files, records, or objects; and transforms them into documents within Elasticsearch.
Connector clients are self-managed connectors that you run on your own infrastructure. These connectors are written in Python and the source code is available in the elastic/connectors repo.
As of Elastic 9.0, managed connectors on Elastic Cloud Hosted are no longer available. All connectors must be self-managed.
Connector clients are available for the following third-party data sources:
The following connectors are available as self-managed connectors:
- Azure Blob Storage
- Box
- Confluence
- Dropbox
- GitHub
- Gmail
- Google Cloud Storage
- Google Drive
- GraphQL
- Jira
- MicrosoftSQL
- MongoDB
- MySQL
- Network drive
- Notion
- OneDrive
- OpenText Documentum
- Oracle
- Outlook
- PostgreSQL
- Redis
- S3
- Salesforce
- ServiceNow
- SharePoint Online
- SharePoint Server
- Slack
- Teams
- Zoom
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:
- Satisfy any data source prerequisites (e.g., create an OAuth application).
- Create a connector in the UI (or via the API).
- Deploy the connector service:
- Option 1: Run with Docker (recommended)
- Option 2: Run from source
- 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.