[ 
https://issues.apache.org/jira/browse/HADOOP-12807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315662#comment-15315662
 ] 

Hadoop QA commented on HADOOP-12807:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} 
| {color:red} HADOOP-12807 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12788166/HADOOP-12807-1.patch |
| JIRA Issue | HADOOP-12807 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/9663/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> S3AFileSystem should read AWS credentials from environment variables
> --------------------------------------------------------------------
>
>                 Key: HADOOP-12807
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12807
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 2.7.2
>            Reporter: Tobin Baker
>            Priority: Minor
>         Attachments: HADOOP-12807-1.patch
>
>
> Unlike the {{DefaultAWSCredentialsProviderChain}} in the AWS SDK, the 
> {{AWSCredentialsProviderChain}} constructed by {{S3AFileSystem}} does not 
> include an {{EnvironmentVariableCredentialsProvider}} instance. This prevents 
> users from supplying AWS credentials in the environment variables 
> {{AWS_ACCESS_KEY_ID}} and {{AWS_SECRET_ACCESS_KEY}}, which is the only 
> alternative in some scenarios.
> In my scenario, I need to access S3 from within a test running in a CI 
> environment that does not support IAM roles but does allow me to supply 
> encrypted environment variables. Thus, the only secure approach I can use is 
> to supply my AWS credentials in environment variables (plaintext 
> configuration files are out of the question).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to