You work with users and roles in the Kibana Management app, accessible from the Security page in the Elasticsearch Service Console or directly from the Kibana side navigation.
The Users tab shows the users that have been configured on your deployment. You can add or delete users here and assign roles that give users specific privileges. A user can be assigned multiple roles.
If you upgraded your deployment to Elasticsearch 5.0 or later from a version before 5.0, the users defined in Shield were also migrated to X-Pack and show up in this list. This includes the default
readonly users, which you can work with like any other user in the Kibana Management app.
The Roles tab shows the roles that exist on your deployment. Roles let you customize exactly which actions a user with the role can do, both on a deployment and an index level. Several users can have the same role. You can also add or delete users.
Two users are always created with new version 5.x deployments:
A superuser that is somewhat similar in scope to the default
adminuser in Shield configurations in Elasticsearch Service before version 5.0. The
elasticuser is not shown in the Kibana Management app and you cannot modify this user, other than to reset the password.
A user for handling incoming requests where no authentication token can be extracted. By default, this user has no privileges. In Kibana, you must create a role called
anonymous, then add one or more permissions to control the access rights of the anonymous user. You can also do this with the Elasticsearch roles API. Note that
anonymousonly works for Elasticsearch, not for Kibana. To learn more, see Enabling Anonymous Access.
To learn more about users and roles in X-Pack, see Setting Up User Authentication.
To send Beats data to a secured cluster in Elasticsearch Service, you should use a user that has the right privileges. When we showed you a Beats example that configured Filebeat on a server to send data to Elasticsearch Service, the user
filebeat_internal was used, with role privileges based on the recommendations in Beats and Security.
To create a similar user and role in the Management app in Kibana:
- Log into the Elasticsearch Service Console and select to your deployment.
On the Deployments page, select your deployment.
Narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
- From your deployment menu, go to Kibana and open the Kibana endpoint.
- From Kibana, go to the Management app.
Select the Roles tab, click New Role and give the role the
Specify the right privileges. Under Cluster Privileges, select
manage_index_templates. Under Indices Privileges, specify
create_indexprivileges for the
filebeat-*indices that the Beat creates.
- Click Save.
Select the Users tab, click New User and give the user the
filebeat-writerrole to the user under Roles.
- Enter a password and confirm the password. Make a note of the password and keep it in a secure location.
- Click Save.
After the user and role are saved, you can use the new user to authenticate when sending data from Filebeat to your cluster.