- 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
This document describes the network products related to NAT Gateway.
EIP
The NAT Gateway and the EIP are two ways for a CVM instance to access the public network. You can use either or both of them in your public network access architecture.
Method 1: using NAT Gateway only
The CVM instance without any public IP uses the public IP of the NAT Gateway to access the public network. Traffic to the public network is forwarded to the NAT Gateway via the private network.
Method 2: using the EIP only
The CVM instance uses EIPs to access the public network without any NAT Gateway. Traffic to the public network will be forwarded from the EIP.
Method 3: using NAT Gateway and EIP
Note:
The CVM instance is bound with an EIP, and the route table directs all traffic from the subnet to the public network to the NAT Gateway.
All traffic from the CVM instance to the public network uses the NAT Gateway through the private network, and the response packets are returned through the NAT Gateway. If you want to use the EIP to access the public network, you can adjust priorities of NAT Gateways and EIPs.
When the traffic from the public network uses the EIPs to access CVM, the CVM response packets are returned through the EIPs.
Bandwidth Package
If your NAT Gateway is bound with multiple EIPs, you can add them to the IP bandwidth package to share the bandwidth and save public network costs. For more information, see Product Overview.
Other Products
The table below lists other products related to the NAT Gateway:
Product Name | Relationship |
The NAT Gateway and the EIP are two ways for CVM instances to access the Internet. | |
The EIP and the NAT Gateway are two ways for CVM instances to access the Internet. | |
NAT Gateway is part of VPC. | |
After creating a NAT Gateway, you need to configure routing policies to direct the subnet traffic to the NAT Gateway. | |
A public gateway is a CVM with the forwarding feature enabled and can be accessed by NAT Gateway. | |
Anti-DDoS Pro instance can be bound to a NAT Gateway to defend against DDoS and CC attacks. | |
Use network ACL to finely control the inbound and outbound traffic of subnets. |
Yes
No
Was this page helpful?