2.7 KiB
Fleet Server
[!WARNING] This extension currently exists for preview purposes and should be considered EXPERIMENTAL. Expect regular changes to the default Fleet settings, both in the Elastic Agent and Kibana.
See Known Issues for a list of issues that need to be addressed before this extension can be considered functional.
Fleet provides central management capabilities for Elastic Agents via an API and web UI served by Kibana, with Elasticsearch acting as the communication layer. Fleet Server is the central component which allows connecting Elastic Agents to the Fleet.
Requirements
The Fleet Server exposes the TCP port 8220 for Agent to Server communications.
Usage
To include Fleet Server in the stack, run Docker Compose from the root of the repository with an additional command line
argument referencing the fleet-compose.yml file:
$ docker-compose -f docker-compose.yml -f extensions/fleet/fleet-compose.yml up
Configuring Fleet Server
Fleet Server — like any Elastic Agent — is configured via Agent Policies which can be either managed through the Fleet management UI in Kibana, or statically pre-configured inside the Kibana configuration file.
To ease the enrollment of Fleet Server in this extension, docker-elk comes with a pre-configured Agent Policy for Fleet
Server defined inside kibana/config/kibana.yml.
Please refer to the following documentation page for more details about configuring Fleet Server through the Fleet management UI: Fleet UI Settings.
Known Issues
- The Elastic Agent auto-enrolls using the
elasticsuper-user. With this approach, you do not need to generate a service token — either using the Fleet management UI or CLI utility — prior to starting this extension. However convenient that is, this approach does not follow security best practices, and we recommend generating a service token for Fleet Server instead.
See also
Screenshots
