Help Center/ VPC Endpoint/ Getting Started/ Configuring a VPC Endpoint for Communications Across VPCs of Different Accounts/ Step 3: Buy a VPC Endpoint
Updated on 2023-08-18 GMT+08:00
View PDF

Step 3: Buy a VPC Endpoint

Scenarios

After you add the required whitelist record, you can buy a VPC endpoint in VPC 1 to connect to the target VPC endpoint service.

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

Procedure

  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.

    The Buy VPC Endpoint page is displayed.

  5. Configure required parameters.
    Table 1 VPC endpoint parameters

    Parameter

    Description

    Region

    Specifies the region where the VPC endpoint is to be located. This region is the same as that of the VPC endpoint service.

    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.

    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 step 8, 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 connected 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 when buying a VPC endpoint.

    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

    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

    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 Predefined Tag Overview.
    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.
  7. 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. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
    2. Locate the target VPC endpoint service and click its name.
    3. On the displayed page, select the Connection Management tab.
      • If you allow a VPC endpoint to connect to this VPC endpoint service, locate the target 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.
    4. 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.
  8. 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.