Step 2: Buy a VPC Endpoint

Scenarios

After you create a VPC endpoint service, you also need to buy a VPC endpoint to access the VPC endpoint service.

This section describes how to buy a VPC endpoint in another VPC of your own.

Select the same region and project as those of the VPC endpoint service.

Procedure

1. Go to the VPC endpoint list page.
2. On the VPC Endpoints page, click Buy VPC Endpoint.

   The Buy VPC Endpoint page is displayed.

3. Configure required parameters.

   Table 1 VPC endpoint parameters

   Parameter	Example Value	Description
   Region	EU-Dublin	Specifies the region where the VPC endpoint is to be located. This region is the same as that of the VPC endpoint service.
   Billing Modes	Pay-per-use	Specifies the billing mode of the VPC endpoint. VPC endpoints can be used or deleted at any time. VPC endpoints support only pay-per-use billing based on the usage duration.
   Service Category	Find a service by name	There are two options: Cloud services: Select this value if the target VPC endpoint service is a cloud service. Find a service by name: Select this value if the target VPC endpoint service is a private service of your own. In this example, select Find a service by name.
   VPC Endpoint Service Name	-	This parameter is available only when you select Find a service by name for Service Category. Enter the VPC endpoint service name recorded in 6 and click Verify. If "Service name found." is displayed, proceed with subsequent operations. If "Service name not found." is displayed, check whether the region is the same as that of the VPC endpoint service or whether the name entered is correct.
   Create a Private Domain Name	-	If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name. This parameter is mandatory when the VPC endpoint will be used to access an interface VPC endpoint service.
   VPC	-	Specifies the VPC where the VPC endpoint is to be deployed.
   Subnet	-	Specifies the subnet where the VPC endpoint is to be located.
   Private IP Address	-	This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service. Specifies the private IP address of the VPC endpoint. You can select Automatically assign or Manually specify.
   Access Control	Enable	This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service. It controls IP addresses and CIDR blocks that are allowed to access the VPC endpoint. If Access Control is enabled, only IP addresses or CIDR blocks in the whitelist are allowed to access the VPC endpoint. If Access Control is disabled, any IP address or CIDR block can access the VPC endpoint.
   Whitelist	-	This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service. Lists the IP addresses or CIDR blocks that are allowed to access the VPC endpoint. You can add a maximum of 20 records.
   Tag	example_key1 example_value1	Specifies the tag that is used to classify and identify the VPC endpoint. This parameter can be modified after you buy a VPC endpoint.
   Description	-	Provides supplementary information about the VPC endpoint.

   Table 2 Tag requirements for VPC endpoints

   Parameter	Requirement
   Tag key	Cannot be left blank. Must be unique for each resource. Can contain a maximum of 36 characters. Can contain only letters, digits, hyphens (-), and underscores (_).
   Tag value	Cannot be left blank. Can contain a maximum of 43 characters. Can contain only letters, digits, hyphens (-), and underscores (_).

4. Confirm the specifications and click Next.
   • If all of the specifications are correct, click Submit.
   • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
5. Manage the connection of the VPC endpoint.
   If the status of the VPC endpoint changes to Accepted, the VPC endpoint is connected to the required VPC endpoint service. If the status is Pending acceptance, connection approval is enabled for the VPC endpoint service, ask the owner of the VPC endpoint service to perform the following operations:

   1. Locate the VPC endpoint service and click its name.
   2. On the displayed page, select the Connection Management tab.
      • If you allow a VPC endpoint to connect to this VPC endpoint service, locate the VPC endpoint and click Accept in the Operation column.
      • If you do not allow a VPC endpoint to connect to this VPC endpoint service, click Reject in the Operation column.
   3. Go back to the VPC endpoint list and check whether the status of the target VPC endpoint changes to Accepted. If yes, the VPC endpoint is connected to the VPC endpoint service.
6. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.

   After a VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name during creation.

   You can use the private IP address or private domain name to access the VPC endpoint service.

Configuration Verification

Remotely log in to an ECS in VPC 1 by running an SSH command and access the private IP address or private domain name of the VPC endpoint, as shown in the following figure.

ssh -p Terminal port IP address of the VPC endpoint

According to the SSH protocol, set the service port to 22 when creating a VPC endpoint service. Or, the SSH command cannot be used for verification.