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 accounts in the same region can communicate with each other.

VPC 1 and VPC 2 belong to different accounts. You can configure ELB in VPC 2 as a VPC endpoint service and buy a VPC endpoint in VPC 1 so that the ECS in VPC 1 can access 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.
• Before you buy a VPC endpoint, add the authorized account ID of VPC 1 to the whitelist of the VPC endpoint service in VPC 2.
• For details about communications between two VPCs of the same account, see Configuring a VPC Endpoint for Communications Across VPCs of the Same Account.

Cross-VPC Communications

Figure 2 shows how to enable communications between two VPCs of different accounts using VPCEP.

Figure 2 Cross-VPC communications flowchart