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 54b39691a8 VPCEP UMN 1201 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com>
Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
2022-12-09 09:40:31 +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 IDC.

Prerequisites

The required VPC endpoint service already exists.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > 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. Set the required parameters.
    Table 1 Required parameters

    Parameter

    Description

    Region

    Specifies the region where the VPC endpoint is located.

    Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    Service Category

    There are two options: Cloud services or Find a service by name.

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

    Example: 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 operations people and you can use it without having to perform the creation operation.

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

    VPC

    Specifies the VPC where the VPC endpoint is deployed.

    Tag

    This parameter is optional.

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 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 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).

    Tag value
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
  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 target VPC endpoint to view its details.
    Figure 2 Summary of the VPC endpoint