Buying a VPC Endpoint

Scenarios

VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.

You can buy a VPC endpoint to connect a resource in your VPC to a VPC endpoint service in another VPC of the same region.

VPC endpoints for accessing gateway VPC endpoint services can be purchased only in regions LA-Mexico City1, LA-Sao Paulo1, and LA-Santiago.

You can buy an interface or a gateway VPC endpoint based the type of the associated VPC endpoint service.

• Buying a VPC Endpoint for Accessing Interface VPC Endpoint Services
• Buying a VPC Endpoint for Accessing Gateway VPC Endpoint Services

Constraints

• VPC endpoints are region-level resources. Select a region and project when you buy such a VPC endpoint.
• Each tenant can buy a maximum of 50 VPC endpoints.
• When you buy a VPC endpoint, ensure that the associated VPC endpoint service exists and is in the same region as the VPC endpoint.
• VPC endpoints are billed based on the subscription duration.

Buying a VPC Endpoint for Accessing Interface VPC Endpoint Services

1. Log in to the management console.
2. Click in the upper left corner and select the required region and project.
3. Click Service List and choose Networking > VPC Endpoint.
4. On the VPC Endpoints page, click Buy VPC Endpoint.
5. On the Buy VPC Endpoint page, configure the parameters.
   Figure 1 Buy VPC Endpoint (Service Category set to Cloud services)
   
   Figure 2 Buy VPC Endpoint (Service Category set to Find a service by name)
   

   Table 1 VPC endpoint parameters

   Parameter	Description
   Region	Specifies the region where the VPC endpoint is to be located. Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
   Billing Mode	Specifies the billing mode of the VPC endpoint. VPC endpoints can be used or deleted at any time and support only pay-per-use billing based on the usage duration.
   Service Category	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.
   Service List	This parameter is available only when you select Cloud services for Service Category. The VPC endpoint service has been created by the O&M personnel and you can directly use it.
   VPC Endpoint Service Name	This parameter is available only when you select Find a service by name for Service Category. In the VPC endpoint service list, locate the target VPC endpoint service, copy its name in the Name column, paste it to the VPC Endpoint Service Name text box, 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	This parameter is available when you want to access an interface VPC endpoint service. Specifies the subnet where the VPC endpoint is to be located.
   Private IP Address	This parameter is available when you want to access an interface VPC endpoint service. Specifies the private IP address of the VPC endpoint. You can select Automatically assign or Manually specify. This parameter needs to be configured only in some regions. For details, see the information displayed on the console.
   Access Control	This parameter is available when you want to access 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 when you want to access an interface endpoint service and Access Control is enabled. Lists the IP addresses or CIDR blocks that are allowed to access the VPC endpoint. You can add a maximum of 20 records. 0.0.0.0 and CIDR blocks in x.x.x.x/0 format are not supported.
   Tag	This parameter is optional. Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 10 tags to each VPC endpoint. Tag keys and values must meet requirements listed in Table 2. NOTE: If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value. For details about predefined tags, see Overview. If you have configured tag policies for VPC endpoints, you need to add tags to this VPC endpoint based on the tag policies. If you add a tag that does not comply with the tag policies, VPC endpoints may fail to be created. Contact your administrator to learn more about tag policies.

   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. Cannot start or end with a space or contain special characters =*<>\,|/
   Tag value	Cannot be left blank. Can contain a maximum of 43 characters. Cannot start or end with a space or contain special characters =*<>\,|/

6. 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.

Buying a VPC Endpoint for Accessing Gateway VPC Endpoint Services

1. Log in to the management console.
2. Click in the upper left corner and select the required region and project.
3. Click Service List and choose Networking > VPC Endpoint.
4. On the VPC Endpoints page, click Buy VPC Endpoint.
5. On the Buy VPC Endpoint page, configure the parameters.
   Figure 3 Buy VPC Endpoint (Service Category set to Cloud services)
   

   Table 3 VPC endpoint parameters

   Parameter	Description
   Region	Specifies the region where the VPC endpoint is to be located. Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
   Billing Mode	Specifies the billing mode of the VPC endpoint. VPC endpoints can be used or deleted at any time and support only pay-per-use billing based on the usage duration.
   Service Category	Specifies the type of services that are configured as gateway VPC endpoint services. Only cloud services are supported. Select Cloud services.
   Service List	This parameter is available only when you select Cloud services for Service Category. In the VPC endpoint service list, select the VPC endpoint service whose type is gateway. The VPC endpoint service has been created by the O&M personnel and you can directly use it.
   VPC	Specifies the VPC where the VPC endpoint is to be deployed.
   Route Table	This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service. NOTE: This parameter is available only in the regions where the route table function is enabled. You are advised to select all route tables. Otherwise, the access to OBS may fail. Select a route table required for the VPC where the VPC endpoint is to be located. For details about how to add a route, see Adding a Custom Route in the Virtual Private Cloud User Guide.
   Tag	This parameter is optional. Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 10 tags to each VPC endpoint. Tag keys and values must meet requirements listed in Table 4. NOTE: If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value. For details about predefined tags, see Predefined Tag Overview. If you have configured tag policies for the VPC endpoint service, add tags to VPC endpoint services based on the tag policies. If you add a tag that does not comply with the tag policies, VPC endpoint services may fail to be created. Contact your administrator to learn more about tag policies.

   Table 4 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. Cannot start or end with a space or contain special characters =*<>\,|/
   Tag value	Cannot be left blank. Can contain a maximum of 43 characters. Cannot start or end with a space or contain special characters =*<>\,|/

6. 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.