nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (NIFI-4256) Add support for all AWS S3 Encryption Options
Date Tue, 08 Aug 2017 05:09:00 GMT


ASF GitHub Bot commented on NIFI-4256:

GitHub user baank opened a pull request:

    NIFI-4256 - Add support for all AWS S3 Encryption Options


You can merge this pull request into a Git repository by running:

    $ git pull NIFI-4256

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2066
commit 1f8df2da50846317513a5b1890f7568368b9eb14
Author: Naden Franciscus <>
Date:   2017-08-08T04:55:40Z

    NIFI-4256 - Add support for all AWS S3 Encryption Options


> Add support for all AWS S3 Encryption Options
> ---------------------------------------------
>                 Key: NIFI-4256
>                 URL:
>             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Ā SSE-S3 encryption (AES256).
> Support needs to be added for:
> * SSE-S3
> * SSE-C
> * 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

View raw message