Add permission for buckets - #948
Merged
Merged
Conversation
xschildw
commented
Sep 21, 2026
| "Resource": "*" | ||
| } | ||
| ] | ||
| }, |
Contributor
Author
There was a problem hiding this comment.
Not sure why it shows this diff, it's in 607... and I see the tag so it go applied...
john-hill
approved these changes
Sep 21, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The instance is failing on ListBucket("arn:aws:s3:::elasticbeanstalk-us-east-1-325565585839"), the policy supports files but not buckets so adding support for buckets.
Note1: repo/workers not affected because they have wider perms on S3
Note2: perms should be more restricted but that's out of scopeq