mirror of
https://github.com/minio/docs.git
synced 2025-07-30 07:03:26 +03:00
cb2aa233a0
This PR simplifies the management of KMS integrations by removing the detailed documentation and linking out to the KES docs site instead. There should be no mention of any specific KMS target. Each OS/platform should have references to the correct paths, OS, and the like. This completes work started on the KES docs side in https://github.com/minio/kes-docs/pull/48. Staged: - [Linux](http://192.241.195.202:9000/staging/ssekms/linux/operations/server-side-encryption/configure-minio-kes.html) - [Windows](http://192.241.195.202:9000/staging/ssekms/windows/operations/server-side-encryption/configure-minio-kes.html) - [Kubernetes](http://192.241.195.202:9000/staging/ssekms/k8s/operations/server-side-encryption/configure-minio-kes.html) - [Containers](http://192.241.195.202:9000/staging/ssekms/container/operations/server-side-encryption/configure-minio-kes.html) - [MacOS](http://192.241.195.202:9000/staging/ssekms/macos/operations/server-side-encryption/configure-minio-kes.html)
1.9 KiB
1.9 KiB
Deploy MinIO and KES with Server-Side Encryption
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"Prerequisite
Depending on your chosen supported KMS target <#supported-kms-targets>
configuration, you may need to pass the kes-server.cert as
a trusted Certificate Authority (CA). Defer to the client documentation
for instructions on trusting a third-party CA.
1) Create the MinIO Configurations
Create the MinIO Environment File
Create the environment file using your preferred text editor. The following example uses the Windows Notepad program:
notepad |minioconfigpath|\minio2) Start the MinIO Server
Note
You must start KES before starting MinIO. The MinIO deployment requires access to KES as part of its startup.
Start the MinIO Server