Edge Services is an additional feature for Scaleway Object Storage buckets, currently available in Private Beta. You must be pre-approved for the Private Beta in order to test Edge Services in the Scaleway console.
Enabling Edge Services on your Object Storage bucket brings you a number of possible benefits:
It is currently only possible to enable and manage Edge Services via the Scaleway console. You cannot carry out Edge Service actions on the Scaleway API, CLI or other developer tools.
Read on to learn how to enable Edge Services on your bucket, and configure your endpoint and cache.
To complete the actions presented below, you must have:
Edge Services is available as a feature on Object Storage buckets. It must be enabled on a bucket-by-bucket basis.
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to enable Edge Services on.
Click the Edge Services tab.
Click Enable Edge Services for free.
A pop-up informs you that your bucket will be exposed via Edge Services and that you can disable Edge Services at any time. Edge Services is free during the beta stage, and you will be notified before it becomes billable.
Click Enable Edge Services to confirm.
Edge Services is enabled on your bucket, and its various features are now visible on the Edge Services tab, ready to be configured.
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 (see below), objects can remain private.
Note the following important information about using Edge Services with the bucket website feature:
Once you have enabled Edge Services on your bucket, you can access your bucket and its content via the following endpoints (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 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.
If you already own a domain, you can use Edge Services to set a subdomain of your choice through which your bucket can be accessed.
For example, if you own beautiful-domain.com, you can configure your bucket to be accessed via the subdomain whatever-i-want.beautiful-domain.com. You must also add an SSL/TLS certificate so that your subdomain can securely serve your bucket’s content via HTTPS.
| Endpoint | Where to find this endpoint in the console | Notes |
|---|---|---|
https://whatever-i-want.beautiful-domain.com | The Edge Services tab (after customization) | Edge Services serves bucket content when this endpoint is used. The pre-existing endpoints shown in the table in the previous section also continue to be functional as before. |
You cannot customize your endpoint with a primary domain directly (e.g. beautiful-domain.com), only with a subdomain of it.
The procedure for adding a customized endpoint is as follows:
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to configure a custom domain for.
Click the Edge Services tab.
In the Endpoint panel, click Configure domain. The following screen displays:
Set a subdomain from which your bucket will be accessible. 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.
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. ✅ blog.example.com ❌ example.com
This step depends on whether the domain used in the previous step is managed with Scaleway Domains and DNS, or an external domain provider. Choose the appropriate tab below.
The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if:
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, to point your subdomain to the Edge Services endpoint for your bucket. This record is generated when you click Customize domain in step 8.
You should not attempt to modify or delete the CNAME record, which will be visible among your DNS records in the Scaleway console.
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 into your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services endpoint for your bucket displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, check out our dedicated documentation
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.
Provide an SSL/TLS certificate for your subdomain so that it can serve traffic over HTTPS. You have three options for this:
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.
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 bucket through this domain, its content will be served via Edge Services.
If you chose to generate a managed Let’s Encrypt certificate, allow a few minutes for the certificate to finish creating. When the process is complete and the certificate is ready, you will see a green status light for SSL/TLS certificate on your endpoint dashboard.
After customizing your domain, you can edit it (or its certificate) at any time as follows:
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to configure a custom domain for.
Click the Edge Services tab.
In the Endpoint panel, click Edit. The Edit Domain screen displays.
Edit the subdomain as desired - do not forget to also set up a new CNAME record, if necessary.
Edit your certificate options as required - choose to generate a managed Let’s Encrypt certificate, managed by Scaleway including automatic renewals, or select a different certificate from Secret Manager, or manually import a new certificate for your custom domain.
Click Edit domain to finish.
Even though the original Edge Services endpoint (e.g. https://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:
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to configure a custom domain for.
Click the Edge Services tab.
In the Endpoint panel, click Reset.
A screen displays warning you that this will reset the bucket’s domain back to the default Edge Services endpoint. Edge Services will consider your customized subdomain as unknown. You should also remember to:
Click Reset domain to finish.
The cache feature allows you to cache your bucket’s content with Edge Services. This means that content can be served directly to users from Edge Services’ servers, enhancing performance.
You can disable and enable caching at will, as well as control the lifetime of an object in the cache. You can also purge your entire cache, or specific objects within it. A log is displayed to help you track your purge events.
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to configure a cache for.
Click the Edge Services tab.
In the Cache panel, use the «Toogle Icon» icon to enable the cache.
The Lifetime configuration box displays. This enables you to define, in seconds, how long an object can be stored in the cache before it must be retrieved freshly from the bucket.
As an example, a value of 0 means that objects will not be cached, unless they have a separately-defined caching directive. Note that in any case, if an object has a caching directive, the caching directive always takes precedence over any lifetime setting defined here in Edge Services.
Leave the default value of 1 hour in place, or enter another value.
The cache is now enabled.
This clears all objects from your cache. Afterwards, Edge Services will retrieve fresh copies from the bucket before it stores them again in the cache.
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to purge the cache for.
Click the Edge Services tab.
In the Purge cache panel, click Purge all.
A screen displays warning you that your cache will be emptied, and Edge Services will have to retrieve objects from your bucket before re-caching them.
Click Purge cache to confirm.
This allows you to specify the precise objects that you want to clear from the cache. Afterwards, Edge Services will retrieve fresh copies from the bucket before it stores them again in the cache.
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to purge cache objects for.
Click the Edge Services tab.
In the Purge cache panel, click Purge by object.
A screen displays prompting you to enter the path of each object you want to purge from the cache.
Enter the path of each object you want to purge. You can purge a maximum of 5 objects at a time.
The path for each object should be defined from the root of the bucket, and must start with a slash. If we imagine a bucket containing one file at the root level called object1.jpg, and a subfolder at root level called videos containing an item called my-video.mp4, we would enter the object paths as follows:
/object1.jpg/videos/my-video.mp4You cannot purge entire subfolders by simply specifying the path to the subfolder, e.g. /videos. Purging objects must done strictly object-by-object, so /videos/my-video1.mp4, /videos/my-video2.mp4, /videos/my-video3.mp4 etc. Watch this space for updates to this feature in the future.
Click Purge objects from cache
The specified objects are purged from your cache and you are returned to the Edge Services dashboard.
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to disable caching for.
Click the Edge Services tab.
In the Cache panel, use the «Toogle Icon» icon to disable the cache.
A pop-up displays, asking you to confirm the action.
Click Disable cache.
Your cache is purged and disabled. Edge Services will now serve content by fetching it from your Object Storage bucket directly. If you reenable your cache at a later point, you will begin with an empty cache.
You can view your Edge Services metrics via Scaleway Cockpit. This allows you to monitor your ingress, egress, request rate and cache hit ratio as well as other metrics, in a convenient managed Grafana dashboard.
Access your Edge Services dashboard in the Scaleway console via the shortcut in Edge Services tab of the bucket in question. Note that you will first need to create a Grafana user and credentials.
The Grafana dashboard presents a number of different metrics. Use the Bucket name drop-down in the top left to select which bucket to view Edge Services metrics for, and the time range drop-down in the top right to modify the time period to apply to the metrics.
Request rate: The number of requests made to Edge Services per second, for the specified bucket, averaged over the specified time period.
Cache hit ratio: The percentage of requests served from Edge Services’ cache, compared to the total number of requests in total to Edge Services for this bucket, over the specified time period.
Cache HIT/MISS: A visual representation of the ratio of cache hits to misses, for the specified bucket, over the specified time period.
Egress (to client): The total volume of data served to clients from Edge Services, for the specified bucket, over the specified time period.
Ingress (from origin): The total volume of data from the origin bucket’s server to Edge Services over the specified time period. This represents the traffic that occurs when Edge Services retrieves content from the bucket’s server in order to fulfill requests.
Edge Services throughput: A visual representation of the rate of data transfer for the specified bucket with Edge Services over the specified time period.
Requests served: The total number of requests that Edge Services has successfully served, for the specified bucket, over the specified time period.
Edge Services response statuses: A visual representation of the distribution of HTTP response statuses for requests served by Edge Services over the specified time period. Consult the full list of HTTP status codes for more information if necessary.
Request origin country: The proportion of requests (to Edge Services for the specified bucket over the specified time period) originating from different countries.
End users location: A visual representation of where Edge Services end users have been making requests from geographically.
You can disable Edge Services at any time via the following procedure:
Click Object Storage in the Storage section of the Scaleway console side menu. The list of your buckets displays.
Click the name of the bucket you want to disable Edge Services for.
Click the Edge Services tab.
In the Disable Edge Services panel at the bottom of the screen, click Disable Edge Services.
A pop-up displays, informing you that the bucket will be removed from Edge Services.
Remember to:
Click Disable Edge Services.
Edge Services is disabled. You can enable it again at any time, but you will need to reconfigure your custom domain, and the cache will initially be empty.