# Confused about filebeat privileges / ILM

**URL:** <https://discuss.elastic.co/t/confused-about-filebeat-privileges-ilm/276112>\
**Category:** Beats\
**Tags:** ilm-index-lifecycle-management, filebeat\
**Created:** [June 16, 2021, 9:47am UTC](https://discuss.elastic.co/t/confused-about-filebeat-privileges-ilm/276112 "2021-06-16T09:47:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/balu/32/37569_2.png) [@Balu](https://discuss.elastic.co/u/Balu)\
**Post date:** [June 16, 2021, 9:47am UTC](https://discuss.elastic.co/t/confused-about-filebeat-privileges-ilm/276112/1 "2021-06-16T09:47:07Z")

</div>

Hey folks,

I am just starting to work with the ELK stack and I am quite often confused by the documentation.

For example while setting up filebeat, [Grant privileges and roles needed for publishing](https://www.elastic.co/guide/en/beats/filebeat/current/privileges-to-publish-events.html#privileges-to-publish-events) tells me

> When using ILM, turn off the ILM setup check in the Filebeat config file before running Filebeat to publish events: `setup.ilm.check_exists: false`

1. Am I using ILM? It's the first time I am reading this acronym after setting up a basic ES cluster...
2. Why do I have to turn off the setup check if I use it? This seems to oppose each other?

It then tells me to add a `read_ilm` privilege which is `Not needed when setup.ilm.check_exists is false.`.

So it first tells me to set it to false and then tells me to add the privilege unless I have set it to false?

This is quite confusing.

---

<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:** [July 14, 2021, 11:47am UTC](https://discuss.elastic.co/t/confused-about-filebeat-privileges-ilm/276112/2 "2021-07-14T11:47:13Z")

</div>

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