Beta

Public GatewayBeta

  • NAT
    Enable access between your Private Network and the internet using dynamic and static rules
  • DHCP
    Enable automatic IP address assignment for resources in your Private Network (dynamic and static)
  • DNS
    Enable local name resolution within your Private Network
  • Gateway to Private Networks
    Up to 8 Private Networks per Public Gateway
  • Compatible ressources
    Development Instances, General Purpose Instances, GPU Instances
Isolate your resources
Enhance security
Control your Network
Available Regions
  • fr-par-1
  • fr-par-2
  • nl-ams-1
  • pl-waw-1
  • Managed by Scaleway
  • Value-Added Features
  • Management via API
Free during beta

Compatible with

  • Dev Instances
  • GP Instances
  • GPU Instances

Automate configuration and enable communication between your Private Networks and the internet

The VPC Public Gateway sits at the border of your Private Networks and provides automatic IP address configuration and internet access to your resources within the Private Network.

A fully managed solution to gain control over your isolated, secure, Private Network

Automatically assign IP addresses to VMs

The DHCP protocol enables the automatic configuration of IP addresses within the subnet of your Private Network, either from a pool of available addresses, or through static assignment based on the MAC address.

Provide internet access to resources within your Private Networks

Dynamic NAT enables egress traffic from the Private Network to the public Internet by dynamically, automatically mapping the outgoing traffic IP addresses and ports with the public IP address and ports of the gateway.

Static NAT enables ingress traffic from the public Internet towards instances on the private network by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the private network.

Provide local name resolution

The Public Gateway acts as a local DNS server for the instances of a private network, resolving the instances’ IP addresses into their hostname.

Fully managed

Stay focused on your code, we handle all your Gateway management. Don’t lose time on your Instance-based Public Gateway’s administration, updates, setup or settings.
Plus, the Public Gateway implements an auto-healing mechanism, so that a failing device is automatically replaced with minimum impact on your traffic.

Discover our top Use Cases for Public Gateway

Automate IP configuration within your Private Network

With the Public Gateway, you don’t need to care about configuring IP addresses within your Private Network. Enable the DHCP feature, specify a subnet (or use the default preconfigured one for your Private Network) and let your instances receive their IP addresses automatically.

Access to the Internet from your Private Networks

The Public Gateway shares its public IPv4 address with your Private Networks via the NAT protocol. Instances within your Private Network do not need a public IP address to access the Internet, download packages or security updates.

Access to specific resources in your Private Network from the Internet

You can assign ports of the Public Gateway’s IPv4 address to specific private IP addresses and ports within your Private Network, for example to give access from the Internet to a web server within your Private Network, without having to configure a public IPv4 address on the instance running the web server.

Sharpen your knowledge on VPC with our blog articles

Discover our compute resources available with Public Gateway

You have a project? Call us:

Q&A

What is a Public Gateway?

Public Gateways sit at the border of private networks. They provide services to automate the allocation of private IP addresses (DHCP) and deal with traffic entering and exiting the network (NAT).

A Public Gateway can be attached to up to 8 Private Networks and up to 50 Public Gateways are supported per organization.

The Public Gateway can be configured through the console or the API.

Does the Public Gateway Require a Public IPv4 Address?

No. A public IPv4 address (aka. Flexible IP) must be assigned to the Public Gateway at creation time, but you can detach it and delete it afterward if you don’t want to use the NAT feature.

Do I Have to Restart Instances After Attaching a Public Gateway to my Private Network?

No. Instances in a Private Network for which autoconfiguration (DHCP) is enabled will automatically benefit from the services provided by the Public Gateway. Autoconfiguration is automatically enabled in recent instances. If your instance is too old, you may have to update it or enable autoconfiguration by hand. For more details about configuring instances, see here.

Can my Instance Access Internet Without a Public IPv4 Address?

Yes. With NAT enabled, the Public Gateway shares its public IPv4 address (aka. Flexible IP) with the instances attached to the Private Network, so that they can access the Internet.

Moreover, the Public Gateway supports static NAT (aka. port forwarding), so that ingress traffic from the public Internet can reach instances on the private network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the private network.