mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 23:21:08 +02:00
0660ea6fac
* Update README Let contributors know that docs will now be located in UDR * Add comments to each mdx doc Comment has been added to all mdx docs that are not partials * chore: added changelog changelog check failure * wip: removed changelog * Fix content errors * Doc spacing * Update website/content/docs/deploy/kubernetes/vso/helm.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> --------- Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
49 lines
2.4 KiB
Plaintext
49 lines
2.4 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Autoload an enterprise license
|
|
description: >-
|
|
Automatically load your Vault enterprise licenses.
|
|
---
|
|
|
|
> [!IMPORTANT]
|
|
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
|
|
|
|
# Autoload an enterprise license
|
|
|
|
@include 'alerts/enterprise-only.mdx'
|
|
|
|
<Tip title="Assumptions">
|
|
|
|
- You have an available Vault Enterprise license key.
|
|
- You have admin privileges for your Vault deployment environment.
|
|
|
|
</Tip>
|
|
|
|
Vault Enterprise automatically looks for valid license information in the
|
|
following locations:
|
|
|
|
Priority | Location | Variable / Field
|
|
:------: | -------------------- | ----------------
|
|
1 | Environment variable | [`VAULT_LICENSE`](/vault/docs/commands#global-vault_license_path)
|
|
2 | Environment variable | [`VAULT_LICENSE_PATH`](/vault/docs/commands#global-vault_license)
|
|
3 | Config file | [`license_path`](/vault/docs/configuration#license_path)
|
|
|
|
To configure license loading:
|
|
|
|
1. Run [`vault version`](/vault/docs/commands/version#version) to confirm the
|
|
build date of your Vault binary is before the expiry date of your license
|
|
key. Vault will not start if the applied license is expired.
|
|
1. Access the run environment for your Vault cluster.
|
|
1. Set the license key on each node of your cluster.
|
|
1. Make sure all nodes within a cluster use the same license key. Vault logs
|
|
warnings if nodes within a cluster use different license key. Different
|
|
clusters can use different license keys.
|
|
1. Call the
|
|
[`/sys/config/reload/license`](/vault/api-docs/system/config-reload#reload-license-file)
|
|
endpoint on each standby node for the cluster. Refreshing the license on
|
|
standby nodes first reduces potential disruptions if you run into problems.
|
|
1. Call the
|
|
[`/sys/config/reload/license`](/vault/api-docs/system/config-reload#reload-license-file)
|
|
endpoint on the leader node for the cluster.
|
|
1. Run `vault license get` on each node or review the unseal logs for each node
|
|
to verify the new license applied correctly. |