[aws] missing metrics when include_linked_accounts set to false

[kaiyan-sheng]

• Version: v1.51.3 AWS integration with 8.8.2 agent
• Operating System: agent running on linux EC2 instance
• Steps to Reproduce:

1. Create RDS instances in the same account and make sure there are metrics coming into CloudWatch:

2. Run agent and install AWS RDS integration with config `latency=10m` just to make sure metric collection does not get impacted by latency. Keep `include_linked_accounts = false` and here are the metrics you can see from Kibana: We only see metrics from 2 RDS instances. 3. Change agent policy to `include_linked_accounts = true`, save the policy and here are the metrics you can see from Kibana: We can see metrics from all 5 RDS instances.

These RDS instances are all from the same AWS account, cross account monitoring is not enabled either. include_linked_accounts should not affect the results.

[elasticmachine]

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

[kaiyan-sheng]

Test list-metrics API, which is the one uses include_linked_accounts config parameter:

aws cloudwatch list-metrics --namespace AWS/RDS --metric-name CPUUtilization --region eu-west-3 --profile elastic-observability --recently-active PT3H --include-linked-accounts --dimensions Name=DBClusterIdentifier

and

aws cloudwatch list-metrics --namespace AWS/RDS --metric-name CPUUtilization --region eu-west-3 --profile elastic-observability --recently-active PT3H --no-include-linked-accounts --dimensions Name=DBClusterIdentifier

returns the same result.

Will test with metricbeat directly next.