[
https://issues.apache.org/jira/browse/HDDS-17774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chung-En Lee updated HDDS-17774:
--------------------------------
Description:
The S3 Gateway rejects {{GetBucketEncryption}} with {{NotImplemented}}, even
for an encrypted bucket. Clients and compliance tools call it to check whether
a bucket encrypts new objects, e.g. {{aws s3api get-bucket-encryption}}. An
encrypted bucket can only be created with {{ozone sh}}, not through the S3 API,
so this is the only way for S3 users to check whether a bucket is encrypted
before writing to it.
The S3 Gateway should support {{GetBucketEncryption}} and report the bucket's
encryption, as {{HeadObject}} reports the encryption of an object since
HDDS-17500.
The S3 API page of the Ozone website should be updated at the same time:
* List {{GetBucketEncryption}} under "Bucket Operations" instead of "Operations
Not Implemented". {{PutBucketEncryption}} and {{DeleteBucketEncryption}} stay
not implemented.
* In "Server-Side Encryption", state that an encrypted bucket can only be
created with {{ozone sh bucket create --bucketkey}}, not through the S3 API.
Today only the Transparent Data Encryption page says this.
was:
The S3 Gateway rejects {{GetBucketEncryption}} with {{NotImplemented}}, even
for an encrypted bucket. Clients and compliance tools call it to check whether
a bucket encrypts new objects, e.g. {{aws s3api get-bucket-encryption}}. An
encrypted bucket can only be created with {{ozone sh}}, not through the S3 API,
so this is the only way for S3 users to check whether a bucket is encrypted
before writing to it.
The S3 Gateway should support {{GetBucketEncryption}} and report the bucket's
encryption, as {{HeadObject}} reports the encryption of an object since
HDDS-17500.
The S3 API page of the Ozone website
({{docs/04-user-guide/01-client-interfaces/03-s3/01-s3-api.md}} in ozone-site)
should be updated at the same time:
* List {{GetBucketEncryption}} under "Bucket Operations" instead of "Operations
Not Implemented". {{PutBucketEncryption}} and {{DeleteBucketEncryption}} stay
not implemented.
* In "Server-Side Encryption", state that an encrypted bucket can only be
created with {{ozone sh bucket create --bucketkey}}, not through the S3 API.
Today only the Transparent Data Encryption page says this.
> S3 Gateway should support GetBucketEncryption
> ---------------------------------------------
>
> Key: HDDS-17774
> URL: https://issues.apache.org/jira/browse/HDDS-17774
> Project: Apache Ozone
> Issue Type: Improvement
> Components: s3gateway
> Reporter: Chung-En Lee
> Priority: Minor
>
> The S3 Gateway rejects {{GetBucketEncryption}} with {{NotImplemented}}, even
> for an encrypted bucket. Clients and compliance tools call it to check
> whether a bucket encrypts new objects, e.g. {{aws s3api
> get-bucket-encryption}}. An encrypted bucket can only be created with {{ozone
> sh}}, not through the S3 API, so this is the only way for S3 users to check
> whether a bucket is encrypted before writing to it.
> The S3 Gateway should support {{GetBucketEncryption}} and report the bucket's
> encryption, as {{HeadObject}} reports the encryption of an object since
> HDDS-17500.
> The S3 API page of the Ozone website should be updated at the same time:
> * List {{GetBucketEncryption}} under "Bucket Operations" instead of
> "Operations Not Implemented". {{PutBucketEncryption}} and
> {{DeleteBucketEncryption}} stay not implemented.
> * In "Server-Side Encryption", state that an encrypted bucket can only be
> created with {{ozone sh bucket create --bucketkey}}, not through the S3 API.
> Today only the Transparent Data Encryption page says this.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]