[
https://issues.apache.org/jira/browse/HADOOP-12548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990569#comment-14990569
]
Larry McCay commented on HADOOP-12548:
--------------------------------------
Cool.
Open Issues from the doc:
1. Do we want to protect the accessKey or just leave it as is? The change
described above enables you to protect it if you like and it shortens the
target URI without requiring any userInfo. You can still not provision it and
provide it alone in the userInfo too - which reduces the provisioning steps
above to only the accessSecret step.
2. Are the current Hadoop providers sufficient for the usecase or do we want to
add some support for AWS specific providers?
#1 is interesting considering the implementation in S3Credentials doesn't
protect accessKey. This could end up with a couple possibilities:
a. only the secret will be protected for s3:// and s3n:// and both would be
supported for s3a://
b. we change S3Credentials to also protect the accessKey and they will all be
the same but it would affect s3n:// as well
c. we only protect secret in s3a:// and all three are the same but s3n:// isn't
affected
> read s3 creds from a file
> -------------------------
>
> Key: HADOOP-12548
> URL: https://issues.apache.org/jira/browse/HADOOP-12548
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/s3
> Reporter: Allen Wittenauer
> Attachments: CredentialProviderAPIforS3FS.pdf
>
>
> It would be good if we could read s3 creds from a file rather than via a java
> property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
