Which connector to choose?
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
The first thing you want to consider before implementing your search is the backend you’re going to use for your data.
- (Recommended) Elasticsearch Connector is the best option for working with Elasticsearch. It’s a flexible option that gives you full control over the request and response flow — but it can also work out of the box with minimal configuration.
- Site Search if you are already using Swiftype, these are basically a single product with two names.
- Use Custom Connector Guide if none of the built-in connectors fit your use case.
The following connectors are no longer recommended for use in new projects:
These products are deprecated and not actively maintained. If you’re still using them, the connectors will technically work — but we suggest migrating to the Elasticsearch Connector.