vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/vpcep/umn/vpcep_02_0303.html
Qin Ying, Fan 5f74a04a37 VPCEP UMN 20240710 version 
Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com>
Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com>
Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
2024-07-29 09:26:39 +00:00

12 KiB
Raw Permalink Blame History

Step 2: Create a VPC Endpoint for Connecting to OBS

Scenarios

This section describes how to create 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 Create VPC Endpoint.

    The Create VPC Endpoint page is displayed.

    Figure 1 Create VPC Endpoint
  5. Configure VPC endpoint parameters.
    Table 1 VPC endpoint parameters

    Parameter

    Description

    Region

    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.

    Service Category

    There are two options:

    • Cloud service: Select this option if the VPC endpoint service to be accessed is a cloud service.
    • Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.

    In this example, select Cloud service.

    Service List

    This parameter is available only when you select Cloud service for Service Category.

    The VPC endpoint service has been created by the O&M personnel and you can directly use it.

    Example: com.t-systems.otc.eu-de.obs

    VPC

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

    Subnet

    Specifies the subnet 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.

    Select a route table for the VPC where the VPC endpoint is to be deployed.

    Tag

    This parameter is optional.

    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.
    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 digits, letters, hyphens (-), underscores (_), and at signs (@).

    Tag value
    • Can contain a maximum of 43 characters.
    • Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
  6. Confirm the specifications and click Create Now.
    • 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 com.t-systems.otc.eu-de.obs is created.

  8. In the VPC endpoint list, click the ID of the VPC endpoint to view its details.
    Figure 2 Summary of the VPC endpoint