Back to Elasticsearch

Content connectors

docs/reference/search-connectors/index.md

9.4.012.4 KB
Original Source

Content connectors

$$$es-connectors-native$$$

:::{note} This page is about Content connectors that synchronize third-party data into {{es}}. 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 {{es}}. Use connectors to create searchable, read-only replicas of your data in {{es}}.

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

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

Setup modes [setup-modes]

You can set up content connectors in two ways. The availability of each setup mode is indicated on the interface of your {{kib}} Content connectors page.

Self-managedElastic managed
InfrastructureYou deploy the connector serviceElastic hosts it for you
AvailabilityAny Elastic environment{{ecloud}} only ({{ech}}/Serverless), for {{product.observability}} and {{product.security}}
Can send data toAny {{es}} instanceDeployment or project the connector is deployed within only
CustomizationSupportedNot supported

Available connectors

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.
ConnectorStatusAdvanced sync rulesLocal binary extraction serviceIncremental syncsDocument level securitySource code
Azure BlobGA-8.11+8.13+-View code
BoxPreview--8.13+-View code
Confluence CloudGA8.9+8.11+8.13+8.10View code
Confluence Data CenterPreview8.13+8.13+8.13+8.14+View code
Confluence ServerGA8.9+8.11+8.13+8.14+View code
DropboxGA-8.11+8.13+8.12+View code
GitHubGA8.10+8.11+8.13+8.12+View code
GmailGA--8.13+8.10+View code
Google Cloud StorageGA-8.11+8.13+-View code
Google DriveGA-8.11+8.13+8.10+View code
GraphQLPreview----View code
Jira CloudGA8.9+8.11+8.13+8.10+View code
Jira Data CenterPreview8.13+8.13+8.13+8.13+*View code
Jira ServerGA8.9+8.11+8.13+-View code
Microsoft SQL ServerGA8.11+---View code
MongoDBGA8.8 native/ 8.12 self-managed---View code
MySQLGA8.8+---View code
Network driveGA8.10+8.14+8.13+8.11+View code
NotionGA8.14+---View code
OneDriveGA8.11+8.11+8.13+8.11+View code
OracleGA----View code
OutlookGA-8.11+8.13+8.14+View code
PostgreSQLGA8.11+---View code
RedisPreview----View code
Amazon S3GA8.12+8.11+--View code
SalesforceGA8.12+8.11+8.13+8.13+View code
ServiceNowGA8.10+8.11+8.13+8.13+View code
Sharepoint OnlineGA8.9+8.9+8.9+8.9+View code
Sharepoint ServerBeta-8.11+8.13+8.15+View code
SlackPreview----View code
TeamsPreview--8.13+-View code
ZoomPreview-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. :::

Overview

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.

Workflow

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.

Data source prerequisites

The first decision you need to make before deploying a connector is which third party service (data source) you want to sync to {{es}}. 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.