adoroszlai commented on a change in pull request #3047:
URL: https://github.com/apache/ozone/pull/3047#discussion_r801014036
##########
File path: hadoop-hdds/docs/content/security/SecuringTDE.md
##########
@@ -71,20 +71,24 @@ will be completely transparent to the clients and end users.
There are two ways to create an encrypted bucket that can be accessed via S3
Gateway.
-####1. Create a bucket using shell under "/s3v" volume
+#### Option 1. Create a bucket using shell under "/s3v" volume
```bash
- ozone sh bucket create -k encKey /s3v/encryptedBucket
+ ozone sh bucket create -k encKey --layout=FILE_SYSTEM_OPTIMIZED
/s3v/encryptedbucket
```
-####2. Create a link to an encrypted bucket under "/s3v" volume
+
+#### Option 2. Create a link to an encrypted bucket under "/s3v" volume
```bash
- ozone sh bucket create -k encKey /vol/encryptedBucket
- ozone sh bucket link /vol/encryptedBucket /s3v/linkencryptedbucket
+ ozone sh bucket create -k encKey --layout=FILE_SYSTEM_OPTIMIZED
/vol/encryptedbucket
Review comment:
> I'm not totally sure of the compatiblity or performance impact if we
specify FSO type for S3-only buckets. (FSO doesn't fully support object store
IIRC but I'm not exactly sure why, or why that decision is made)
Same here, that's why I asked.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
