[
https://issues.apache.org/jira/browse/NIFI-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555095#comment-15555095
]
ASF GitHub Bot commented on NIFI-2799:
--------------------------------------
Github user ktseytlin commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1112#discussion_r82389180
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/credentials/provider/factory/CredentialPropertyDescriptors.java
---
@@ -44,7 +45,7 @@
.allowableValues("true", "false")
.defaultValue("false")
.description("If true, uses the Default Credential chain,
including EC2 instance profiles or roles, " +
- "environment variables, default user credentials, etc.")
+ "environment variables, default user credentials,
etc.")
--- End diff --
Yes, it's just a formatting change to make it clear that the break in the
string means that it's still part of the description.
> 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)
