diff --git a/pages/edge-services/faq.mdx b/pages/edge-services/faq.mdx
index 01a47b721a..3bbc4b3e74 100644
--- a/pages/edge-services/faq.mdx
+++ b/pages/edge-services/faq.mdx
@@ -42,6 +42,10 @@ Yes, if you choose to [customize your Edge Services endpoint with your own subdo
 
 For now, WAF is only compatible with Load Balancers and Object Storage. You must put other resources behind a Load Balancer in order to benefit from WAF. Watch this space for other solutions in the future.
 
+<Message type="note">
+WAF can be configured via the console for Load Balancer pipelines only. To configure WAF for an Object Storage bucket pipeline, use the [API](https://www.scaleway.com/en/developers/api/edge-services/).
+</Message>
+
 ## Can I use WAF and caching simultaneously?
 
 Yes, you can have both of these features enabled at the same time on the same Load Balancer pipeline. WAF protects your Load Balancer origin only: it does not filter requests served by the cache.
diff --git a/pages/edge-services/how-to/configure-waf.mdx b/pages/edge-services/how-to/configure-waf.mdx
index 6eb7e22ea5..7cc4a8dce1 100644
--- a/pages/edge-services/how-to/configure-waf.mdx
+++ b/pages/edge-services/how-to/configure-waf.mdx
@@ -29,6 +29,10 @@ To read more about how WAF works, try our [Understanding WAF](/edge-services/ref
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
 - An Edge Services pipeline for a [Load Balancer](/edge-services/how-to/create-pipeline-lb/) origin
 
+<Message type="note">
+WAF can be configured via the console for Load Balancer pipelines only. To configure WAF for an Object Storage bucket pipeline, use the [API](https://www.scaleway.com/en/developers/api/edge-services/).
+</Message>
+
 ## How to enable and configure WAF
 
 1. In the Scaleway console, navigate to the Edge Services dashboard for the Load Balancer pipeline on which you want to enable WAF:
diff --git a/pages/edge-services/reference-content/understanding-waf.mdx b/pages/edge-services/reference-content/understanding-waf.mdx
index 9599eaf8ed..da534a9d48 100644
--- a/pages/edge-services/reference-content/understanding-waf.mdx
+++ b/pages/edge-services/reference-content/understanding-waf.mdx
@@ -35,7 +35,6 @@ You can set **exclusions**, so that certain requests are not evaluated by WAF an
 
 In an Edge Services pipeline, WAF sits before the origin stage. This means that WAF only protects your origin, it does not protect or filter requests towards the cache.
 
-
 <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. A Web Application Firewall sits between the cache and origin, protecting the origin from threats." />
 
 If you have both WAF and cache enabled, requests that can be served by the cache will not go through WAF. Only requests that cannot be served by the cache will be filtered by WAF, and allowed to pass to the origin or not depending on your WAF configuration.
@@ -96,3 +95,4 @@ Each exclusion can consist of:
 - WAF protects your origin only, and not your cache.
 - You can add a maximum of 100 WAF exclusions
 - You cannot currently specify exclusions at the individual rule level. Requests matching exclusion filters bypass WAF entirely. 
+- WAF can be configured via the console for Load Balancer pipelines only. To configure WAF for an Object Storage bucket pipeline, use the [API](https://www.scaleway.com/en/developers/api/edge-services/)