[AWS] Add dimensions to EC2 data stream.

[constanca-m]

What does this PR do?

Set the dimension fields for EC2 data stream.

All dimension.* fields in fields.yml are dimensions.

For the ecs fields, the reasoning for the fields can be found in this comment.

Result of successful testing:

All 130 documents taken from index .ds-metrics-aws.ec2_metrics-default-2023.08.22-000001 were successfully placed to index tsdb-index-enabled.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Related issues

Relates to #6293.

[zmoog]

LGTM.

Out of curiosity: you didn't define cloud.instance.id as a dimension because we already have aws.dimensions.InstanceId, right?

[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

• Start Time: 2023-08-22T07:34:12.745+0000

• Duration: 49 min 2 sec

Test stats 🧪

Test	Results
Failed	0
Passed	208
Skipped	4
Total	212

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (17/17)	💚
Files	94.444% (17/18)	👎 -5.556
Classes	94.444% (17/18)	👎 -5.556
Methods	85.953% (257/299)	👎 -14.047
Lines	86.024% (7509/8729)	👎 -13.976
Conditionals	100.0% (0/0)	💚

[constanca-m]

Out of curiosity: you didn't define cloud.instance.id as a dimension because we already have aws.dimensions.InstanceId, right?

Yes @zmoog, and to also keep the consistency on the ecs fields defined as dimension across the AWS data streams.

[elasticmachine]

Package aws - 1.53.4 containing this change is available at https://epr.elastic.co/search?package=aws