Skip to content

Commit 0a9fece

Browse files
author
Bruno Farache
authored
Add note about API keys limits
1 parent c7d2e6f commit 0a9fece

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

deploy-manage/api-keys/elastic-cloud-api-keys.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,13 @@ These keys provides access to the API that enables you to manage your deployment
3232

3333
By default, API keys expire after three months. You can set the expiration to a different preset value or to a specific date, up to one year. If you need the key to work indefinitely, you can also set its expiration to Never. In this case, the key won’t expire.
3434

35+
Each user is allowed to create up to 64 API keys.
36+
3537
::::{note}
3638
When an API key is nearing expiration, Elastic sends an email to the creator of the API key and each of the operational contacts. When you use an API key to authenticate, the API response header `X-Elastic-Api-Key-Expiration` indicates the key’s expiration date. You can log this value to detect API keys that are nearing expiration.
3739
::::
3840

39-
5. Click **Create API key**, copy the generated API key, and store it in a safe place. You can also download the key as a CSV file.
41+
6. Click **Create API key**, copy the generated API key, and store it in a safe place. You can also download the key as a CSV file.
4042

4143
The API key needs to be supplied in the `Authorization` header of a request, in the following format:
4244

0 commit comments

Comments
 (0)