[kubasobon]

Summary

Follow-up to #19795, supporting the two new AWS asset types cloudbeat now emits: Route53 DNS records and EKS clusters (plus additional EC2 and ELB attributes).

No new mappings are required — these flow through fields already added in 1.7.0:

• entity.attributes (type: flattened) absorbs all new resource-specific keys (Route53 Type/ResourceRecords/ZoneID/…, EKS Status/Version/Endpoint/…, EC2/ELB extras) without a mapping change.
• entity.lifecycle.CreatedAt (type: date) carries the EKS cluster creation time.
• entity.type / entity.sub_type (keyword) hold the new asset-type values.

Changes:

• Enriched the entity.attributes description with the new example keys
• Version bumped 1.7.0 → 1.8.0

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.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Related issues

• Closes https://github.com/elastic/security-team/issues/17750
• Related cloudbeat PR: [Cloud Asset Inventory] Add extra resource fields #2 (EKS & Route 53) cloudbeat#7183

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: 44aff52

History

• 💔 Build #45479 failed d34737e
• 💔 Build #45478 failed d31a665

cc @kubasobon

[kubasobon]

Closing, folded into #19795