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 - allow IAM roles without root listing? #9635

Closed
cyberduck opened this issue Jul 26, 2016 · 1 comment
Closed

S3 - allow IAM roles without root listing? #9635

cyberduck opened this issue Jul 26, 2016 · 1 comment
Assignees
Labels
enhancement fixed low priority s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Jul 26, 2016

2d2570c created the issue

Before the last update we could use our IAM account for controlling access to just a specific bucket by setting the right initial bucket to connect to in the connection settings. (The IAM role is not allowed to list all the buckets - least privilige access for optimum security!)

Since the last update this does not work anymore,
according to the documentation this should not have worked in the first place, stating that the accounts must have root access.

This is really counter optimum security practice and since it used to work we where hoping if this might be something to bring back in future versions?

cheers!

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jul 26, 2016

@dkocher commented

I think what you see is an error because of missing permissions to list multipart uploads. This should now fail silently with 7ffc8d2. Please test with the current snapshot build.

@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
enhancement fixed low priority s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants