Are sg_config files tied to ES ?

Search Guard
1

Hello,

I’ve been experimenting for a bit with SearchGuard, really appreciate it.

Although, there’s one thing I still don’t get: are the sg_config/* files needed when running ES ? I mean, once the ES node is spun up, that I ran sgadmin from a remote machine, and thus the searchguard index is populated, does the ES node still need the sg_config/* files in its directory hierarchy to function properly ? Did it ever need them in its directory hierarchy ?

Thanks.

2

No, you don’t need to keep any sg_configurtion file(s) on any node. This is the point / advantage of using sgadmin and keeping the complete configuration in the Search Guard index: If you populate the SG index from a remote machine, your nodes never have to see any of the config files :slight_smile:

···

On Thursday, September 28, 2017 at 4:06:19 PM UTC+2, PL D wrote:

Hello,

I’ve been experimenting for a bit with SearchGuard, really appreciate it.

Although, there’s one thing I still don’t get: are the sg_config/* files needed when running ES ? I mean, once the ES node is spun up, that I ran sgadmin from a remote machine, and thus the searchguard index is populated, does the ES node still need the sg_config/* files in its directory hierarchy to function properly ? Did it ever need them in its directory hierarchy ?

Thanks.