[
https://issues.apache.org/jira/browse/NIFI-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236730#comment-16236730
]
ASF GitHub Bot commented on NIFI-4256:
--------------------------------------
GitHub user baank opened a pull request:
https://github.com/apache/nifi/pull/2248
NIFI-4256 - Add support for all AWS S3 Encryption Options
Rebased and updated to include feedback discussed in the JIRA.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/baank/nifi master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2248.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2248
----
commit 0e9f62710e2ec08df9ca749d0c2b98f745b26314
Author: Naden Franciscus <[email protected]>
Date: 2017-11-02T22:28:27Z
NIFI-4256 - Add support for all AWS S3 Encryption Options
----
> Add support for all AWS S3 Encryption Options
> ---------------------------------------------
>
> Key: NIFI-4256
> URL: https://issues.apache.org/jira/browse/NIFI-4256
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.2.0
> Reporter: Franco
> Priority: Major
> Labels: aws, aws-s3, security
>
> NiFi currently only supports SSE-S3 encryption (AES256).
> Support needs to be added for:
> * SSE-S3
> * SSE-KMS
> * SSE-C
> * CSE-KMS CMK
> * CSE-Master Key
> With all of the appropriate configuration options and such that SSE is
> available only for PutS3Object whilst CSE is available also for FetchS3Object.
> Given that this will add another 20 or so UI properties the intention is to
> split it into a Client Side Encryption Service and Server Side Encryption
> Service. This will allow users to reuse "encryption" across different
> workflows.
> Existing flows using the Server Side Encryption option will still work as is
> but will be overridden if a service is added.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
