AWS waf documentation change
Summary
Updated terminology from 'protection pack or web ACL' to 'protection pack (web ACL)' for consistency and clarity in label match examples
Security assessment
The changes are purely terminological clarifications to align documentation phrasing. There is no indication of addressing vulnerabilities, exploits, or security weaknesses. The updates improve consistency but do not introduce or modify security-related content.
Diff
diff --git a/waf/latest/developerguide/waf-rule-label-match-examples.md b/waf/latest/developerguide/waf-rule-label-match-examples.md index 9669e6d1b..672ef5181 100644 --- a//waf/latest/developerguide/waf-rule-label-match-examples.md +++ b//waf/latest/developerguide/waf-rule-label-match-examples.md @@ -17 +17 @@ This section provides examples of match specifications, for the label match rule -These JSON listings were created in the console by adding a rule to a protection pack or web ACL with the label match specifications and then editing the rule and switching to the **Rule JSON editor**. You can also get the JSON for a rule group or protection pack or web ACL through the APIs or the command line interface. +These JSON listings were created in the console by adding a rule to a protection pack (web ACL) with the label match specifications and then editing the rule and switching to the **Rule JSON editor**. You can also get the JSON for a rule group or protection pack (web ACL) through the APIs or the command line interface. @@ -53 +53 @@ The following JSON listing shows a label match statement for a label that's been -If you use this match statement in account 111122223333, in a rule that you define for protection pack or web ACL `testWebACL`, it would match the following labels. +If you use this match statement in account 111122223333, in a rule that you define for protection pack (web ACL) `testWebACL`, it would match the following labels. @@ -66 +66 @@ It wouldn't match the following label, because the label string isn't an exact m -It wouldn't match the following label, because the context isn't the same, so the prefix doesn't match. This is true even if you added the rule group `productionRules` to the protection pack or web ACL `testWebACL`, where the rule is defined. +It wouldn't match the following label, because the context isn't the same, so the prefix doesn't match. This is true even if you added the rule group `productionRules` to the protection pack (web ACL) `testWebACL`, where the rule is defined. @@ -73 +73 @@ It wouldn't match the following label, because the context isn't the same, so th -The following JSON listing shows a label match rule that matches against a label from a rule inside a user-created rule group. The prefix is required in the specification for all rules running in the protection pack or web ACL that aren't part of the named rule group. This example label specification matches only the exact label. +The following JSON listing shows a label match rule that matches against a label from a rule inside a user-created rule group. The prefix is required in the specification for all rules running in the protection pack (web ACL) that aren't part of the named rule group. This example label specification matches only the exact label. @@ -130 +130 @@ The following JSON listing shows a label match statement for a local namespace. -Similar to the local `Label` match, if you use this statement in account 111122223333, in a rule that you define for protection pack or web ACL `testWebACL`, it would match the following label. +Similar to the local `Label` match, if you use this statement in account 111122223333, in a rule that you define for protection pack (web ACL) `testWebACL`, it would match the following label.