Files
threshold/website/content/docs/configuration/kms/aead.mdx
T
Dan HeathandRobin Beck 2290ffc260 docs: Update meta content - Configuration (#5225)
* docs: Update meta content - Configuration

* docs: Revisions

* docs: Edits

* docs: Update KMS topics

* docs: Updates credential management topics

* docs: Updates IAM topics

* docs: Updates session recording topics

* docs: Updates configuration topics

* docs: Update titles

* Apply batch suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

---------

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
2024-12-04 13:28:17 -05:00

32 lines
1.0 KiB
Plaintext

---
layout: docs
page_title: AEAD KMS configuration
description: >-
Learn about using the Authenticated Encryption with Associated Data (AEAD) KMS for key management. AEAD is typically used for development workflows or testing.
---
# `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`, `bsr`, 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.