1 Answers
I’m no expert — but…
Typically in these scenarios, a WAF is an associated resource. i.e. In order for it to work, it needs to be associated with either a CloudFront distribution, an ALB, or an API Gateway. If it is not associated with any of these — it still exists, but doesn’t effectively block any traffic from anything.
You can associated the WAF to these resources, either when creating the WAF (as in your picture), or when creating the resources (like a Cloudfront distribution).
It’s basically a chicken n’ egg scenario — you can either create the WAF first, or the Cloudfront distribution first, and then associate the two once both are created. But in the former, you still need the ability to create the WAF without any associations.