Updated on 2024-12-11 GMT+08:00

Step 2: Buy a VPC Endpoint for Connecting to OBS

Scenarios

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

Prerequisites

The required VPC endpoint service is available.

Procedure

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

    The Buy VPC Endpoint page is displayed.

  3. Configure VPC endpoint parameters.
    Table 1 VPC endpoint parameters

    Parameter

    Example Value

    Description

    Region

    EU-Dublin

    Specifies the region where the VPC endpoint is to be deployed.

    Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.

    Billing Mode

    Pay-per-use

    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

    Cloud services

    There are two options:

    • Cloud services: Select this value if the VPC endpoint service to be accessed is a cloud service.
    • Find a service by name: Select this value if the VPC endpoint service to be accessed 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.

    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

    example_key1

    example_value1

    Specifies the tag that is used to classify and identify the VPC endpoint.

    This parameter can be modified after you buy a VPC endpoint.

    Description

    -

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

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