Help Center/ VPC Endpoint/ Best Practices/ Using VPC Endpoint and Direct Connect to Enable On-premises Data Centers to Access Cloud Services/ Resource and Cost Planning
Updated on 2026-01-19 GMT+08:00
View PDF

Resource and Cost Planning

This section describes the resource and cost planning for using a VPC endpoint in a VPC to connect an on-premises data center to an ECS in another VPC. The details include:
Table 1 Description for cross-region VPC communications

Region

Resource

Description

Quantity

Billing

EU-Dublin

VPC

Subnet of VPC1: 192.168.0.0/16

Subnet of VPC2: 172.16.0.0/16

2

Free

Connection
  • Local subnet of the virtual gateway: 192.168.5.0/24
  • Local gateway of the virtual interface: 10.0.0.1/30
  • Remote gateway of the virtual interface: 10.0.0.2/30
  • Remote subnet of the virtual interface: 10.1.123.0/24

1

For details, see Direct Connect Product Pricing Details.

ECS

The IP address is automatically assigned.

2

For details, see ECS Product Pricing Details.

VPC endpoint

The IP address is automatically assigned.

1

For details, see VPC Endpoint Product Pricing Details.

The network topology is as follows.

  • The on-premises data center is connected to VPC1 through Direct Connect.
  • VPC1 accesses the ECS in VPC2 through the VPC endpoint service.
  • The on-premises data center accesses the ECS in VPC2 through VPC1.
Figure 1 Network topology