oyd
/
minio
6
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

fixed typo in KMS documentation (#9384)

Browse Source
master
sreenivas alapati 5 years ago committed by GitHub
parent 3e78ea8acc
commit d02deff3d7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Show Stats Download Patch File Download Diff File
  1. 2
      docs/kms/README.md

2
docs/kms/README.md
Unescape View File

@ -4,7 +4,7 @@ MinIO uses a key-management-system (KMS) to support SSE-S3. If a client requests
is enabled, the MinIO server encrypts each object with an unique object key which is protected by a master key is enabled, the MinIO server encrypts each object with an unique object key which is protected by a master key
managed by the KMS. managed by the KMS.
> MinIO still provides native Hashicorp Vault support. However, this is feature is **deprecated** and may be > MinIO still provides native Hashicorp Vault support. However, this feature is **deprecated** and may be
> removed in the future. Therefore, we strongly recommend to use the architecture and KMS Guide below. > removed in the future. Therefore, we strongly recommend to use the architecture and KMS Guide below.
> If you have to maintain a legacy MinIO-Vault deployment you can find the legacy documentation [here](https://docs.min.io/docs/minio-vault-legacy.html). > If you have to maintain a legacy MinIO-Vault deployment you can find the legacy documentation [here](https://docs.min.io/docs/minio-vault-legacy.html).

Write Preview
Loading…
Cancel
Save