Skip to navigationSkip to main contentSkip to footerScaleway Docs HomepageAsk our AI
Ask our AI
Log inSign up

How to deploy a Serverless Container behind Edge Services

Before you start

To complete the actions presented below, you must have:

Introduction

This guide walks you through deploying a Serverless Container behind a Scaleway Edge Services pipeline. Create a namespace and deploy a container. Then configure an Edge Services pipeline with stages for backend routing, TLS termination, and DNS to expose a public endpoint.

Note

This same procedure applies to Serverless Functions. The Edge Services backend stage supports both backends. Replace the container namespace and container resources with the equivalent Function namespace and function resources. Then use the corresponding function ID in the backend stage configuration.

Important

Edge Services forwards incoming requests to your Serverless Container and Serverless Functions through its default (auto-generated) endpoint, not through a custom domain. It cannot reach a private or IAM-secured container, so the backend container must be public.

Going further

Now that you have deployed your Serverless Container behind Edge Services, you can explore additional configurations:

Limitations

Note

Availability: This feature is available via the API, CLI, SDK, and Terraform. It is not available in the Scaleway console.

Note

You cannot disable the default endpoint of a Serverless Container or Serverless Function, for example to keep only a custom domain. This capability is planned for a future release. The default endpoint stays active, and Edge Services relies on it to forward requests to the container or function.

See Also
How to configure alerts for a containerHow to delete a container
Still need help?

Create a support ticket
No Results