First Step

The first step was to add a WAF to the ALB.

Web ACLs

Web ACLs that you have defined in the selected region.

Find web ACLs

US West (N. California)

Second Step

The second step was to add the AWS Core Rule Set to the WAF.

Add managed rule groups

Managed rule groups are created and maintained for you by AWS and AWS Marketplace sellers. Any fees that a managed rule group provider charges for using a managed rule group are in addition to the standard service charges for AWS WAF. AWS WAF Pricing.

AWS managed rule groups

Free rule groups

You can use the free rule groups without any added charges beyond the standard service charges for AWS WAF.

Final Step

The final step is to set every rule other than GenericFLI_URIPATH to Count in order to preserve existing Nexus functionality.

Core rule set rules

The rules apply actions and labels to requests that match their criteria.

By default, the rule group uses its configured rule actions. You can override the actions for all rules and for individual rules. For a single rule, use the rule dropdown to specify an override action or to remove an override.

Allow and Block actions terminate web ACL evaluation for matching requests. Count action counts matching requests and continues the web ACL evaluation.

Override all rule actions

Choose rule action override:

• Override to Block
• Override to Allow
• Override to Count
• Override to CAPTCHA
• Override to Challenge
• Remove all overrides

CrossSiteScripting_BODY_RC_COUNT Rule action: Count

• Override to Count

UserAgent_BadBots_HEADER_RC_COUNT

CrossSiteScripting_QUERYARGUMEN TS_RC_COUNT Rule action: Count

• Override to Count

NoUserAgent_HEADER Rule action: Block

GenericLFI_URIPATH

Rule action: Block

• Override to Block
• Override to Allow
• Override to Block
• Override to Count
• Override to CAPTCHA
• Override to Challenge
• Remove Override