How to give read only privileges in the Index management module?

[AClerk]

Hello,
How can I give read-only permissions to the "Index Management" module?
So users can search for indices, but not delete, freeze, flush, etc.

The use case is, that I want to give users permission to create index patterns. But in the index patterns module, not all indices are exposed. I believe it is only first 100 indices?!

Thanks

[Marius_Dragomir]

For now this isn't possible straightforward. Once this PR https://github.com/elastic/kibana/pull/67791 gets merged, you will be able to configure it more. For now, the workaround would be to set custom cluster privileges for the roles of the users, from this list:
https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html

At first glance I'm thinking of giving them only: read, view_index_metadata, monitor but not manage or maintenance.
Look over the list and it's description to see if they give them a permission that you don't want them to have.

[Marius_Dragomir]

FYI: i created an enhancement request for this exact use case. You can find it and track it here: https://github.com/elastic/kibana/issues/77347

[AClerk]

@Marius_Dragomir
Thanks for the advice and reference.
The article says

Read-only access to actions (count, explain, get, mget, get indexed scripts, more like this, multi percolate/search/termvector, percolate, scroll, clear_scroll, search, suggest, tv).

I understood it is via DEV tools?
Will it be available also in Kibana UI?

Cheers!

[AClerk]

@Marius_Dragomir

FYI: i created an enhancement request for this exact use case. You can find it and track it here: Read-only mode for Index management · Issue #77347 · elastic/kibana · GitHub

That's great.
Thanks!

[Marius_Dragomir]

@AClerk

Will it be available also in Kibana UI?

Yes, this will apply to all requests made from within Kibana by the user that's logged in. For now they will still be able to see the DELETE, FREEZE and so on options in the UI for index management, but the action will throw an error and won't allow them to complete the action.
This user experience will be improved once that enhancement is solved.

[AClerk]

Thanks for clarifying.