Backport of #20403 to `backport-aws-6.x` so that users on the 8.x Kibana
stack (package 6.x, Kibana `^8.19.4 || ^9.2.1`) receive the CloudTrail
ingest pipeline improvements. This brings the `cloudtrail` data stream to
parity with `main`.
Because `backport-aws-6.x` did not have the intermediate CloudTrail change
from #20318, that change is included here as well (it is a prerequisite for
the #20403 pipeline and is part of the same CloudTrail quality effort).
Enhancements:
- Replace every `ignore_failure: true` with an `ignore_missing` flag, a
condition guard, or an explicit `on_failure` handler reporting to
`error.message`, so real faults surface instead of being silently swallowed.
- Add support for CloudTrail fields that were previously dropped.
- Populate the `cloud.provider`, `cloud.service.name` and `related.*` ECS fields.
- Stop storing the assumed-role ARN session name in `user.changes.*`. The session
name is now added to `related.user` for cross-source correlation; when it is an
email, both the full email and the local-part prefix are added. `user.name`
continues to hold the IAM role name for detection rules. (#20318)
Bugfixes:
- Stop populating `file.hash.sha256` on digest records, where it held the hash of
the previous digest file while `file.path` pointed at the current one. The value
is still available as `aws.cloudtrail.digest.previous_hash_value` and in
`related.hash`.
- Fix `DeleteObject` using `event.type: delete`, which is not a valid ECS value.
It is now `deletion`.
- Fix `Publish`, `SendCommand` and `Converse` producing no `event.type`. They now
use `info`, `start` and `info` respectively.
- Fix `retain: none` behaving like `retain: all`. It now drops both the keyword and
the flattened copies as documented.
- Fix `retain: keyword` and `retain: minimal` discarding digest and Insights records.
The setting governs API call payloads and no longer affects either record type.
- Fix `aws.cloudtrail.service_event_details` surviving `retain: flattened` and
`retain: none`. It is now governed like the other payload fields.
Proposed commit message
Note
bugfix, not abreaking-change. With that in mind, none of the changes above fall into thebreaking-changecategory.To Reviewers:
Checklist
changelog.ymlfile.How to test this PR locally
Related issues