Public Gateways
Public Gateways
What is a Public Gateway?
Public Gateways sit at the border of Private Networks. They provide services to deal with traffic entering and exiting the network (NAT), and SSH bastion. 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 do not want to use the NAT feature.
Can my Instances and other resources access the Internet without a public IPv4 address?
Yes. With NAT enabled, the Public Gateway shares its public IPv4 address (aka. flexible IP) with the Instances and other resources 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.
Why is a new VPC created for each of my Public Gateways?
This is a temporary measure until we release a new version of the Public Gateway which is fully compatible with our internal IPAM. For more information, see our dedicated documentation.
What happened to static leases (DHCP reservations) when DHCP moved from the Public Gateway to Private Networks?
On 12 July 2023, DHCP functionality moved from Public Gateways to Private Networks. See our dedicated migration documentation for full details.
Pre-existing static leases created via the Public Gateway were fully migrated and still work for your attached resources on a Private Network. Manual static lease configuration is still available via the API and other devtools, but is no longer available via the Scaleway console.