---
title: Edge Services - Quickstart
description: Quickly set up Scaleway Edge Services pipeline to serve cached content with our guide. Learn to configure pipelines, customize endpoints, and manage caching for optimal performance.
tags: edge-services edge services pipeline custom-domain cache
dates:
  validation: 2026-06-09
  creation: 2024-07-24
---
import Requirements from '@macros/iam/requirements.mdx'

import image from './assets/scaleway-edge-services-pipeline.webp'

Edge Services is a comprehensive solution for exposing HTTP services to the internet with built-in security, reliability, and performance. Creating Edge Services [pipelines](/edge-services/concepts/#pipeline) towards your Scaleway resources provides:

- A [caching service](/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [backend](/edge-services/concepts/#backend), and 
- A [Web Application Firewall](/edge-services/how-to/configure-waf/) to protect your backend from threats and malicious activity, 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.

To use Edge Services, you must take out a subscription plan, which then enables you to create a certain number of Edge Services pipelines towards your backends.

<Lightbox image={image} 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 a backend. A Web Application Firewall sits between the cache and backend, protecting the backend from threats." />

<Requirements />

- A Scaleway account logged into the [console](https://console.scaleway.com)
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
- Created either a [Load Balancer](/load-balancer/how-to/create-load-balancer/) or an [Object Storage bucket](/object-storage/how-to/create-a-bucket/)

<Message type="tip">
You can also use Serverless Containers and Serverless Functions as Edge Services backends. This feature is not available in the Scaleway console. See [How to deploy a Serverless Container behind Edge Services](/serverless-containers/how-to/deploy-container-behind-edge-services/) for instructions using the CLI or Terraform.
</Message>

## How to subscribe to Edge Services

To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan includes a fixed number of pipelines, a certain amount of egress cache data, and a fixed number of WAF requests. 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](/edge-services/reference-content/understanding-pricing/) page, or follow the steps below to subscribe.

1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu.

2. Click **Subscribe to Edge Services**. Information about available [pricing plans](https://www.scaleway.com/en/pricing/network/#edge-services) is displayed.

3. Select a plan, and click **Subscribe to Edge Services**.

    Your subscription is created, and you are returned to the Edge Services dashboard, on the **Pipelines** tab. All your Edge Services pipelines will display here.

    On the **Plans** tab you can view your current subscription plan, and your Edge Services consumption in relation to your plan's limits on pipelines, cache and WAF.

## How to create an Edge Services pipeline

You can create a [pipeline](/edge-services/concepts/#pipeline) for any of your backends.

1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu.

2. Click **Create pipeline**. The pipeline creation wizard displays.

3. Under **Configure backend**, select the **Backend type** for this pipeline, then configure the backend depending on the type you selected:

    <Tabs>
      <TabsTab label="Load Balancer">
        - Select the **Zone** of the Load Balancer you want this pipeline to serve content for.
        - Select the **Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content.
        - Select a **frontend** associated with the Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same Load Balancer, each one must be configured for a different frontend.
        - Select the **Protocol** that Edge Services should use when making requests to the backend, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup.
        - Optionally, enter a [Destination host](/edge-services/concepts/#destination-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. If no destination host is specified, the Host from the incoming request will be used.

        <Message type="tip">
        For Kubernetes Load Balancers, see our [dedicated documentation](/edge-services/how-to/create-pipeline/#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend.
        </Message>

      </TabsTab>
      <TabsTab label="Object Storage">
        - Select the **Region** of the bucket you want this pipeline to serve content for.
        - Select the **bucket** itself from the dropdown list.

      </TabsTab>
    </Tabs>

4. Under **Configure options**, set the options you want for this pipeline:
    - **Cache**: When enabled, content from your backend is cached with Edge Services and served directly to users from Edge Services' servers. Set a **Lifetime** value to dictate how long objects should remain in the cache before being freshly retrieved from the backend. A value of `0` means objects will not be cached, unless they have a caching directive. [Find out more about caching](/edge-services/how-to/configure-cache/).
    - **WAF**: When enabled, requests to your backend are evaluated by a Web Application Firewall. Malicious requests are blocked or logged, depending on your settings. Set a paranoia level to determine WAF aggressivity, and a mode (block or log) for dealing with malicious requests. [Find out more about WAF](/edge-services/reference-content/understanding-waf/).

5. Enter a name for the pipeline, or keep the randomly generated one.

6. Check the cost summary for the pipeline, then click **Create Edge Services pipeline**.

    You are returned to the **Pipelines** tab, where the newly created pipeline now displays. Click on the pipeline to go to its **Overview** page and start configuration.

    <Message type="important">
    For Object Storage backends, your bucket's [visibility](/object-storage/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [public](/object-storage/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private.
    </Message>

## How to configure a custom domain

If you already own a domain, you can customize an Edge Services pipeline endpoint with a subdomain of your choice, e.g. `subdomain.mydomain.com`. This means you can access your backend through Edge Services via your own subdomain rather than the standardized Edge Services endpoint.

1. In the Scaleway console, navigate to the Edge Services dashboard for the pipeline whose domain you want to customize:

2. In the **Endpoint** panel, click **Configure domain**. The following screen displays:

3. Set a subdomain from which your backend will be accessible via its Edge Services pipeline. You must already own the primary domain. For example, if you own `beautiful-domain.com`, choose any subdomain you like and enter `my-chosen-subdomain.beautiful-domain.com` into the box.

    <Message type="important">
    It is **not** possible to use only a root domain (aka primary domain or apex domain), you must use a subdomain. This is because CNAME records, essential to point your domain to your Edge Services endpoint, cannot by definition be created for root domains, only for subdomains.
    </Message>

4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/domains-and-dns/), or an external domain provider. Choose the appropriate tab below.

    <Tabs>
    
        <TabsTab label="Domains and DNS">
        The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if:
        - You [registered the domain](/domains-and-dns/how-to/register-internal-domain/) with Domains and DNS, or
        - You [transferred an externally-registered domain](/domains-and-dns/how-to/transfer-external-domain/) to Domains and DNS

        If either of the above is true, Scaleway will auto-detect that the domain is managed by Domains and DNS, and a message will display confirming that you do not need to create a CNAME record. We will auto-generate the appropriate CNAME record in your domain's [DNS records](/domains-and-dns/how-to/manage-dns-records/), to point your subdomain to the Edge Services endpoint. This record is generated when you click `Customize domain` in step 6.

        You should not attempt to modify or delete the CNAME record, which will be visible among your [DNS records](/domains-and-dns/how-to/manage-dns-records/) in the Scaleway console.
        </TabsTab>

        <TabsTab label="External provider">
        Scaleway cannot itself create the appropriate CNAME record to point your subdomain to Edge Services if your domain is managed by an external provider. You must create the CNAME record yourself.

        Log in to your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services pipeline endpoint displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, [check out our dedicated documentation](/edge-services/reference-content/cname-record/).

        Back in the Scaleway console, click the `Verify CNAME` button to check whether your CNAME record has been correctly configured. Edge Services will carry out a check, and if it is successful the following message displays:

        If the check fails, an error message will display. See the documentation linked above for help troubleshooting such errors. Note that it may take a short time for the DNS record to be propagated and the check to pass.
        </TabsTab>
    </Tabs>

5. Provide an SSL/TLS certificate for your subdomain so that Edge Services can serve traffic for it over HTTPS. You have three options for this:
    - Generate a free Let's Encrypt certificate, managed by Scaleway, including automatic renewals.
    - Select an existing certificate that you have stored in [Scaleway Secret Manager](/secret-manager/quickstart/).
    - Manually import a certificate into Scaleway Secret Manager:
      - Enter a name for your certificate (alphanumeric characters only)
      - Optionally, add tags by typing each tag and then pressing enter
      - Copy and paste the full PEM-formatted certificate chain into the box.
      Your certificate will be automatically stored in Secret Manager and [billed accordingly](https://www.scaleway.com/en/pricing/security-and-account/).

    <Message type="tip">
    For help with SSL/TLS certificates for Edge Services, and/or dealing with any errors you encounter importing a certificate into Secret Manager, see our [dedicated documentation](/edge-services/reference-content/ssl-tls-certificate/).
    </Message>

6. Click **Customize domain** to finish.

Your customized domain is set up, and you are returned to the Edge Services dashboard. The customized domain displays in the Endpoint panel. When you access your backend through this domain, its content will be served via Edge Services.

## How to configure caching and WAF

Enabling a cache and/or a Web Application Firewall on your Edge Services pipeline are both optional steps.

- Enabling a **cache** means that Edge Services stores copies of files from your backend, and can serve them directly to users from this cache rather then fetching them freshly from your backend each time. This reduces load on your backend and can improve performance. [Find out how to configure a cache](/edge-services/how-to/configure-cache/)

- Enabling **WAF** means that Edge Services can filter out and block potentially malicious requests to your backend. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set exclusions  to define traffic that shouldn't be filtered by WAF. [Find out how to configure WAF](/edge-services/how-to/configure-waf/)

## How to delete an Edge Services pipeline

1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. The **Pipelines** tab displays.

2. Click the pipeline that you want to delete. You are taken to the pipeline's **Overview** page.

3. In the **Delete Edge Services pipeline** panel at the bottom of the screen, click **Delete Edge Services pipeline**.

    A pop-up displays, asking you to confirm that you want to delete the pipeline.
      - The backend will no longer be accessible via its Edge Services endpoint, or any customized domains pointing to this endpoint.
      - Any files stored in the Edge Services cache will be removed.
    
    <Message type="tip">
    If you customized your pipeline's domain, remember to:
        - Delete any CNAME records created for this pipeline from your domain provider, unless your domain is managed with Scaleway Domains and DNS, in which case we take care of deletion for you.
        - Delete any SSL/TLS certificates you imported into Secret Manager for this pipeline (if no longer required elsewhere), so that you are no longer billed for them. If you generated a managed Let's Encrypt certificate however, Scaleway takes care of the deletion for you.
    </Message>

4. Click **Confirm**.

    The Edge Services pipeline is deleted. You can create a new pipeline for this backend at any time, but you will need to reconfigure your custom domain, and the cache will initially be empty.

## How to terminate an Edge Services subscription

You can terminate your Edge Services subscription at any time, as long as you have deleted all your pipelines. You will be charged pro rata for the month you cancel, based on how many days in that month your subscription was active.

1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays.

2. Click the **Plans** tab. An overview of your current plan displays, along with options to manage your plan or terminate your subscription.

3. Scroll down to the **Terminate subscription** section, and click **Terminate subscription**.

    A pop-up displays, asking you to confirm that you want to terminate your subscription.

4. Type **DELETE** in the box, and click **Terminate** to confirm.

    Your Edge Services subscription is terminated. You can subscribe again at any time.