You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/08/13 19:28:00 UTC

[jira] [Commented] (NIFI-4256) Add support for all AWS S3 Encryption Options

    [ https://issues.apache.org/jira/browse/NIFI-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906553#comment-16906553 ] 

ASF subversion and git services commented on NIFI-4256:
-------------------------------------------------------

Commit e841f4d5b7da7cf88cbb1805d351bf75ca8a3280 in nifi's branch refs/heads/master from Troy Melhase
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e841f4d ]

NIFI-4256 Adds AWS Encryption Controller Service.
NIFI-4256 Adds AWS S3 FlowFile encryption attributes, more javadocs,
better names.

This closes #3574.

Signed-off-by: Andy LoPresto <al...@apache.org>


> 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
>            Assignee: Troy Melhase
>            Priority: Major
>              Labels: aws, aws-s3, security
>         Attachments: Screenshot_20190706_115751.png
>
>          Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> 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
(v7.6.14#76016)