[
https://issues.apache.org/jira/browse/NIFI-14593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953615#comment-17953615
]
Peter Turcsanyi commented on NIFI-14593:
----------------------------------------
[~xamarc] Thanks for the additional info that clarifies your use case. So you
are using an S3-compatible service and connecting to a custom, non-AWS region
which is not in the Region list.
A solution could be to add a new item in the Region list called 'Use Custom
Region' and to display a new property (Custom Region) to specify the region as
free text. It needs to be evaluated in more detail but should work.
The other option would be to add an optional upstream connection to ListS3 and
it could receive a "control" FlowFile which conveys the 's3.region' attribute
and triggers the listing. I feel it fits less well into the concept of List
processors but if there are (possibly) multiple configuration items to provide
for the processor (not only the region), it is also a considerable option.
> s3.region attribute not present in ListS3 processor
> ---------------------------------------------------
>
> Key: NIFI-14593
> URL: https://issues.apache.org/jira/browse/NIFI-14593
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: MARC Xavier
> Priority: Major
>
> The attribute "s3.region" is not present in the ListS3 processor while it is
> present in the other s3 processors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
