Edge WAF deployment using the Next-Gen WAF API

IMPORTANT: This guide only applies to customers who want to deploy the Edge WAF on a Compute service and cannot access the Next-Gen WAF in the Fastly control panel or want to deploy the Edge WAF on a CDN service that meets one of the following conditions:

• The service doesn't have the ngwaf_oob_enabled parameter set.
• The service has the ngwaf_oob_enabled parameter disabled (false) and uses mutual TLS (mTLS).

If you don't meet these requirements, refer to the Fastly control panel guide instead.