[
https://issues.apache.org/jira/browse/NIFI-10969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Palfy updated NIFI-10969:
-------------------------------
Fix Version/s: 1.20.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Create extension point for Signer Override in AWS S3 processors
> ---------------------------------------------------------------
>
> Key: NIFI-10969
> URL: https://issues.apache.org/jira/browse/NIFI-10969
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Peter Turcsanyi
> Assignee: Peter Turcsanyi
> Priority: Major
> Labels: aws
> Fix For: 1.20.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> AWS S3 processors have the {{Signer Override}} property where V4 or V2
> signers can be configured. These signers are part of the AWS SDK for Java
> library.
> However, some special use cases require to use a user defined signer (e.g
> when a gateway is located between NiFi and the AWS Service and it changes the
> request).
> To support these scenarios, add an extension point in the processors for
> configuring user provided custom signers.
> The S3 processors may be configured to use Assume Role credentials which
> accesses the STS service in the backround. For this reason, the custom signer
> extension point is needed for that service too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
