[
https://issues.apache.org/jira/browse/HADOOP-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297046#comment-15297046
]
Sean Mackrory commented on HADOOP-12537:
----------------------------------------
I'm getting a 301 Moved Permanently as though my bucket and S3 endpoint weren't
matching up, but I've double-checked they're right. I also just tested with
version 1.11.2 of the SDK and did not have success. I'm less concerned by the
fact that it seems to require matching STS and S3 regions much of the time,
although it sounds from my previous comments like it was more flexible last
time around.
> 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.001.patch, HADOOP-12537.002.patch,
> HADOOP-12537.003.patch, HADOOP-12537.004.patch, HADOOP-12537.diff,
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
