# Role settings for logging user (Beats)

**URL:** <https://discuss.elastic.co/t/role-settings-for-logging-user-beats/71083>\
**Category:** Beats\
**Created:** [January 10, 2017, 12:39pm UTC](https://discuss.elastic.co/t/role-settings-for-logging-user-beats/71083 "2017-01-10T12:39:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cylindric](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cylindric/32/5660_2.png) [@Cylindric](https://discuss.elastic.co/u/Cylindric)\
**Post date:** [January 10, 2017, 12:39pm UTC](https://discuss.elastic.co/t/role-settings-for-logging-user-beats/71083/1 "2017-01-10T12:39:34Z")

</div>

I'm trying to configure our new cloud cluster (1e7502) and I would like to create a user that only has access to create indices and log data to them. Basically, for my FileBeat/MetricBeat/anyBeat agents.

I created a new role "DataLoggers", with no cluster privileges, no "run as" privileges, and one index privilege of "\*" -\> "all".

That user gets "403 Forbidden" errors when trying to log data.

What are the required privs for this?

 ![](https://us1.discourse-cdn.com/elastic/original/2X/8/8a30a313aa40a729b0734413d46f3231261502a5.png)

---

<div class="post-metadata">

**Author:** ![jakommo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jakommo/32/6716_2.png) [@jakommo](https://discuss.elastic.co/u/jakommo)\
**Post date:** [January 10, 2017, 5:36pm UTC](https://discuss.elastic.co/t/role-settings-for-logging-user-beats/71083/2 "2017-01-10T17:36:51Z")

</div>

Hi @Cylindric,

first off, allowing `index privilege of "*" -> "all"` does not sound secure. This user will have [all index privileges](https://www.elastic.co/guide/en/x-pack/5.1/security-privileges.html#privileges-list-indices) on all your indices.  
Assuming that you did this for testing only but still.  
If this user is only used for indexing, you should be fine with `write,create and delete` (not sure if delete is required in your use case), then assign this only to index patterns the beats are using.

The 403 comes from the missing [Cluster privileges](https://www.elastic.co/guide/en/x-pack/5.1/security-privileges.html#privileges-list-cluster), I tested with a simple filebeat config and you need at least `monitor and manage_index_templates`.

I think the monitor is needed to gets stats about the cluster itself (e.g. if it's healthy) and manage\_index\_templates is needed to check if there is an template or to put the template if not.

Hope that helps.

Note: I moved this to the Beats section as it seems more related to Beats than Elastic Cloud.

---

<div class="post-metadata">

**Author:** ![Cylindric](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cylindric/32/5660_2.png) [@Cylindric](https://discuss.elastic.co/u/Cylindric)\
**Post date:** [January 11, 2017, 9:16am UTC](https://discuss.elastic.co/t/role-settings-for-logging-user-beats/71083/3 "2017-01-11T09:16:40Z")

</div>

It's not a Beats problem, it's any app I use to try and create records in ES. It's entirely an ES/Shield question.

I'll try with those cluster privileges, that makes sense.

Thanks.

---

<div class="post-metadata">

**Author:** ![Cylindric](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cylindric/32/5660_2.png) [@Cylindric](https://discuss.elastic.co/u/Cylindric)\
**Post date:** [January 11, 2017, 9:46am UTC](https://discuss.elastic.co/t/role-settings-for-logging-user-beats/71083/4 "2017-01-11T09:46:37Z")

</div>

Yep, adding the "monitor" cluster privilege fixed it - thank you!

---

<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:** [January 14, 2017, 9:46am UTC](https://discuss.elastic.co/t/role-settings-for-logging-user-beats/71083/5 "2017-01-14T09:46:40Z")

</div>

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