* docs: Update headings for new style rule * docs: Fix headings - Get started * docs: Fix headings - Install * docs: Fix headings - Concepts * docs: Fix typos * docs: Fix headings - Configuration * docs: Fix headings - Operations * docs: Fix headings - Troubleshoot * docs: Fix headings - Clients and Develop * docs: Fix headings - HCP and ENT * docs: Fix headings - Release notes * docs: Fix typos * docs: Fix capitalization in TOC
32 lines
922 B
Plaintext
32 lines
922 B
Plaintext
---
|
|
layout: docs
|
|
page_title: AEAD - configuration
|
|
description: |-
|
|
The AEAD KMS configures AEAD-specific parameters.
|
|
---
|
|
|
|
# `aead` KMS
|
|
|
|
~> **Note:** This is mostly used for `dev` workflows or testing. The key will be exposed
|
|
to anyone that can view the configuration file. If using this KMS, consider
|
|
using `boundary config encrypt` to encrypt all but the `config` KMS and using an
|
|
external KMS for `config` purposes.
|
|
|
|
```hcl
|
|
kms "aead" {
|
|
purpose = "worker-auth"
|
|
aead_type = "aes-gcm"
|
|
key = "8fZBjCUfN0TzjEGLQldGY4+iE9AkOvCfjh7+p0GtRBQ="
|
|
key_id = "global_worker-auth"
|
|
}
|
|
```
|
|
|
|
- `purpose` - Purpose of this KMS, acceptable values are: `worker-auth`, `worker-auth-storage`,
|
|
`root`, `previous-root`, `recovery`, or `config`.
|
|
|
|
- `aead_type` - The type of encryption this KMS uses. Currently only `aes-gcm` is implemented.
|
|
|
|
- `key` - The base64-encoded 256-bit encryption key.
|
|
|
|
- `key_id` - The unique name of this key.
|