[
https://issues.apache.org/jira/browse/HADOOP-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HADOOP-12537:
-----------------------------------
Attachment: HADOOP-12537.diff
Attaching a patch that I think may do the trick. I've tested it against several
different S3 and STS endpoints (including Frankfurt in both cases). Not sure
how best to make sure it's skipped when using a non-AWS option, although that
is important since an STS implementation is probably uncommon outside of AWS
too. Need to do a bit more testing tomorrow before I really think this is worth
consideration, just posting what I have now in case I can't actually get to it
tomorrow...
> s3a: Add flag for session ID to allow Amazon STS temporary credentials
> ----------------------------------------------------------------------
>
> Key: HADOOP-12537
> URL: https://issues.apache.org/jira/browse/HADOOP-12537
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/s3
> Affects Versions: 2.7.1
> Reporter: Sean Mackrory
> Priority: Minor
> Attachments: HADOOP-12537.diff
>
>
> Amazon STS allows you to issue temporary access key id / secret key pairs for
> your a user / role. However, using these credentials also requires specifying
> a session ID. There is currently no such configuration property or the
> required code to pass it through to the API (at least not that I can find) in
> any of the S3 connectors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
