[cloud_security_posture] Revert ECS field definition removal from misconfiguration transform - #17654
Merged
Conversation
…configuration transform Restoring explicit ECS mappings and `dynamic: false` to prevent field explosion from `ecs@mappings` dynamic templates. Removing `dynamic: false` (preview08) caused cloudbeat's `resource.raw` fields to be dynamically mapped, exceeding the 1000 total fields limit.
maxcold
force-pushed
the
csp-transform-remove-dynamic-false
branch
from
March 4, 2026 10:58
20be1ae to
e9f355d
Compare
maxcold
added
Integration:cloud_security_posture
maxcold
marked this pull request as ready for review
March 4, 2026 11:00
Contributor
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
seanrathier
approved these changes
Mar 4, 2026
Contributor
|
Package cloud_security_posture - 3.3.0-preview09 containing this change is available at https://epr.elastic.co/package/cloud_security_posture/3.3.0-preview09/ |
Contributor
|
Package cloud_security_posture - 3.3.0 containing this change is available at https://epr.elastic.co/package/cloud_security_posture/3.3.0/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
[cloud_security_posture] Revert ECS field definition removal from misconfiguration transform
Restoring explicit ECS mappings (
fields/ecs.yml) anddynamic: falseto the misconfiguration transform destination index template. This reverts the CSP-specific changes from #17552 (preview07) and the attempted fix in #17637 (preview08).Why: Removing
dynamic: false(preview08) caused cloudbeat'sresource.rawfields — raw cloud provider API responses with deeply nested, variable-structure JSON — to be dynamically mapped viaecs@mappings, exceedingtotal_fields.limitof 1000. The proper fix requires addingenabled: falseforresource.raw,result.evidence, andresult.expectedbeforedynamic: falsecan be safely removed. This is tracked in elastic/security-team#16225.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
dynamic: falsecloud.account.id) are explicitly mapped in the destination indexRelated issues
enabled: falsefor noisy sub-objects)resource.rawmapping issue)