Skip to content

Fix FMS/WAF Logs processing rule to process cloudfront waf logs - #115

Open
komal-SkyNET wants to merge 1 commit into
dynatrace-oss:mainfrom
komal-SkyNET:fix_fms_waf_logs_s3_object_path
Open

Fix FMS/WAF Logs processing rule to process cloudfront waf logs#115
komal-SkyNET wants to merge 1 commit into
dynatrace-oss:mainfrom
komal-SkyNET:fix_fms_waf_logs_s3_object_path

Conversation

@komal-SkyNET

@komal-SkyNET komal-SkyNET commented Jun 10, 2025

Copy link
Copy Markdown

The AWS Firewall Manager (FMS) service stores WAF logs in S3 with object paths that include both standard AWS region names (e.g., ap-southeast-2) and the special case cloudfront. While the existing aws_region_pattern regex supports typical region identifiers, it excludes cloudfront—intentionally—since that pattern may also be used in contexts where strict region validation is required.

To address this without altering the original regex behavior, this change introduces a new pattern: aws_fms_waf_region_pattern.

This dedicated pattern is designed to explicitly support both region names and cloudfront, ensuring that all AWS WAF/FMS logs are accurately recognized and processed by the ingestion pipeline.

@dynatrace-cla-bot

dynatrace-cla-bot commented Jun 10, 2025

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@sonarqubecloud

Copy link
Copy Markdown

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