API keys enable you to create secondary credentials so that you can send requests on behalf of a user. Secondary credentials have the same or lower access rights.
For example, if you extract data from an Elasticsearch cluster on a daily basis, you might create an API key tied to your credentials, configure it with minimum access, and then put the API credentials into a cron job. Or, you might create API keys to automate ingestion of new data from remote sources, without a live user interaction.
To manage API keys, open the main menu, then click Stack Management > API Keys.
You must have the
manage_api_key, or the
cluster privileges to use API keys in Kibana. To manage roles, open the main menu, then click
Stack Management > Roles, or use the Kibana Role Management API.
Create an API keyedit
To create an API key, open the main menu, then click Stack Management > API Keys > Create API key.
Once created, you can copy the API key (Base64 encoded) and use it to send requests to Elasticsearch on your behalf. For example:
curl --location --request GET 'http://localhost:5601/api/security/role' \ --header 'Content-Type: application/json;charset=UTF-8' \ --header 'kbn-xsrf: true' \ --header 'Authorization: ApiKey aVZlLUMzSUJuYndxdDJvN0k1bU46aGxlYUpNS2lTa2FKeVZua1FnY1VEdw==' \
API keys are intended for programmatic access to Kibana and Elasticsearch. Do not use API keys to authenticate access via a web browser.
View and delete API keysedit
The API Keys feature in Kibana lists your API keys, including the name, date created, and status. If an API key expires, its status changes from
If you have
you can view the API keys of all users, and see which API key was
created by which user in which realm.
If you have only the
manage_own_api_key permission, you see only a list of your own keys.
You can delete API keys individually or in bulk.
You cannot modify an API key. If you need additional privileges, you must create a new key with the desired configuration and invalidate the old key.