Skip to navigationSkip to main contentSkip to footerScaleway Docs HomepageAsk our AI
Ask our AI

Serverless Containers and Private Networks integration

Compatibility

Scaleway Serverless Containers support Virtual Private Cloud (VPC) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. See Use Private Networks for more information.

VPC routing: custom routes and cross-PN automatic routing are supported on Serverless Containers.

Features

  • Containers in the same namespace can be attached to different Private Networks.
  • Both sandbox environments (V1 and V2) are compatible with Private Networks.
  • Attaching Serverless Containers to Private Networks does not incur additional costs.
  • Egress (outbound private traffic from a container to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be routed through the public endpoint of the container.
  • Enable the private endpoint for your container to support incoming traffic from other resources attached to Private Networks within the same VPC.
  • Disable the public endpoint for your container to isolate it from the public internet.
  • All DNS resolution is done through the Private Network (using the VPC DNS server 169.254.169.254), which allows to resolve *.internal records.

Quotas

See Organization Quotas for more information on Private Networks quotas for Serverless Containers.

Limitations

  • Only one Private Network can be attached to a Serverless Container.
  • Each container instance has a unique IP automatically assigned by Scaleway in the Private Network. This implies the following:
    • Users cannot preemptively book an IP with IPAM, and reference it in the attachment.
    • A single Serverless Container can have a large number of IPs being used within the Private Network, depending on the number of concurrent instances.
    • Cold-starts are slightly longer due to the additional steps required to attach the node to the Private Network and book an IP.

Transient connectivity issues

When a Serverless Container is attached to a Private Network, connections to other resources in the Private Network, such as a database, can occasionally fail or take longer to establish. For more information about how to mitigate these connection errors, see My container gets transient connection errors when connecting to Private Network resources.

Still need help?

Create a support ticket
No Results