When installing elasticsearch with a RPM or DEB package, the configuration directory /etc/elasticsearch should be owned by user root and group elasticsearch with 750 permissions (root has full access, read/list access for users of elasticsearch group and nothing for others users)
When installing a plugin that contains configuration files like /etc/elasticsearch/awesome-plugin/, the plugin directory should be owned by user root and group elasticsearch with 750 permissions.
When installing a plugin that contains bin/ files like /usr/share/elasticsearch/bin/awesome-plugin/, the plugin directory and all its files should be owned by user root and group elasticsearch with 750 permissions (root has read/write/execute access, read/execute access for users of elasticsearch group and nothing for others users).
We also need to test how RPM/DEB packages handle permissions/ownership changes when upgrading a package.
When installing elasticsearch with a RPM or DEB package, the configuration directory
/etc/elasticsearchshould be owned by userrootand groupelasticsearchwith750permissions (roothas full access, read/list access for users ofelasticsearchgroup and nothing for others users)When installing a plugin that contains configuration files like
/etc/elasticsearch/awesome-plugin/, the plugin directory should be owned by userrootand groupelasticsearchwith750permissions.When installing a plugin that contains bin/ files like
/usr/share/elasticsearch/bin/awesome-plugin/, the plugin directory and all its files should be owned by userrootand groupelasticsearchwith750permissions (roothas read/write/execute access, read/execute access for users ofelasticsearchgroup and nothing for others users).We also need to test how RPM/DEB packages handle permissions/ownership changes when upgrading a package.