This document will introduce you to network products related to NAT Gateway.
Elastic IP
NAT Gateway and EIP are two ways for CVMs to access the internet. You can choose one or both for the architecture design of your public network access.
Solution 1: Use only a NAT Gateway
The CVM is not bound to an EIP. Traffic accessing the internet is forwarded to the NAT Gateway through the private network and is not subject to the public network bandwidth limit at the time of purchase. The network traffic generated by the NAT Gateway does not occupy the public network bandwidth outlet of the CVM.
Solution 2: Use only an EIP
The CVM is only bound to an EIP and does not use a NAT Gateway. All internet access traffic is transferred out through the EIP and is subject to the public network bandwidth limit at the time of purchase.
Solution 3: Use both a NAT Gateway and an EIP
The CVM is bound to an EIP, and the subnet route accessing the internet traffic points to the NAT Gateway.
- All traffic from CVMs actively accessing the internet is only forwarded to the NAT Gateway through the private network. The return packet also passes through the NAT Gateway and returns to the CVM. This part of the traffic is subject to the public network bandwidth limit at the time of purchase.
- When traffic from the internet actively accesses the EIP of the CVM, the CVM return packets are uniformly returned through the EIP, and the generated public network outbound traffic is subject to the public network bandwidth limit at the time of purchase.
For more information about EIP, see document Elastic IP Overview.
Other Products
For related product information, see the following table:
| Product | Relationship with NAT Gateway |
|---|---|
| Cloud Virtual Machine | NAT Gateway and EIP are two ways for CVMs to access the internet. |
| Elastic IP | EIP and NAT Gateway are two ways for CVMs to access the internet. |
| Virtual Private Cloud | NAT Gateway is a sub-product of VPC. |
| Route Tables | After you create a NAT Gateway, you need to configure routing rules to direct subnet traffic to the NAT Gateway. |
| Public Gateway | The public network gateway is a CVM with a forwarding feature enabled, which supports NAT connect. |
| Network ACL | After the subnet where the NAT Gateway backend CVM is located is bound to the network ACL, the traffic in and out of the subnet can be precisely controlled. |