Setup Elastic search heartbeat

We need two elements, User and Role, both can be set in the Security Panel of your Elastic Management Board:

A new role that defines all the required permissions. We will call it heartbeat_role. This requires the following Cluster privilieges:

• monitor // explain
• manage_ilm // explain

It also requires a Index Privilege:

• The privilege manage for the index heartbeat-* // explain

Here is an image depicting what needs to be set:

The user is even simpler; just create a sample user and assign the given roles:

• heartbeat_role // this one we created ourself
• kibana_admin
• ingest_admin

Here is an image depicting how this can look:

Afterwards you can configure your heartbeat on a server. On Linux the heartbeat.yml is saved in /etc/heartbeat/heartbeat.yml:

cloud.id: "MySites:ZXVyb3BlLXdlc3QzLmdjcC5jbG91ZC5lcy5pbyRhZDllOWExN2Y1MzM0ODdmYTgxOGQ1NDdlMDJlYTU5ZCQyYjljZTkwNzUyZGI0NTBlODc2MzRlNWVhYzhjOTM4Ng=="
cloud.auth: "elastic:<password>"