- Enterprise Search Guide: other versions:
- Getting started
- Prerequisites
- Ingestion
- Web crawler
- Connectors
- Native connectors
- Connector clients
- Elastic connector framework
- Workplace Search connectors
- Using connectors
- Known issues
- Troubleshooting
- Document level security
- Logs
- Security
- Content syncs
- Sync rules
- Content extraction
- Reference: Azure Blob Storage
- Reference: Confluence
- Reference: Dropbox
- Reference: GitHub
- Reference: Gmail
- Reference: Google Cloud Storage
- Reference: Google Drive
- Reference: Jira
- Reference: Microsoft SQL
- Reference: MongoDB
- Reference: MySQL
- Reference: Network drive
- Reference: OneDrive
- Reference: Oracle
- Reference: PostgreSQL
- Reference: S3
- Reference: Salesforce
- Reference: ServiceNow
- Reference: SharePoint Online
- Reference: SharePoint Server
- Reference: Slack
- Ingestion APIs
- Ingest pipelines
- Document enrichment with ML
- ELSER text expansion
- Indices, engines, content sources
- Programming language clients
- Behavioral analytics
- Search UI
- App Search and Workplace Search
- Search Applications
- Enterprise Search server
- Run using Docker images
- Run using downloads (packages)
- Enterprise Search server known issues
- Troubleshooting
- Troubleshooting setup
- Monitoring
- Read-only mode
- Management APIs
- Monitoring APIs
- Read-only mode API
- Storage API
- Configuration
- Configuring encryption keys
- Configuring a mail service
- Configuring SSL/TLS
- Upgrading and migrating
- Upgrading self-managed deployments
- Upgrading from Enterprise Search 7.x
- Upgrading from Enterprise Search 7.11 and earlier
- Migrating from App Search on Elastic Cloud
- Migrating from App Search on Swiftype.com
- Migrating from self-managed App Search
- Logs and logging
- Known issues
- Troubleshooting
- Help, support, and feedback
- Release notes
- 8.10.4 release notes
- 8.10.3 release notes
- 8.10.2 release notes
- 8.10.1 release notes
- 8.10.0 release notes
- 8.9.2 release notes
- 8.9.1 release notes
- 8.9.0 release notes
- 8.8.2 release notes
- 8.8.1 release notes
- 8.8.0 release notes
- 8.7.1 release notes
- 8.7.0 release notes
- 8.6.2 release notes
- 8.6.1 release notes
- 8.6.0 release notes
- 8.5.3 release notes
- 8.5.2 release notes
- 8.5.1 release notes
- 8.5.0 release notes
- 8.4.3 release notes
- 8.4.2 release notes
- 8.4.1 release notes
- 8.4.0 release notes
- 8.3.3 release notes
- 8.3.2 release notes
- 8.3.1 release notes
- 8.3.0 release notes
- 8.2.3 release notes
- 8.2.2 release notes
- 8.2.1 release notes
- 8.2.0 release notes
- 8.1.3 release notes
- 8.1.2 release notes
- 8.1.1 release notes
- 8.1.0 release notes
- 8.0.1 release notes
- 8.0.0 release notes
- 8.0.0-rc2 release notes
- 8.0.0-rc1 release notes
- 8.0.0-beta1 release notes
- 8.0.0-alpha2 release notes
- 8.0.0-alpha1 release notes
Native connectors
editNative connectors
editNative connectors are Elastic connectors available directly within your Elastic Cloud deployment. No additional infrastructure is required.
Native connectors sync data sources directly to Elasticsearch indices. Create these indices using the Connector workflow within Kibana.
The following connectors are available as native connectors. See each connector reference for additional information specific to each connector.
Availability and prerequisites
editNative connectors were introduced in Elastic version 8.5.0.
Your Elastic cloud deployment must include the following Elastic services:
- Elasticsearch
- Kibana
- Enterprise Search
Refer to Native Integrations on the Elastic subscriptions page, in the Elastic Search section for native connector licensing requirements.
Usage
editFollow the Connector workflow in Kibana to select the Connector ingestion method. Choose a data source, create an Elasticsearch index, and configure a native connector to manage the index.

Select a connector
editChoose the data source to sync from the available options and select Continue.
Create index
editCreate a new index to be managed by the connector:
-
Name your index and optionally change the language analyzer to match the human language of your data source.
(The index name will be automatically prefixed with
search-
.) - Select Create index.
The index is created and ready to configure.
This operation requires access to Kibana and the write
indices privilege for the .elastic-connectors
index.
Configure connector
editCreate a new index to be managed by the connector.
Continue from above, or navigate to the following location within Kibana:
Search > Content > Elasticsearch indices
Choose the index to configure, and then choose the Configuration tab.
Configure the connector:
- Edit the name and description for the connector. Your team can use this information to differentiate this index from other connector indices. (These fields describe the connector and are independent of the Elasticsearch index name.)
- Save your changes.
- Edit the data source configuration. The fields here vary by connector. Refer to the documentation for each connector for details (see list of native connectors, above). See Security for security considerations.
- Save your changes.
Optionally choose Edit sync schedule to begin managing the connector.
This operation requires access to Kibana and the write
indices privilege for the .elastic-connectors
index.
Manage connector
editTo manage documents, syncs, sync rules, ingest pipelines, and other connector features, see Using connectors.
These processes are identical for native connectors and connector clients.
End-to-end example
editThe following example demonstrates how to use a native connector: MongoDB connector tutorial.
Convert a native connector
editYou can convert a native connector to a self-managed connector client to be run on your own infrastructure. You’ll find instructions in the UI on the connector index’s overview page.
Converting a native connector to a self-managed connector client is an irreversible operation!
On this page