Rule, which contains the
objects, and other predicates that identify the requests that you want
to block. If you add more than one predicate to a
Rule, a request must
match all of the specifications to be allowed or blocked. For example,
suppose that you add the following to a
waf_create_rule(Name, MetricName, ChangeToken, Tags)
[required] A friendly name or description of the Rule. You can't change the name
[required] A friendly name or description for the metrics for this
[required] The value returned by the most recent call to GetChangeToken.
IPSet that matches the IP address
ByteMatchSet that matches
BadBot in the
You then add the
Rule to a
WebACL and specify that you want to
blocks requests that satisfy the
Rule. For a request to be blocked, it
must come from the IP address 192.0.2.44 and the
in the request must contain the value
To create and configure a
Rule, perform the following steps:
Create and update the predicates that you want to include in the
Rule. For more information, see CreateByteMatchSet, CreateIPSet,
Use GetChangeToken to get the change token that you provide in the
ChangeToken parameter of a
GetChangeToken to get the change token that you provide in the
ChangeToken parameter of an UpdateRule request.
UpdateRule request to specify the predicates that you
want to include in the
Create and update a
WebACL that contains the
Rule. For more
information, see CreateWebACL.
For more information about how to use the AWS WAF API to allow or block HTTP requests, see the AWS WAF Developer Guide.
1 2 3 4 5 6 7 8 9 10 11
1 2 3 4 5 6
# The following example creates a rule named WAFByteHeaderRule. svc$create_rule( ChangeToken = "abcd12f2-46da-4fdb-b8d5-fbd4c466928f", MetricName = "WAFByteHeaderRule", Name = "WAFByteHeaderRule" )
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.