docs/source/includes/linux/steps-configure-minio-kes-azure.rst

Deploy MinIO and KES with Server-Side Encryption using Azure KeyVault for Local Development

Prior to starting these steps, create the following folders if they do not already exist:

mkdir -P |kescertpath|
mkdir -P |kesconfigpath|
mkdir -P |miniocertpath|

1) Download KES and Create the Service File

1. Download KES
2. Create the Service File

2) Generate TLS Certificates for KES and MinIO

3) Create the KES and MinIO Configurations

Important

Starting with RELEASE.2023-02-17T17-52-43Z, MinIO requires expanded KES permissions for functionality. The example configuration in this section contains all required permissions.

1. Create the KES Configuration File

   Create the configuration file using your preferred text editor. The following example uses nano:

   nano /etc/kes/config.yaml

   • Set MINIO_IDENTITY_HASH to the identity hash of the MinIO mTLS certificate.

     The following command computes the necessary hash:

     kes identity of |miniocertpath|/minio-kes.cert

   • Replace the endpoint with the URL for the Keyvault instance.

   • Set TENANTID, CLIENTID, and CLIENTSECRET to match the credentials for a project user with the required permissions <minio-sse-azure-prereq-azure>.

2. Configure the MinIO Environment File

   Modify the MinIO Server environment file for all hosts in the target deployment to include the following environment variables.

   MinIO defaults to expecting this file at /etc/default/minio. If you modified your deployment to use a different location for the environment file, modify the file at that location.

4) Start KES and MinIO

You must start KES before starting MinIO. The MinIO deployment requires access to KES as part of its startup.

This step uses systemd for starting and managing both the KES and MinIO server processes:

1. Start the KES Service on All Hosts
2. Start the MinIO Server

5) Generate a New Encryption Key

6) Enable SSE-KMS for a Bucket