Buying a Private NAT Gateway

Scenarios

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

Notes and Constraints

• 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

Procedure

1. Go to the Buy Private NAT Gateway page.
2. Configure required parameters. For details, see Table 1.

   Table 1 Descriptions of private NAT gateway parameters

   Parameter	Description
   Billing Mode	Private NAT gateways can be billed on a pay-per-use basis.
   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 purchased.
   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 purchased.
   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.
   Enterprise Project	The enterprise project that the private NAT gateway belongs to. If an enterprise project has been configured, select the enterprise project. If you have not configured any enterprise project, select the default enterprise project.
   Tag	The private NAT gateway tag. A tag is a key-value pair. You can add up to 20 tags to each private NAT gateway. If you have configured tag policies for private NAT gateways, add tags to your private NAT gateways based on the tag policies. If you add a tag that does not comply with the tag policies, private NAT gateways may fail to be created. Contact your administrator to learn more about tag policies. The tag key and value must meet the requirements listed in Table 2.
   Description	Supplementary information about the private NAT gateway. Enter up to 255 characters. Angle brackets (<>) are not allowed.

   Table 2 Tag requirements

   Parameter	Requirement
   Key	Cannot be left blank. Must be unique for each NAT gateway. Can contain a maximum of 36 characters. Cannot contain equal signs (=), asterisks (*), left angle brackets (<), right angle brackets (>), backslashes (\), commas (,), vertical bars (|), and slashes (/), and the first and last characters cannot be spaces.
   Value	Can contain a maximum of 43 characters. Cannot contain equal signs (=), asterisks (*), left angle brackets (<), right angle brackets (>), backslashes (\), commas (,), vertical bars (|), and slashes (/), and the first and last characters cannot be spaces.

3. Click Buy Now.

Other Operations

• Assigning a Transit IP Address
• Adding an SNAT Rule
• Adding a DNAT Rule
• Managing Private NAT Gateways