Skip to content

Conversation

@mavam
Copy link
Member

@mavam mavam commented Dec 12, 2025

Summary

  • Refactor amazon_security_lake package to use user-defined operators (UDOs) instead of individual pipelines per OCSF class
  • Add new amazon_vpc_flow package for parsing and mapping VPC Flow Logs to OCSF

Changes

amazon_security_lake

  • Replace 51 individual pipeline files with 2 reusable operators (cast, send)
  • Simplify architecture using UDOs for better maintainability

amazon_vpc_flow (new)

  • amazon_vpc_flow::parse - Generic parser with configurable header argument
  • amazon_vpc_flow::parse_v2 - Convenience wrapper for default AWS format (14 fields)
  • amazon_vpc_flow::to_ocsf - Maps to OCSF Network Activity events (class 4001)
  • S3 ingestion pipeline for automated log processing
  • Comprehensive test suite

Test plan

  • Run tenzir-test for amazon_security_lake package
  • Run tenzir-test for amazon_vpc_flow package

🤖 Generated with Claude Code

mavam and others added 2 commits December 12, 2025 12:12
Replace ~50 nearly identical pipelines with two modular user-defined
operators that handle all OCSF event classes dynamically. The new
operators cast and send OCSF events to Amazon Security Lake using the
event's class_uid for automatic routing.

BREAKING CHANGE: Package ID renamed from amazon-security-lake to
amazon_security_lake (dash to underscore).

Co-Authored-By: Claude <[email protected]>
This new package provides utilities for parsing and mapping Amazon VPC
Flow Logs to OCSF Network Activity events. It includes:

- Generic parameterized parser (parse) accepting custom header argument
- Convenience wrapper (parse_v2) for default AWS format (14 fields)
- OCSF Network Activity mapping operator (to_ocsf)
- S3 ingestion pipeline for automated log processing
- Comprehensive test suite with sample data

Co-Authored-By: Claude <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants