IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Deployment models
editDeployment models
editThere are various models for setting up Elastic Agents to work with Elasticsearch. The recommended approach is to use Fleet, a web-based UI in Kibana, to centrally manage all of your Elastic Agents and their policies. Using Fleet requires having an instance of Fleet Server that acts as the interface between the Fleet UI and your Elastic Agents.
For an overview of Fleet Server, including details about how it communicates with Elasticsearch, how to ensure high availability, and more, refer to What is Fleet Server?.
The requirements for setting up Fleet Server differ, depending on your particular deployment model:
- Elastic Cloud serverless
- In a serverless environment, Fleet Server is offered as a service, it is configured and scaled automatically without the need for any user intervention.
- Elasticsearch Service
- If you’re running Elasticsearch and Kibana hosted on Elasticsearch Service, no extra setup is required unless you want to scale your deployment. Elasticsearch Service runs a hosted version of Integrations Server that includes Fleet Server. For details about this deployment model, refer to Deploy on Elastic Cloud.
- Elasticsearch Service with Fleet Server on-premise
- When you use a hosted Elasticsearch Service deployment you may still choose to run Fleet Server on-premise. For details about this deployment model and set up instructions, refer to Deploy Fleet Server on-premises and Elasticsearch on Cloud.
- Self-managed
- For self-managed deployments, you must install and host Fleet Server yourself. For details about this deployment model and set up instructions, refer to Deploy on-premises and self-managed.