Updated on 2023-08-18 GMT+08:00

Step 2: Buy a VPC Endpoint for Connecting to OBS

Scenarios

This section describes how to buy a VPC endpoint to access OBS from an on-premises data center.

Prerequisites

The required VPC endpoint service is available.

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 VPC endpoint parameters.
    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.

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

    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

    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 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 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. Click Back to VPC Endpoint List after the task is submitted.

    If the status of the VPC endpoint changes from Creating to Accepted, the VPC endpoint for connecting to the VPC endpoint service for OBS is created.

  8. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.