See ‘aws help’ for descriptions of global parameters.įor more information, see Managed Rule Groups in the AWS WAF, AWS Firewall Manager, and AWS Shield Advanced Developer Guide.
If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.Īutomatically prompt for CLI input parameters. Similarly, if provided yaml-input it will print a sample input YAML that can be used with -cli-input-yaml. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for -cli-input-json. Prints a JSON skeleton to standard output without sending an API request. This may not be specified along with -cli-input-yaml. To do this, you first define the response body key and value in the CustomResponseBodiessetting for the WebACL or RuleGroup where you want to use it. You can define a custom response for a rule action or a default web ACL action that is set to block. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. References the response body that you want WAF to return to the web request client. If other arguments are provided on the command line, those values will override the JSON-provided values. Choose one or more of these rule groups to establish baseline protection for your resources. The JSON string follows the format provided by -generate-cli-skeleton. Baseline managed rule groups provide general protection against a wide variety of common threats. Reads arguments from the JSON string provided. cli-input-json | -cli-input-yaml (string) ĪPI and SDKs - For all calls, use the Region endpoint us-east-1. Virginia) as follows:ĬLI - Specify the Region when you use the CloudFront scope: -scope=CLOUDFRONT -region=us-east-1. To work with CloudFront, you must also specify the Region US East (N. A regional application can be an Application Load Balancer (ALB) or an API Gateway stage. Specifies whether this is for an AWS CloudFront distribution or for a regional application.
0 kommentar(er)
