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

S3/IAM connect to "folder" #6229

Closed
cyberduck opened this issue Sep 15, 2011 · 4 comments
Closed

S3/IAM connect to "folder" #6229

cyberduck opened this issue Sep 15, 2011 · 4 comments
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Sep 15, 2011

994529c created the issue

With credentials that are authorized to a particular path, I get "I/O Error: Connection failed. Cannot read container configuration".

The config is not completely vanilla and I do have issues with several other clients as well (Cloudberry, S3Browser) but can act normally with some others (Transmit, S3Fox).

I will attach my IAM policy, Cyberduck connection config, and Cyberduck log output. Please let me know if I can provide anything more. I have replaced my real bucket name with "bucket-name" but that is the only change.

Also: I get the same error with "*" for actions in the attached IAM policy.

I am using OSX 10.6.8 and Cyberduck 4.1.2.

  • Jim

Attachments

@cyberduck
Copy link
Collaborator Author

cyberduck commented Sep 15, 2011

@dkocher commented

As a workaround add CloudFront read permission to the policy.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Sep 15, 2011

994529c commented

Adding this didn't seem to do it.

{
      "Action": "cloudfront:*",
      "Effect": "Allow",
      "Resource": "*"
}

The bucket itself doesn't have anything about CloudFront permissions. Assume that's not part of what you're recommending?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 7, 2011

@dkocher commented

Sorry for not replying earlier. I am just investigating this issue. We are sending a HEAD request against the bucket to test the bucket is accessible given the login credentials. This fails for this bucket because the IAM user does not have read permission for the bucket itself.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 7, 2011

@dkocher commented

In 41d1cba.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants