Each private link must contain an endpoint service. It is created and maintained by the service provider. When endpoints in another VPC send connection requests to the endpoint service, the endpoint service accepts the requests and establish private connections. After that, applications deployed in the service provider's VPC can be accessed in the VPC of another service consumer.
Prerequisites
(Service provider) Create the VPC and subnet.
Deploy the service to be accessed
Directions
1. Log in to the VPC console.
2. Select Private Link > VPC Endpoint Service in the left sidebar. On the page that appears, click Create.
3. Configure the endpoint service parameters in the pop-up window.
Parameter | Description |
Service name | The custom name of the endpoint service, which can contain up to 80 characters, including [a-z], [A-Z], [0-9], [_-.] and Chinese characters. |
Region | The region where the endpoint service is located. |
Network | Select the VPC. |
Service type | The type of the endpoint service. Currently, it supports private layer-4 CLB, MySQL and Redis instances. |
Backend service | The backend service instance ID. |
Accept endpoint connection requests | Specify whether the endpoint service automatically accepts the connection requests from endpoints. It is defaulted to No: Yes: The endpoint service accepts requests from all connected endpoints by default. After an endpoint is successfully created, it is in Available status. No: The connection status of the endpoint is Pending. You need to manually Accept the request to make the connection available. |
4. Click OK and the created endpoint service will be displayed in the list.
예
아니오
문제 해결에 도움이 되었나요?