NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.
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.
When you use central management, configurations are stored centrally in Elasticsearch. To prevent an attacker from leveraging the configurations to attack your infrastructure, you must secure Elasticsearch and Kibana before using central management.
Beats central management provides a way to define and manage configurations in a central location in Kibana and quickly deploy configuration changes to all Beats running across your enterprise.
To learn more, see How central management works.
To use central management, enroll your Beats, then use the Central Management UI in Kibana to create and apply the configurations.
This feature requires an Elastic license that includes Beats central management.
Don’t have a license? You can start a 30-day trial. At the end of the trial period, you can purchase a subscription to keep using central management. For more information, see https://www.elastic.co/subscriptions and License Management.