Provision a Vultr NAT Gateway so VPC instances without public IPs reach the internet, via Console, API, or CLI.
Vultr NAT Gateway provides centralized, secure internet egress for compute instances on a VPC that do not have public IP addresses. The service supports controlled inbound access via port forwarding, with all traffic governed by NAT Gateway firewall rules. Typical use cases include isolating workloads from the public internet while allowing package updates, conserving IPv4 addresses, and simplifying perimeter security by managing rules at the gateway.
Follow this guide to provision a NAT Gateway subscription using the Vultr Console, API, CLI, or Terraform.
NAT Gateway provisions automatically when you create a VPC Network with Private Instances behind NAT Gateway connectivity. This approach creates both the VPC and NAT Gateway subscription simultaneously.
Navigate to Products, expand the Network drop-down and select VPC Networks.
Click Add VPC Network.
Enter a new label in the VPC Network Name field to identify the network.
In the VPC Connectivity section, select Private Instances behind NAT Gateway.
This option automatically provisions a NAT Gateway subscription for the VPC.
Select your target Vultr location to deploy the VPC Network and NAT Gateway.
In the Network Settings section, enable Custom IP Range to enter a custom private IPv4 subnet, or keep it disabled to automatically assign an IP range.
Review the Summary panel to verify the configuration and monthly cost.
Click Create VPC Network.
0 Comments
Be the first to comment and share your perspective with the community.