Step 1: Create a VPC Endpoint Service
Scenarios
To enable communication across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.
This section describes how to create a VPC endpoint service by selecting an elastic load balancer as an example backend service in VPC 2 using domain B.
Prerequisites
There are available backend resources in the same VPC.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services and click Create VPC Endpoint Service.
The Create VPC Endpoint Service page is displayed.
- Set the required parameters.
Table 1 Required parameters Parameter
Description
Region
Specifies the region where the VPC endpoint service is located.
Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.
VPC
Specifies the VPC where the VPC endpoint service is located.
Service Type
Specifies the type of the VPC endpoint service. The value can only be Interface.
Connection Approval
Specifies whether the connection between a VPC endpoint and a VPC endpoint service requires approval from the owner of the VPC endpoint service.
You can determine whether to enable or disable the connection approval.
If connection approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see step 7.
Port Mapping
Specifies the protocol and ports used for communication between the VPC endpoint service and VPC endpoint. The protocol is TCP.
- Service Port: A service port is provided by the backend service bound to the endpoint service.
- Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
The service and terminal port numbers range from 1 to 65535. A maximum of 50 port mappings can be added at a time.
NOTE:Accessing a VPC endpoint service from a VPC endpoint is to access the service port from the associated terminal port.
Backend Resource Type
Specifies the type of the backend resource that provides services to be accessed.
The following backend resources are supported:
- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
Example: Elastic load balancerNOTE:Security groups use the whitelist mechanism. For the security group containing the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/20. For details, see section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide.
Load Balancer
When Backend Resource Type is set to Elastic load balancer, select the load balancer that provides services from the drop-down list.
NOTE:If an elastic load balancer is used as the backend resource, the source IP address received by the VPC endpoint service is not the real address of the client.
Tag
This parameter is optional.
Specifies the VPC endpoint service tag, which consists of a key and a value. You can add a maximum of 10 tags to each VPC endpoint service.
Tag keys and values must meet requirements listed in Table 2.
Table 2 Tag requirements for VPC endpoint services Parameter
Requirement
Tag key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 Unicode characters.
- Cannot start or end with a space or contain special characters =*<>\,|/
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Cannot start or end with a space or contain special characters =*<>\,|/
- Click Create Now.
- Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view the details.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot