From e4d62bdf7b137371815577d934982fa009100fa8 Mon Sep 17 00:00:00 2001
From: Daryl White <53910321+djwfyi@users.noreply.github.com>
Date: Sat, 10 Feb 2024 09:47:08 -0500
Subject: [PATCH] Fixes for product names
---
source/administration/server-side-encryption.rst | 12 ++++++------
.../server-side-encryption-sse-kms.rst | 12 ++++++------
.../server-side-encryption-sse-s3.rst | 12 ++++++------
.../container/steps-configure-minio-kes-azure.rst | 2 +-
.../includes/k8s/steps-configure-minio-kes-aws.rst | 4 ++--
source/includes/k8s/tenant-values.yaml | 12 ++++++------
source/operations/checklists/security.rst | 4 ++--
source/operations/server-side-encryption.rst | 6 +++---
8 files changed, 32 insertions(+), 32 deletions(-)
diff --git a/source/administration/server-side-encryption.rst b/source/administration/server-side-encryption.rst
index d24785f8..6e43baf0 100644
--- a/source/administration/server-side-encryption.rst
+++ b/source/administration/server-side-encryption.rst
@@ -52,10 +52,10 @@ supports the following encryption strategies:
production MinIO deployments, use one of the following guides:
- :kes-docs:`Azure Key Vault `
- - :kes-docs:`AWS SecretsManager `
+ - :kes-docs:`AWS Secrets Manager `
- :kes-docs:`Fortanix SDKMS `
- - :kes-docs:`Google Cloud SecretManager `
- - :kes-docs:`Hashicorp KeyVault `
+ - :kes-docs:`Google Cloud Secret Manager `
+ - :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
.. tab-item:: SSE-S3
@@ -73,10 +73,10 @@ supports the following encryption strategies:
production MinIO deployments, use one of the following guides:
- :kes-docs:`Azure Key Vault `
- - :kes-docs:`AWS SecretsManager `
+ - :kes-docs:`AWS Secrets Manager `
- :kes-docs:`Fortanix SDKMS `
- - :kes-docs:`Google Cloud SecretManager `
- - :kes-docs:`Hashicorp KeyVault `
+ - :kes-docs:`Google Cloud Secret Manager `
+ - :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
.. tab-item:: SSE-C
diff --git a/source/administration/server-side-encryption/server-side-encryption-sse-kms.rst b/source/administration/server-side-encryption/server-side-encryption-sse-kms.rst
index a8781242..e58bcac2 100644
--- a/source/administration/server-side-encryption/server-side-encryption-sse-kms.rst
+++ b/source/administration/server-side-encryption/server-side-encryption-sse-kms.rst
@@ -55,10 +55,10 @@ MinIO SSE-KMS is functionally compatible with AWS S3
following KMS providers:
- :kes-docs:`Azure Key Vault `
-- :kes-docs:`AWS SecretsManager `
+- :kes-docs:`AWS Secrets Manager `
- :kes-docs:`Fortanix SDKMS `
-- :kes-docs:`Google Cloud SecretManager `
-- :kes-docs:`Hashicorp KeyVault `
+- :kes-docs:`Google Cloud Secret Manager `
+- :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
.. _minio-encryption-sse-kms-quickstart:
@@ -73,10 +73,10 @@ For extended development or production environments, use one of the following
supported external Key Management Services (KMS):
- :kes-docs:`Azure Key Vault `
-- :kes-docs:`AWS SecretsManager `
+- :kes-docs:`AWS Secrets Manager `
- :kes-docs:`Fortanix SDKMS `
-- :kes-docs:`Google Cloud SecretManager `
-- :kes-docs:`Hashicorp KeyVault `
+- :kes-docs:`Google Cloud Secret Manager `
+- :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
.. include:: /includes/common/common-minio-kes.rst
diff --git a/source/administration/server-side-encryption/server-side-encryption-sse-s3.rst b/source/administration/server-side-encryption/server-side-encryption-sse-s3.rst
index 46e37a42..d0084cc4 100644
--- a/source/administration/server-side-encryption/server-side-encryption-sse-s3.rst
+++ b/source/administration/server-side-encryption/server-side-encryption-sse-s3.rst
@@ -51,10 +51,10 @@ MinIO SSE-S3 is functionally compatible with AWS S3
following KMS providers:
- :kes-docs:`Azure Key Vault `
-- :kes-docs:`AWS SecretsManager `
+- :kes-docs:`AWS Secrets Manager `
- :kes-docs:`Fortanix SDKMS `
-- :kes-docs:`Google Cloud SecretManager `
-- :kes-docs:`Hashicorp KeyVault `
+- :kes-docs:`Google Cloud Secret Manager `
+- :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
.. _minio-encryption-sse-s3-quickstart:
@@ -69,10 +69,10 @@ For extended development or production environments, use one of the following
supported external Key Management Services (KMS):
- :kes-docs:`Azure Key Vault `
-- :kes-docs:`AWS SecretsManager `
+- :kes-docs:`AWS Secrets Manager `
- :kes-docs:`Fortanix SDKMS `
-- :kes-docs:`Google Cloud SecretManager `
-- :kes-docs:`Hashicorp KeyVault `
+- :kes-docs:`Google Cloud Secret Manager `
+- :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
.. include:: /includes/common/common-minio-kes.rst
diff --git a/source/includes/container/steps-configure-minio-kes-azure.rst b/source/includes/container/steps-configure-minio-kes-azure.rst
index 6f12dd5b..25eabfee 100644
--- a/source/includes/container/steps-configure-minio-kes-azure.rst
+++ b/source/includes/container/steps-configure-minio-kes-azure.rst
@@ -50,7 +50,7 @@ a. Create the KES Configuration File
-v |kescertpath|/certs:/certs \
kes:|kes-stable| tool identity of /certs/minio-kes.cert
- - Replace the ``endpoint`` with the URL for the Keyvault instance.
+ - Replace the ``endpoint`` with the URL for the Key Vault instance.
- Set ``TENANTID``, ``CLIENTID``, and ``CLIENTSECRET`` to match the credentials for a project user with the :ref:`required permissions `.
diff --git a/source/includes/k8s/steps-configure-minio-kes-aws.rst b/source/includes/k8s/steps-configure-minio-kes-aws.rst
index 51df1b11..b88d930e 100644
--- a/source/includes/k8s/steps-configure-minio-kes-aws.rst
+++ b/source/includes/k8s/steps-configure-minio-kes-aws.rst
@@ -1,5 +1,5 @@
-Deploy MinIO Tenant with Server-Side Encryption using AWS SecretsManager
-------------------------------------------------------------------------
+Deploy MinIO Tenant with Server-Side Encryption using AWS Secrets Manager
+-------------------------------------------------------------------------
1) Access the Operator Console
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/source/includes/k8s/tenant-values.yaml b/source/includes/k8s/tenant-values.yaml
index 14a7e6de..1ecec2d1 100644
--- a/source/includes/k8s/tenant-values.yaml
+++ b/source/includes/k8s/tenant-values.yaml
@@ -388,14 +388,14 @@ tenant:
# status: # Vault status configuration. The server will periodically reach out to Vault to check its status.
# ping: 10s # Duration until the server checks Vault's status again.
# # aws:
- # # # The AWS SecretsManager key store. The server will store
- # # # secret keys at the AWS SecretsManager encrypted with
+ # # # The AWS Secrets Manager key store. The server will store
+ # # # secret keys at the AWS Secrets Manager encrypted with
# # # AWS-KMS. See: https://aws.amazon.com/secrets-manager
# # secretsmanager:
- # # endpoint: "" # The AWS SecretsManager endpoint - e.g.: secretsmanager.us-east-2.amazonaws.com
- # # region: "" # The AWS region of the SecretsManager - e.g.: us-east-2
- # # kmskey: "" # The AWS-KMS key ID used to en/decrypt secrets at the SecretsManager. By default (if not set) the default AWS-KMS key will be used.
- # # credentials: # The AWS credentials for accessing secrets at the AWS SecretsManager.
+ # # endpoint: "" # The AWS Secrets Manager endpoint - e.g.: secretsmanager.us-east-2.amazonaws.com
+ # # region: "" # The AWS region of the Secrets Manager - e.g.: us-east-2
+ # # kmskey: "" # The AWS-KMS key ID used to en/decrypt secrets at the Secrets Manager. By default (if not set) the default AWS-KMS key will be used.
+ # # credentials: # The AWS credentials for accessing secrets at the AWS Secrets Manager.
# # accesskey: "" # Your AWS Access Key
# # secretkey: "" # Your AWS Secret Key
# # token: "" # Your AWS session token (usually optional)
diff --git a/source/operations/checklists/security.rst b/source/operations/checklists/security.rst
index 9fbd7356..cf9a20e9 100644
--- a/source/operations/checklists/security.rst
+++ b/source/operations/checklists/security.rst
@@ -43,8 +43,8 @@ MinIO supports the following external KMS providers through :kes-docs:`Key Encry
- :kes-docs:`Azure Key Vault `
- :kes-docs:`AWS SecretsManager `
- :kes-docs:`Fortanix SDKMS `
-- :kes-docs:`Google Cloud SecretManager `
-- :kes-docs:`Hashicorp KeyVault `
+- :kes-docs:`Google Cloud Secret Manager `
+- :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
.. list-table::
diff --git a/source/operations/server-side-encryption.rst b/source/operations/server-side-encryption.rst
index 3916a4c1..1bb76004 100644
--- a/source/operations/server-side-encryption.rst
+++ b/source/operations/server-side-encryption.rst
@@ -33,10 +33,10 @@ keys for use with MinIO SSE.
MinIO supports the following |KMS| providers as the central key store:
- :kes-docs:`Azure Key Vault `
-- :kes-docs:`AWS SecretsManager `
+- :kes-docs:`AWS Secrets Manager `
- :kes-docs:`Fortanix SDKMS `
-- :kes-docs:`Google Cloud SecretManager `
-- :kes-docs:`Hashicorp KeyVault `
+- :kes-docs:`Google Cloud Secret Manager `
+- :kes-docs:`Hashicorp Vault `
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) `
MinIO SSE requires enabling :ref:`minio-tls`.