Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.2.1
Description
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.
Attachments
Issue Links
- causes
-
HADOOP-17167 ITestS3AEncryptionWithDefaultS3Settings fails if default bucket encryption != KMS
- Resolved
- is related to
-
HADOOP-17966 S3A SSE-KMS inconsistency issue during rename
- Resolved
- links to