IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Configure SSL/TLS for the Logstash output Fleet UI settings »

›

Centrally manage Elastic Agents in Fleet

edit

Centrally manage Elastic Agents in Fleet

edit

The Fleet app in Kibana supports both Elastic Agent infrastructure management and agent policy management. You can use Fleet to:

Manage Elastic Agent binaries and specify settings installed on the host that determine whether the Elastic Agent is enrolled in Fleet, what version of the agent is running, and which agent policy is used.
Manage agent policies that specify agent configuration settings, which integrations are running, whether agent monitoring is turned on, input settings, and so on.

Advanced users who don’t want to use Fleet for central management can use an external infrastructure management solution and install Elastic Agent in standalone mode instead.

Fleet currently requires a Kibana user with All privileges on Fleet and Integrations. Since many Integrations assets are shared across spaces, users need the Kibana privileges in all spaces.

To learn how to add Elastic Agents to Fleet, refer to Install Fleet-managed Elastic Agents.

To use Fleet go to Management > Fleet in Kibana. The following table describes the main management actions you can perform in Fleet:

Component	Management actions
Fleet UI settings	Configure global settings available to all Elastic Agents managed by Fleet, including Fleet Server hosts and output settings.
Elastic Agents	Enroll, unenroll, upgrade, add tags, and view Elastic Agent status and logs.
Policies	Create and edit agent policies and add integrations to them.
Fleet enrollment tokens	Create and revoke enrollment tokens.
Uninstall tokens	(Elastic Defend integration only) Access tokens to allow uninstalling Elastic Agent from endpoints with Agent tamper protection enabled.
Data streams	View data streams and navigate to dashboards to analyze your data.

« Configure SSL/TLS for the Logstash output Fleet UI settings »