[
https://issues.apache.org/jira/browse/HADOOP-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315828#comment-15315828
]
Steve Loughran commented on HADOOP-13237:
-----------------------------------------
I don't see us being able to fix this; I've tried to bypass auth or insert fake
credentials, and the s3 reads of the public landsat dataset fail at the
{{verifyBucketExists()}} call. Command that out and it fails on the first read.
That's even though the datasets are visible over http.
Assumption: you really need credentials to use the AWS library, even if you are
accessing other people's public data. The client is presumably setting up auth
without negotiating over requirements at the far end, and bailing out early if
there aren't any. And, if you make up credentials, they get rejected s3 side
for being invalid.
> s3a initialization against public bucket fails if caller lacks any credentials
> ------------------------------------------------------------------------------
>
> Key: HADOOP-13237
> URL: https://issues.apache.org/jira/browse/HADOOP-13237
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> If an S3 bucket is public, anyone should be able to read from it.
> However, you cannot create an s3a client bonded to a public bucket unless you
> have some credentials; the {{doesBucketExist()}} check rejects the call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
