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.
For more detailed instructions see the Developer's Guide.
- Golang see .go-version file for the current supported version.
- Make
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- Theschema://host:portfor 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.
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.ymlFleet-server should run on port 8220 an can be checked with:
curl -XGET -v http://localhost:8220/api/statusPlease 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.