[
https://issues.apache.org/jira/browse/IMPALA-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110232#comment-17110232
]
Steve Loughran commented on IMPALA-3717:
----------------------------------------
this has long been done in s3a. please close.
> Additional s3 setting to allow encryption algorithm
> ---------------------------------------------------
>
> Key: IMPALA-3717
> URL: https://issues.apache.org/jira/browse/IMPALA-3717
> Project: IMPALA
> Issue Type: New Feature
> Components: Infrastructure
> Affects Versions: Impala 2.6.0
> Reporter: Pavas Garg
> Priority: Minor
> Labels: s3
>
> distcp and impala requires an additional s3 setting on the configuration
> 1. To allow not only the selection of encryption algorithm but
> 2. Also the master key name (which will be held within the AWS KMS).
> The S3 API has the following option on the rest service to achieve this
> "x-amz-server-side-encryption-aws-kms-key-id".
> This should just be a case of adding the config option and passing this onto
> the S3 call.
> Please see Server-Side Encryption Specific Request Headers on -
> http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]