Details

    • 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
    • Labels:
      None
    • 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.

      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.

        Attachments

        1. HADOOP-13237.001.patch
          4 kB
          Chris Nauroth
        2. HADOOP-13237-branch-2.002.patch
          10 kB
          Chris Nauroth

          Activity

            People

            • Assignee:
              cnauroth Chris Nauroth
              Reporter:
              stevel@apache.org Steve Loughran
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: