nifi icon indicating copy to clipboard operation
nifi copied to clipboard

NIFI-15359 - Upgrade S3 Encryption Client to 4.0.0

Open pvillard31 opened this issue 1 month ago • 0 comments

Summary

NIFI-15359 - Upgrade S3 Encryption Client to 4.0.0

It includes a breaking change as explained here:

https://github.com/aws/amazon-s3-encryption-client-java/releases/tag/v4.0.0

builderV4() now defaults to commitmentPolicy (REQUIRE_ENCRYPT_REQUIRE_DECRYPT) and encryptionAlgorithm (ALG_AES_256_GCM_HKDF_SHA512_COMMIT_KEY)

It means that we may be in a situation where we could not decrypt existing data with FetchS3 because of the new default.

Proposition is to expose a new property for the user to select the commitment policy but to still apply the new default of the client given the security posture that it implies.

The recommendation for the user, would be to set the property with:

Scenario Recommended Policy
New deployment (no legacy data) Require Encrypt Require Decrypt (default)
Migration period (need to read legacy + write new) Require Encrypt Allow Decrypt
Read-only access to legacy data Forbid Encrypt Allow Decrypt

This breaking change would be documented in the migration guide with guidance on what value to select for this new property if needed.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • [ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

  • [ ] Pull Request based on current revision of the main branch
  • [ ] Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • [ ] Build completed using ./mvnw clean install -P contrib-check
    • [ ] JDK 21
    • [ ] JDK 25

Licensing

  • [ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • [ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • [ ] Documentation formatting appears as expected in rendered files

pvillard31 avatar Dec 17 '25 11:12 pvillard31