aherman
/
boundary
mirror of https://github.com/hashicorp/boundary
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update configure-workers.mdx (#4772) (#4774)

Browse Source 
Co-authored-by: soly-hashicorp <106975916+soly-hashicorp@users.noreply.github.com>
pull/4779/head
Dan Heath 2 years ago committed by GitHub
parent 9e3151fed8
commit 65434c30a4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
website/content/docs/install-boundary/configure-workers.mdx
Unescape View File

@ -50,7 +50,7 @@ The worker-auth storage KMS key is used by a Worker for the encrypted storage of
This is recommended Workers using controller-led or worker-led methods. If it is not specified, the authentication keys are not encrypted on disk.
Optionally, if you deploy KMS authentication-driven Boundary workers, an additional KMS key must be generated to authenticate the Boundary worker with the controller.
HashiCorp strongly recommends using the Key Management Ssytem (KMS) of the cloud provider where you deploy your Boundary workers.
HashiCorp strongly recommends using the Key Management System (KMS) of the cloud provider where you deploy your Boundary workers.
Keep in mind that Boundary workers must have the correct level of permissions for interacting with the cloud provider's KMS.
Refer to your cloud provider's documentation, for more information.

Write Preview
Loading…
Cancel
Save