# Fleet Server Config via Kibana yaml file

**URL:** <https://discuss.elastic.co/t/fleet-server-config-via-kibana-yaml-file/312821>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [August 24, 2022, 2:50pm UTC](https://discuss.elastic.co/t/fleet-server-config-via-kibana-yaml-file/312821 "2022-08-24T14:50:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DefensiveDepth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/defensivedepth/32/110034_2.png) [@DefensiveDepth](https://discuss.elastic.co/u/DefensiveDepth)\
**Post date:** [August 24, 2022, 2:50pm UTC](https://discuss.elastic.co/t/fleet-server-config-via-kibana-yaml-file/312821/1 "2022-08-24T14:50:41Z")

</div>

According to the [docs](https://www.elastic.co/guide/en/kibana/8.3/fleet-settings-kb.html#_preconfiguration_settings_for_advanced_use_cases), we can pre-define Fleet Server integrations & policies via the Kibana config file: `Use these settings to pre-define integrations and agent policies that you want Fleet to load up by default.`

Based on my testing, it appears that when Kibana starts, it will create the policies etc defined in the Kibana config, but it will not update the policies if the config changes in the Kibana yaml.

In other words, it initially creates the config and that's it - doesn't modify or re-create it in subsequent restarts.

Is this accurate?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 21, 2022, 2:50pm UTC](https://discuss.elastic.co/t/fleet-server-config-via-kibana-yaml-file/312821/2 "2022-09-21T14:50:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.