[
https://issues.apache.org/jira/browse/HADOOP-16470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913589#comment-16913589
]
Hudson commented on HADOOP-16470:
---------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17169 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17169/])
HADOOP-16470. Make last AWS credential provider in default auth chain (stevel:
rev 61b2df23317767833b327e5f69dbe73e8d4f0fc1)
* (edit) hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
* (edit)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/auth/IAMInstanceCredentialsProvider.java
* (edit) hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
* (add)
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/SharedInstanceCredentialProvider.java
> Make last AWS credential provider in default auth chain
> EC2ContainerCredentialsProviderWrapper
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-16470
> URL: https://issues.apache.org/jira/browse/HADOOP-16470
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Fix For: 3.3.0
>
>
> There's a new credential provider in the AWS SDK,
> {{com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper}}
> this is designed to work within AWS containers as well as EC2 VMs, using env
> vars to find container credentials first, falling back to the IAM metadata
> service. This way, when deployed in a container or EC2 VM, it will always
> find the session credentials for the deployed IAM Role
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
