Scenarios and Advantages
Private Link provides the capability for VPCs to access other VPCs through internal networking. It facilitates easy connections between various services across VPCs within the same account or across different accounts. Compared to public network services, it can save public network bandwidth, offer higher security, and significantly simplify network architecture.
With Private Link, you can establish secure and stable private connections between VPCs and cloud services, simplifying network architecture and avoiding potential security risks associated with accessing services via the public network.
Product Components
Private Link involves two important product entities:
- Terminal node services: Terminal node services are services that can be accessed by other VPCs through the creation of terminal nodes to establish private network connections. Terminal node services are created and managed by service providers.
- Terminal nodes: Terminal nodes can be associated with terminal node services to establish network connections for accessing external services via VPC private networks. Terminal nodes are created and managed by service users.
Restrictions
Quotas for Terminal Node Services
| Resources | Limitation |
|---|---|
| The quantity of Terminal Node Services per single account. | 100 |
| The quantity of Terminal Nodes that can be added to a single Terminal Node Service. | 500 |
| Supported resource types for the backend service of an Terminal Node Service. | Application-type Layer-4 CLB in the internal network; each Terminal Node Service is associated with 1 CLB and can be associated with multiple listeners. |
| Traffic supported by Terminal Node Service | - IPv4 traffic - IPv6 traffic |
| Protocols supported by "Terminal Node Service" | TCP protocol, UDP protocol, and HTTP protocol |
Quotas for "Terminal Node"
| Resources | Limitation |
|---|---|
| Quantity of Terminal Nodes that can be created per single VPC. | 50 |
| Quantity of Terminal Node Services that can be associated with a single Terminal Node. | 1 |
| Traffic supported by Terminal Node. | - IPv4 traffic - IPv6 traffic |
| Protocols supported by Terminal Node. | TCP protocol, UDP protocol, and HTTP protocol |
Billing description
- No instance fees are charged for Terminal Nodes and Terminal Node Services.
- No traffic communication fees are charged for Terminal Nodes and Terminal Node Services.
- No fees are charged for internal network CLB instances