feat(edge): Edge Services GA

faq/edge-services.mdx

@@ -12,15 +12,21 @@ category: network
 
 ## What is Edge Services?
 
-Edge Services is a feature for Scaleway Load Balancers and Object Storage buckets, currently available in [Public Beta](https://www.scaleway.com/en/betas/). It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/network/edge-services/concepts/#origin), and a customizable and secure endpoint for accessing content via Edge Services, which can be set to a subdomain of your choice.
+Edge Services is a feature for Scaleway Load Balancers and Object Storage buckets. Creating Edge Services [pipelines](/network/edge-services/concepts/#pipeline) towards your Load Balancers or Object Storage buckets provides: 
+-A [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/network/edge-services/concepts/#origin), and 
+- A customizable and secure endpoint for accessing content via Edge Services, which can be set to a subdomain of your choice and secured with an SSL/TLS certificate.
+
+<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" />
 
 ## Which products are compatible with Edge Services?
 
 Edge Services is currently available for Scaleway [Object Storage buckets](/storage/object/) and Scaleway [Load Balancers](/network/load-balancer/).
 
 ## How much does Edge Services cost?
 
-Since Edge Services is currently in Public Beta, it is free to use and not billed. On November 1st 2024, it will transition to General Availability, and pricing will be based on subscription plans. See our documentation for help with understanding the [transition to General Availability](/network/edge-services/reference-content/understanding-ga/).
+On November 1st 2024, Edge Services transitioned from Public Beta to General Availability, and became billable. Pricing is based on [monthly subscription plans](https://www.scaleway.com/en/pricing/network/#edge-services): three plans are available, each allowing a fixed number of pipelines, and a certain amount of egress cache data. Any consumption that exceeds the limits of the plan is charged at an additional rate.
+
+Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page.
 
 ## If I customize my Edge Services endpoint with my own domain, can it serve content over HTTPS?
 

macros/edge-services/edge-services-bucket-benefits copy.mdx

@@ -0,0 +1,10 @@
+---
+macro: edge-services-bucket-benefits
+---
+
+- Customize your bucket's endpoint using a subdomain of your own domain
+- Add your own SSL/TLS certificate, safeguarded in [Scaleway Secret Manager](/identity-and-access-management/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.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/edge-services-lb-benefits.mdx

@@ -0,0 +1,16 @@
+---
+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" />
+
+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)
+- 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](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers) are not compatible with Edge Services.

menu/navigation.json

@@ -3075,6 +3075,10 @@
                     "label": "Use a Load Balancer with a Private Network",
                     "slug": "use-with-private-network"
                   },
+                  {
+                    "label": "Set up an Edge Services pipeline",
+                    "slug": "use-edge-services"
+                  },
                   {
                     "label": "Set up a customized error page",
                     "slug": "set-up-s3-failover"
@@ -3193,6 +3197,10 @@
               },
               {
                 "items": [
+                  {
+                    "label": "Subscribe to Edge Services",
+                    "slug": "subscribe-edge-services"
+                  },
                   {
                     "label": "Create an Object Storage pipeline",
                     "slug": "create-pipeline-bucket"
@@ -3214,8 +3222,12 @@
                     "slug": "monitor-cockpit"
                   },
                   {
-                    "label": "Delete or disable an Edge Services pipeline",
+                    "label": "Delete an Edge Services pipeline",
                     "slug": "delete-pipeline"
+                  },
+                  {
+                    "label": "Terminate an Edge Services subscription",
+                    "slug": "terminate-edge-services"
                   }
                 ],
                 "label": "How to",
@@ -3231,6 +3243,10 @@
                     "label": "CNAME records for Edge Services",
                     "slug": "cname-record"
                   },
+                  {
+                    "label": "Understanding pricing",
+                    "slug": "understanding-pricing"
+                  },
                   {
                     "label": "Understanding General Availability",
                     "slug": "understanding-ga"
@@ -4230,6 +4246,10 @@
                     "label": "Use Object Storage with Private Networks",
                     "slug": "use-obj-stor-with-private-networks"
                   },
+                  {
+                    "label": "Set up an Edge Services pipeline",
+                    "slug": "get-started-edge-services"
+                  },
                   {
                     "label": "Delete an object",
                     "slug": "delete-an-object"

network/edge-services/concepts.mdx

@@ -8,7 +8,7 @@ content:
 tags: edge-services edge services pipeline custom-domain cache
 dates:
   creation: 2024-07-24
-  validation: 2024-07-24
+  validation: 2024-10-14
 categories:
   - networks
 ---
@@ -29,7 +29,7 @@ The CNAME record pointing your subdomain to the Edge Services endpoint, if you h
 
 ## Edge Services
 
-Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets, currently available in [Public Beta](https://www.scaleway.com/en/betas/). It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](#origin), and a customizable and secure [endpoint](#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice.
+Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](#origin), and a customizable and secure [endpoint](#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice.
 
 ## Endpoint
 
@@ -56,9 +56,11 @@ The Load Balancer defined by the user as origin for a given Edge Services pipeli
 
 ## Pipeline
 
+<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" />
+
 An Edge Services pipeline consists of an [origin](#origin) for which Edge Services requests and [caches](#cache) content, and an [endpoint](#endpoint) from which this content is served via Edge Services. The pipeline's endpoint can be customized with a user-defined [subdomain](#subdomain) and associated [certificate](#certificate) so that Edge Services can serve content over HTTPS. 
 
-You can create one or more Edge Services pipelines for each of your Object Storage buckets or Load Balancer origins. 
+You can create an Edge Services pipelines for each of your Object Storage buckets  or Load Balancer origins. Note that the cache can be enabled and disabled at will, so is an optional part of the pipeline, as is the customization of the endpoint.
 
 ## Protocol
 

network/edge-services/how-to/configure-cache.mdx

@@ -6,7 +6,7 @@ content:
   h1: How to configure an Edge Services cache
   paragraph: Learn how to configure a cache for Edge Services. Enhance performance and finely control your cached objects via purging (cache invalidation).
 dates:
-  validation: 2024-07-24
+  validation: 2024-10-15
   posted: 2024-07-24
 tags: object-storage edge-services cdn network cache purge
 categories:
@@ -19,7 +19,7 @@ You can disable and enable caching at will, as well as control the lifetime of a
 
 ## How to enable the cache
 
-1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin for which you want to enable caching:
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline on which you want to enable caching:
 
     <Lightbox src="scaleway-edge-services-dashboard.webp" alt="A screenshot of the Edge Services dashboard in the Scaleway console. This is a dashboard for Edge Services on an Object Storage bucket, showing links to the documentation, Scaleway Cockpit, the endpoint, cache settings and a button to disable the pipeline." />
 
@@ -41,7 +41,7 @@ The cache is now enabled.
 
 Purging objects clears all objects from your cache. Afterward, Edge Services will retrieve fresh copies from the origin (Object Storage bucket or Load Balancer) before it stores them again in the cache.
 
-1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose cache you want to purge:
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge:
 
     <Lightbox src="scaleway-edge-services-dashboard.webp" alt="A screenshot of the Edge Services dashboard in the Scaleway console. This is a dashboard for Edge Services on an Object Storage bucket, showing links to the documentation, Scaleway Cockpit, the endpoint, cache settings and a button to disable the pipeline." />
 
@@ -57,7 +57,7 @@ Purging objects clears all objects from your cache. Afterward, Edge Services wil
 
 This allows you to specify the precise objects that you want to clear from the cache. Afterward, Edge Services will retrieve fresh copies from the origin (Object Storage bucket or Load Balancer) before it stores them again in the cache.
 
-1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose cache you want to purge:
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to purge:
 
     <Lightbox src="scaleway-edge-services-dashboard.webp" alt="A screenshot of the Edge Services dashboard in the Scaleway console. This is a dashboard for Edge Services on an Object Storage bucket, showing links to the documentation, Scaleway Cockpit, the endpoint, cache settings and a button to disable the pipeline." />
 
@@ -88,9 +88,19 @@ This allows you to specify the precise objects that you want to clear from the c
 
     The specified objects are purged from your cache and you are returned to the Edge Services dashboard.
 
+## How to use Cache-Control
+
+To avoid repeated purging, you can also set the `Cache-Control` HTTP header directly on your files/objects. This allows you to define how long items should remain in the cache before being freshly retrieved from the origin. Edge Services will respect this header when determining from where to fetch content.
+
+For Object Storage bucket origins, the following example call to the S3 API updates the `Cache-Control` header for **all** objects in the bucket, setting a maximum age of 60 seconds before they must be freshly retrieved. 
+
+```
+./s3cmd --recursive modify --add-header="Cache-Control:max-age=60" s3://yourbucket/
+```
+
 ## How to disable your cache
 
-1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose cache you want to disable:
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose cache you want to disable:
 
     <Lightbox src="scaleway-edge-services-dashboard.webp" alt="A screenshot of the Edge Services dashboard in the Scaleway console. This is a dashboard for Edge Services on an Object Storage bucket, showing links to the documentation, Scaleway Cockpit, the endpoint, cache settings and a button to disable the pipeline." />
 

network/edge-services/how-to/configure-custom-domain.mdx

@@ -6,7 +6,7 @@ content:
   h1: How to configure a custom domain for Edge Services
   paragraph: Learn how to configure an Edge Services endpoint with a custom subdomain. Access your Object Storage bucket or Load Balancer origin via your own domain name instead of the standardized endpoint.
 dates:
-  validation: 2024-07-24
+  validation: 2024-10-15
   posted: 2024-07-24
 tags: object-storage edge-services cdn network domain ssl tls https
 categories:
@@ -23,7 +23,7 @@ You cannot customize your endpoint with a primary domain directly (e.g. `beautif
 
 The procedure for adding a customized endpoint is as follows:
 
-1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose domain you want to customize:
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage or Load Balancer pipeline whose domain you want to customize:
 
     <Lightbox src="scaleway-edge-services-dashboard.webp" alt="A screenshot of the Edge Services dashboard in the Scaleway console. This is a dashboard for Edge Services on an Object Storage bucket, showing links to the documentation, Scaleway Cockpit, the endpoint, cache settings and a button to disable the pipeline." />
 
@@ -94,7 +94,7 @@ If you chose to generate a managed Let's Encrypt certificate, allow a few minute
 
 After customizing your domain, you can edit it (or its certificate) at any time as follows:
 
-1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose domain you want to customize:
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to customize:
 
     <Lightbox src="scaleway-edge-services-dashboard.webp" alt="A screenshot of the Edge Services dashboard in the Scaleway console. This is a dashboard for Edge Services on an Object Storage bucket, showing links to the documentation, Scaleway Cockpit, the endpoint, cache settings and a button to disable the pipeline." />
 
@@ -110,7 +110,7 @@ After customizing your domain, you can edit it (or its certificate) at any time
 
 Even though the original Edge Services endpoint (e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`) will continue to work after you add a customized domain, you can choose to remove your customized domain completely and go back to the original Edge Services endpoint only. This is done via the reset function:
 
-1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer origin whose domain you want to reset:
+1. In the Scaleway console, navigate to the Edge Services dashboard for the Object Storage bucket or Load Balancer pipeline whose domain you want to reset:
 
     <Lightbox src="scaleway-edge-services-dashboard.webp" alt="A screenshot of the Edge Services dashboard in the Scaleway console. This is a dashboard for Edge Services on an Object Storage bucket, showing links to the documentation, Scaleway Cockpit, the endpoint, cache settings and a button to disable the pipeline." />