Log in to Kibana with the user ID that has
roles (for example,
These roles enable the user to see the system metrics in Kibana (for example, on the Discover page or in the Metricbeat system overview dashboard).
Congratulations! You’ve successfully set up authentication and authorization by using the native realm. You learned how to create user IDs and roles that prevent unauthorized access to the Elastic Stack.
Later, when you’re ready to increase the number of nodes in your cluster, you’ll want to encrypt communications across the Elastic Stack. To learn how, read Encrypting communications.
For more detailed information about securing the Elastic Stack, see:
- Configuring security in Elasticsearch. Encrypt inter-node communications, set passwords for the built-in users, and manage your users and roles.
- Configuring security in Kibana. Set the authentication credentials in Kibana and encrypt communications between the browser and the Kibana server.
- Configuring security in Logstash. Set the authentication credentials for Logstash and encrypt communications between Logstash and Elasticsearch.
- Configuring security in the Beats. Configure authentication credentials and encrypt connections to Elasticsearch. For example, see Configure Filebeat to use security features.
- Configuring Elasticsearch for Apache Hadoop to use secured transport.
Intro to Kibana
ELK for Logs & Metrics