Restricting Security Index deletion and minimal configuration requirement for user other than super user for health management with XPACK 6.8.1


We are facing issues with security implementation of XPACK-elastic 6.8.1.
1- Security index got deleted twice automatically recently due to super user password change but earlier reason was unknown. I have certain queries as mentioned below-
a- Is there any relation between super user password change and security index?
b- Is there any way that we can recover the deleted security index and other indexes if any?
c- Is there any way that we can restrict the security index deletion after the initial setup/installation of Xpack.
2- elastic super user name and password is visible in the elastic json of DCOS is there any way that we can encrypt it or use a different user all together to mitigate the security risk.


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.