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 "Steve Loughran (Jira)" <ji...@apache.org> on 2020/03/02 17:33:00 UTC
[jira] [Commented] (HADOOP-16794) S3A reverts KMS encryption to the
bucket's default KMS key in rename/copy
[ https://issues.apache.org/jira/browse/HADOOP-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049471#comment-17049471 ]
Steve Loughran commented on HADOOP-16794:
-----------------------------------------
OK, merged in to trunk...feel free to backport
> S3A reverts KMS encryption to the bucket's default KMS key in rename/copy
> -------------------------------------------------------------------------
>
> Key: HADOOP-16794
> URL: https://issues.apache.org/jira/browse/HADOOP-16794
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.1
> Reporter: Mukund Thakur
> Assignee: Mukund Thakur
> Priority: Major
> Fix For: 3.3.0
>
>
> When using (bucket-level) S3 Default Encryption with SSE-KMS and a CMK, all files uploaded via the HDFS {{FileSystem}} {{s3a://}} scheme receive the wrong encryption key, always falling back to the region-specific AWS-managed KMS key for S3, instead of retaining the custom CMK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org