Our users do not want to understand and often ask general queries like: *:* or *logs*.
Such requests touch all of our logs and cause our cluster to crash.
Is there a chance to block the creation or search of such index templates. But at the same time, searching for narrower patterns should work, for example *logs-aaa*
It looks like we could implement the indices_re or introduce regex pattern into the existing rule. But keep in mind that the indices rule for RO request doesn’t block, but filter the indices only. Here we want to block some requests according to some rules on indices names.
Thanks for the advice @coutoPL . I’ll test with a redirect.
In general, it’s enough for me to prohibit the creation of patterns in kibana. Because dashboards that use this pattern cause problems.
Initially, I thought that this would be a list of patterns that cannot be created.
Can this be done with a kibana-only setting?
Sorry for not writing this earlier.
But what happens if you put an indices rule in a type: forbid block?
ACL is evaluated block by block. When a block is matched, the evaluation of further blocks is stopped (this is not obviously true for the login request, where all blocks are evaluated in parallel and results are collected from the matched blocks … but let’s not bother with this now).
Then when we have a result of ACL evaluation, which is a matched block or mismatch result (no block matched) we take into consideration the type:
if type: allow and there is a matched block, then allow processing; otherwise - forbid
if type: forbid and there is a matched block, then forbid processing; otherwise - allow
As you can see, the indices rule semantics doesn’t matter much (I recall - the semantics is “filtering”, not “blocking” … so it’s almost always matched (for RO requests)).
About the introduction of the regex in indices rule. Do you see it can introduce particular complications?
I think it would be a problem with it. But it requires deeper analysis. Will back to you with it.