Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Tue, 8 Aug 2017 04:55:00 +0000 (UTC)
From: "Franco (JIRA)" <jira@apache.org>
To: issues@nifi.apache.org
Message-ID: <JIRA.13091786.1501654904000.114730.1502168100083@Atlassian.JIRA>
In-Reply-To: <JIRA.13091786.1501654904000@Atlassian.JIRA>
References: <JIRA.13091786.1501654904000@Atlassian.JIRA> <JIRA.13091786.1501654904346@jira-lw-us.apache.org>
Subject: [jira] [Updated] (NIFI-4256) Add support for all AWS S3 Encryption
 Options
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 08 Aug 2017 04:55:09 -0000


     [ https://issues.apache.org/jira/browse/NIFI-4256?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Franco updated NIFI-4256:
-------------------------
    Description:=20
NiFi currently only supports=C2=A0SSE-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 avai=
lable 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 workf=
lows.

Existing flows using the Server Side Encryption option will still work as i=
s but will be overridden if a service is added.

  was:
NiFi currently only supports=C2=A0SSE-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 avai=
lable 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 workf=
lows.

Note: We will not support the existing server-side-encryption option so thi=
s will be a breaking change for existing users.=20


> 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
>              Labels: aws, aws-s3, security
>             Fix For: 1.4.0
>
>
> NiFi currently only supports=C2=A0SSE-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 av=
ailable 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 Encryptio=
n Service. This will allow users to reuse "encryption" across different wor=
kflows.
> 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)