-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
fix: fix iam permissions to retrieve logs from aws s3 #9798
fix: fix iam permissions to retrieve logs from aws s3 #9798
Conversation
Signed-off-by: Lukas Heppe <lukas.heppe@agido.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the difference?
It's the same problem as in the SO post below. You are allowed to perform actions on the resources (objects) within the bucket (marked by the wildcard *), but you are not allowed to list the bucket itself. If you want to access the logs of some worklfow via UI, the S3 client seems to try to perform a "ListBucket" operation, but it is not allowed to do so. Therefore, this policy explicitly whitelists this action. I will try to find the respective codeline later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for helping to figure out what the right policy settings should be! What you've written makes sense to me.
Thanks for clarifying! |
You are welcome! Thank you providing such nice projects 👍 |
Signed-off-by: juchao <juchao@coscene.io>
Signed-off-by: Lukas Heppe lukas.heppe@agido.com
Fixes #TODO
Please do not open a pull request until you have checked ALL of these:
make pre-commit -B
to fix codegen and lint problems.If changes were requested, and you've made them, dismiss the review to get it reviewed again.
Description
When using the IAM policy provided in the docs I couldn't view the logs via UI. By allowing the
ListBucket
Policy on the bucket instead of the objects within, I was able to retrieve those.The prinicple is also described in the AWS Blog post https://aws.amazon.com/de/blogs/security/writing-iam-policies-how-to-grant-access-to-an-amazon-s3-bucket/.