I have a ELK server into a redhat OS, with kibana version 4.4.1.
In order to have access from kibana to indexes I have made this role:
config_user:
cluster: monitor
indices:
'*':
privileges: all
and this works, because it's similar with power_user.
But What I need is to have access in kibana only in read mode ( to be able to use some saved queries, views and dashboards) and for that I have change the script like that:
I'm not sure Kibana will run correctly if you don't give the user write access to the .kibana index, but I've never actually tried it, so it might be fine until you go to save something, which sounds like what you want anyway. Still there are some writes that Kibana does behind the scenes even without saving items directly, so you could still run in to problems.
The suggest Kibana user roles changed in 2.3, but you can look at the recommendation in 2.2 to get an idea of what you'll probably need access to in order for Kibana to work.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.