[8.x](backport #40691) [AWS] Support owning account for cross account monitoring #40860
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
Adds
owning_account
configuration option for AWS where it accepts a source account ID. Internally, this maps to the ListMetrics API's 1OwningAccount
parameter. Note thatinclude_linked_accounts
should be set totrue
to use the account filtering.See the screenshot below from an actual run with owning account filtering,
In comparison, consider the screenshot below where both monitoring account and linked accounts are visible as there is no filtering for
owning_account
,Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Disruptive User Impact
None :
owning_account
is a new configurationHow to test this PR locally
include_linked_accounts
set to true (default is already true) &owning_account
account IDcloud.account.id
match withowning_account
IDRelated issues
Closes #40570
This is an automatic backport of pull request #40691 done by [Mergify](https://mergify.com).
Footnotes
https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_ListMetrics.html#API_ListMetrics_RequestParameters ↩