MyFavMirrors/minio
1
0
Fork 0
mirror of https://github.com/minio/minio.git synced 2024-12-25 06:35:56 -05:00
Code Issues Packages Projects Releases Wiki Activity

fix KMS quickstart guide layout (#9658)

Browse Source 
This commit fixes a layout issue w.r.t. the KMS
Quickstart guide. The problem seems to be caused
by docs server not converting the markdown into html
as expected.

This commit fixes this by converting the ordered list
into subsections.
This commit is contained in:
Andreas Auernhammer 2020-05-20 22:55:54 +02:00 committed by GitHub
parent 189c861835
commit 2164984d2b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 26 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
docs/kms/README.md
View File

@ -12,25 +12,31 @@ a KMS just fetch the root identity, set the following environment variables and
If you havn't installed MinIO, yet, then follow the MinIO [install instructions](https://docs.min.io/docs/minio-quickstart-guide) If you havn't installed MinIO, yet, then follow the MinIO [install instructions](https://docs.min.io/docs/minio-quickstart-guide)
first. first.
1. As initial step fetch the private key and certificate of the root identity: #### 1. Fetch the root identity
```sh As the initial step, fetch the private key and certificate of the root identity:
curl -sSL --tlsv1.2 \
```sh
curl -sSL --tlsv1.2 \
-O 'https://raw.githubusercontent.com/minio/kes/master/root.key' \ -O 'https://raw.githubusercontent.com/minio/kes/master/root.key' \
-O 'https://raw.githubusercontent.com/minio/kes/master/root.cert' -O 'https://raw.githubusercontent.com/minio/kes/master/root.cert'
``` ```
2. Set the MinIO-KES related environment variables:
```sh #### 2. Set the MinIO-KES configuration
export MINIO_KMS_KES_ENDPOINT=https://play.min.io:7373
export MINIO_KMS_KES_KEY_FILE=root.key ```sh
export MINIO_KMS_KES_CERT_FILE=root.cert export MINIO_KMS_KES_ENDPOINT=https://play.min.io:7373
export MINIO_KMS_KES_KEY_NAME=my-minio-key export MINIO_KMS_KES_KEY_FILE=root.key
``` export MINIO_KMS_KES_CERT_FILE=root.cert
3. Start the MinIO server: export MINIO_KMS_KES_KEY_NAME=my-minio-key
```sh ```
export MINIO_ACCESS_KEY=minio
export MINIO_SECRET_KEY=minio123 #### 3. Start the MinIO Server
minio server ~/export
``` ```sh
export MINIO_ACCESS_KEY=minio
export MINIO_SECRET_KEY=minio123
minio server ~/export
```
> The KES instance at `https://play.min.io:7373` is meant to experiment and provides a way to get started quickly. > The KES instance at `https://play.min.io:7373` is meant to experiment and provides a way to get started quickly.
> Note that anyone can access or delete master keys at `https://play.min.io:7373`. You should run your own KES > Note that anyone can access or delete master keys at `https://play.min.io:7373`. You should run your own KES
@ -49,7 +55,7 @@ A typical MinIO deployment that uses a KMS for SSE-S3 looks like this:
└─────────┘ └─────────┘
``` ```
So, there are `n` MinIO instances talking to `m` KES servers but only `1` central KMS. The most simple In a given setup, there are `n` MinIO instances talking to `m` KES servers but only `1` central KMS. The most simple
setup consists of `1` MinIO server or cluster talking to `1` KMS via `1` KES server. setup consists of `1` MinIO server or cluster talking to `1` KMS via `1` KES server.
The main difference between various MinIO-KMS deployments is the KMS implementation. The following table The main difference between various MinIO-KMS deployments is the KMS implementation. The following table