After you add the required whitelist record, you can create a VPC endpoint in VPC 1 to connect to the target VPC endpoint service.
Select the same region and project as those of the VPC endpoint service.
Parameter |
Description |
---|---|
Region |
Specifies the region where the VPC endpoint is located. This region is the same as that of the VPC endpoint service. |
Service Category |
There are two options: Cloud services or Find a service by name.
Example: Find a service by name |
VPC Endpoint Service Name |
This parameter is available only when you select Find a service by name for Service Category. Enter the VPC endpoint service name recorded in step 8,, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f and click Verify.
|
Private Domain Name |
If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when creating a VPC endpoint. After the VPC endpoint is created, you can access it using the domain name.
|
VPC |
Specifies the VPC where the VPC endpoint is deployed. |
Subnet |
Specifies the subnet where the VPC endpoint is located. |
Private IP Address |
This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service. Specifies the private IP address of the VPC endpoint. You can select Automatic or Manual. |
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 |
|
You can use the private IP address or private domain name to access the VPC endpoint service.