From 2fa33d59ae0e38c9066d6e06e93239551350aea4 Mon Sep 17 00:00:00 2001 From: ntimo Date: Sat, 16 Jul 2022 11:12:18 +0000 Subject: [PATCH] Fixed aws kes config example --- .../configure-minio-kes-aws.rst | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/source/operations/server-side-encryption/configure-minio-kes-aws.rst b/source/operations/server-side-encryption/configure-minio-kes-aws.rst index 2fdd3e69..114f408c 100644 --- a/source/operations/server-side-encryption/configure-minio-kes-aws.rst +++ b/source/operations/server-side-encryption/configure-minio-kes-aws.rst @@ -192,13 +192,14 @@ Manager: # This example assumes that the associated AWS account has the necessary # access key and secret key keystore: - secretsmanager: - endpoint: secretsmanager.REGION.amazonaws # use the Secrets Manager endpoint for your region - region: REGION # e.g. us-east-1 - kmskey: "" # Optional. The root AWS KMS key to use for cryptographic operations. Formerly described as the "Customer Master Key". - credentials: - accesskey: "${AWSACCESSKEY}" # AWS Access Key - secretkey: "${AWSSECRETKEY}" # AWS Secret Key + aws: + secretsmanager: + endpoint: secretsmanager.REGION.amazonaws.com # use the Secrets Manager endpoint for your region + region: REGION # e.g. us-east-1 + kmskey: "" # Optional. The root AWS KMS key to use for cryptographic operations. Formerly described as the "Customer Master Key". + credentials: + accesskey: "${AWSACCESSKEY}" # AWS Access Key + secretkey: "${AWSSECRETKEY}" # AWS Secret Key Save the configuration file as ``~/kes/config/kes-config.yaml``. Any field with