[AWS] Fix EC2 dashboard

[kaiyan-sheng]

What does this PR do?

This PR is to fix EC2 OOTB dashboard:

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 [AWS] Dashboards are using wrong field names #3703

[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: 2022-08-25T14:15:47.304+0000

• Duration: 39 min 20 sec

Test stats 🧪

Test	Results
Failed	0
Passed	162
Skipped	2
Total	164

🤖 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% (13/13)	💚
Files	92.857% (13/14)	👎 -4.334
Classes	92.857% (13/14)	👎 -4.334
Methods	84.232% (203/241)	👎 -5.162
Lines	95.697% (5204/5438)	👍 4.77
Conditionals	100.0% (0/0)	💚

[drewdaemon]

These changes look good to me.

At least some of the old field names appear to also be valid. For example, I see you changed aws.ec2.diskio.write.bytes to host.disk.write.bytes, but the old field appears to exist (no error here):

So, I'm assuming you had other reasons for changing the fields?

[kaiyan-sheng]

So, I'm assuming you had other reasons for changing the fields?

Yep we switched the fields to the new ECS fields as a part of the inventory schema initiative: elastic/beats#19757