Connect to the public network
You can use the following products or features to achieve access between VPC and the public network.
| Product | Features | Features |
|---|---|---|
| Ordinary Public IP | Support cloud servers accessing the internet or users accessing cloud servers from the public network. | Only available when purchasing cloud servers; if not assigned during purchase, you can use EIP or NAT Gateway. |
| Elastic Public IP (EIP) | A single cloud server can bind one or more EIPs to access the internet or be accessed from the public network. | A type of IP resource that can be independently purchased and owned. Can be dynamically bound and unbound with cloud servers and NAT gateways. You can adjust the bandwidth limit of EIP according to your business needs. |
| NAT Gateway | SNAT: Supports multiple cloud servers under the same VPC to access the internet through the same public IP. DNAT: Maps the private IP, protocol, and port of cloud servers within the VPC to external IP, protocol, and port, enabling services on cloud servers to be accessed from the public network. | NAT Gateway can be used for multiple cloud servers to access the internet. You can adjust the bandwidth limit of NAT Gateway according to your business needs. |
| Cloud Load Balancer (CLB) | By evenly distributing access traffic to multiple cloud servers to provide services externally. | Provides layer-4 and layer-7 CLB features based on ports, supporting users to access CVMs from the Internet through CLB (CLB). It eliminates single points of failure and improves the availability of application systems. |
| Public Gateway | A type of cloud server with forwarding capabilities enabled. Cloud servers without public IP addresses can access the internet through public gateways located in different subnets. | Unlike cloud servers with regular public IP addresses, public gateways can forward traffic from other subnet cloud servers to the internet, while cloud servers with regular public IP addresses can only meet their own internet access needs. If you need to use it, you need to refer to the Configure Cloud Server as Public Gateway page for self-configuration. |
Connect to other VPCs
You can use the following products or features to achieve communication between VPCs and one-way access to VPCs.
| Product | Features | Features |
|---|---|---|
| Peering connection | Used for intra-network communication between two VPCs. | The CIDRs of the two VPCs must not overlap. Manual configuration of routes is required. Support communication between VPCs in different accounts and regions. |
| Private Connection | Used for one-way service access between two VPCs. | It supports sharing application services deployed in VPC with other VPCs in the same account or across accounts through private connections. |
Connect to local data centers
You can use the following products or features to interconnect VPC with an on-premises data center.
| Product | Features | Features |
|---|---|---|
| VPN Connection | Establish a connection between the on-premises data center and VPC through an encrypted channel over the internet. | Network quality depends on the public internet. Network transmission is encrypted based on IKE protocol with pre-shared keys. |
| Direct Connect | Connects VPC and the on-premises data center using a physical dedicated connection. | Provide reliable network latency. Exclusive network link with high security. Supports configuring network address translation services on the gateway to resolve address conflicts. |
Connect to the classic network
You can use the following products or features to interconnect VPC with the classic network.
| Product | Features | Features |
|---|---|---|
| Classic Network Interconnection | Associates cloud servers in the classic network with a specified VPC, allowing cloud servers in the classic network to communicate with cloud servers, databases, and other cloud services in the VPC. | Cloud servers in the classic network can access cloud resources such as cloud servers, cloud databases, internal load balancers, and cloud caches in the VPC. Cloud servers in the VPC can only access interconnected cloud servers in the classic network and cannot access other computing resources in the classic network. |
| Terminal Connection | Enable instances in the VPC to communicate with non-cloud server instances in the classic network through the intranet. | Support basic network products for connection include: CLB, MySQL, Memcached, Redis®, and MongoDB. Terminal connections do not support cross-region or cross-account connections. If you need to establish a terminal connection, please submit a ticket for assistance. |