If you’re using AWS WAF as a web application firewall, you can ship its alerts to your Logz.io Cloud SIEM.
Configure AWS WAF to enrich observability
Add an ACL rule to your AWS WAF to log all HTTP requests. In your AWS WAF admin console:
- Go to your web ACLs screen and select the relevant Region.
- Select an ACL and go to the Rules tab.
- Add a new rule. Make the following selections:
- Rule type: Select Regular Rule.
- Use the OR separator.
- Create a statement with the following fields:
- Inspect: HTTP method
- Match type: Starts with string
- String to match: GET
- Add additional statements, separated by OR for every HTTP method you would like to monitor. At the very least, we recommend monitoring GET and POST methods.
- Then: Select the Count action.
- Save the rule.
Adjust the rule’s hierarchy, if relevant.
If there are several ACL rules, we recommend that the rule created for Logz.io be as high in the hierarchy as possible.
Configure AWS WAF to send logs to an S3 Bucket
You’ll first need to make sure all your logs are being written to an S3 bucket.
- In your AWS WAF console, go to your web ACL screen. Select the web ACL you would like to send logs from.
- Set the web ACL to forward the logs to an S3 bucket.
Configure Logz.io to read AWS WAF logs from an S3 Bucket
Before you begin, you’ll need:
- A user with permissions to list the buckets on the relevant S3 Bucket.
- Permission to Get from all the paths under the bucket name.
In your Logz.io account, use the Logz.io S3 Bucket wizard to configure Logz.io to read AWS WAF logs from the S3 Bucket.
In the log type section menu of Logz.io configuration wizard, select
otherand type in
awswaf. The log type section menu is located beside the hosting region selection menu.
If you run into issues, you can reference the guide for troubleshooting user permissions.
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open Kibana and search for
If you still don’t see your logs, see log shipping troubleshooting.