Fleet UI settingsedit

The settings described here are configurable through the Fleet UI. Refer to Fleet settings in Kibana for a list of settings that you can configure in the kibana.yml configuration file.

Configure Fleet settings to apply global settings to all Elastic Agents enrolled in Fleet:

  1. In Kibana, open the main menu, then click Management > Fleet.
  2. Click Fleet settings

    Fleet Server hosts

    The URLs your Elastic Agents will use to connect to a Fleet Server. This setting is required. On self-managed clusters, you must specify one or more URLs.

    Not sure if Fleet Server is running? Refer to Add a Fleet Server.

    On Elastic Cloud, this field is populated automatically. If you are using Azure Private Link, GCP Private Service Connect, or AWS PrivateLink and enrolling the Elastic Agent with a private link URL, ensure that this setting is configured. Otherwise, Elastic Agent will reset to use a default address instead of the private link URL.

    If a URL is specified without a port, Kibana sets the port to 80 (http) or 443 (https).

    By default, Fleet Server is typically exposed on the following ports:

    Default Fleet Server port for self-managed clusters
    443 or 9243
    Default Fleet Server port for Elastic Cloud. Look at Fleet settings to see the actual port that’s used.

    The exposed ports must be open for ingress and egress in the firewall and networking rules on the host to allow Elastic Agents to communicate with Fleet Server.

    Specify multiple URLs to scale out your deployment and provide automatic failover.

    If multiple URLs exist, Fleet shows the first provided URL for enrollment purposes. Enrolled Elastic Agents will connect to the URLs in round robin order until they connect successfully.

    When a Fleet Server is added or removed from the list, all agent policies are updated automatically.


    • https://abae718c1276457893b1096929e0f557.fleet.eu-west-1.aws.qa.cld.elstc.co:443
    • https://[2001:db8::1]:8220

    Elasticsearch hosts

    The Elasticsearch URLs where Elastic Agents will send data. By default, Elasticsearch is exposed on the following ports:

    Default Elasticsearch port for self-managed clusters
    Default Elasticsearch port for Elastic Cloud


    • https://1d7a52f5eb344de18ea04411fe09e564.fleet.eu-west-1.aws.qa.cld.elstc.co:443
    • https://[2001:db8::1]:9200

    Elasticsearch output configuration (YAML)

    YAML settings that will be added to the Elasticsearch output section of each policy. This setting allows you to specify global output settings for all Elastic Agents enrolled in Fleet. Make sure you specify valid YAML. The UI does not currently provide validation.

  3. Save and apply the settings.