Skip to content

The Fleet server allows managing a fleet of Elastic Agents.

License

Notifications You must be signed in to change notification settings

elastic/fleet-server

Folders and files

NameName
Last commit message
Last commit date
Jan 31, 2025
Feb 6, 2025
Feb 14, 2025
Feb 6, 2025
Dec 5, 2024
Feb 18, 2025
Jan 17, 2025
Apr 20, 2023
Feb 6, 2025
Feb 5, 2025
Feb 5, 2025
Feb 18, 2025
Jan 30, 2025
Oct 1, 2021
Aug 2, 2024
Feb 10, 2025
Feb 10, 2025
Feb 5, 2025
Jan 22, 2025
Oct 28, 2024
Jul 29, 2024
Sep 23, 2024
Jan 17, 2025
Nov 10, 2020
Jan 17, 2025
Feb 18, 2025
Oct 28, 2024
Jun 10, 2024
Feb 14, 2025
Feb 6, 2025
Jan 12, 2023
Feb 18, 2025
Feb 18, 2025
Jan 22, 2025
May 31, 2023
Feb 8, 2024

Repository files navigation

Fleet Server

Build status Coverage

Fleet server is the control server to manage a fleet of elastic-agents.

Please refer to the official documentation for more details. For production deployments the fleet-server is supervised and bootstrapped by an elastic-agent.

Quick Start

For more detailed instructions see the Developer's Guide.

Requirements

  • Golang see .go-version file for the current supported version.
  • Make

Elasticsearch + Kibana

An Elasticsearch instance is needed in order to run fleet-server. The following environment variables will need to be set with values from Elasticsearch/Kibana in order to run fleet-server:

  • ELASTICSEARCH_HOSTS - The schema://host:port for Elasticsearch.
  • ELASTICSEARCH_CA_TRUSTED_FINGERPRINT - The CA fingerprint for Elasticsearch.
  • ELASTICSEARCH_SERVICE_TOKEN - The fleet-server service token.
  • FLEET_SERVER_POLICY_ID - The fleet policy with the fleet-server integration.

For instructions/options on how to run the Elastic stack please refer to the Developer's Guide.

Build and run

To build the fleet-server binary to run locally use:

make local # Use SNAPSHOT=true if targetting a SNAPSHOT build.

In order to run the fleet-server instance run:

./bin/fleet-server -c fleet-server.yml

Fleet-server should run on port 8220 an can be checked with:

curl -XGET -v http://localhost:8220/api/status

Please note that when running a stand-alone fleet-server instance, it will not appear in Kibana's agents view and another (agent-enrolled) instance may be required in order to the the UI to function as expected. Please refer to the Developer's Guide for more details.