forked from docs/doc-exports
Qin Ying, Fan
54b39691a8
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com> Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
3.1 KiB
3.1 KiB
Overview
Scenarios
With VPCEP, you can access resources across VPCs in the same region.
Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP addresses. After you create a VPC endpoint, you can use a private IP address to access resources across two VPCs despite of network isolation between them.
This section describes how cloud resources in VPCs of different domains in the same region can communicate with each other across VPCs.
VPC 1 and VPC 2 belong to different domains , respectively. You can take the ELB in VPC 2 as a VPC endpoint service and create a VPC endpoint in VPC 1 so that the ECS in VPC 1 can access the ELB in VPC 2 using the private IP address.
Figure 1 Cross-VPC communications
- Only one-way communications from the VPC endpoint to the VPC endpoint service are supported.
- For details about communications between two VPCs of different domains, see Configuring a VPC Endpoint for Communications Across VPCs of Different Domains.
Configuration Process
Figure 2 shows how to enable communications between VPCs of the same domain using VPCEP.
