Security - Configuration
Open Distro for Elasticsearch includes the Security plugin for authentication and access control. The plugin provides numerous features to help you secure your cluster.
|Node-to-node encryption||Encrypts traffic between nodes in the Elasticsearch cluster.|
|HTTP basic authentication||A simple authentication method that includes a user name and password as part of the HTTP request.|
|Support for Active Directory, LDAP, Kerberos, SAML, and OpenID Connect||Use existing, industry-standard infrastructure to authenticate users, or create new users in the internal user database.|
|Role-based access control||Roles define the actions that users can perform: the data they can read, the cluster settings they can modify, the indices to which they can write, and so on. Roles are reusable across users, and users can have multiple roles.|
|Index-level, document-level, and field-level security||Restrict access to entire indices, certain documents within an index, or certain fields within documents.|
|Audit logging||These logs let you track access to your Elasticsearch cluster and are useful for compliance purposes or after a security breach.|
|Cross-cluster search||Use a coordinating cluster to submit search requests to remote clusters.|
|Kibana multi-tenancy||Create shared (or private) spaces for index patterns, visualizations, and dashboards.|
The plugin includes demo certificates so that you can get up and running quickly, but before using Open Distro for Elasticsearch in a production environment, you should configure it manually:
- Replace the demo certificates
elasticsearch.ymlto use your certificates
config.ymlto use your authentication backend (if you don’t plan to use the internal user database)
- Modify the configuration YAML files
- Apply changes using securityadmin.sh
- Start Elasticsearch.
- Add users, roles, role mappings, and tenants
If you don’t want to use the plugin, see Disable security.