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 "Mingliang Liu (Jira)" <ji...@apache.org> on 2020/02/21 21:15:00 UTC
[jira] [Updated] (HADOOP-16794) S3 Encryption is always using
default region-specific AWS-managed KMS key
[ https://issues.apache.org/jira/browse/HADOOP-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingliang Liu updated HADOOP-16794:
-----------------------------------
Target Version/s: 3.0.4, 3.3.0, 3.1.4, 3.2.2, 2.10.1
[~stevel@apache.org] and [[~mukund-thakur] It seems this is also happening in Hadoop 2.x. Our engineer is reporting similar issue and I'll confirm that shortly. I think we can also include the target branch 2.10.
> S3 Encryption is always using default region-specific AWS-managed KMS key
> -------------------------------------------------------------------------
>
> 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
>
> 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