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 2018/01/17 13:51:00 UTC

[jira] [Updated] (HADOOP-15176) Enhance IAM assumed role support in S3A client

     [ https://issues.apache.org/jira/browse/HADOOP-15176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-15176:
------------------------------------
    Environment: 




  was:
Followup HADOOP-15141 with

* Code to generate basic AWS json policies somewhat declaratively (no hand coded strings)
* Tests to simulate users with different permissions down the path of a single bucket
* test-driven changes to S3A client to handle user without full write up the FS tree
* move the new authenticator into the s3a sub-package "auth", where we can put more auth stuff (that base s3a package is getting way too big)



    Description: 
Followup HADOOP-15141 with

* Code to generate basic AWS json policies somewhat declaratively (no hand coded strings)
* Tests to simulate users with different permissions down the path of a single bucket
* test-driven changes to S3A client to handle user without full write up the FS tree
* move the new authenticator into the s3a sub-package "auth", where we can put more auth stuff (that base s3a package is getting way too big)

> Enhance IAM assumed role support in S3A client
> ----------------------------------------------
>
>                 Key: HADOOP-15176
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15176
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 3.1.0
>         Environment: 
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Major
>
> Followup HADOOP-15141 with
> * Code to generate basic AWS json policies somewhat declaratively (no hand coded strings)
> * Tests to simulate users with different permissions down the path of a single bucket
> * test-driven changes to S3A client to handle user without full write up the FS tree
> * move the new authenticator into the s3a sub-package "auth", where we can put more auth stuff (that base s3a package is getting way too big)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org