feat(edge): add doc for using WAF in the console (#4968)

* feat(edge): add waf doc

* feat(waf): continue doc

* feat(es): more waf

* feat(edge): more waf

* feat(edge): continue waf

* fix(waf): diagrams and flows

* fix(waf): fix faq

* fix(edge): fixed todo

* fix(faq): remove

* fix(waf): final doc

* Apply suggestions from code review

Co-authored-by: ldecarvalho-doc <[email protected]>

---------

Co-authored-by: ldecarvalho-doc <[email protected]>

Author: RoRoJ

macros/edge-services/assets/scaleway-edge-services-pipeline-diag.webp

@@ -7,4 +7,4 @@ macro: edge-services-bucket-benefits
 - Enhance performance by caching your stored objects, to be served directly by Edge Services from the cache
 - Finely control your cached objects via purging (cache invalidation)
 
-<Lightbox src="scaleway-edge-services-pipeline.webp" alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />
+<Lightbox src="scaleway-edge-services-pipeline-nowaf.webp" alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />

macros/edge-services/assets/scaleway-edge-services-pipeline-nowaf.webp

@@ -4,12 +4,13 @@ macro: edge-services-lb-benefits
 
 Creating an Edge Services pipeline for your Load Balancer helps to reduce load on your Load Balancer's backend servers. The origin configuration you define is used by Edge Services to connect to your Load Balancer and request content, which is then stored in the cache. Then, when your Load Balancer origin is accessed via its customizable Edge Services endpoint, the requested content is served from the cache (if present), without the need to fetch this content via the Load Balancer and its backend servers.
 
-<Lightbox src="scaleway-edge-services-pipeline.webp" alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />
+<Lightbox src="scaleway-edge-services-pipeline-diag.webp" alt="A diagram shows the elements and workflow of an Edge Services pipeline. The user connects to the customizable Edge Services endpoint (with its SSL/TLS certificate), which fetches content from the Edge Services cache, which itself fetches content to cache from an origin which is either an Object Storage bucket or Load Balancer" />
 
 Edge Services lets you:
 
 - Define the specific origin (Load Balancer, frontend port, and host) for a given pipeline and its associated cache
 - Choose the TTL for cached objects, and purge the entire cache or specific cached objects at any time (cache invalidation)
+- Configure a [Web Application Firewall (WAF)](/edge-services/how-to/configure-waf/) to protect your origin from threats and malicious activity
 - Customize your Edge Services pipeline endpoint using a subdomain of your own domain
 - Add an SSL/TLS certificate so that Edge Services can serve content over HTTPS for your subdomain
 

macros/edge-services/assets/scaleway-edge-services-pipeline.webp

@@ -3678,6 +3678,10 @@
                     "label": "Configure a cache",
                     "slug": "configure-cache"
                   },
+                  {
+                    "label": "Configure WAF",
+                    "slug": "configure-waf"
+                  },
                   {
                     "label": "Monitor with Cockpit",
                     "slug": "monitor-cockpit"