[Filebeat] Enable awscloudwatch input to collect logs from linked source accounts

[tommyers-elastic]

When log_group_arn is configured, use it directly, instead of parsing the log group name and using that instead. This allows log collection from linked source accounts.

In order to 'fully' support cross account collection with log group prefixes, we need to add additional configuration options to allow DescribeLogGroups to discover log groups in linked accounts. This change will come separately.

• 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.

Fixes #36642

[mergify]

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

[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

• Duration: 114 min 17 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 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!)

[kaiyan-sheng]

The change looks good to me. Maybe we can add some documentation about this feature too in https://github.com/elastic/beats/blob/main/x-pack/filebeat/docs/inputs/input-aws-cloudwatch.asciidoc?

[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 enable-cross-account-cloudwatch-logs upstream/enable-cross-account-cloudwatch-logs
git merge upstream/main
git push upstream enable-cross-account-cloudwatch-logs

[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 enable-cross-account-cloudwatch-logs upstream/enable-cross-account-cloudwatch-logs
git merge upstream/main
git push upstream enable-cross-account-cloudwatch-logs

[mergify]

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

[hesingon]

May I check when can this PR be done? waiting for this feature..

[nsshah1288]

Hi @kaiyan-sheng, it would be amazing if this PR could get completed! We are very keen to use this feature to collect CW logs from multiple accounts with a centralized elastic agent. thank you!

[kaiyan-sheng]

@tommyers-elastic I'm closing this PR since we've merged @Kavindu-Dodan's instead :) Thank you!!