hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Sautins (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9293) For S3 use credentials file
Date Fri, 08 Feb 2013 23:45:12 GMT

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

Andy Sautins updated HADOOP-9293:
---------------------------------

    Description: 
The following document describes the current way that S3 credentials can be specified ( http://wiki.apache.org/hadoop/AmazonS3
).  In summary they are:

  * in the S3 URI.
  * in the hadoop-site.xml file as 
  ** fs.s3.awsAccessKeyId
  ** fs.s3.awsSecretAccessKey 
  ** fs.s3n.awsAccessKeyId
  ** fs.s3n.aswSecretAccessKey

The amazon EMR tool elastic-mapreduce already provide the ability to use a credentials file
( see http://s3.amazonaws.com/awsdocs/ElasticMapReduce/latest/emr-qrc.pdf ).  

I would propose that we allow roughly the same access to credentials through a credentials
file that is currently provided by elastic-mapreduce.  This should allow for centralized administration
of credentials which should be positive for security.

I propose the following properties:

   <property><name>f3.s3.awsCredentialsFile</name><value>/path/to/file</value></property>
   <property><name>fs.s3n.awsCredentialsFile</name><value>/path/to/file</value></property>



  was:
The following document describes the current way that S3 credentials can be specified ( http://wiki.apache.org/hadoop/AmazonS3
).  In summary they are:

  - in the S3 URI.
  - in the hadoop-site.xml file as 
     - fs.s3.awsAccessKeyId
     - fs.s3.awsSecretAccessKey 
     - fs.s3n.awsAccessKeyId
     - fs.s3n.aswSecretAccessKey

The amazon EMR tool elastic-mapreduce already provide the ability to use a credentials file
( see http://s3.amazonaws.com/awsdocs/ElasticMapReduce/latest/emr-qrc.pdf ).  

I would propose that we allow roughly the same access to credentials through a credentials
file that is currently provided by elastic-mapreduce.  This should allow for centralized administration
of credentials which should be positive for security.

I propose the following properties:

   <property><name>f3.s3.awsCredentialsFile</name><value>/path/to/file</value></property>
   <property><name>fs.s3n.awsCredentialsFile</name><value>/path/to/file</value></property>



    
> For S3 use credentials file
> ---------------------------
>
>                 Key: HADOOP-9293
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9293
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 1.0.2
>         Environment: Linux
>            Reporter: Andy Sautins
>            Priority: Minor
>              Labels: features, newbie
>         Attachments: HADOOP-9293.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The following document describes the current way that S3 credentials can be specified
( http://wiki.apache.org/hadoop/AmazonS3 ).  In summary they are:
>   * in the S3 URI.
>   * in the hadoop-site.xml file as 
>   ** fs.s3.awsAccessKeyId
>   ** fs.s3.awsSecretAccessKey 
>   ** fs.s3n.awsAccessKeyId
>   ** fs.s3n.aswSecretAccessKey
> The amazon EMR tool elastic-mapreduce already provide the ability to use a credentials
file ( see http://s3.amazonaws.com/awsdocs/ElasticMapReduce/latest/emr-qrc.pdf ).  
> I would propose that we allow roughly the same access to credentials through a credentials
file that is currently provided by elastic-mapreduce.  This should allow for centralized administration
of credentials which should be positive for security.
> I propose the following properties:
>    <property><name>f3.s3.awsCredentialsFile</name><value>/path/to/file</value></property>
>    <property><name>fs.s3n.awsCredentialsFile</name><value>/path/to/file</value></property>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message