This section describes how to create a VPC endpoint to access OBS from an IDC.
The required VPC endpoint service already exists.
The Create VPC Endpoint page is displayed.
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.
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. |
Parameter |
Requirement |
---|---|
Tag key |
|
Tag value |
|
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.