docs/source/includes/windows/steps-configure-minio-kes-gcp.rst

Deploy MinIO and KES with Server-Side Encryption using GCP Secrets Manager

Prior to starting these steps, create the following folders:

New-Item -Path "|kescertpath|" -ItemType "directory"
New-Item -Path "|kesconfigpath|" -ItemType "directory"
New-Item -Path "|miniodatapath|" -ItemType "directory"

1) Download KES for Windows

2) Generate TLS Certificates for KES and MinIO

3) Create the KES and MinIO Configurations

1. Create the KES Configuration File

   Create the configuration file using your preferred text editor. The following example uses the Windows Notepad program:

   notepad |kesconfigpath|\kes-config.yaml

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

     The following command computes the necessary hash:

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

   • Set GCPPROJECTID to the GCP project for the Secrets Manager instance KES should use.

   • Set GCPCLIENTEMAIL, GCPCLIENTID, GCPPRIVATEKEYID, and GCPPRIVATEKEY to the credentials associated to the GCP Service Account <minio-sse-gcp-prereq-gcp> KES should use when accessing the Secrets Manager service.

2. Create the MinIO Environment File

   Create the environment file using your preferred text editor. The following example uses the Windows Notepad program:

   notepad |minioconfigpath|\minio

4) Start KES and MinIO

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

1. Start the KES Server
2. Start the MinIO Server

5) Generate a New Encryption Key

6) Enable SSE-KMS for a Bucket