Quickstart
Learn how to create an Edge Services pipeline.
View QuickstartEdge Services WAF is now available via the Edge Services API!
Web Application Firewall (WAF) for Edge Services is now in Public Beta and available via the Edge Services API. Enable WAF to protect your Load Balancer origin from threats and malicious requests. Find out more in our dedicated documentation.
Edge Services
Edge Services is a feature for Scaleway Load Balancers and Object Storage buckets. It provides a caching service to improve performance by reducing load on your origin, and a customizable, secure endpoint for accessing content via Edge Services.
Edge Services QuickstartGetting StartedLink to this anchor
Concepts
Core concepts that give you a better understanding of Edge Services.
View ConceptsHow-tos
Check our guides to creating and configuring Edge Services.
View How-tosAdditional Content
Go beyond the basics with detailed, in-depth guides to configuring Edge Services.
Read moreEdge Services API
Manage Edge Services pipelines using the Scaleway API.
Go to Edge Services APIChangelogLink to this anchor
Edge Services
Scaleway’s Web Application Firewall (WAF) is currently available in public beta and provides automated protection for web applications against common threats and vulnerabilities, including SQL injection, XSS, remote code execution, and more. It is based on the OWASP Core Rule Set to detect and block malicious requests.
This WAF solution is fully managed and designed to be easy to integrate into existing architectures, particularly when combined with Scaleway's Edge Services.
WAF is currently available only via the Edge Services API.
Edge Services
DeprecatedEdge Services v1alpha1 deprecation
The Edge Services
v1alpha1API is about to be deprecated. Update your tooling to use the Edge Servicesv1beta1API if you are still using it.View the
v1beta1documentation on the Edge Services API reference page.
Edge Services
Starting November 13, 2024, Edge Services cache servers will change how they handle HTTP (
port 80) requests. Instead of serving content over HTTP, they will issue anHTTP 302redirect to HTTPS (port 443), keeping the rest of the URL unchanged. This update applies only to Edge Services integrations with Object Storage.
Questions?
Visit our Help Center and find the answers to your most frequent questions.
Visit Help CenterWas this page helpful?