Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15620 Über-jira: S3A phase VI: Hadoop 3.3 features
  3. HADOOP-16794

S3A reverts KMS encryption to the bucket's default KMS key in rename/copy

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.2.1
    • 3.3.0
    • fs/s3

    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

          Sub-task - The sub-task of the issue HADOOP-17167 ITestS3AEncryptionWithDefaultS3Settings fails if default bucket encryption != KMS

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-17966 S3A SSE-KMS inconsistency issue during rename

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #1823

          Web Link GitHub Pull Request #1843

          Web Link GitHub Pull Request #1875

          Activity

            People

              mukund-thakur Mukund Thakur
              mukund-thakur Mukund Thakur
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h 10m
                  1h 10m