Continuing the discussion from How to backup and restore .signals_* indices,
it seems the easiest way to use the ES snapshot API to backup and restore protected indices (searchguard signals indices, as well as the Search Guard security index) is to use the TLS admin certificate that you would also use for sgadmin.
Describe the issue:
searchguard.ssl.http.enabled is disabled, TLS is disabled on the REST layer. Only when TLS client authentication is enabled, REST clients can send a TLS certificate with the HTTP request to provide identity information to the security plugin.
My use-case: I use elasticsearch in k8s environment with istio mtls enabled. With that, as pod-to-pod mtls is handled by istio, and so tls on REST layer for searchguard has been disabled.
With this, I can connect to the REST api with user credentials on http (like http://localhost:9200 -u < uname>:< pwd>), but I cannot use certificate-based authentication.
Now, lets say, I want to periodically backup all data in ES (including these protected indices) using elasticsearch snapshots and restore from it in case of disaster recovery. In the current situation, I can only restore other indices while there would be data loss for these protected indices.
Is there a way to mitigate this issue? Can an admin user in internal_users.yml (having unlimited permissions like “sgs_all_access”) be used to restore .these indices instead of admin-certificates?
Any pointers would be appreciated.