How to create an Edge Services pipeline for an Object Storage bucket

Reviewed on 15 October 2024 • Published on 24 July 2024

Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. Creating an Edge Services pipeline towards your Object Storage bucket brings you a number of possible benefits:

Customize your bucket's endpoint using a subdomain of your own domain
Add your own SSL/TLS certificate, safeguarded in Scaleway Secret Manager, 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)

Read on to learn how to create an Edge Services pipeline for your Object Storage bucket.

Before you start

To complete the actions presented below, you must have:

A Scaleway account logged into the console
Owner status or IAM permissions allowing you to perform actions in the intended Organization
An active Edge Services subscription
An Object Storage bucket

How to create an Edge Services pipeline

Tip

You can create an Edge Services pipeline from the Object Storage section of the console, by navigating to your bucket’s dashboard and clicking the Edge Services tab. However, in this documentation, we describe how to create a pipeline directly from the Edge Services section of the console.

Click Edge Services in the Network section of the Scaleway console side menu.
Click Create pipeline. The pipeline creation wizard displays.
Select Object Storage as the origin type.
Choose the bucket you want this pipeline to serve content for, under Origin bucket.
Enter a name for the pipeline, or leave the randomly generated name in place.
Check the summary cost for the pipeline, and 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.

Important
Your bucket’s visibility can be set to private, but any objects within it that you want to expose via Edge Services must be set to public visibility. However, in the case that you are using Edge Services with bucket website, objects can remain private.

How to access your bucket via Edge Services

Once you have created an Edge Services pipeline for your bucket, you can access your bucket and its content via the following endpoints. Make sure that you replace bucket-name with the name of your bucket.

Endpoint	Where to find this endpoint in the console	Notes
`https://bucket-name.s3.nl-ams.scw.cloud`	The Bucket settings tab	Edge Services is bypassed when the bucket is accessed via this endpoint
`https://bucket-name.svc.edge.scw.cloud`	The Edge Services tab	Edge Services serves bucket content when this endpoint is used

The two endpoints shown above are available as standard. However, with Edge Services, you can also choose to configure a custom domain from which your bucket can be accessed. Read more about this in the next section.