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.

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

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 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 to connect 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 Interface VPC Endpoint Services

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.
   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 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 quicker access, select the region nearest to your on-premises data center.
   Billing Mode	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	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 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 Endpoint Type	This parameter is displayed based on the type of the VPC endpoint service to be connected. If you are going to connect to an interface VPC endpoint service, Interface is displayed by default. If you are going to connect a gateway VPC endpoint service, Gateway is displayed by default.
   VPC Endpoint Edition	This parameter is mandatory when you are going to connect to an interface VPC endpoint service. Professional is selected by default. Professional VPC endpoints are available in the CN East2, ME-Riyadh, CN East-Qingdao, and AF-Cairo regions. A VPC endpoint supports up to 10 Gbit/s of bandwidth and IPv4 and IPv6 dual stack.
   Network Type	This parameter is mandatory when you are going to connecting to an interface VPC endpoint service whose Mode is Advanced. This parameter can be set to IPv4 or Dual stack. IPv4: Only IPv4 networks are supported. Dual stack: Both IPv4 and IPv6 networks are supported.
   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.
   IPv4 Address	IPv4 addresses can be automatically assigned or manually specified.
   IPv6 Address	This parameter is mandatory when you select Professional for VPC Endpoint Edition and Dual stack for Network Type. IPv6 addresses can be automatically assigned or manually specified.
   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. It 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.
   Policy	Specifies the VPC endpoint policy. VPC endpoint policies are a type of resource-based policies. You can configure a policy to control which principals can use the VPC endpoint to access VPC endpoint services.
   Tag	This parameter is optional. It specifies the VPC endpoint tag, which 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. If you have configured tag policies for VPC Endpoint, 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.
   Description	Provides supplementary information about the VPC endpoint service.

   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 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 Gateway VPC Endpoint Services

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.
   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 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 quicker access, select the region nearest to your on-premises data center.
   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. 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. NOTE: You can configure OBS as a gateway VPC endpoint service on the VPC Endpoint console only in the LA-Mexico City1, LA-Sao Paulo1, and LA-Santiago regions. Select the VPC endpoint service for OBS by region: LA-Mexico City1: com.myhuaweicloud.na-mexico-1.obs LA-Sao Paulo1: com.myhuaweicloud.sa-brazil-1.obs LA-Santiago: com.myhuaweicloud.la-south-2.obs To access OBS as gateway VPC endpoint services in other regions, you need to search for it by name. To obtain its name, you can 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 "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.
   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. Select all route tables. Or, 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.
   Policy	Specifies the VPC endpoint policy. VPC endpoint policies are a type of resource-based policies. You can configure a policy to control which principals can use the VPC endpoint to access VPC endpoint services.
   Tag	This parameter is optional. It specifies the VPC endpoint tag, which 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. If you have configured tag policies for VPC Endpoint, 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.
   Description	Provides supplementary information about the VPC endpoint service.

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