This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
Fleet is currently only available to users with the superuser role. This role is necessary to create indices, install integration assets, and update Elastic Agent policies. In order to use Fleet, the Elastic Agents must have a direct network connection to Kibana and Elasticsearch. It is also possible to run the Elastic Agents in standalone mode in cases where a network connection is not available or not needed.
This feature has additional limitations at the current time:
- Support for a limited number of integrations (more coming soon)
- No output to Logstash, Kafka, or other remote clusters
- No proxy support for Fleet Server
- Requires internet access for Kibana to download integration packages from the Elastic Package Registry
- Elastic Agent requires internet access to perform binary upgrades from Fleet
- Limited support in the Fleet app for advanced Beats settings like multiline, processors, and so on
On Elastic Cloud, there’s a limit to the number of enrolled Elastic Agents that a single Kibana instance can handle:
Beta releases are not supported at a production level, but we encourage you to report issues in our discuss forum.