OpenObserve Docs
IntegrationCloudAws

Integration with AWS WAF via Firehose

Updated View MarkdownOpen in ChatGPTOpen in Claude

This guide explains how to configure AWS WAF to stream logs to OpenObserve using S3, Lambda, and Kinesis Data Firehose.

Overview

AWS WAF logs include detailed information about requests evaluated against your WebACL rules (e.g., ALLOW, BLOCK, CAPTCHA actions). This integration forwards those logs to OpenObserve via Firehose, enabling real-time monitoring of web traffic security and threat analysis.

Steps to Integrate

Prerequisites
  • OpenObserve account (Cloud or Self-Hosted)
  • AWS IAM permissions to manage WAF, S3, Lambda, Kinesis Firehose, CloudFormation
  • An existing AWS WAF WebACL attached to CloudFront, ALB, or API Gateway
  • An S3 bucket to receive WAF logs
Step 1: Enable WAF Logging to S3

  1. Go to AWS Console → WAF & Shield

  2. Select the WebACL you want to log

  3. In the sidebar, click Logging and metrics → Enable logging Enable WAF Logging to S3

  4. Choose your target S3 bucket (must be in the same region as the WebACL)

    Enable WAF Logging to S3

Make sure your S3 bucket has proper permissions to receive logs from AWS WAF.

Step 2: Get OpenObserve Ingestion URL and Access Key

  1. In OpenObserve: go to Data > Data sources > Recommended > Amazon Web Services(AWS). The Manual Configuration block shows the HTTP endpoint and Access Key

  2. Copy the HTTP ingestion URL and Access Key

    Manual Configuration block with the HTTP endpoint and access key

Example ingestion URL:

https://<your-openobserve-domain>/aws/<org_id>/<stream_name>/_kinesis_firehose
Step 3: Deploy CloudFormation Stack to Set Up Lambda and Firehose
  1. Use the CloudFormation template from Openobserve Template Repository.
  2. Go to CloudFormation → Create Stack → With new resources (standard)
  3. Upload the template file
  4. Set the following parameters:
    • OpenObserve Ingestion URL (the Firehose endpoint from Step 2)
    • Access Key
    • Source S3 Bucket (WAF Logs)
    • Backup S3 Bucket (Optional) Deploy CloudFormation Stack
  5. Complete the stack creation process
  6. Ensure the IAM roles, Lambda function, Kinesis Firehose, and S3 configurations are created successfully. Deploy CloudFormation Stack

NOTE: Due to AWS limitations, the S3 trigger for Lambda must be added manually after stack creation.

Deploy CloudFormation Stack

Step 4: Verify Log Ingestion in OpenObserve
  1. Go to OpenObserve → Logs
  2. Select your stream and click Run Query

AWS WAF logs in the Logs page

You can also import a sample AWS WAF dashboard JSON from Dashboards > Import > Custom to visualize top IPs, blocked requests, and more.

Troubleshooting

  • No logs visible in OpenObserve

    • Confirm WAF logging is enabled and logs are being written to the S3 bucket
    • Check Lambda logs in CloudWatch for errors
    • Ensure the Firehose stream is active and the endpoint and credentials are correct

  • CloudFormation stack fails

    • Review error messages—common issues include invalid S3 bucket names or missing permissions
    • Ensure the IAM roles for Lambda and Firehose are created successfully

  • Firehose shows delivery errors

    • Check that your OpenObserve ingestion URL includes the correct stream
    • Validate that your access key is correct
    • Confirm that the HTTP endpoint is reachable and accepts Firehose POST requests
Was this page helpful?

AWS Route 53

Stream AWS Route 53 DNS query logs to OpenObserve via CloudWatch Logs and Kinesis Firehose for real-time DNS monitoring.

API Gateway logs

Stream AWS API Gateway access logs to OpenObserve using Kinesis Firehose for real-time API observability.

On this page

Integration with AWS WAF via FirehoseOverviewSteps to Integrate