[HADOOP-13237] s3a initialization against public bucket fails if caller lacks any credentials

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: fs/s3
• Release Note: S3A now supports read access to a public S3 bucket even if the client does not configure any AWS credentials. See the documentation of configuration property fs.s3a.aws.credentials.provider for further details.
• Assignee: Chris Nauroth
• Reporter: Steve Loughran
• Created: 03/Jun/16 20:45
• Updated: 30/Aug/16 01:14
• Resolved: 09/Jun/16 16:58

Description

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.