You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Troy Melhase (JIRA)" <ji...@apache.org> on 2019/07/06 20:10:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Troy Melhase updated NIFI-4256:
-------------------------------
    Status: Patch Available  (was: Open)

> 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
>          Time Spent: 0.5h
>  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.3#76005)