- Enterprise Search Guide: other versions:
- Getting started
- Prerequisites
- Ingestion
- Web crawler
- Connectors
- Native connectors
- Connector clients and frameworks
- Workplace Search connectors
- Usage
- Known issues
- Troubleshooting
- Logs
- Security
- Sync rules
- Content extraction
- Reference: Azure Blob Storage
- Reference: Confluence
- Reference: Google Cloud Storage
- Reference: Jira
- Reference: Microsoft SQL
- Reference: MongoDB
- Reference: MySQL
- Reference: Network drive
- Reference: Oracle
- Reference: PostgreSQL
- Reference: S3
- Reference: SharePoint
- 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.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
Elastic connectors
editElastic connectors
editA connector is a type of Elastic integration that syncs data from an original data source to an Elastic deployment. Each connector extracts the original files, records, or objects; and transforms them into documents within Elasticsearch.
Several connector workflows are available. Get started by choosing a workflow and a data source.
Native connectors
editNative connectors are 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. See Native connectors.
The following connectors are available as native connectors:
Connector clients and frameworks
editConnector clients are open-code connector implementations you can deploy to your own infrastructure. Connector clients allow you to customize connectors to satisfy your needs, use new connectors before they are available natively within Elastic Cloud, and build your own connectors for custom data sources.
Connector clients sync data sources directly to Elasticsearch indices. Create these indices using the Connector workflow within Kibana. See Connector clients and frameworks.
The following connectors are available as connector clients:
- Azure Blob Storage (Python)
- Confluence (Python)
- Google Cloud Storage (Python)
- Jira (Python)
- MongoDB (Python)
- MicrosoftSQL (Python)
- MySQL (Python)
- Network drive (Python)
- Oracle (Python)
- PostgreSQL (Python)
- S3 (Python)
- SharePoint (Python)
Connector clients are built using connector frameworks. Use these frameworks to deploy existing connector clients, or create your own clients to sync from custom data sources.
The following connector frameworks are available:
- Python (branch 8.8, compatible with Elastic 8.8)
Workplace Search connectors
editWorkplace Search connectors are available directly within your Elastic deployment, through the Workplace Search product. No additional infrastructure is required. Workplace Search connector packages are open-code connector implementations you can deploy to your own infrastructure.
Workplace Search connectors (and connector packages) sync data sources to Workplace Search content sources. Create these content sources using the Workplace Search product within Kibana. See Workplace Search connectors.
The following Workplace Search connectors are available:
- Box
- Confluence Cloud
- Confluence Cloud (Ruby connector package)
- Confluence Server
- Dropbox
- GitHub
- Gmail
- Google Drive
- Jira Cloud
- Jira Server
- Network drives (Python connector package)
- OneDrive
- Outlook (Python connector package)
- Salesforce
- ServiceNow
- SharePoint Online
- SharePoint Online (Ruby connector package)
- SharePoint Server (Python connector package)
- Slack
- Teams (Python connector package)
- Zendesk
- Zoom (Python connector package)