Cherry-pick #26832 to 7.x: Add Proxy settings to AWS Common #28217
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 #26832 to 7.x branch. Original message:
What does this PR do?
Adds the ability to set a proxy to the AWS SDK config.
Why is it important?
This is useful when the Beats outbound connections need to go through a proxy but don't want it to affect other inputs/outputs. When using the HTTP_PROXY env variable, this also affects the Beats output to Elasticsearch. Having a dedicated setting allows only the AWS requests to be proxied and not affect any other input/output.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs