x-pack/filebeat/input/awss3 Add AWS Endpoint resolver

[bhapas]

What does this PR do?

This PR adds endpoint resolver to the AWS config.

Why is it important?

By adding custom endpoint resolver config options to AWSConfig , It becomes flexible to use the input against any AWS like resources, for example , when testing against Localstack.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.
• I have made my commit title and message explanatory about the purpose and the reason of the change

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @bhapas? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fix-enpoint-resolver upstream/fix-enpoint-resolver
git merge upstream/main
git push upstream fix-enpoint-resolver

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-08-14T12:00:10.827+0000

• Duration: 139 min 6 sec

Test stats 🧪

Test	Results
Failed	0
Passed	6264
Skipped	353
Total	6617

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[bhapas]

/test

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b fix-enpoint-resolver upstream/fix-enpoint-resolver
git merge upstream/main
git push upstream fix-enpoint-resolver

[bhapas]

/test

[zmoog]

LGTM.

It seems we're using endpoint resolution v1, please correct me if I'm wrong. This is fine if this is the case since AWS recently released AWS will release v2 in Q3.

Are there considerations or plans for v1 vs. v2?

[bhapas]

LGTM.

It seems we're using endpoint resolution v1, please correct me if I'm wrong.

This is fine if this is the case since AWS released v2 recently. Are there considerations or plans for v1 vs. v2?

V2 sounds more practical for testing purposes , specially Localstack . Probably would revisit this when the V2 is officially out in Q3 2023

Created an issue to track this - #36319