hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15525) s3a: clarify / improve support for mixed ACL buckets
Date Sat, 09 Jun 2018 13:27:00 GMT

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

Steve Loughran commented on HADOOP-15525:

+the other permissions issue to handle is *caller doesn't have access to the KMS key to read
a file. rename() will fail there in the COPY; delete & HEAD checks will be OK. I think
the error is slightly different...it'd be good to actually expand that text better to make
clear its a KMS permission, so not mislead people into thinking it is bucket access. I don't
know about other people, but it's confused me in the past

> s3a: clarify / improve support for mixed ACL buckets
> ----------------------------------------------------
>                 Key: HADOOP-15525
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15525
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 3.0.0
>            Reporter: Aaron Fabbri
>            Assignee: Aaron Fabbri
>            Priority: Major
> Scenario: customer wants to only give a Hadoop cluster access to a subtree of an S3
> For example, assume Hadoop uses some IAM identity "hadoop", which they wish to grant
full permission to everything under the following path:
> s3a://bucket/a/b/c/hadoop-dir
> they don't want hadoop user to be able to read/list/delete anything outside of the hadoop-dir
> Problems: 
> To implement the "directory structure on flat key space" emulation logic we use to present
a Hadoop FS on top of a blob store, we need to create / delete / list ancestors of {{hadoop-dir}}.
(to maintain the invariants (1) zero-byte object with key ending in '/' exists iff empty directory
is there and (2) files cannot live beneath files, only directories.)
> I'd like us to (1) document a an example with IAM ACLs policies that gets this basic
functionality, and consider (2) making improvements to make this easier.
> We've discussed some of these issues before but I didn't see a dedicated JIRA.

This message was sent by Atlassian JIRA

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

View raw message