diff --git a/macros/edge-services/edge-services-bucket-benefits.mdx b/macros/edge-services/edge-services-bucket-benefits.mdx
index 6e9bdd70cf..552563275d 100644
--- a/macros/edge-services/edge-services-bucket-benefits.mdx
+++ b/macros/edge-services/edge-services-bucket-benefits.mdx
@@ -2,9 +2,11 @@
 macro: edge-services-bucket-benefits
 ---
 
+import EdgeServicesPipelineNoWAF from './assets/scaleway-edge-services-pipeline-nowaf.webp'
+
 - Customize your bucket's endpoint using a subdomain of your own domain
 - Add your own SSL/TLS certificate, safeguarded in [Scaleway Secret Manager](/secret-manager/quickstart/), or generate a managed Let's Encrypt certificate, so your subdomain can serve content from your bucket over HTTPS
 - 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-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" />
\ No newline at end of file
+<Lightbox image={EdgeServicesPipelineNoWAF} 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" />
diff --git a/macros/edge-services/edge-services-lb-benefits.mdx b/macros/edge-services/edge-services-lb-benefits.mdx
index 99514fb61a..ad2a0dcacc 100644
--- a/macros/edge-services/edge-services-lb-benefits.mdx
+++ b/macros/edge-services/edge-services-lb-benefits.mdx
@@ -2,9 +2,11 @@
 macro: edge-services-lb-benefits
 ---
 
+import EdgeServicesPipelineDiag from './assets/scaleway-edge-services-pipeline-diag.webp'
+
 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-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" />
+<Lightbox image={EdgeServicesPipelineDiag} 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:
 
@@ -14,4 +16,4 @@ Edge Services lets you:
 - 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
 
-An Edge Services pipeline can be created for any Load Balancer with a public IP address. Load Balancers with frontends/backends using both TCP and/or HTTP are supported. [Private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers) are not compatible with Edge Services.
\ No newline at end of file
+An Edge Services pipeline can be created for any Load Balancer with a public IP address. Load Balancers with frontends/backends using both TCP and/or HTTP are supported. [Private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers) are not compatible with Edge Services.