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.

To select OBS as a gateway VPC endpoint service, you need to search for it by name. To obtain its name, submit a service ticket or contact the OBS O&M engineers.

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

• Buying a VPC Endpoint for Accessing an Interface VPC Endpoint Service
• Buying a VPC Endpoint for Accessing a Gateway VPC Endpoint Service

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 is deployed in the same region as the VPC endpoint.
• Only one basic VPC endpoint can be created in a VPC subnet for accessing a VPC endpoint service.
• When you create multiple VPC endpoints in a VPC for accessing the same VPC endpoint service, you can enable Create a Private Domain Name for only one VPC endpoint. If you want to access multiple VPC endpoints using a private domain name, you need to modify the DNS record set.
• VPC endpoints are billed based on the subscription duration.

Buying a VPC Endpoint for Accessing an Interface VPC Endpoint Service

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

   Table 1 VPC endpoint parameters

   Parameter	Description
   Region	Specifies the region where the VPC endpoint will be used to connect a VPC endpoint service. Resources in different regions cannot communicate with each other over an intranet. For lower latency and faster access, select the region nearest to where your services will be accessed.
   Billing Mode	Specifies the billing mode of the VPC endpoint. You are billed by how long you use each VPC endpoint. VPC endpoints can be used or deleted at any time. Only pay-per-use billing is supported.
   Service Category	There are two options: Cloud services: Select it if the target VPC endpoint service is a cloud service. Find a service by name: Select it if the target VPC endpoint service is your private service.
   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 VPC endpoint service, copy its name in the Name column, paste it to the VPC Endpoint Service Name text box, and click Verify. If the service is found, proceed with subsequent operations. If the service is not found, 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 deployed.
   Access Control	This parameter is available when you want to access an interface VPC endpoint service. You can specify IP addresses and CIDR blocks that are allowed to access the VPC endpoint. If Access Control is enabled, only IP addresses and CIDR blocks in the whitelist are allowed to access the VPC endpoint. If Access Control is disabled, any IP address and 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. You can specify the IP addresses and 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 (Optional)	Specifies the tags that are used to classify and identify the VPC endpoint. Each tag consists of a key and a value. You can add up to 20 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 Predefined Tag Overview.
   Description (Optional)	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 128 characters. Can contain letters, digits, spaces, and any of the following characters: _.:=+-@. It cannot start or end with a space, or start with _sys_.
   Tag value	Can be left blank. Can contain a maximum of 255 characters. Can contain letters, digits, spaces, and any of the following characters: _.:=+-@. It cannot start or end with a space.

4. Confirm the settings and click Next.
   • If all of the settings are correct, click Submit.
   • If any of the settings are incorrect, click Previous to modify the parameter settings as needed, and click Submit.

Buying a VPC Endpoint for Accessing a Gateway VPC Endpoint Service

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

   Table 3 VPC endpoint parameters

   Parameter	Description
   Region	Specifies the region where the VPC endpoint will be used to connect a VPC endpoint service. Resources in different regions cannot communicate with each other over an intranet. For lower latency and faster access, select the region nearest to where your services will be accessed.
   Billing Mode	Specifies the billing mode of the VPC endpoint. You are billed by how long you use each VPC endpoint. VPC endpoints can be used or deleted at any time. Only pay-per-use billing is supported.
   Service Category	There are two options: Cloud services: Select it if the target VPC endpoint service is a cloud service. Find a service by name: Select it if the target VPC endpoint service is your private service.
   Service List	This parameter is available only when you select Cloud services for Service Category. In the VPC endpoint service list, select a gateway VPC endpoint service. The VPC endpoint service has been created by the O&M personnel and you can directly use it. NOTE: To access OBS as a gateway VPC endpoint service, you need to search for it by name. To obtain its name, submit a service ticket or contact the OBS O&M engineers.
   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 5 and click Verify. If the service is found, proceed with subsequent operations. If the service is not found, check whether the region is the same as that of the VPC endpoint service or whether the name entered is correct.
   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 accessing 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, access may fail. Select the route tables in the VPC where the VPC endpoint is created as required. For details about how to add a route, see Adding a Custom Route in the Virtual Private Cloud User Guide.
   Tag (Optional)	Specifies the tags that are used to classify and identify the VPC endpoint. Each tag consists of a key and a value. You can add up to 20 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.
   Description (Optional)	Provides supplementary information about the VPC endpoint.

   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 128 characters. Can contain letters, digits, spaces, and any of the following characters: _.:=+-@. It cannot start or end with a space, or start with _sys_.
   Tag value	Can be left blank. Can contain a maximum of 255 characters. Can contain letters, digits, spaces, and any of the following characters: _.:=+-@. It cannot start or end with a space.

4. Confirm the settings and click Next.
   • If all of the settings are correct, click Submit.
   • If any of the settings are incorrect, click Previous to modify the parameter settings as needed, and click Submit.