From common-issues-return-146898-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Jan 17 12:51:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 6066818066D for ; Wed, 17 Jan 2018 12:51:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 51379160C1B; Wed, 17 Jan 2018 11:51:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 94D71160C35 for ; Wed, 17 Jan 2018 12:51:04 +0100 (CET) Received: (qmail 52973 invoked by uid 500); 17 Jan 2018 11:51:03 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 52962 invoked by uid 99); 17 Jan 2018 11:51:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jan 2018 11:51:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 10E111A3CB0 for ; Wed, 17 Jan 2018 11:51:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.711 X-Spam-Level: X-Spam-Status: No, score=-100.711 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id VWvCp75BeBuj for ; Wed, 17 Jan 2018 11:51:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 321A15F570 for ; Wed, 17 Jan 2018 11:51:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BE3F5E12AB for ; Wed, 17 Jan 2018 11:51:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 540C8212FE for ; Wed, 17 Jan 2018 11:51:00 +0000 (UTC) Date: Wed, 17 Jan 2018 11:51:00 +0000 (UTC) From: "Steve Loughran (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-15141) Support IAM Assumed roles in S3A MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-15141?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 328656#comment-16328656 ]=20 Steve Loughran commented on HADOOP-15141: ----------------------------------------- Oh, OK. I had just been working on some changes :) * move the new authenticator to a new patch, s3a.auth * add a class alongside., "RoleModel" to actually build up the JSON to pump= out as valid AWS role policy * tests to understand what permissions * fix to innerDelete() so that if you can't create a mock parent dir marker= on a directory delete, it doesn't trigger a failure The latter means that If I only have write access to /user/stevel and I del= ete /user/stevel, if the attempt to create a /user/ marker fails, the delet= e still succeeds. Essentially, I'm adding support into S3A to handle the situation "user does= n't have write access to everywhere" via test-and-see, using this for the t= ests, with RoleModel there to set up the statements & policies properly. I'= ll no doubt need to play with: rename, MPU (large files, commit, commit -> = abort), s3guard. Apart from the move to the new package, no other changes to the authenticat= or itself, that' s just adding the ability to do the user lockdown Let me merge mine back in and do a followup =C2=A0 > Support IAM Assumed roles in S3A > -------------------------------- > > Key: HADOOP-15141 > URL: https://issues.apache.org/jira/browse/HADOOP-15141 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.0.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Major > Fix For: 3.1.0 > > Attachments: HADOOP-15141-001.patch, HADOOP-15141-002.patch, HADO= OP-15141-003.patch, HADOOP-15141-004.patch, HADOOP-15141-005.patch, HADOOP-= 15141-006.patch > > > Add the ability to use assumed roles in S3A > * Add a property fs.s3a.assumed.role.arn for the ARN of the assumed role > * add a new provider which grabs that and other properties and then creat= es a {{STSAssumeRoleSessionCredentialsProvider}} from it. > * This also needs to support building up its own list of aws credential = providers, from a different property; make the changes to S3AUtils for that > * Tests > * docs > * and have the AwsProviderList forward closeable to it. > * Get picked up automatically by DDB/s3guard -- 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