Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Failed to read attributes - 301 Moved Permanently but no location header #11640

Closed
cyberduck opened this issue Mar 31, 2021 · 5 comments
Closed

Failed to read attributes - 301 Moved Permanently but no location header #11640

cyberduck opened this issue Mar 31, 2021 · 5 comments
Assignees
@dkocher
Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Milestone
7.9.0

Comments

@cyberduck
Copy link
Collaborator

4840c0a created the issue

Cannot download from a bucket in us-east-2. When I try, I get "Failure to read attributes of . Received redirect response HTTP/1.1 301 Moved Permanently but no location header."

When I expand the Error window, I see that it is trying to use the URL .s3.dualstack.us-east-1.amazonaws.com

The Location header may be missing, but I do see a
x-amz-bucket-region: us-east-2 response header in there that could be helpful.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

We are querying the bucket region using GET /?location= HTTP/1.1. Can you verify this requests succeeds meaning that your IAM policy allows to query the region of a bucket. This requires the user has the s3:GetBucketLocation permission.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please provide the full log output if you are unable to resolve.

@cyberduck
Copy link
Collaborator Author

4840c0a commented

Replying to [comment:1 dkocher]

The credentials in question have the AmazonS3FullAccess built-in policy attached. That policy contains:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "s3:*",
            "Resource": "*"
        }
    ]
}

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In e5f8881.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug fixed high priority s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
7.9.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck