Cherry-pick #20887 to 7.x: additional bucket name validation for S3 bucket regex #21199
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.
Cherry-pick of PR #20887 to 7.x branch. Original message:
What does this PR do?
This is a bug fix when functionbeat errors out with a blanket error message. According to me, this error can be mitigated pretty early by validating the S3 bucket name by creating the regex patterns from the rules for bucket naming.
https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html#bucketnamingrules
Why is it important?
This will restrict users from shooting themselves in their foot when they pass an incorrect bucket name in the functionbeat configuration.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration files- no change to configuration file neededCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.~~ - haven't added to the changelog as this is just a bugfix, can do so if requiredAuthor's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs