Modify check_bucket method from AWSServerAccess #16116
Merged
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.
Description
AWSServerAccess integration was not processing logs found in the root folder of the bucket unless it had folders inside of it.
Bug and Fix is described here:
Fix consist in evaluating existence of "Contents" list after getting Bucket Objects.
Logs/Alerts example
Until now, when trying to get server access S3 bucket objects without a folder existing in the root folder, this error would appear:
Now logs are found when there are no folders in root of Bucket as seen on image,
S3 Bucket Image:
Tests