From 17eabe2ed5391cd1ad09da091de299a0c23338eb Mon Sep 17 00:00:00 2001 From: Amy Phillips <aphillips@gitlab.com> Date: Wed, 22 May 2024 19:09:59 +0000 Subject: [PATCH] Update Dedicated BYOK docs with key type details --- doc/administration/dedicated/create_instance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/administration/dedicated/create_instance.md b/doc/administration/dedicated/create_instance.md index d13b5981174ec..62922ff024790 100644 --- a/doc/administration/dedicated/create_instance.md +++ b/doc/administration/dedicated/create_instance.md @@ -42,7 +42,7 @@ complete your onboarding to create a new instance. NOTE: To enable BYOK, you must do it before onboarding. -You can opt to encrypt your GitLab data at rest with AWS KMS keys, which must be made accessible to GitLab Dedicated infrastructure. GitLab Dedicated only supports keys with AWS-managed key material (the [AWS_KMS](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-origin) origin type). +You can opt to encrypt your GitLab data at rest with AWS KMS keys, which must be made accessible to GitLab Dedicated infrastructure. Due to key rotation requirements, GitLab Dedicated only supports keys with AWS-managed key material (the [AWS_KMS](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-origin) origin type). In GitLab Dedicated, you can use KMS keys in two ways: -- GitLab