Creating a Private NAT Gateway

You can a private NAT gateway to enable servers in your VPC to access or provide services accessible from on-premises data centers and other VPCs.

Manually add routes in a VPC to connect it to a remote private network through a VPC peering connection, Direct Connect, or VPN connection.
SNAT and DNAT rules cannot share a transit IP address.
The total number of DNAT and SNAT rules that can be added on a private NAT gateway varies with the private NAT gateway specifications.
- Small: 20 or less
- Medium: 50 or less
- Large: 200 or less
- Extra-large: 500 or less

When you create a private NAT gateway, you must specify its VPC, subnet, and specifications.

Log in to the management console.
Click Service List in the upper left corner. Under Network, select NAT Gateway.
The NAT gateway console is displayed.
In the navigation pane on the left, choose NAT Gateway > Private NAT Gateways.
On the Private NAT Gateways page, click Create Private NAT Gateway.

Configure required parameters. For details, see Table 1.

**Table 1** Descriptions of private NAT gateway parameters
Parameter	Description
Region	The region where the private NAT gateway is located
Name	The name of the private NAT gateway Enter up to 64 characters. Only digits, letters, underscores (_), hyphens (-), and periods (.) are allowed.
VPC	The VPC that the private NAT gateway belongs to The selected VPC cannot be changed after the private NAT gateway is created.
Subnet	The subnet that the private NAT gateway belongs to The subnet must have at least one available IP address. The selected subnet cannot be changed after the private NAT gateway is created.
Specifications	The specifications of the private NAT gateway The value can be Extra-large, Large, Medium, or Small. For details about specifications, see NAT Gateway Specifications.
Description	Supplementary information about the private NAT gateway Enter up to 255 characters. Angle brackets (<>) are not allowed.