Tools: How to Update an Elasticsearch/Kibana License Using Kibana Dev Tools

Tools: How to Update an Elasticsearch/Kibana License Using Kibana Dev Tools

Overview

Step 1: Log in to Kibana

Step 2: Select the Space (if applicable)

Step 3: Open Dev Tools

Step 4: Check Current License

Important Note About License Format

Step 5: Update the License

Step 6: Verify the Update

Key Notes

Summary Licensing in the Elastic Stack (Elasticsearch + Kibana) controls access to advanced features such as security, alerting, machine learning, and enterprise capabilities. Licenses have expiration dates, and once expired, certain features may be limited or disabled. Updating your license ensures: One important detail: licenses are applied at the cluster level, not per space or namespace.

This means updating the license once applies it globally across all spaces/namespaces in Kibana. If your Kibana instance uses multiple spaces: Important:Even though you select a specific space, the license update will apply to the entire cluster — all spaces will inherit the updated license. Run the following request to view the current license: Sometimes the license you receive (for example from Elastic or a vendor) comes as a single-line JSON string. Example (hard to read / error-prone): Before pasting it into Kibana Dev Tools, you should: This helps avoid syntax errors when running the request in Dev Tools. Run the following request: Expected result:You should receive an acknowledgment response confirming the license update. Updating a license via Dev Tools in Kibana is a quick and reliable method: Remember:

One update applies to all namespaces/spaces in the cluster. Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to ? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse

Code Block

Copy

GET _license GET _license GET _license {"license":{"uid":"xxx","type":"enterprise","issue_date_in_millis":1700000000000,"expiry_date_in_millis":1800000000000,"signature":"ABC..."}} {"license":{"uid":"xxx","type":"enterprise","issue_date_in_millis":1700000000000,"expiry_date_in_millis":1800000000000,"signature":"ABC..."}} {"license":{"uid":"xxx","type":"enterprise","issue_date_in_millis":1700000000000,"expiry_date_in_millis":1800000000000,"signature":"ABC..."}} { "license": { "uid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "type": "enterprise", "issue_date_in_millis": 1700000000000, "expiry_date_in_millis": 1800000000000, "max_nodes": null, "max_resource_units": 6, "issued_to": "Your Company", "issuer": "API", "signature": "REPLACE_WITH_SIGNATURE", "start_date_in_millis": 1700000000000 } } { "license": { "uid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "type": "enterprise", "issue_date_in_millis": 1700000000000, "expiry_date_in_millis": 1800000000000, "max_nodes": null, "max_resource_units": 6, "issued_to": "Your Company", "issuer": "API", "signature": "REPLACE_WITH_SIGNATURE", "start_date_in_millis": 1700000000000 } } { "license": { "uid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "type": "enterprise", "issue_date_in_millis": 1700000000000, "expiry_date_in_millis": 1800000000000, "max_nodes": null, "max_resource_units": 6, "issued_to": "Your Company", "issuer": "API", "signature": "REPLACE_WITH_SIGNATURE", "start_date_in_millis": 1700000000000 } } PUT _license { "license": { "uid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "type": "enterprise", "issue_date_in_millis": 1700000000000, "expiry_date_in_millis": 1800000000000, "max_nodes": null, "max_resource_units": 6, "issued_to": "Your Company", "issuer": "API", "signature": "REPLACE_WITH_SIGNATURE", "start_date_in_millis": 1700000000000 } } PUT _license { "license": { "uid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "type": "enterprise", "issue_date_in_millis": 1700000000000, "expiry_date_in_millis": 1800000000000, "max_nodes": null, "max_resource_units": 6, "issued_to": "Your Company", "issuer": "API", "signature": "REPLACE_WITH_SIGNATURE", "start_date_in_millis": 1700000000000 } } PUT _license { "license": { "uid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "type": "enterprise", "issue_date_in_millis": 1700000000000, "expiry_date_in_millis": 1800000000000, "max_nodes": null, "max_resource_units": 6, "issued_to": "Your Company", "issuer": "API", "signature": "REPLACE_WITH_SIGNATURE", "start_date_in_millis": 1700000000000 } } GET _license GET _license GET _license - Continued access to premium features - Compliance with your subscription level - Avoidance of service interruptions - Open your Kibana URL in a browser - Log in with a user that has sufficient privileges. - Use the space selector (top-left corner) - Choose any space you want - In the left-hand menu, go to: Management → Dev Tools (or simply “Dev Tools” depending on your version) - This opens the Console where you can run Elasticsearch API requests - Format (pretty-print) the JSON - Ensure proper indentation - Verify there are no missing brackets or quotes - The license type is updated - The expiry date reflects the new license - The issued organization is correct - License updates apply cluster-wide, not per space - You must have sufficient privileges to update the license - Changes take effect immediately — no restart required - Always validate your license before applying it in production - Log in → Select space → Open Dev Tools - Check current license → Apply new license → Verify