[HADOOP-9384] Update S3 native fs implementation to use AWS SDK to support authorization through roles

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Component/s: fs/s3
• Labels: BB2015-05-TBR

Environment

Locally: RHEL 6, AWS S3
Remotely: AWS EC2 (RHEL 6), AWS S3

• Assignee: Unassigned
• Reporter: D. Granit
• Created: 08/Mar/13 11:07
• Updated: 05/Jan/17 19:44
• Resolved: 07/May/15 09:53

Description

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.

Issue Links

• is duplicated by: HADOOP-11038 Support AWS roles to talk to AWS-S3 largely for cross-AWS-account integration
• is related to: HADOOP-10400 Incorporate new S3A FileSystem implementation
• is required by: FLUME-1691 Allow use of EC2 roles with S3 sink