Diese Seite ist in Ihrer lokalen Sprache noch nicht verfügbar. Wir arbeiten daran, weitere Sprachversionen hinzuzufügen. Vielen Dank für Ihre Unterstützung.
VPC Endpoint
VPC Endpoint
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
-
VPC Endpoint Services
- VPC Endpoint Service Overview
- Creating a VPC Endpoint Service
- Viewing a VPC Endpoint Service
- Deleting a VPC Endpoint Service
- Managing Connections of a VPC Endpoint Service
- Managing Whitelist Records of a VPC Endpoint Service
- Viewing Port Mappings of a VPC Endpoint Service
- Managing Tags of a VPC Endpoint Service
- VPC Endpoints
- Permissions Management
- Quotas
-
VPC Endpoint Services
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Version Management
-
VPC Endpoint Services
- Creating a VPC Endpoint Service
- Querying VPC endpoint services
- Querying details of a VPC endpoint service
- Modifying a VPC endpoint service
- Deleting a VPC Endpoint Service
- Querying connections of a VPC endpoint service
- Accepting or Rejecting a VPC Endpoint
- Querying whitelist records of a VPC endpoint service
- Batch Adding or Deleting Whitelist Records of a VPC Endpoint Service
- Changing the Name of the VPC Endpoint Service
- This API is used to update the description of the VPC endpoint connection.
- Batch Adding or Deleting Whitelist Records of a VPC Endpoint Service
- Batch Adding or Deleting Whitelist Records of a VPC Endpoint Service
- Updating the Description of a Whitelist Record of a VPC Endpoint Service
-
VPC Endpoints
- Querying public VPC endpoint services
- Querying basic information of a VPC endpoint service
- Creating a VPC endpoint
- Querying VPC endpoints
- Querying details of a VPC endpoint
- Deleting Endpoint
- Updating the Whitelist of a VPC Endpoint
- Changing a route table of a VPC endpoint
- Modifying Route Tables Associated with a VPC Endpoint
- Modifying Route Tables Associated with a VPC Endpoint
- Resource Quotas
- Tags
- Application Examples
- Appendix
- Change History
- SDK Reference
- Best Practices
- FAQs
On this page
Show all
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
Resource and Cost Planning
Updated on 2024-12-13 GMT+08:00
The following table describes the resource planning in the best practice.
|
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 |
|
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
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
