AWSX-1006 fix s3 listobject issue visible in CloudTrail #836
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.
What does this PR do?
Fix the wrong path declared in the CFT so the retry mechanism has access to the proper s3 prefix
Motivation
Issues reported by a few customers
Testing Guidelines
Additional Notes
I think the intent was to give
ListBucket
permission here but I'm a bit confused why we have 2 similar blockswith different actions an resource id here and here.
Also I see in this commit that the
ListBucket
was removed from the first block by an external contributor.In the change which was introduced 3 months ago to store and retry, there might be a mistake. IIUC, the call to list_objects uses the prefix
failed_events
while the template gives permission to the s3 prefixretry
The other prefix
log-group-cache
seems to be used properly from the other file you pointed out.Types of changes
Check all that apply