HomeServerlessContainersHow to
Add a custom domain to a container
Jump toUpdate content

How to add a custom domain to a container

Reviewed on 19 September 2023Published on 21 February 2022

Each container comes with an automatically generated domain on which it is available. However, it is possible to use your own domain name to address your containers to facilitate their use.

Security & Identity (IAM):

You may need certain IAM permissions to carry out some actions described on this page. This means:

  • you are the Owner of the Scaleway Organization in which the actions will be carried out, or
  • you are an IAM user of the Organization, with a policy granting you the necessary permission sets
  • You have an account and are logged into the Scaleway console
  • A running Serverless Container
  • You have registered a domain name with the provider of your choice and have access to the domain name’s DNS zone file
  • If you are using Cloudflare DNS, see the note below regarding proxying
  1. On your domain provider’s platform (for example Scaleway’s domains), add a CNAME record pointing to your container default URL in the domain’s DNS zone file.

    • All domains are supported.
    • CNAME flattening is supported. CNAME flattening speeds up CNAME resolution and allows you to use a CNAME record at your root/apex domain.
    • If your DNS provider does not support CNAME flattening, you need to create an ALIAS on your root domain (named @ or with an empty name) instead of a CNAME.
  2. Click the Endpoints tab on your containers’ page.

  3. Click on + Add endpoint.

  4. Enter your custom domain name and validate the form.

  5. The console runs checks on the CNAME and TLS configuration of the custom domain name. Connect to your container using your custom domain once all checks have completed.


Be aware that Custom Domains does not currently support websockets. If you need to use websockets you must configure them with the original container URL.

Cloudflare DNS

If you are using Cloudflare DNS to configure your custom domain, you need to set the CNAME record’s proxy status to DNS Only while adding it to your container. We perform a number of validation checks on our side when configuring your domain, and if the CNAME record is proxied during these checks, the checks will fail.

Once you have configured your domain and your container is responding correctly, you can set the CNAME record back to Proxied if you wish.

The Cloudflare documentation on Proxy Status describes how to change the Proxy Status of a CNAME record via the Cloudflare web UI.

See Also