VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • 2.8.0
    • None
    • fs/s3
    • None

    Description

      There's a whole section in s3a troubleshooting because requests can get auth failures for many reasons, including

      • no credentials
      • wrong credentials
      • right credentials, wrong bucket
      • wrong endpoint for v4 auth
      • trying to use private S3 server without specifying endpoint, so AWS being hit
      • clock out
      • joda time
        ....

      We can aid with debugging this by including as much as we can in in the message and a URL To a new S3A bad auth wiki page.

      Info we could include

      • bucket
      • fs.s3a.endpoint
      • nslookup of endpoint
      • Anything else relevant but not a security risk

      Goal; people stand a chance of working out what is failing within a bounded time period

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            stevel@apache.org Steve Loughran
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment