mirror of
https://github.com/minio/docs.git
synced 2025-08-09 13:02:53 +03:00
Fixes for product names
This commit is contained in:
@@ -52,10 +52,10 @@ supports the following encryption strategies:
|
||||
production MinIO deployments, use one of the following guides:
|
||||
|
||||
- :kes-docs:`Azure Key Vault <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`AWS Secrets Manager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
.. 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 <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`AWS Secrets Manager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
.. tab-item:: SSE-C
|
||||
|
@@ -55,10 +55,10 @@ MinIO SSE-KMS is functionally compatible with AWS S3
|
||||
following KMS providers:
|
||||
|
||||
- :kes-docs:`Azure Key Vault <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`AWS Secrets Manager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
.. _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 <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`AWS Secrets Manager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
.. include:: /includes/common/common-minio-kes.rst
|
||||
|
@@ -51,10 +51,10 @@ MinIO SSE-S3 is functionally compatible with AWS S3
|
||||
following KMS providers:
|
||||
|
||||
- :kes-docs:`Azure Key Vault <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`AWS Secrets Manager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
.. _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 <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`AWS Secrets Manager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
.. include:: /includes/common/common-minio-kes.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 <minio-sse-azure-prereq-azure>`.
|
||||
|
||||
|
@@ -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
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
@@ -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)
|
||||
|
@@ -43,8 +43,8 @@ MinIO supports the following external KMS providers through :kes-docs:`Key Encry
|
||||
- :kes-docs:`Azure Key Vault <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
.. list-table::
|
||||
|
@@ -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 <integrations/azure-keyvault/>`
|
||||
- :kes-docs:`AWS SecretsManager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`AWS Secrets Manager <integrations/aws-secrets-manager/>`
|
||||
- :kes-docs:`Fortanix SDKMS <integrations/fortanix-sdkms/>`
|
||||
- :kes-docs:`Google Cloud SecretManager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp KeyVault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Google Cloud Secret Manager <integrations/google-cloud-secret-manager/>`
|
||||
- :kes-docs:`Hashicorp Vault <integrations/hashicorp-vault-keystore/>`
|
||||
- :kes-docs:`Thales Digital Identity and Security (formerly Gemalto) <integrations/thales-ciphertrust/>`
|
||||
|
||||
MinIO SSE requires enabling :ref:`minio-tls`.
|
||||
|
Reference in New Issue
Block a user