mirror of
https://github.com/hashicorp/vault.git
synced 2026-05-05 20:36:26 +02:00
Chris Hoffman
GitHub
parent
250c1b9719
commit
219285850b
@ -127,7 +127,6 @@
|
||||
title: "Vault Enterprise"
|
||||
docs:
|
||||
- docs/enterprise/replication/index.html
|
||||
- docs/enterprise/auto-unseal/index.html
|
||||
- docs/enterprise/hsm/index.html
|
||||
- docs/enterprise/sealwrap/index.html
|
||||
- docs/enterprise/namespaces/index.html
|
||||
|
||||
@ -33,6 +33,10 @@ Either the `key` or `reset` parameter must be provided; if both are provided,
|
||||
- `reset` `(bool: false)` – Specifies if previously-provided unseal keys are
|
||||
discarded and the unseal process is reset.
|
||||
|
||||
- `migrate` `(string: "")` - Available in 1.0 Beta - Used to migrate the seal
|
||||
from shamir to autoseal or autoseal to shamir. Must be provided on all unseal
|
||||
key calls. Valid values are "shamir" and "autoseal".
|
||||
|
||||
### Sample Payload
|
||||
|
||||
```json
|
||||
|
||||
@ -71,3 +71,47 @@ a single operator with root privileges.
|
||||
This way, if there is a detected intrusion, the Vault data can be locked
|
||||
quickly to try to minimize damages. It can't be accessed again without
|
||||
access to the master key shards.
|
||||
|
||||
## Auto Unseal
|
||||
|
||||
Auto Unseal was developed to aid in reducing the operational complexity of
|
||||
keeping the master key secure. This feature delegates the responsibility of
|
||||
securing the master key from users to a trusted device or service. Instead of
|
||||
only constructing the key in memory, the master key is encrypted with one of
|
||||
these services or devices and then stored in the storage backend allowing Vault
|
||||
to decrypt the master key at startup and unseal automatically.
|
||||
|
||||
When using a Auto Unseal, there are certain operations in Vault that still
|
||||
require a quorum of users to perform an operation such as generating a root token.
|
||||
During the initialization process, a set of Shamir keys are generated that are called
|
||||
Recovery Keys and are used for these operations.
|
||||
|
||||
For a list of examples and supported providers, please see the
|
||||
[seal documentation](/docs/configuration/seal/index.html).
|
||||
|
||||
## Seal Migration
|
||||
|
||||
The seal can be migrated between Shamir keys and automatic migration and vice versa.
|
||||
|
||||
To migrate from Shamir keys to Auto Unseal, take your server cluster offline and update
|
||||
the [seal configuration](/docs/configuration/seal/index.html) with the appropriate seal
|
||||
configuration. When you bring up your server back up, run the unseal process with the
|
||||
`-migrate` flag. All unseal commands must specify the `-migrate` flag. Once the
|
||||
required threshold of unseal keys are entered, the unseal keys will be migrated to
|
||||
recovery keys.
|
||||
|
||||
```
|
||||
$ vault unseal -migrate autoseal
|
||||
```
|
||||
|
||||
To migrate from Auto Unseal to Shamir keys, take your server cluster offline and update
|
||||
the [seal configuration](/docs/configuration/seal/index.html) and add `disabled = "true"`
|
||||
to the seal block. This allows the migration to use this information to decrypt the key
|
||||
but will not unseal Vault. When you bring up your server back up, run the unseal process
|
||||
with the `-migrate` flag and use the Recovery Keys to perform the migration. All unseal
|
||||
commands must specify the `-migrate` flag. Once the required threshold of recovery keys
|
||||
are entered, the recovery keys will be migrated to be used as unseal keys.
|
||||
|
||||
```
|
||||
$ vault unseal -migrate shamir
|
||||
```
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: "docs"
|
||||
page_title: "AliCloud KMS - Seals - Configuration"
|
||||
sidebar_title: "AliCloud KMS <sup>ENT</sup>"
|
||||
sidebar_title: "AliCloud KMS <sup>1.0 BETA</sup>"
|
||||
sidebar_current: "docs-configuration-seal-alicloudkms"
|
||||
description: |-
|
||||
The AliCloud KMS seal configures Vault to use AliCloud KMS as the seal wrapping
|
||||
@ -11,7 +11,7 @@ description: |-
|
||||
# `alicloudkms` Seal
|
||||
|
||||
The AliCloud KMS seal configures Vault to use AliCloud KMS as the seal wrapping mechanism.
|
||||
Vault Enterprise's AliCloud KMS seal is activated by one of the following:
|
||||
The AliCloud KMS seal is activated by one of the following:
|
||||
|
||||
* The presence of a `seal "alicloudkms"` block in Vault's configuration file.
|
||||
* The presence of the environment variable `VAULT_SEAL_TYPE` set to `alicloudkms`. If
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: "docs"
|
||||
page_title: "AWS KMS - Seals - Configuration"
|
||||
sidebar_title: "AWS KMS <sup>ENT</sup>"
|
||||
sidebar_title: "AWS KMS <sup>1.0 BETA</sup>"
|
||||
sidebar_current: "docs-configuration-seal-awskms"
|
||||
description: |-
|
||||
The AWS KMS seal configures Vault to use AWS KMS as the seal wrapping
|
||||
@ -11,7 +11,7 @@ description: |-
|
||||
# `awskms` Seal
|
||||
|
||||
The AWS KMS seal configures Vault to use AWS KMS as the seal wrapping mechanism.
|
||||
Vault Enterprise's AWS KMS seal is activated by one of the following:
|
||||
The AWS KMS seal is activated by one of the following:
|
||||
|
||||
* The presence of a `seal "awskms"` block in Vault's configuration file
|
||||
* The presence of the environment variable `VAULT_SEAL_TYPE` set to `awskms`. If
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: "docs"
|
||||
page_title: "Azure Key Vault - Seals - Configuration"
|
||||
sidebar_title: "Azure Key Vault <sup>ENT</sup>"
|
||||
sidebar_title: "Azure Key Vault <sup>1.0 BETA</sup>"
|
||||
sidebar_current: "docs-configuration-seal-azurekeyvault"
|
||||
description: |-
|
||||
The Azure Key Vault seal configures Vault to use Azure Key Vault as the seal wrapping
|
||||
@ -11,8 +11,7 @@ description: |-
|
||||
# `azurekeyvault` Seal
|
||||
|
||||
The Azure Key Vault seal configures Vault to use Azure Key Vault as the seal
|
||||
wrapping mechanism. Vault Enterprise's Azure Key Vault seal is activated by one of
|
||||
the following:
|
||||
wrapping mechanism. The Azure Key Vault seal is activated by one of the following:
|
||||
|
||||
* The presence of a `seal "azurekeyvault"` block in Vault's configuration file.
|
||||
* The presence of the environment variable `VAULT_SEAL_TYPE` set to `azurekeyvault`.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
layout: "docs"
|
||||
page_title: "GCP Cloud KMS - Seals - Configuration"
|
||||
sidebar_title: "GCP Cloud KMS <sup>ENT</sup>"
|
||||
sidebar_title: "GCP Cloud KMS <sup>1.0 BETA</sup>"
|
||||
sidebar_current: "docs-configuration-seal-gcpckms"
|
||||
description: |-
|
||||
The GCP Cloud KMS seal configures Vault to use GCP Cloud KMS as the seal wrapping
|
||||
@ -11,8 +11,7 @@ description: |-
|
||||
# `gcpckms` Seal
|
||||
|
||||
The GCP Cloud KMS seal configures Vault to use GCP Cloud KMS as the seal
|
||||
wrapping mechanism. Vault Enterprise's GCP Cloud KMS seal is activated by one of
|
||||
the following:
|
||||
wrapping mechanism. The GCP Cloud KMS seal is activated by one of the following:
|
||||
|
||||
* The presence of a `seal "gcpckms"` block in Vault's configuration file.
|
||||
* The presence of the environment variable `VAULT_SEAL_TYPE` set to `gcpckms`.
|
||||
|
||||
@ -16,7 +16,8 @@ will use the Shamir algorithm to cryptographically split the master key if this
|
||||
is not configured.
|
||||
|
||||
As of Vault 0.9.0, the seal can also be used for [seal wrapping][sealwrap] to
|
||||
add an extra layer of protection and satisfy compliance and regulatory requirements.
|
||||
add an extra layer of protection and satisfy compliance and regulatory requirements.
|
||||
This feature is only available in Vault Enterprise.
|
||||
|
||||
For more examples, please choose a specific auto unsealing technology from the
|
||||
sidebar.
|
||||
|
||||
@ -1,33 +0,0 @@
|
||||
---
|
||||
layout: "docs"
|
||||
page_title: "Vault Enterprise Auto Unseal"
|
||||
sidebar_title: "Auto Unseal"
|
||||
sidebar_current: "docs-vault-enterprise-auto-unseal"
|
||||
description: |-
|
||||
Vault Enterprise supports automatic unsealing via cloud technologies like KMS.
|
||||
---
|
||||
|
||||
# Vault Enterprise Auto Unseal
|
||||
|
||||
As of version 0.9, Vault Enterprise supports opt-in automatic unsealing via
|
||||
cloud technologies such Amazon KMS or Google Cloud KMS. This feature enables
|
||||
operators to delegate the unsealing process to trusted cloud providers to ease
|
||||
operations in the event of partial failure and to aid in the creation of new or
|
||||
ephemeral clusters.
|
||||
|
||||
## Enabling Auto Unseal
|
||||
|
||||
Automatic unsealing is not enabled by default. To enable automatic unsealing,
|
||||
specify the `seal` stanza in your Vault configuration file:
|
||||
|
||||
```hcl
|
||||
seal "awskms" {
|
||||
region = "us-east-1"
|
||||
access_key = "..."
|
||||
secret_key = "..."
|
||||
kms_key_id = "..."
|
||||
}
|
||||
```
|
||||
|
||||
For a complete list of examples and supported technologies, please see the
|
||||
[seal documentation](/docs/configuration/seal/index.html).
|
||||
@ -28,7 +28,7 @@ instance that can utilize an encryption key from [AWS Key Management Services
|
||||
|
||||
## Reference Material
|
||||
|
||||
- [Vault Enterprise Auto Unseal](/docs/enterprise/auto-unseal/index.html)
|
||||
- [Vault Auto Unseal](/docs/configuration/seal/index.html)
|
||||
- [Configuration: `awskms` Seal](/docs/configuration/seal/awskms.html)
|
||||
|
||||
|
||||
|
||||
@ -318,8 +318,7 @@ within that replication set must use an HSM as well.
|
||||
secret sharing method), the clusters within that replication set can be mixed,
|
||||
such that some may use an HSM, others may use Shamir.
|
||||
|
||||
For sake of this discussion, the [cloud
|
||||
auto-unseal](/docs/enterprise/auto-unseal/index.html) feature is treated as an
|
||||
For sake of this discussion, the cloud auto-unseal feature is treated as an
|
||||
HSM.
|
||||
|
||||
## Additional References
|
||||
|
||||
@ -324,7 +324,6 @@
|
||||
category: 'enterprise',
|
||||
content: [
|
||||
{ category: 'replication' },
|
||||
{ category: 'auto-unseal' },
|
||||
{
|
||||
category: 'hsm',
|
||||
content: ['behavior', 'security']
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user