Open r00tu53r opened 2 years ago
I think that thsi is not supported in Kibana/Fleet yet, see https://github.com/elastic/kibana/issues/134321
I am encountering the same issue working on https://github.com/elastic/security-ml/issues/83, commenting here for documentation. I am aware of and following
As a temporary workaround, I created the destination index manually before installing the package with a PUT
command.
The curious thing is that for one (out of 2) of the transforms in the package I'm developing, it does seem to be able to create the destination index:
@susan-shu-c Sorry I didn't think of this earlier, but I wonder if it's a permissions issue with creating the other index?
@szeitlin I'm curious if that's the case - I did re-name both indices to a pattern that elastic/kibana
service account has access to (.alerts*
pattern):
.alerts-security.host-risk-score
(destination for the 1st transform in this package, named "pivot transform").alerts-security.host-risk-score-latest
(destination for 2nd transform, named "latest transform")[Edit with new information]
That service account has kibana_system
role if I recall correctly
If I do not use a naming pattern that service account has access to, there is this following error when I install the package:
susan@computer host_risk_score % elastic-package install
Install the package
Error: can't install the package: can't install the package: could not install package; API status code = 500; response body = {"statusCode":500,"error":"Internal Server Error","message":"security_exception: [security_exception] Reason: action [indices:admin/delete] is unauthorized for service account [elastic/kibana] on indices [ml_host_risk_score_default], this action is granted by the index privileges [delete_index,manage,all]"}
A package with a transform does not create the required destination index. When installing the package kibana displays the following error -
Docker logs from the kibana instance -