AWS::WAFv2::WebACL ManagedRuleGroupStatement

A rule statement used to run the rules that are defined in a managed rule group. To use this, provide the vendor name and the name of the rule group in this statement.

You cannot nest a ManagedRuleGroupStatement, for example for use inside a NotStatement or OrStatement. It can only be referenced as a top-level statement within a rule.

Syntax

To declare this entity in your AWS CloudFormation template, use the following syntax:

JSON

{
  "ExcludedRules" : [ ExcludedRule, ... ],
  "ManagedRuleGroupConfigs" : [ ManagedRuleGroupConfig, ... ],
  "Name" : String,
  "RuleActionOverrides" : [ RuleActionOverride, ... ],
  "ScopeDownStatement" : Statement,
  "VendorName" : String,
  "Version" : String
}

YAML

  ExcludedRules: 
    - ExcludedRule
  ManagedRuleGroupConfigs: 
    - ManagedRuleGroupConfig
  Name: String
  RuleActionOverrides: 
    - RuleActionOverride
  ScopeDownStatement: 
    Statement
  VendorName: String
  Version: String

Properties

ExcludedRules

Rules in the referenced rule group whose actions are set to Count.

Note

Instead of this option, use RuleActionOverrides. It accepts any valid action setting, including Count.

Required: No

Type: List of ExcludedRule

Maximum: 100

Update requires: No interruption

ManagedRuleGroupConfigs

Additional information that's used by a managed rule group. Many managed rule groups don't require this.

Use the AWSManagedRulesATPRuleSet configuration object for the account takeover prevention managed rule group, to provide information such as the sign-in page of your application and the type of content to accept or reject from the client.

Use the AWSManagedRulesBotControlRuleSet configuration object to configure the protection level that you want the Bot Control rule group to use.

Required: No

Type: List of ManagedRuleGroupConfig

Update requires: No interruption

Name

The name of the managed rule group. You use this, along with the vendor name, to identify the rule group.

Required: Yes

Type: String

Minimum: 1

Maximum: 128

Pattern: ^[\w\-]+$

Update requires: No interruption

RuleActionOverrides

Action settings to use in the place of the rule actions that are configured inside the rule group. You specify one override for each rule whose action you want to change.

You can use overrides for testing, for example you can override all of rule actions to Count and then monitor the resulting count metrics to understand how the rule group would handle your web traffic. You can also permanently override some or all actions, to modify how the rule group manages your web traffic.

Required: No

Type: List of RuleActionOverride

Update requires: No interruption

ScopeDownStatement

An optional nested statement that narrows the scope of the web requests that are evaluated by the managed rule group. Requests are only evaluated by the rule group if they match the scope-down statement. You can use any nestable Statement in the scope-down statement, and you can nest statements at any level, the same as you can for a rule statement.

Required: No

Type: Statement

Update requires: No interruption

VendorName

The name of the managed rule group vendor. You use this, along with the rule group name, to identify the rule group.

Required: Yes

Type: String

Minimum: 1

Maximum: 128

Pattern: .*\S.*

Update requires: No interruption

Version

The version of the managed rule group to use. If you specify this, the version setting is fixed until you change it. If you don't specify this, AWS WAF uses the vendor's default version, and then keeps the version at the vendor's default when the vendor updates the managed rule group settings.

Required: No

Type: String

Minimum: 1

Maximum: 64

Pattern: ^[\w#:\.\-/]+$

Update requires: No interruption

Examples

Configure the managed rule group statement for AWSManagedRulesATPRuleSet

The following shows an example ManagedRuleGroupStatement for the AWS WAF ATP managed rule group. The ManagedRuleGroupConfigs settings are provided as a number of individual ManagedRuleGroupConfig settings.

YAML

ManagedRuleGroupStatement:
  VendorName: AWS
  Name: AWSManagedRulesATPRuleSet
  ManagedRuleGroupConfigs:
    - LoginPath: /api/accounts/login
    - PayloadType: JSON
    - PasswordField:
        Identifier: /form/password
    - UsernameField:
        Identifier: /form/username 

JSON

{
  "ManagedRuleGroupStatement": {
    "VendorName": "AWS",
    "Name": "AWSManagedRulesATPRuleSet",
    "ManagedRuleGroupConfigs": [
      {
        "LoginPath": "/api/accounts/login"
      },
      {
        "PayloadType": "JSON"
      },
      {
        "PasswordField": {
          "Identifier": "/form/password"
        }
      },
      {
        "UsernameField": {
          "Identifier": "/form/username"
        }
      }
    ]
  }
} 

Configure a standard managed rule group statement

The following shows an example ManagedRuleGroupStatement for a managed rule group that doesn't require additional configuration.

YAML

ManagedRuleGroupStatement:
  VendorName: AWS
  Name: AWSManagedRulesCommonRuleSet 

JSON

{
  "ManagedRuleGroupStatement": {
    "VendorName": "AWS",
    "Name": "AWSManagedRulesCommonRuleSet"
  }
}