Add s3 support functionbeat

[JoupainMD]

trafficstars

What does this PR do?

Add support for S3 notifications.

Why is it important?

Because most of AWS service logging are using S3 buckets (example ALB/ELB, Redshift, GuardDuty) and the existing solutions (logstash s3 input for example) are really painful to use or not efficient.

Checklist

• [x] My code follows the style guidelines of this project
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] 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
• [x] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

mage build mage test

Related issues

https://github.com/elastic/beats/issues/11603

Use cases

Screenshots

Logs

[elasticmachine]

:grey_exclamation: Build Aborted

The PR is not allowed to run in the CI yet

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: 2022-08-12T13:26:09.644+0000

• Duration: 6 min 49 sec

Steps errors

Expand to view the steps failures

Load a resource file from a shared library

• Took 0 min 0 sec . View more details here
• Description: approval-list/elastic/beats.yml

Error signal

• Took 0 min 0 sec . View more details here
• Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/JoupainMD return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/JoupainMD : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/JoupainMD : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/reference/orgs#check-organization-membership-for-a-user"}

:robot: 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!)

[cla-checker-service[bot]]

💚 CLA has been signed

[mergify[bot]]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @JoupainMD? 🙏. 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[bot]]

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 add_s3_support_functionbeat upstream/add_s3_support_functionbeat
git merge upstream/main
git push upstream add_s3_support_functionbeat

[mergify[bot]]

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 add_s3_support_functionbeat upstream/add_s3_support_functionbeat
git merge upstream/main
git push upstream add_s3_support_functionbeat

[mergify[bot]]

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 add_s3_support_functionbeat upstream/add_s3_support_functionbeat
git merge upstream/main
git push upstream add_s3_support_functionbeat

[mergify[bot]]

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 add_s3_support_functionbeat upstream/add_s3_support_functionbeat
git merge upstream/main
git push upstream add_s3_support_functionbeat

[mergify[bot]]

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 add_s3_support_functionbeat upstream/add_s3_support_functionbeat
git merge upstream/main
git push upstream add_s3_support_functionbeat

[mergify[bot]]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @JoupainMD? 🙏. 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

[jlind23]

Closing this as it is for now outdated and hasn't been worked on for quite some time. Feel free to reopen it if need be.