Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 7 May 2015 09:54:00 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12636002.1362740857000.34434.1430992440392@Atlassian.JIRA>
In-Reply-To: <JIRA.12636002.1362740857000@Atlassian.JIRA>
References: <JIRA.12636002.1362740857000@Atlassian.JIRA>
 <JIRA.12636002.1362740857188@arcas>
Subject: [jira] [Updated] (HADOOP-9384) Update S3 native fs implementation
 to use AWS SDK to support authorization through roles
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran updated HADOOP-9384:
-----------------------------------
       Resolution: Won't Fix
    Fix Version/s: 2.7.1
         Assignee:     (was: D. Granit)
           Status: Resolved  (was: Patch Available)

I'm closing this as a wontfix; s3a is the aws-tookit based successor to s3n, s3n is sensitive enough to change that we're scared of touching it out of fear of introducing yet-another-regression.

thanks for your contribution...don't be afraid to submit changes to the s3a code to suit your need, as that one we are actively evolving/tuning. Even testing is welcome.

> Update S3 native fs implementation to use AWS SDK to support authorization through roles
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9384
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9384
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>         Environment: Locally: RHEL 6, AWS S3
> Remotely: AWS EC2 (RHEL 6), AWS S3
>            Reporter: D. Granit
>            Priority: Minor
>              Labels: BB2015-05-TBR
>             Fix For: 2.7.1
>
>         Attachments: HADOOP-9384-v2.patch, HADOOP-9384.patch
>
>
> Currently the S3 native implementation {{org.apache.hadoop.fs.s3native.Jets3tNativeFileSystemStore}} requires credentials to be set explicitly. Amazon allows setting credentials for instances instead of users, via roles. Such are rotated frequently and kept in a local cache all of which is handled by the AWS SDK in this case the {{AmazonS3Client}}. The SDK follows a specific order to establish whether credentials are set explicitly or via a role:
> - Environment Variables: AWS_ACCESS_KEY_ID and AWS_SECRET_KEY
> - Java System Properties: aws.accessKeyId and aws.secretKey
> - Instance Metadata Service, which provides the credentials associated with the IAM role for the EC2 instance
> as seen in http://docs.aws.amazon.com/IAM/latest/UserGuide/role-usecase-ec2app.html
> To support this feature the current {{NativeFileSystemStore}} implementation needs to be altered to use the AWS SDK instead of the JetS3t S3 libraries.
> A request for this feature has previously been raised as part of the Flume project (FLUME-1691) where the HDFS on top of S3 implementation is used as a manner of logging into S3 via an HDFS Sink.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)