检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
So, the four ECSs (ECS-A01, ECS-A02, ECS-B01, and ECS-B02) can communicate with each other, but they cannot receive traffic from the NAT gateway.
Notes and Constraints If you want to delete a subnet that has custom routes, virtual IP addresses, or other resources (ECSs, load balancers, or NAT gateways), you need to delete these resources as prompted on the console first. Procedure Log in to the management console.
If the local host communicates with the ECS using NAT, this problem may occur. Run the following command to check whether tcp_tw_recycle is enabled on the ECS: sysctl -a|grep tcp_tw_recycle If the value of tcp_tw_recycle is 1, the function is enabled.
Can Be Replicated to the Default Route Table Can Be Replicated to a Custom Route Table Local No No Server Yes Yes Extension NIC Yes Yes BMS user-defined network No Yes VPN gateway No Yes Direct Connect gateway No Yes Cloud connection No Yes Supplementary network interface Yes Yes NAT
Creates a NAT gateway with an EIP bound and configures SNAT rules to enable Subnet-01 to connect to the Internet. Account B Principal Creates ECSs and RDS instances in Subnet-01 to deploy applications that can be accessed over the Internet.
NAT gateway Creates and manages NAT gateways in the shared subnet. Cannot create NAT gateways in the shared subnet. VPN gateway Creates and manages VPN gateways in the shared subnet. Cannot create VPN gateways in the shared subnet.
subeni: IP address of a supplementary network interface neutron:LOADBALANCERV2: IP address of a shared load balancer neutron:LOADBALANCERV3: IP address of a dedicated load balancer network:endpoint_interface: IP address of a VPC endpoint network:nat_gateway: IP address used by a NAT
You can bind EIPs to products such as ECSs, NAT gateways, and load balancers so that these products can use the shared bandwidth. Shared Data Package A shared data package is a prepaid package for public network traffic.
Each EIP can only be bound to one cloud resource, such as an ECS, a NAT gateway, or a load balancer. A shared bandwidth can be used by multiple pay-per-use EIPs. The shared bandwidth is dynamically allocated to the EIPs based on the actual usage conditions.
You can use EIPs, NAT gateways, Direct Connect connections, VPN connections, and load balancers to enable access to or from the Internet. By default, instances in different VPCs cannot communicate with each other.
To enable this, you can use the NAT Gateway service or configure an SNAT server. For details, see Enabling Internet Connectivity for an ECS Without an EIP. Parent Topic: VPC Peering Connection
subeni: IP address of a supplementary network interface neutron:LOADBALANCERV2: IP address of a shared load balancer neutron:LOADBALANCERV3: IP address of a dedicated load balancer network:endpoint_interface: IP address of a VPC endpoint network:nat_gateway: IP address used by a NAT
subeni: IP address of a supplementary network interface neutron:LOADBALANCERV2: IP address of a shared load balancer neutron:LOADBALANCERV3: IP address of a dedicated load balancer network:endpoint_interface: IP address of a VPC endpoint network:nat_gateway: IP address used by a NAT
You can use EIP, NAT Gateway, or ELB to allow the resources in VPCs to access or be accessed by the public network.
If you want multiple resources to share an EIP, refer to Using NAT Gateway and VPC Peering to Enable Communication Between VPCs and Internet. Figure 6 Networking diagram Parent Topic: VPC Peering Connection Usage
