githubEdit

AWS WAF Classic

circle-info

This page was generated from content adapted from the AWS Developer Guidearrow-up-right

Setting up AWS WAF Classic

  • Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your resources, see Migrating your AWS WAF Classic resources to AWS WAFarrow-up-right. For the latest version of AWS WAF, see AWS WAFarrow-up-right.

  • Note If you're a new user to AWS WAF, don't follow these setup steps for AWS WAF Classic. Instead, follow the steps for the latest version of AWS WAF, at Setting uparrow-up-right.

  • Note AWS Shield Standard is included with AWS WAF Classic and does not require additional setup. For more information, see How AWS Shield worksarrow-up-right.

How AWS WAF Classic works

  • Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your resources, see Migrating your AWS WAF Classic resources to AWS WAFarrow-up-right. For the latest version of AWS WAF, see AWS WAFarrow-up-right.

  • Note You can also use AWS WAF Classic to protect your applications that are hosted in Amazon Elastic Container Service (Amazon ECS) containers. Amazon ECS is a highly scalable, fast container management service that makes it easy to run, stop, and manage Docker containers on a cluster. To use this option, you configure Amazon ECS to use an AWS WAF Classic enabled Application Load Balancer to route and protect HTTP/HTTPS (layer 7) traffic across the tasks in your service. For more information, see the topic Service Load Balancingarrow-up-right in the Amazon Elastic Container Service Developer Guide.

AWS WAF Classic pricing

Getting started with AWS WAF Classic

Creating and configuring a Web Access Control List (Web ACL)

Working with AWS WAF Classic rule groups for use with AWS Firewall Manager

  • Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your resources, see Migrating your AWS WAF Classic resources to AWS WAFarrow-up-right. For the latest version of AWS WAF, see AWS WAFarrow-up-right.

  • Important If you want to add an AWS Marketplace rule group to your Firewall Manager policy, each account in your organization must first subscribe to that rule group. After all accounts have subscribed, you can then add the rule group to a policy. For more information, see AWS Marketplace rule groupsarrow-up-right.

Getting started with AWS Firewall Manager to enable AWS WAF Classic rules

Tutorial: Creating a AWS Firewall Managerpolicy with hierarchical rules

Logging Web ACL traffic information

Listing IP addresses blocked by rate-based rules

How AWS WAF Classic works with Amazon CloudFront features

  • Note This is AWS WAF Classic documentation. You should only use this version if you created AWS WAF resources, like rules and web ACLs, in AWS WAF prior to November 2019, and you have not migrated them over to the latest version yet. To migrate your resources, see Migrating your AWS WAF Classic resources to AWS WAFarrow-up-right. For the latest version of AWS WAF, see AWS WAFarrow-up-right.

  • Note CloudFront can't distinguish between an HTTP status code 403 that is returned by your origin and one that is returned by AWS WAF Classic when a request is blocked. This means that you can't return different custom error pages based on the different causes of an HTTP status code 403.

Security

AWS WAF Classic quotas

Last updated