[ https://issues.apache.org/jira/browse/NIFI-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110780#comment-16110780 ]
Pierre Villard commented on NIFI-4256: -------------------------------------- I'm a bit worried about: bq. Note: We will not support the existing server-side-encryption option so this will be a breaking change for existing users. If this is a breaking change and if existing workflows are going to behave differently after a NiFi upgrade, this change might need to wait a v2.0.0 release. > 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Ā 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. > Note: We will not support the existing server-side-encryption option so this > will be a breaking change for existing users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)