pvillard31 opened a new pull request, #10659: URL: https://github.com/apache/nifi/pull/10659
# Summary NIFI-15359 - Upgrade S3 Encryption Client to 4.0.0 Upgrade the S3 Encryption Client to latest 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) {code} 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 - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### 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](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
