You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "James Wing (JIRA)" <ji...@apache.org> on 2016/09/21 14:28:20 UTC
[jira] [Assigned] (NIFI-2799) AWS Credentials for Assume Role Need
Proxy
[ https://issues.apache.org/jira/browse/NIFI-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Wing reassigned NIFI-2799:
--------------------------------
Assignee: James Wing
> AWS Credentials for Assume Role Need Proxy
> ------------------------------------------
>
> Key: NIFI-2799
> URL: https://issues.apache.org/jira/browse/NIFI-2799
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Keren Tseytlin
> Assignee: James Wing
> Priority: Minor
> Fix For: 1.1.0
>
>
> As a user of Nifi, when I want to enable cross account fetching of S3 objects I need the proxy variables to be set in order to generate temporary AWS tokens for STS:AssumeRole.
> Within some enterprise environments, it is necessary to set the proxy variables prior to running AssumeRole methods. Without this being set, the machine in VPC A times out on generating temporary keys and is unable to assume a role as a machine in VPC B.
> This ticket arose from this conversation: http://apache-nifi-developer-list.39713.n7.nabble.com/Nifi-Cross-Account-Download-With-A-Profile-Flag-td13232.html#a13252
> Goal: There are files stored in an S3 bucket in VPC B. My Nifi machines are in VPC A. I want Nifi to be able to get those files from VPC B. VPC A and VPC B need to be communicating in the FetchS3Object component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)