- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Public NAT Gateway Operation Guide
- Private NAT Gateway Operation Guide
- Practical Tutorial
- Enabling Cross-VPC Access to Public Network via Standard NAT Gateway
- Enabling Mutual Access between a Specified VPC Subnet and Public Network Resources via Private NAT Gateway
- Enabling Secure Mutual Access with Public Network via Public CLB and NAT Gateway
- Adjusting the Priorities of NAT Gateways and EIPs
- API Documentation
- FAQ
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Public NAT Gateway Operation Guide
- Private NAT Gateway Operation Guide
- Practical Tutorial
- Enabling Cross-VPC Access to Public Network via Standard NAT Gateway
- Enabling Mutual Access between a Specified VPC Subnet and Public Network Resources via Private NAT Gateway
- Enabling Secure Mutual Access with Public Network via Public CLB and NAT Gateway
- Adjusting the Priorities of NAT Gateways and EIPs
- API Documentation
- FAQ
- Service Level Agreement
- Contact Us
- Glossary
NAT Gateway offers various packages based on product features and specifications, and is classified into Public NAT Gateway and Private NAT Gateway.
Public NAT Gateway
Public NAT Gateway enables multiple CVMs having no public IPs in the VPC to actively access the public network, and also supports mapping the EIPs and ports to the CVM's private IPs and ports so that the CVMs in the VPC can be accessed from the public network. It is classified into Traditional NAT Gateway and Standard NAT Gateway.
Note
Public NAT Gateway - Standard NAT Gateway is in beta testing and currently supports Beijing, Shanghai, Guangzhou, Chengdu, Chongqing, Hong Kong (China), Singapore, and Bangkok. If you need to use it, please submit a ticket for request.
Public NAT Gateway - Traditional NAT Gateway includes the original Small, Medium, and Large NAT Gateways.
After you activate the Standard NAT Gateway, the original NAT Gateway types will be automatically renamed as Traditional NAT Gateway - Small, Traditional NAT Gateway - Medium, and Traditional NAT Gateway - Large. For details, please see Announcement on the Renaming of the NAT Gateway Type.
If you do not activate the Standard NAT Gateway, the console experience will remain unchanged.
The comparison between the Standard NAT Gateway and the Traditional NAT Gateway is as follows:
Comparison Item | Standard NAT Gateway | Traditional NAT Gateway |
High availability | Natively supports multi-AZ disaster recovery. | Achieves cross-availability zone disaster recovery through rapid migration. |
Gateway specification | 2,000,000 concurrent connections 100,000 new connections per second 5 Gbps bandwidth cap | Supports 3 connection specifications: Small (up to 1,000,000 connections) Medium (up to 3,000,000 connections) Large (up to 10,000,000 connections) Peak bandwidth: Optional maximum public network outbound bandwidth (in Mbps): 10, 20, 50, 100, 200, 500, 1,000, 2,000, 5,000. Maximum public network inbound bandwidth: 5,000 Mbps by default, not adjustable. |
Gateway fee | Gateway fee = instance fee + CU (Capacity Unit) fee Instance fee: charged hourly. CU fee: charged by usage, namely calculated by converting the actual performance consumption to the number of CUs. | The fixed instance fee is charged hourly based on different gateway specifications. |
ECMP | Supported | Supported |
Gateway traffic control | Not supported yet | Supported |
Gateway traffic logs | Not supported yet | Supported |
Note
Public NAT Gateway supports binding up to 10 EIPs.
Restricted by standard protocols, for the same protocol/destination IP/destination port of SNAT, the maximum number of connections = number of bound EIPs * 55,000. To increase the number of connections, bind new EIPs or adjust the destination IP/port.
Hybrid ECMP of the Standard NAT Gateway and the Traditional NAT Gateway is not supported.
If you need other specifications, please submit a ticket.
Private Network NAT Gateway
Private NAT Gateway enables the CVM instances in the VPC to access public VPCs and also supports accessing the CVM instances from the public VPCs.
Note:
Private NAT Gateway is in beta testing and currently supports Guangzhou, Shanghai, Beijing, Chengdu, Chongqing, Hong Kong (China), Singapore, Tokyo, and Virginia. If you need to use it, please submit a ticket for request.
Yes
No
Was this page helpful?