Overview
AWS WAF logs every request a web ACL evaluates, capturing:
ALLOW,BLOCK,COUNT, andCAPTCHAactions per rule- Source IP, country, headers, and User-Agent
- Matched managed rule group (for example,
AWSManagedRulesCommonRuleSet) - Rate-based rule trigger details
Atatus reads WAF logs from a CloudWatch log group that the web ACL delivers logs to.
Prerequisites
- An AWS WAF web ACL with logging enabled to CloudWatch Logs.
- IAM credentials with read access to that log group.
Step 1: Enable WAF logging to CloudWatch Logs
- Open the AWS Console → WAF & Shield → Web ACLs and select your web ACL.
- Open the Logging and metrics tab and click Enable logging.
- Choose CloudWatch Logs and select (or create) a log group whose name begins with
aws-waf-logs-(for example,aws-waf-logs-prod). - Optionally redact sensitive fields, then click Enable logging.
Step 2: Create an IAM user with log read access
- Open IAM → Users → Create user, name it
atatus-waf-reader. - Attach an inline policy granting:
logs:DescribeLogGroupslogs:DescribeLogStreamslogs:GetLogEventslogs:FilterLogEvents
- Scope the policy to the WAF log group ARN.
- Create an access key under Security credentials → Create access key and copy both values.
Step 3: Connect AWS WAF in Atatus
- In Atatus, go to Security → Cloud SIEM → Integrations.
- Locate the AWS WAF card and click Connect.
- Fill in the form:
| Field | Description | Example |
|---|---|---|
| AWS Access Key ID | IAM user access key from Step 2. | AKIA... |
| AWS Secret Access Key | The matching secret key. | •••••••• |
| AWS Region | Region of the web ACL. | us-east-1 |
| CloudWatch Log Group | WAF log group name (must begin with aws-waf-logs-). |
aws-waf-logs-prod |
| Poll Interval (minutes) | How often to fetch new entries. | 5 |
| Enabled | Turn collection on. | true |
- Click Connect.
Verification
- The AWS WAF card shows Configured.
- WAF events appear in Security → Cloud SIEM → Audit Logs → Events with source
aws_waf.
+1-415-800-4104