Buying a Private NAT Gateway
Scenarios
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.
Constraints and Limitations
- 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 buy a private NAT gateway, you must specify its VPC, subnet, and specifications.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List in the upper left corner. Under Networking, 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 Buy Private NAT Gateway.
- Configure required parameters. For details, see Table 1.
Table 1 Descriptions of private NAT gateway parameters Parameter
Description
Billing Mode
Private NAT gateways are 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.
Tag
The private NAT gateway tag, which consists of a key and value pair. You can add up to 10 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.
- Click Buy Now.
Helpful Links
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot