# Minimum Permissions for Heartbeat

**URL:** <https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [July 18, 2019, 4:25pm UTC](https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246 "2019-07-18T16:25:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tadgh](https://avatars.discourse-cdn.com/v4/letter/t/9f8e36/32.png) [@tadgh](https://discuss.elastic.co/u/tadgh)\
**Post date:** [July 18, 2019, 4:25pm UTC](https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246/1 "2019-07-18T16:25:45Z")

</div>

Hey there

What are the minimum permissions to get heartbeat up and running? I don't really want to provide superuser credentials to heartbeat, so I'd like to know what the very minimum I can get away with is, including setup of dashboards.

Cheers,

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [July 18, 2019, 5:54pm UTC](https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246/2 "2019-07-18T17:54:00Z")

</div>

If you don't need ICMP then it doesn't need to be root. It just needs to be able to write its logs out and speak to any endpoints + elasticsearch with TCP.

---

<div class="post-metadata">

**Author:** ![tadgh](https://avatars.discourse-cdn.com/v4/letter/t/9f8e36/32.png) [@tadgh](https://discuss.elastic.co/u/tadgh)\
**Post date:** [July 18, 2019, 8:50pm UTC](https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246/3 "2019-07-18T20:50:33Z")

</div>

Sorry I should have clarified

I mean which elasticsearch permissions does the user need to successfully push up the dashboards and index its heartbeat events into elastic?. In the heartbeat.yml config's output.elasticsearch section, i need a username and a password. I'm wondering what the minumum elasticearch permissions are that i can assign to this user for doing everything heartbeat needs to do

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [July 22, 2019, 1:33pm UTC](https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246/4 "2019-07-22T13:33:16Z")

</div>

Ah, I think the docs on [granting access to secured resources](https://www.elastic.co/guide/en/beats/heartbeat/current/feature-roles.html) are what you're looking for. Let me know if that doesn't fit the bill.

---

<div class="post-metadata">

**Author:** ![tadgh](https://avatars.discourse-cdn.com/v4/letter/t/9f8e36/32.png) [@tadgh](https://discuss.elastic.co/u/tadgh)\
**Post date:** [July 22, 2019, 4:48pm UTC](https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246/5 "2019-07-22T16:48:29Z")

</div>

Thanks, that was exactly what I was looking for.

---

<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:** [August 19, 2019, 4:48pm UTC](https://discuss.elastic.co/t/minimum-permissions-for-heartbeat/191246/6 "2019-08-19T16:48:34Z")

</div>

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