How to deploy a Serverless Container behind Edge Services

Reviewed on June 15, 2026

Before you start

To complete the actions presented below, you must have:

Owner status or IAM permissions allowing you to perform actions in the intended Project

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.

Going further

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

Configure caching to optimize content delivery performance
Configure WAF to add web application firewall protection
Monitor with Cockpit to track your pipeline's metrics and logs
Add a custom domain to your Edge Services pipeline
Secure a container with IAM authentication for private access
Use Private Networks to connect your Serverless Container to other Scaleway resources in an isolated network

Limitations

Note

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

Before you start

Introduction

Going further

Limitations