[
https://issues.apache.org/jira/browse/HDDS-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chung-En Lee updated HDDS-17773:
--------------------------------
Description:
In an encrypted bucket, the S3 Gateway returns {{x-amz-server-side-encryption}}
on write responses only when the request has that header (HDDS-17498). An
object written without it, which is the default for SDK clients, is still
encrypted with the bucket's key, and since HDDS-17500 {{HeadObject}} and
{{GetObject}} report it as {{aws:kms}} with the key. But {{PutObject}},
{{CopyObject}}, {{CreateMultipartUpload}}, {{UploadPart}}, {{UploadPartCopy}}
and {{CompleteMultipartUpload}} return no header for it, so the write response
says the object is not encrypted while the read response says it is.
AWS S3 returns the encryption of the object on all of these responses, also
when the request has no header. The write responses should report the same
encryption as {{HeadObject}}.
was:
In an encrypted bucket, the S3 Gateway returns {{x-amz-server-side-encryption}}
on write responses only when the request has that header (HDDS-17498). An
object written without it, which is the default for SDK clients, is still
encrypted with the bucket's key, and since HDDS-17500 {{HeadObject}} and
{{GetObject}} report it as {{aws:kms}} with the key. But {{PutObject}},
{{CopyObject}}, {{CreateMultipartUpload}}, {{UploadPart}}, {{UploadPartCopy}}
and {{CompleteMultipartUpload}} return no SSE header for it, so the write
response says the object is not encrypted while the read response says it is.
AWS S3 returns the encryption of the object on all of these responses, also
when the request has no SSE header. The write responses should report the same
encryption as {{HeadObject}}.
> S3 Gateway should return x-amz-server-side-encryption on write responses for
> encrypted objects
> ----------------------------------------------------------------------------------------------
>
> Key: HDDS-17773
> URL: https://issues.apache.org/jira/browse/HDDS-17773
> Project: Apache Ozone
> Issue Type: Bug
> Components: s3gateway
> Reporter: Chung-En Lee
> Assignee: Billy Shen
> Priority: Minor
>
> In an encrypted bucket, the S3 Gateway returns
> {{x-amz-server-side-encryption}} on write responses only when the request has
> that header (HDDS-17498). An object written without it, which is the default
> for SDK clients, is still encrypted with the bucket's key, and since
> HDDS-17500 {{HeadObject}} and {{GetObject}} report it as {{aws:kms}} with the
> key. But {{PutObject}}, {{CopyObject}}, {{CreateMultipartUpload}},
> {{UploadPart}}, {{UploadPartCopy}} and {{CompleteMultipartUpload}} return no
> header for it, so the write response says the object is not encrypted while
> the read response says it is.
> AWS S3 returns the encryption of the object on all of these responses, also
> when the request has no header. The write responses should report the same
> encryption as {{HeadObject}}.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]