Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[8.6](backport #33699) [Filebeat] aws.vpcflow - use parse_aws_vpc_flow_log processor #33710

Merged
merged 1 commit into from
Nov 17, 2022
Merged

[8.6](backport #33699) [Filebeat] aws.vpcflow - use parse_aws_vpc_flow_log processor #33710

merged 1 commit into from
Nov 17, 2022

Commits on Nov 17, 2022

  1. aws.vpcflow - use parse_aws_vpc_flow_log processor (#33699) 

    Update the aws.vpcflow dataset in the AWS module to use the parse_aws_vpc_flow_log processor.
I also updated the module to be aligned with ECS. It was not using valid event.category
and event.type values. It will now produce `event.category: [network]`. And `event.type: [connection]`
or `[connection, allowed]` or `[connection, denied]`.

(cherry picked from commit 703d529)
    @andrewkroh @mergify
    andrewkroh authored and mergify[bot] committed Nov 17, 2022
    Configuration menu
    Copy the full SHA
    f442354 View commit details
    Browse the repository at this point in the history