You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2019/08/22 16:30:00 UTC
[jira] [Resolved] (HADOOP-16470) Make last AWS credential provider
in default auth chain EC2ContainerCredentialsProviderWrapper
[ https://issues.apache.org/jira/browse/HADOOP-16470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-16470.
-------------------------------------
Fix Version/s: 3.3.0
Resolution: Fixed
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org