upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-02-18 18:38:08 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

Update seal-ha.mdx (#28863)

Browse source 
Fix typo and text formatting
This commit is contained in:
ram-parameswaran 2024-11-09 01:24:00 +11:00 committed by GitHub
parent 73702dbc8b
commit 6f653692ea
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
website/content/docs/configuration/seal/seal-ha.mdx
View file

@ -49,7 +49,7 @@ values. Because there may be two seals of the same type, one must
disambiguate the environment variables used. To do this, in HA setups,
append an underscore followed by the seal's configured name (matching its
case) to any environment variable names. For example, in the sample
configuration below, the AWS acces skey could be provided as `ACCESS_KEY_aws_east`.
configuration below, the AWS access key could be provided as `ACCESS_KEY_aws_east`.
Keep in mind that the seal name must be valid in an environment variable name to use it.
Priority is mandatory if more than one seal is specified. Priority tells Vault
@ -158,4 +158,4 @@ use the HA seal feature. To migrate back to a single seal:
1. Perform a [seal migration](/vault/docs/concepts/seal#seal-migration) as described.
2. Monitor [`sys/sealwrap/rewrap`](/vault/api-docs/system/sealwrap-rewrap) until the API returns `fully_wrapped=true`.
3. Remove `enable_multiseal` from all Vault configuration files in the cluster.
4. Restart Vault.
4. Restart Vault.