This document describes the network products related to NAT Gateway.
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.
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.
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.
For more information about EIPs, see Elastic IP.
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.
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.
The table below lists other products related to the NAT Gateway:
|CVM||The NAT Gateway and the EIP are two ways for CVM instances to access the Internet.|
|EIP||The EIP and the NAT Gateway are two ways for CVM instances to access the Internet.|
|VPC||NAT Gateway is part of VPC.|
|Route Table||After creating a NAT Gateway, you need to configure routing policies to direct the subnet traffic to the NAT Gateway.|
|Public Gateway||A public gateway is a CVM with the forwarding feature enabled and can be accessed by NAT Gateway.|
|Anti-DDoS Pro||Anti-DDoS Pro instance can be bound to a NAT Gateway to defend against DDoS and CC attacks.|
|Network ACL||Use network ACL to finely control the inbound and outbound traffic of subnets.|