[
https://issues.apache.org/jira/browse/NIFI-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072957#comment-15072957
]
Mans Singh commented on NIFI-1325:
----------------------------------
@tkurc - An alternative could be on every FetchS3Object.onTrigger, we make an
explicit call to onScheduled which will refresh the credentails by making a
call to createClient. If this affects only cases where we have temp creds we
can make this call in onTrigger conditional only for cases where role arn is
set. But I think keeping it simple (and unconditional) seems fine since we
don't expect so many triggering calls to S3.
Another alternative is to add onTrigger to the AbstractS3Processor with call to
onScheduled so that it is available to all S3 processors. All subclasses would
need to super.onTrigger in their onTrigger method.
Please let me know your thoughts and if there is another suggestion or
recommendation and I will start reworking on the impl.
Thanks again.
> Enhance AWS S3 fetch to access bucket across accounts
> -----------------------------------------------------
>
> Key: NIFI-1325
> URL: https://issues.apache.org/jira/browse/NIFI-1325
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 0.4.1
> Environment: All
> Reporter: Mans Singh
> Assignee: Tony Kurc
> Priority: Minor
> Labels: easyfix
> Fix For: 0.4.1
>
> Attachments: nifi-1325.patch.zip
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The AWS S3 Fetch Object component does not allow access to bucket across
> accounts. AWS S3 Fetch Object with can be enhanced to provide this
> functionality by using assume role session/credentials
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
