Gateways
NAT gateway
A NAT gateway allows you to grant internet access permissions to cloud resources without assigning public IP addresses to them. Instead, they will access the internet via the NAT gateway that uses dynamic public IP addresses from the Yandex Cloud pool. These addresses may change. You cannot reserve them or assign a static public IP address to the gateway.
A gateway is a regional resource one can find in all availability zones. You can manage gateways using the management console, CLI, Terraform, or API.
To route traffic through a gateway, specify it as the next hop in a route table. Currently, you can only use a route with the 0.0.0.0/0 destination prefix with a NAT gateway: all traffic bound outside the network will pass through the gateway.
Note
If the external resource restrict access by IP addresses, keep in mind that public IP addresses of a NAT gateway may change and that you cannot reserve them. For access from a fixed IP address, use a NAT instance with a static public IP address. Add this address to the list of addresses allowed on the external resource.
Ranges of public IPv4 addresses of Yandex Cloud resources use different cloud clients. Adding all these ranges to the list of allowed ones will ensure network access from IP addresses of other clients as well.
If a VM network interface has a public IP address assigned, and the subnet this interface is connected to has a route table with a configured gateway, the VM will access the internet through the public IP address rather than the gateway.