Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/362
@miquillo , what do you think about using
[ClientConfiguration::setSignerOverride()](http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/ClientConfiguration.html#setSignerOverride(java.lang.String))
to control the signature version? One of the advantages I see to it is better
isolation for the processor vs. any other NiFi AWS processors. I'm a bit
worried that one PutS3Object processor using SSE-KMS would change the settings
other processors running at the same time. I believe an appropriate location
to do this would be in AbstractS3Processor::createClient(). That would allow
the configuration code to be shared, while the configured value would remain
specific to individual processors.
But I'm not sure I agree with configuring the version as a true/false
setting for signature version 4. I would recommend a list of values:
* AWS SDK default (as the default selection)
* Signature v2
* Signature v4
That leaves room for the AWS SDK default to change if/when we upgrade to a
newer SDK, and it would allow for users to explicitly request either v4 or v2
to match whatever features and endpoint they are using. What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
