[8.x](backport #41188) [Filebeat] [AWS] Add support to source AWS cloudwatch logs from linked accounts #41240
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.
Proposed commit message
PR adds support to Cloudwatch logs from source linked accounts. This is implemented by using existing configuration
log_group_arn
and mapping it toLogGroupIdentifier
of FilterLogEvents API [1]Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Note for reviewers
You could review commit by commit for better understanding of the changes
How to test this PR locally
This require a linked cloudwatch account. If already has one, then,
CLOUDWATCH_LOG
) [2]log_group_arn
Related issues
Addresses: #36642
And makes #36645 PR obsolete
closes #37681
Next step
Utilize
includeLinkedAccounts
when dealing with prefixes. To be done in a dedicated PR.[1] - https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_FilterLogEvents.html
[1] - https://github.com/Kavindu-Dodan/data-gen
This is an automatic backport of pull request #41188 done by Mergify.