You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by GitBox <gi...@apache.org> on 2020/02/04 13:03:21 UTC

[GitHub] [hadoop] davidarcher edited a comment on issue #1823: HADOOP-16794 S3 Encryption key is not getting set properly during put operation.

davidarcher edited a comment on issue #1823: HADOOP-16794 S3 Encryption key is not getting set properly during put operation.
URL: https://github.com/apache/hadoop/pull/1823#issuecomment-581898688
 
 
   Hi @mukund-thakur and thank you for offering up this PR. I've run into this bug and while removing the SSE header when copying will work (assuming the bucket has that KMS set as the default encryption on the bucket), another option could be to copy both the SSE header `x-amz-server-side-encryption` as well as the `x-amz-server-side-encryption-aws-kms-key-id` header that specifies the specific key to use. That would ensure that files don't revert to using the generic `aws/s3` KMS key and might be less likely to cause issues in edge cases. Just my $0.02... :)

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org