You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ozone.apache.org by we...@apache.org on 2025/09/03 04:34:14 UTC

(ozone) branch master updated: HDDS-13631. Encrypted bucket creation correction on --key option (#8996)

This is an automated email from the ASF dual-hosted git repository.

weichiu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git


The following commit(s) were added to refs/heads/master by this push:
     new 696978cc1e4 HDDS-13631. Encrypted bucket creation correction on --key option (#8996)
696978cc1e4 is described below

commit 696978cc1e4639b98d2ad3f08f297999509bb5a6
Author: Venkat Sambath <sv...@cloudera.com>
AuthorDate: Wed Sep 3 00:34:09 2025 -0400

    HDDS-13631. Encrypted bucket creation correction on --key option (#8996)
---
 hadoop-hdds/docs/content/security/SecuringTDE.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/hadoop-hdds/docs/content/security/SecuringTDE.md b/hadoop-hdds/docs/content/security/SecuringTDE.md
index e8a0decb51e..842cfb22fff 100644
--- a/hadoop-hdds/docs/content/security/SecuringTDE.md
+++ b/hadoop-hdds/docs/content/security/SecuringTDE.md
@@ -67,16 +67,16 @@ For example:
 
 ### Creating an Encrypted Bucket
 
-Use the Ozone shell `ozone sh bucket create` command with the `-k` (or `--key`) option to specify the encryption key:
+Use the Ozone shell `ozone sh bucket create` command with the `-k` (or `--bucketkey`) option to specify the encryption key:
 
 ```shell
-  ozone sh bucket create --key <key_name> /<volume_name>/<bucket_name>
+  ozone sh bucket create --bucketkey <key_name> /<volume_name>/<bucket_name>
 ```
 
 For example:
 
 ```shell
-  ozone sh bucket create --key enckey /vol1/encrypted_bucket
+  ozone sh bucket create --bucketkey enckey /vol1/encrypted_bucket
 ```
 
 Now, all data written to `/vol1/encrypted_bucket` will be encrypted at rest. As long as the client is configured correctly to use the key, such encryption is completely transparent to the end users.
@@ -132,13 +132,13 @@ When creating an encrypted bucket that will be accessed via S3G:
     The `/s3v` volume is the default volume for S3 buckets.
 
 ```shell
-  ozone sh bucket create --key <key_name> /s3v/<bucket_name> --layout=OBJECT_STORE
+  ozone sh bucket create --bucketkey <key_name> /s3v/<bucket_name> --layout=OBJECT_STORE
 ```
 
 2.  **Alternatively, create an encrypted bucket elsewhere and link it:**
 
 ```shell
-  ozone sh bucket create --key <key_name> /<volume_name>/<bucket_name> --layout=OBJECT_STORE
+  ozone sh bucket create --bucketkey <key_name> /<volume_name>/<bucket_name> --layout=OBJECT_STORE
   ozone sh bucket link /<volume_name>/<bucket_name> /s3v/<link_name>
 ```
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@ozone.apache.org
For additional commands, e-mail: commits-help@ozone.apache.org