Constraints
- VPC endpoint services are region-level resources. Select a region and project when you create such a service.
- Each tenant can create a maximum of 20 VPC endpoint services.
- The following private services can be configured into VPC endpoint services:
- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers.
Constraints
- VPC endpoint services are region-level resources. Select a region and project when you create such a service.
- Each tenant can create a maximum of 20 VPC endpoint services.
- The following private services can be configured into VPC endpoint services:
- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers. The BMS type will be discarded. The ELB type is recommended.
- VIP : Backend resources of this type serve as virtual IP addresses. The VIP type will be discarded. The ELB type is recommended.
- One VPC endpoint service corresponds to only one backend resource.
-Prerequisites
There are available backend resources in the same VPC.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the required region and project. - Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services, and click Create VPC Endpoint Service.The Create VPC Endpoint Service page is displayed.Figure 1 Create VPC Endpoint Service+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services. In the upper right corner, click Create VPC Endpoint Service.The Create VPC Endpoint Service page is displayed.Figure 1 Create VPC Endpoint Service
- Configure parameters by referring to Table 1.
-
Table 1 Required parameters Parameter
+Table 1 Parameters for creating a VPC endpoint service Parameter
Description
Region
Specifies the region where the VPC endpoint service is deployed.
-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.
+Specifies the region where the VPC endpoint service 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.
Name
@@ -30,12 +31,12 @@This parameter is optional.
Specifies the name of the VPC endpoint service.
The name can contain a maximum of 16 characters, including letters, digits, underscores (_), and hyphens (-).
-- If you do not enter a name, the system automatically generates a name in the region.service_id format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f
- If you enter a name, the system automatically generates a name in the region.Name.service_id format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0
- If you do not enter a name, the system generates a name in {region}.{service_id} format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f.
- If you enter a name, the system generates a name in {region}.{Name}.{service_id} format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0.
VPC
Specifies the VPC where the VPC endpoint service is deployed.
+Specifies the VPC where the VPC endpoint service is to be deployed.
Service Type
@@ -46,14 +47,14 @@Connection Approval
Specifies whether the connection between a VPC endpoint and a VPC endpoint service requires approval from the owner of the VPC endpoint service.
-You can determine whether to enable or disable the connection approval.
-If connection approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see Managing Connections of a VPC Endpoint Service.
+You can enable or disable Connection Approval.
+When Connection Approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see Managing Connections of a VPC Endpoint Service.
Port Mapping
Specifies the protocol and ports used for communications between the VPC endpoint service and VPC endpoint. The protocol is TCP.
-- Service Port: A service port is provided by the backend service bound to the endpoint service.
- Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
Specifies the protocol and ports used for communications between the VPC endpoint service and a VPC endpoint. The protocol is TCP.
+- Service Port: provided by the backend resource bound to the VPC endpoint service.
- Terminal Port: provided by the VPC endpoint, allowing you to access the VPC endpoint service.
The service and terminal port numbers range from 1 to 65535. A maximum of 50 port mappings can be added at a time.
NOTE:Accessing a VPC endpoint service from a VPC endpoint is to access the service port from the associated terminal port.
After a port mapping is added, it cannot be modified or deleted.
@@ -62,10 +63,10 @@Backend Resource Type
Specifies the type of the backend resource that provides services to be accessed.
-The following backend resources are supported:
-- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers.
Example: Elastic load balancerNOTE:For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
+Specifies the backend resource that provides services to be accessed.
+The following backend resource types are supported:
+- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers. The BMS type will be discarded. The ELB type is recommended.
In this example, select Elastic load balancer.NOTE:For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
ECS List
When Backend Resource Type is set to ECS, select the ECS that provides services from the ECS list.
+When Backend Resource Type is set to ECS, select an ECS from the ECS list.
BMS List
When Backend Resource Type is set to BMS, select the BMS that provides services from the BMS list.
+When Backend Resource Type is set to BMS, select a BMS from the BMS list.
+NOTE:The BMS type will be discarded. The ELB type is recommended.
+Tag
This parameter is optional.
-Specifies the VPC endpoint service tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint service.
+Specifies the VPC endpoint service tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint service.
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.
@@ -109,12 +112,12 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoint service in another VPC of the same region.
A VPC endpoint comes with a VPC endpoint service. VPC endpoints vary depending on the type of the VPC endpoint services that they can access:-- VPC endpoints for accessing interface VPC endpoint services are elastic network interfaces that have private IP addresses.
- VPC endpoints for accessing gateway VPC endpoint services are gateways, with routes configured to distribute traffic to the associated VPC endpoint services.
You can create different types of VPC endpoints based the types of associated VPC endpoint services:
+You can create an interface or a gateway VPC endpoint based the type of the associated VPC endpoint service.
Creating a VPC Endpoint for Accessing Interface VPC Endpoint Services
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- On the displayed page, click Create VPC Endpoint.
- On the Create VPC Endpoint page, configure the parameters.Figure 1 Create VPC Endpoint (Service Category set to Cloud service)-
Figure 2 Create VPC Endpoint (Service Category set to Find a service by name)+
Creating a VPC Endpoint for Accessing Interface VPC Endpoint Services
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.
- On the Create VPC Endpoint page, configure the parameters.
+
-
Table 1 Required parameters Parameter
+-Table 1 VPC endpoint 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.
+Specifies the region where the VPC endpoint is to be located. 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 as follows:
+There are two options:
- 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.
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.
+The VPC endpoint service has been created by the O&M personnel and you can directly use it.
VPC Endpoint Service Name
This parameter is available only when you select Find a service by name for Service Category.
-You can enter the VPC endpoint service name recorded in Viewing Summary of a VPC Endpoint Service and click Verify.
-- If Service name found is displayed, proceed with subsequent operations.
- If Service name not found is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the entered service name is correct.
You can enter the VPC endpoint service name recorded in Viewing the Summary of a VPC Endpoint Service and click Verify.
+- If "Service name found." is displayed, proceed with subsequent operations.
- If "Service name not found." is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the name entered is correct.
Private Domain Name
+Create a 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.
-This parameter is only configured for interface VPC endpoints.
+If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when buying a VPC endpoint.
+This parameter is only available for interface VPC endpoints.
- For the gateway type, this parameter is unavailable.
- For the interface type, this parameter is optional.
VPC
Specifies the VPC where the VPC endpoint is deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
Subnet
This parameter is available when you want to access an interface endpoint service.
-Specifies the subnet where the VPC endpoint is located.
+This parameter is available when you want to access an interface VPC endpoint service.
+Specifies the subnet where the VPC endpoint is to be located.
Private IP Address
This parameter is available when you want to access an interface endpoint service.
-Specifies the private IP address of the VPC endpoint. You can select Automatic or Manual.
+This parameter is available when you want to access an interface VPC endpoint service.
+Specifies the private IP address of the VPC endpoint. You can select Automatically assign or Manually specify.
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.
+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.
@@ -87,32 +87,32 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
- 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.
Creating a VPC Endpoint for Accessing Gateway VPC Endpoint Services
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- On the displayed page, click Create VPC Endpoint.
- On the Create VPC Endpoint page, configure the parameters.Figure 3 Create VPC Endpoint (Service Category set to Cloud service)+
Creating a VPC Endpoint for Accessing Gateway VPC Endpoint Services
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.
- On the Create VPC Endpoint page, configure the parameters.Figure 3 Create VPC Endpoint (Service Category set to Cloud services)
-Table 3 Required parameters Parameter
+-Table 3 VPC endpoint parameters Parameter
Description
+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.
+Specifies the region where the VPC endpoint is to be located. Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
Service Category
@@ -123,20 +123,25 @@Service List
This parameter is available only when you select Cloud services for Service Category.
+This parameter is available only when you select Cloud services for Service Category.
In the VPC endpoint service list, select the VPC endpoint service whose type is gateway.
-The VPC endpoint service has been created by operations people and you can use it without having to perform the creation operation.
+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 deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
+Subnet
+Specifies the subnet where the VPC endpoint is to be located.
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.
+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 4.
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.
@@ -147,27 +152,27 @@Table 4 Tag requirements for VPC endpoints Parameter
+-Table 4 Tag requirements for VPC endpoints Parameter
Requirement
+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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
- Confirm the specifications and click Create Now.
diff --git a/docs/vpcep/umn/en-us_topic_0131645193.html b/docs/vpcep/umn/en-us_topic_0131645193.html index 2e3d7f9a6..2baf939dc 100644 --- a/docs/vpcep/umn/en-us_topic_0131645193.html +++ b/docs/vpcep/umn/en-us_topic_0131645193.html @@ -14,6 +14,8 @@- 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.
- VPCEP and Other Services
+
- Permissions
+- Product Concepts
diff --git a/docs/vpcep/umn/en-us_topic_0131645194.html b/docs/vpcep/umn/en-us_topic_0131645194.html index bef105b45..edbaafb9b 100644 --- a/docs/vpcep/umn/en-us_topic_0131645194.html +++ b/docs/vpcep/umn/en-us_topic_0131645194.html @@ -14,7 +14,7 @@
diff --git a/docs/vpcep/umn/en-us_topic_0131645196.html b/docs/vpcep/umn/en-us_topic_0131645196.html index 7f89594b5..759ec03fd 100644 --- a/docs/vpcep/umn/en-us_topic_0131645196.html +++ b/docs/vpcep/umn/en-us_topic_0131645196.html @@ -5,14 +5,14 @@Accessing VPCEP
A web-based console and HTTPS APIs are provided for you to access VPCEP.
- Web-based console
You can access VPCEP using the web-based console.
Upon a quick configuration on the management console, you can start using VPCEP.
- - APIs
Access VPCEP by calling APIs if you need to integrate VPCEP into a third-party system for secondary development. For details, see VPC Endpoint API Reference.
+ - APIs
Use this method if you need to integrate VPCEP into a third-party system for secondary development. For details, see VPC Endpoint API Reference.
You can use VPCEP in different scenarios.
High-Speed Access to Cloud Services
After you connect an IDC to a VPC using VPN or Direct Connect, you can use a VPC endpoint to connect the VPC to a cloud service or one of your private services, so that the IDC can access the cloud service or private service.
-Figure 1 shows the process of connecting an IDC to VPC 1 over VPN or Direct Connect, for the purpose of:
+Figure 1 shows the process of connecting an IDC to VPC 1 over VPN or Direct Connect, for the purposes of:
- Accessing OBS or DNS using VPC endpoint 1
- Accessing ECS 1 in the same VPC using VPC endpoint 2
- Accessing ECS 2 in VPC 2 using VPC endpoint 3
For cloud migration, VPCEP has the following advantages:
- Simple and efficient
The IDC is directly connected to the VPC endpoint service over a private network, reducing access latency and improving efficiency.
- Low cost
With VPCEP, your IDC can access cloud resources over a private network, reducing your costs on public resources.
For details, see Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address.
+For details, see Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks.
Cross-VPC Connection
With VPCEP, resources in two different VPCs can communicate with each other despite of logic isolation between them as long as the two VPCs are in the same region.
VPC endpoints and VPC peering connections are different in security, communications methods, route configurations, and more.
diff --git a/docs/vpcep/umn/en-us_topic_0154804561.html b/docs/vpcep/umn/en-us_topic_0154804561.html deleted file mode 100644 index 9b80ae0b0..000000000 --- a/docs/vpcep/umn/en-us_topic_0154804561.html +++ /dev/null @@ -1,24 +0,0 @@ - - -What Is a Quota?
---What Is a Quota?
Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number and capacity of resources available to users, for example, how many cloud resources you can create.
-You can also increase the quota if the existing quota cannot meet your service requirements.
--How Do I View My Quotas?
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - In the upper right corner of the page, click
.The Service Quota page is displayed.
- - View the used and total quota of each type of resources on the displayed page.
If a quota cannot meet service requirements, apply for a higher quota.
-
-How Do I Apply for a Higher Quota?
The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.
-Before dialing the hotline number or sending an email, make sure that the following information has been obtained:
-- Domain name, project name, and project ID, which can be obtained by performing the following operations:
Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.
- - Quota information, which includes:
- Service name
- Quota type
- Required quota
-- diff --git a/docs/vpcep/umn/vpcep_01_0005.html b/docs/vpcep/umn/vpcep_01_0005.html index 5e550ed45..b8e101722 100644 --- a/docs/vpcep/umn/vpcep_01_0005.html +++ b/docs/vpcep/umn/vpcep_01_0005.html @@ -15,7 +15,7 @@--Parent topic: FAQ-20
+ VPC endpoints per account
diff --git a/docs/vpcep/umn/vpcep_01_0007.html b/docs/vpcep/umn/vpcep_01_0007.html index 442322f45..258a1ffca 100644 --- a/docs/vpcep/umn/vpcep_01_0007.html +++ b/docs/vpcep/umn/vpcep_01_0007.html @@ -23,12 +23,14 @@VPN
Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address
+Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks
Connecting an IDC to your VPC using a direct connection and connecting your VPC to a cloud service through VPCEP
+Connecting an IDC to your VPC using a Direct Connect connection and connecting your VPC to a cloud service through VPCEP
Direct Connect
+Direct Connect
+Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks
When an enterprise needs to provide VPCEP for multiple users, IAM can be used to create users and control access of these domains to enterprise resources.
@@ -38,7 +40,7 @@Configured as a gateway VPC endpoint service by default. You can create a VPC endpoint to access the VPC endpoint service.
+Configured as a gateway VPC endpoint service by default. You can create a VPC endpoint to access these VPC endpoint services.
OBS
Configuring a private service as a VPC endpoint service. You can create a VPC endpoint to access the VPC endpoint service.
+Configuring a private service as a VPC endpoint service. You can create a VPC endpoint to access the VPC endpoint service.
ELB
+ ECS
+Configuring a private service as a VPC endpoint service. You can create a VPC endpoint to access the VPC endpoint service.
+ECS
+BMS
+Configuring a private service as a VPC endpoint service. You can create a VPC endpoint to access the VPC endpoint service.
+BMS
+NOTE:+The BMS type will be discarded. The ELB type is recommended.
+A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.
There are two types of VPC endpoint services: gateway and interface.-- Gateway VPC endpoint services are created only for cloud services.
- Interface VPC endpoint services can be created for both cloud services and your private services. All VPC endpoint services for cloud services are created by default while those for private services need to be created by users themselves.
Gateway VPC Endpoint Services
Gateway endpoint services are configured from cloud services by the system. You do not have the permission to configure such services but can select them when creating a VPC endpoint.
- Supported cloud services vary in different regions. For details, see the list of services that can be configured on the management console.
+Gateway VPC Endpoint Services
Gateway VPC endpoint services are configured from cloud services by the system. You do not have the permissions to configure such VPC endpoint services but can select them when creating a VPC endpoint.
+ Supported cloud services vary in different regions. For details, see the services that can be configured on the management console.
Table 1 Supported gateway VPC endpoint services VPC Endpoint Service
@@ -39,11 +39,11 @@Interface VPC Endpoint Services
Interface VPC endpoint services are mainly configured from:
-- Cloud services. You do not have the permission to configure such endpoint services, but can select them when creating a VPC endpoint.
- Your private services
Supported cloud services vary in different regions. For details, see the list of services that can be configured on the management console.
+- Cloud services. You do not have the permissions to configure such VPC endpoint services but can select them when creating a VPC endpoint.
- Your private services
- Supported cloud services vary in different regions. For details, see the services that can be configured on the management console.
Table 2 Supported interface VPC endpoint services VPC Endpoint Service
+Table 2 Supported interface VPC endpoint services VPC Endpoint Service
Category
None
VPC endpoint services work as servers.
-NOTE:Only region eu-de supports BMSs.
+NOTE:+The BMS type will be discarded. The ELB type is recommended.
+VIP
+Users' private service
+Interface
+None
+Backend resources of this type serve as virtual IP addresses.
+NOTE:The VIP type will be discarded. The ELB type is recommended.
- Configuring a VPC Endpoint for Communications Across VPCs of Different Domains
-
- Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address
+- Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks
-
- Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address
+- Configuring a VPC Endpoint for Accessing the Public IP Address of OBS over Public Networks
diff --git a/docs/vpcep/umn/vpcep_02_02021.html b/docs/vpcep/umn/vpcep_02_02021.html index 76a456615..24c323ff3 100644 --- a/docs/vpcep/umn/vpcep_02_02021.html +++ b/docs/vpcep/umn/vpcep_02_02021.html @@ -3,8 +3,8 @@
Overview
Scenarios
With VPCEP, you can access resources across VPCs in the same region.
Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP addresses. After you create a VPC endpoint, you can use a private IP address to access resources across two VPCs despite of network isolation between them.
-This section describes how cloud resources in VPCs of different domains in the same region can communicate with each other across VPCs.
-VPC 1 and VPC 2 belong to different domains , respectively. You can take the ELB in VPC 2 as a VPC endpoint service and create a VPC endpoint in VPC 1 so that the ECS in VPC 1 can access the ELB in VPC 2 using the private IP address.
+This section describes how cloud resources in VPCs of the same domain in the same region can communicate with each other.
+VPC 1 and VPC 2 belong to the same domain in the same region. You can configure ELB in VPC 2 as a VPC endpoint service and create a VPC endpoint in VPC 1. Then the ECS in VPC 1 can access ELB in VPC 2 using the private IP address.
Figure 1 Cross-VPC communications
diff --git a/docs/vpcep/umn/vpcep_02_02022.html b/docs/vpcep/umn/vpcep_02_02022.html index 76b1fb78b..171dca239 100644 --- a/docs/vpcep/umn/vpcep_02_02022.html +++ b/docs/vpcep/umn/vpcep_02_02022.html @@ -2,17 +2,17 @@ - Only one-way communications from the VPC endpoint to the VPC endpoint service are supported.
- For details about communications between two VPCs of different domains, see Configuring a VPC Endpoint for Communications Across VPCs of Different Domains.
Step 1: Create a VPC Endpoint Service
Scenarios
To enable communications across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.
-This section uses an elastic load balancer as an example backend service to describe how to create a VPC endpoint service.
+This section uses an elastic load balancer as an example to describe how to create a VPC endpoint service.
-Prerequisites
There are available backend resources in the same VPC.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services, and click Create VPC Endpoint Service.
The Create VPC Endpoint Service page is displayed.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services. In the upper right corner, click Create VPC Endpoint Service.
The Create VPC Endpoint Service page is displayed.
Figure 1 Create VPC Endpoint Service- - Configure the required parameters.
-
Table 1 Required parameters Parameter
+- Configure required parameters. +
-Table 1 Parameters for creating a VPC endpoint service Parameter
Description
Region
Specifies the region where the VPC endpoint service is deployed.
-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.
+Specifies the region where the VPC endpoint service 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.
Name
@@ -29,12 +29,12 @@This parameter is optional.
Specifies the name of the VPC endpoint service.
The name can contain a maximum of 16 characters, including letters, digits, underscores (_), and hyphens (-).
-- If you do not enter a name, the system automatically generates a name in the region.service_id format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f.
- If you enter a name, the system automatically generates a name in the region.Name.service_id format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0.
- If you do not enter a name, the system generates a name in {region}.{service_id} format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f.
- If you enter a name, the system generates a name in {region}.{Name}.{service_id} format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0.
VPC
Specifies the VPC where the VPC endpoint service is deployed.
+Specifies the VPC where the VPC endpoint service is to be deployed.
Service Type
@@ -45,14 +45,14 @@Connection Approval
Specifies whether the connection between a VPC endpoint and a VPC endpoint service requires approval from the owner of the VPC endpoint service.
-You can determine whether to enable or disable the connection approval.
-If connection approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see step 7.
+You can enable or disable Connection Approval.
+When Connection Approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see step 7.
Port Mapping
Specifies the protocol and ports used for communications between the VPC endpoint service and VPC endpoint. The protocol is TCP.
-- Service Port: A service port is provided by the backend service bound to the endpoint service.
- Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
Specifies the protocol and ports used for communications between the VPC endpoint service and a VPC endpoint. The protocol is TCP.
+- Service Port: provided by the backend resource bound to the VPC endpoint service.
- Terminal Port: provided by the VPC endpoint, allowing you to access the VPC endpoint service.
The service and terminal port numbers range from 1 to 65535. A maximum of 50 port mappings can be added at a time.
NOTE:Accessing a VPC endpoint service from a VPC endpoint is to access the service port from the associated terminal port.
After a port mapping is added, it cannot be modified or deleted.
@@ -61,10 +61,10 @@Backend Resource Type
Specifies the type of the backend resource that provides services to be accessed.
-The following backend resources are supported:
-- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers.
Example: Elastic load balancerNOTE:For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
+Specifies the backend resource that provides services to be accessed.
+The following backend resource types are supported:
+- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers. The BMS type will be discarded. The ELB type is recommended.
In this example, select Elastic load balancer.NOTE:For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
Tag
This parameter is optional.
-Specifies the VPC endpoint service tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint service.
+Specifies the VPC endpoint service tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint service.
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.
@@ -98,18 +98,18 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Click Create Now.
- Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view the details.
Figure 2 Summary of the VPC endpoint service+
- Click Create Now.
- Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view its details.
diff --git a/docs/vpcep/umn/vpcep_02_02023.html b/docs/vpcep/umn/vpcep_02_02023.html index 20cfa2d0f..3231fb0ec 100644 --- a/docs/vpcep/umn/vpcep_02_02023.html +++ b/docs/vpcep/umn/vpcep_02_02023.html @@ -2,14 +2,14 @@Figure 2 Summary of the VPC endpoint service
Step 2: Create a VPC Endpoint
-Scenarios
After you create a VPC endpoint service, you also need to create a VPC endpoint to access the VPC endpoint service.
-This section describes how to create a VPC endpoint in another VPC of your own for connecting to the VPC endpoint service.
+This section describes how to create a VPC endpoint in another VPC of your own.
Select the same region and project as those of the VPC endpoint service.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.The Create VPC Endpoint page is displayed.Figure 1 Create VPC Endpoint (Service Category set to Find a service by name)+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.The Create VPC Endpoint page is displayed.-Figure 1 Create VPC Endpoint (Service Category set to Find a service by name)
- Set the required parameters.
-
Table 1 Required parameters Parameter
+- Configure required parameters. +
-Table 1 VPC endpoint parameters Parameter
Description
Region
Specifies the region where the VPC endpoint is located. This region is the same as that of the VPC endpoint service.
+Specifies the region where the VPC endpoint is to be 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.
-- Cloud services: 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: Find a service by name
+There are two options:
+- 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.
In this example, select 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.
-- If Service name found is displayed, proceed with subsequent operations.
- If Service name not found is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the entered service name is correct.
Enter the VPC endpoint service name recorded in step 8, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f and click Verify.
+- If "Service name found." is displayed, proceed with subsequent operations.
- If "Service name not found." is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the name entered is correct.
Private Domain Name
+Create a 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.
+If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when buying a VPC endpoint.
- For the gateway type, this parameter is unavailable.
- For the interface type, this parameter is optional.
VPC
Specifies the VPC where the VPC endpoint is deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
Subnet
Specifies the subnet where the VPC endpoint is located.
+Specifies the subnet where the VPC endpoint is to be 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.
+Specifies the private IP address of the VPC endpoint. You can select Automatically assign or Manually specify.
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.
+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.
@@ -78,28 +78,28 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
- Manage the connection of the VPC endpoint.
If the status of the VPC endpoint changes to Accepted, the VPC endpoint is connected to the required VPC endpoint service. If the status is Pending acceptance, connection approval is enabled for the endpoint service, ask the owner of the endpoint service to perform the following operations:- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Connection Management tab.
- If you allow a VPC endpoint to connect to this VPC endpoint service, locate the target VPC endpoint and click Accept in the Operation column.
- If you refuse a VPC endpoint from connecting to this VPC endpoint service, click Reject in the Operation column.
- 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.
- Manage the connection of the VPC endpoint.If the status of the VPC endpoint changes to Accepted, the VPC endpoint is connected to the required VPC endpoint service. If the status is Pending acceptance, connection approval is enabled for the VPC endpoint service, ask the owner of the VPC endpoint service to perform the following operations:-
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- Locate the target VPC endpoint service and click its name.
- On the displayed page, select the Connection Management tab.
- If you allow a VPC endpoint to connect to this VPC endpoint service, locate the target VPC endpoint and click Accept in the Operation column.
- If you do not allow a VPC endpoint to connect to this VPC endpoint service, click Reject in the Operation column.
- Go back to the VPC endpoint list and check whether the status of the target VPC endpoint changes to Accepted. If yes, the VPC endpoint is connected to the VPC endpoint service.
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.After a VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name.-Figure 2 Summary of the VPC endpoint+
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
After a VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name during creation.Figure 2 Summary of the VPC endpoint
You can use the private IP address or private domain name to access the VPC endpoint service.
Configuration Verification
Log in to an ECS in VPC 1 remotely and access the VPC endpoint using its private IP address or private domain name.
-Figure 3 Logging in to the ECS to access the VPC endpoint+
Configuration Verification
Remotely log in to an ECS in VPC 1 and access the private IP address or private domain name of the VPC endpoint.
+Figure 3 Logging in to an ECS to access the VPC endpointdiff --git a/docs/vpcep/umn/vpcep_02_02031.html b/docs/vpcep/umn/vpcep_02_02031.html index f667ad305..07b6bebf9 100644 --- a/docs/vpcep/umn/vpcep_02_02031.html +++ b/docs/vpcep/umn/vpcep_02_02031.html @@ -3,8 +3,8 @@Overview
Scenarios
With VPCEP, you can access resources across VPCs in the same region.
Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP addresses. After you create a VPC endpoint, you can use a private IP address to access resources across two VPCs despite of network isolation between them.
-This section describes how cloud resources in VPCs of different domains in the same region can communicate with each other across VPCs.
-VPC 1 and VPC 2 belong to different domains. You can take the ELB in VPC 2 as a VPC endpoint service and create a VPC endpoint in VPC 1 so that the ECS in VPC 1 can access the ELB in VPC 2 using the private IP address.
+This section describes how cloud resources in VPCs of different domains in the same region can communicate with each other.
+VPC 1 and VPC 2 belong to different domains. You can configure ELB in VPC 2 as a VPC endpoint service and create a VPC endpoint in VPC 1 so that the ECS in VPC 1 can access ELB in VPC 2 using the private IP address.
Figure 1 Cross-VPC communicationsdiff --git a/docs/vpcep/umn/vpcep_02_02032.html b/docs/vpcep/umn/vpcep_02_02032.html index 1851fc13d..79e2345d5 100644 --- a/docs/vpcep/umn/vpcep_02_02032.html +++ b/docs/vpcep/umn/vpcep_02_02032.html @@ -6,13 +6,13 @@ - Only one-way communications from the VPC endpoint to the VPC endpoint service are supported.
- Before you create a VPC endpoint, add the authorized domain ID of VPC 1 to the whitelist of the VPC endpoint service in VPC 2.
- For details about communications between two VPCs of the same domain, see Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain.
-Prerequisites
There are available backend resources in the same VPC.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services, and click Create VPC Endpoint Service.
The Create VPC Endpoint Service page is displayed.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services. In the upper right corner, click Create VPC Endpoint Service.
The Create VPC Endpoint Service page is displayed.
Figure 1 Create VPC Endpoint Service- - Configure the required parameters.
-
Table 1 Required parameters Parameter
+- Configure required parameters. +
-Table 1 Parameters for creating a VPC endpoint service Parameter
Description
Region
Specifies the region where the VPC endpoint service is deployed.
-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.
+Specifies the region where the VPC endpoint service 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.
Name
@@ -29,12 +29,12 @@This parameter is optional.
Specifies the name of the VPC endpoint service.
The name can contain a maximum of 16 characters, including letters, digits, underscores (_), and hyphens (-).
-- If you do not enter a name, the system automatically generates a name in the region.service_id format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f.
- If you enter a name, the system automatically generates a name in the region.Name.service_id format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0.
- If you do not enter a name, the system generates a name in {region}.{service_id} format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f.
- If you enter a name, the system generates a name in {region}.{Name}.{service_id} format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0.
VPC
Specifies the VPC where the VPC endpoint service is deployed.
+Specifies the VPC where the VPC endpoint service is to be deployed.
Service Type
@@ -45,14 +45,14 @@Connection Approval
Specifies whether the connection between a VPC endpoint and a VPC endpoint service requires approval from the owner of the VPC endpoint service.
-You can determine whether to enable or disable the connection approval.
-If connection approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see step 7.
+You can enable or disable Connection Approval.
+When Connection Approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see step 7.
Port Mapping
Specifies the protocol and ports used for communications between the VPC endpoint service and VPC endpoint. The protocol is TCP.
-- Service Port: A service port is provided by the backend service bound to the endpoint service.
- Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
Specifies the protocol and ports used for communications between the VPC endpoint service and a VPC endpoint. The protocol is TCP.
+- Service Port: provided by the backend resource bound to the VPC endpoint service.
- Terminal Port: provided by the VPC endpoint, allowing you to access the VPC endpoint service.
The service and terminal port numbers range from 1 to 65535. A maximum of 50 port mappings can be added at a time.
NOTE:Accessing a VPC endpoint service from a VPC endpoint is to access the service port from the associated terminal port.
After a port mapping is added, it cannot be modified or deleted.
@@ -61,10 +61,10 @@Backend Resource Type
Specifies the type of the backend resource that provides services to be accessed.
-The following backend resources are supported:
-- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers.
Example: Elastic load balancerNOTE:For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
+Specifies the backend resource that provides services to be accessed.
+The following backend resource types are supported:
+- Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
- ECS: Backend resources of this type serve as servers.
- BMS: Backend resources of this type serve as servers. The BMS type will be discarded. The ELB type is recommended.
In this example, select Elastic load balancer.NOTE:For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
Tag
This parameter is optional.
-Specifies the VPC endpoint service tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint service.
+Specifies the VPC endpoint service tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint service.
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.
@@ -98,18 +98,18 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Click Create Now.
- Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view the details.
Figure 2 Summary of the VPC endpoint service+- Click Create Now.
- Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view its details.
diff --git a/docs/vpcep/umn/vpcep_02_02034.html b/docs/vpcep/umn/vpcep_02_02034.html index 1520f77d7..b21cec78b 100644 --- a/docs/vpcep/umn/vpcep_02_02034.html +++ b/docs/vpcep/umn/vpcep_02_02034.html @@ -2,22 +2,22 @@Figure 2 Summary of the VPC endpoint serviceStep 2: Add a Whitelist Record
-Scenarios
Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.
-After a VPC endpoint service is created, you can add an authorized domain ID to or delete it from the whitelist of the endpoint service.
-The following operations describe how to obtain your own domain ID and add it to the whitelist of an existing VPC endpoint service in another domain.
+After a VPC endpoint service is created, you can add an authorized domain ID to or delete it from the whitelist of the VPC endpoint service.
+The following operations describe how to obtain your domain ID and add it to the whitelist of an existing VPC endpoint service in another domain.
Prerequisites
The required VPC endpoint service already exists.
+Prerequisites
There is a VPC endpoint service available.
Obtain the ID of Your Own Domain
- Log in to the management console.
- Click My Credentials under the domain.Figure 1 My Credentials-
The My Credentials page is displayed. You can view and record the Domain ID.-Figure 2 Domain ID+
The My Credentials page is displayed. You can view and record the domain ID.Figure 2 Domain IDAdd an Authorized Domain ID to the Whitelist of a VPC Endpoint Service
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab and click Add to Whitelist.
- Enter an authorized domain ID in the required format and click OK.Figure 3 Add to Whitelist+
Add Domain IDs to Be Authorized to the Whitelist of a VPC Endpoint Service
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab and click Add to Whitelist.
- Enter an authorized domain ID in the required format and click OK.Figure 3 Add to Whitelist-
- Your domain is in the whitelist of your VPC endpoint service by default.
- The authorized domain ID is in the iam:domain::domain_id format.
domain_id indicates the ID of the authorized domain, for example, iam:domain::1564ec50ef2a47c791ea5536353ed4b9
- Adding * to the whitelist means that all users can access the VPC endpoint service.
- Click OK.
- Click
diff --git a/docs/vpcep/umn/vpcep_02_02035.html b/docs/vpcep/umn/vpcep_02_02035.html index ab5ac5afb..ce9073190 100644 --- a/docs/vpcep/umn/vpcep_02_02035.html +++ b/docs/vpcep/umn/vpcep_02_02035.html @@ -5,10 +5,10 @@- Select the same region and project as those of the VPC endpoint service.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.The Create VPC Endpoint page is displayed.Figure 1 Create VPC Endpoint (Service Category set to Find a service by name)+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.The Create VPC Endpoint page is displayed.-Figure 1 Create VPC Endpoint (Service Category set to Find a service by name)
- Set the required parameters.
-
Table 1 Required parameters Parameter
+- Configure required parameters. +
-Table 1 VPC endpoint parameters Parameter
Description
Region
Specifies the region where the VPC endpoint is located. This region is the same as that of the VPC endpoint service.
+Specifies the region where the VPC endpoint is to be 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.
-- Cloud services: 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: Find a service by name
+There are two options:
+- 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.
In this example, select 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.
-- If Service name found is displayed, proceed with subsequent operations.
- If Service name not found is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the entered service name is correct.
Enter the VPC endpoint service name recorded in step 8, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f and click Verify.
+- If "Service name found." is displayed, proceed with subsequent operations.
- If "Service name not found." is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the name entered is correct.
Private Domain Name
+Create a 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.
+If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when buying a VPC endpoint.
- For the gateway type, this parameter is unavailable.
- For the interface type, this parameter is optional.
VPC
Specifies the VPC where the VPC endpoint is deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
Subnet
Specifies the subnet where the VPC endpoint is located.
+Specifies the subnet where the VPC endpoint is to be 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.
+Specifies the private IP address of the VPC endpoint. You can select Automatically assign or Manually specify.
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.
+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.
@@ -77,22 +77,22 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
- Manage the connection of the VPC endpoint.
If the status of the VPC endpoint changes to Accepted, the VPC endpoint is connected to the required VPC endpoint service. If the status is Pending acceptance, connection approval is enabled for the endpoint service, ask the owner of the endpoint service to perform the following operations:- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Connection Management tab.
- If you allow a VPC endpoint to connect to this VPC endpoint service, locate the target VPC endpoint and click Accept in the Operation column.
- If you refuse a VPC endpoint from connecting to this VPC endpoint service, click Reject in the Operation column.
- 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.
- Manage the connection of the VPC endpoint.If the status of the VPC endpoint changes to Accepted, the VPC endpoint is connected to the required VPC endpoint service. If the status is Pending acceptance, connection approval is enabled for the VPC endpoint service, ask the owner of the VPC endpoint service to perform the following operations:-
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- Locate the target VPC endpoint service and click its name.
- On the displayed page, select the Connection Management tab.
- If you allow a VPC endpoint to connect to this VPC endpoint service, locate the target VPC endpoint and click Accept in the Operation column.
- If you do not allow a VPC endpoint to connect to this VPC endpoint service, click Reject in the Operation column.
- Go back to the VPC endpoint list and check whether the status of the target VPC endpoint changes to Accepted. If yes, the VPC endpoint is connected to the VPC endpoint service.
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.After a VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name.Figure 2 Summary of the VPC endpoint+
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
diff --git a/docs/vpcep/umn/vpcep_02_0300.html b/docs/vpcep/umn/vpcep_02_0300.html index dd5c46af9..1ff3ccfd3 100644 --- a/docs/vpcep/umn/vpcep_02_0300.html +++ b/docs/vpcep/umn/vpcep_02_0300.html @@ -1,6 +1,6 @@ -After a VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name during creation.Figure 2 Summary of the VPC endpointYou can use the private IP address or private domain name to access the VPC endpoint service.
Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address
+Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks
-
diff --git a/docs/vpcep/umn/vpcep_02_0301.html b/docs/vpcep/umn/vpcep_02_0301.html
index 76cf38cc2..71556cd58 100644
--- a/docs/vpcep/umn/vpcep_02_0301.html
+++ b/docs/vpcep/umn/vpcep_02_0301.html
@@ -1,23 +1,23 @@
- VPC endpoint service for DNS: resolves the OBS domain name at the IDC. -
- VPC endpoint service for OBS: provides the OBS service for the IDC. +
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.The Create VPC Endpoint page is displayed.Figure 1 Create VPC Endpoint+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.The Create VPC Endpoint page is displayed.-Figure 1 Create VPC Endpoint
- Set the required parameters.
-
Table 1 Required parameters Parameter
+- Configure VPC endpoint parameters. +
-Table 1 VPC endpoint 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.
+Specifies the region where the VPC endpoint is to be located.
+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 services or Find a service by name.
+There are two options:
- 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
+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 operations people and you can use it without having to perform the creation operation.
-Example: com.t-systems.otc.eu-de.dns
+The VPC endpoint service has been created by the O&M personnel and you can directly use it.
+In this example, select com.t-systems.otc.eu-de.dns.
Private Domain Name
+Create a 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.
-This parameter can only be configured for VPC endpoints of the interface type, and its setting depends on the type of target VPC endpoint services:
+If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when buying a VPC endpoint.
+This parameter is only available for interface VPC endpoints, and its setting depends on the type of target VPC endpoint services.
- For the gateway type, this parameter is unavailable.
- For the interface type, this parameter is optional.
VPC
Specifies the VPC where the VPC endpoint is deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
Subnet
This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.
-Specifies the subnet where the VPC endpoint is located.
+Specifies the subnet where the VPC endpoint is to be 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.
+Specifies the private IP address of the VPC endpoint. You can select Automatically assign or Manually specify.
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.
+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.
@@ -81,27 +80,27 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
- Click Back to VPC Endpoint List after the task is submitted.
If the status of the VPC endpoint changes to Accepted, the VPC endpoint for connecting to com.t-systems.otc.eu-de.dns is created.
-- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
After a VPC endpoint for accessing interface VPC endpoint services is created, a private IP address is generated together with a private domain name if you select Create a Private Domain Name during creation.Figure 2 Summary of the VPC endpoint+
- 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.
- Click Back to VPC Endpoint List after the task is submitted.
If the status of the VPC endpoint changes to Accepted, the VPC endpoint for connecting to com.t-systems.otc.eu-de.dns is created.
+- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
diff --git a/docs/vpcep/umn/vpcep_02_0303.html b/docs/vpcep/umn/vpcep_02_0303.html index e7dd5e9c1..580a7d134 100644 --- a/docs/vpcep/umn/vpcep_02_0303.html +++ b/docs/vpcep/umn/vpcep_02_0303.html @@ -1,16 +1,14 @@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.
+-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 already exists.
+-Prerequisites
The required VPC endpoint service is available.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.
The Create VPC Endpoint page is displayed.
-- -Figure 1 Create VPC Endpoint-
- Set the required parameters.
-
Table 1 Required parameters Parameter
+Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.
The Create VPC Endpoint page is displayed.
+Figure 1 Create VPC Endpoint+
- Configure VPC endpoint parameters.
+-
Table 1 VPC endpoint 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.
+Specifies the region where the VPC endpoint is to be located.
+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 services or Find a service by name.
+There are two options:
- 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
+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 operations people and you can use it without having to perform the creation operation.
+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 deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
+Subnet
+Specifies the subnet where the VPC endpoint is to be located.
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.
+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.
@@ -63,18 +66,18 @@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 (_).
- 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
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
- 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.
- 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.
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.Figure 2 Summary of the VPC endpoint
diff --git a/docs/vpcep/umn/vpcep_02_0304.html b/docs/vpcep/umn/vpcep_02_0304.html index f25b2ac7d..4a2a73c84 100644 --- a/docs/vpcep/umn/vpcep_02_0304.html +++ b/docs/vpcep/umn/vpcep_02_0304.html @@ -1,36 +1,36 @@Step 3: Access OBS
-Scenarios
This section describes how to access OBS using a VPN connection or a direct connection.
+-Scenarios
This section describes how to access OBS using a VPN or Direct Connect connection.
Prerequisites
Your local data center has been connected to your VPC using a VPN or Direct Connect connection.- The local subnet of the VPC that interconnects with your VPN contains the OBS CIDR block 100.125.0.0/16.
For details about how to create a VPN connection, see Creating a VPN in the Virtual Private Network User Guide.
- - The CIDR block of the virtual gateway associated with your direct connection contains the OBS CIDR block 100.125.0.0/16.
For details about how to enable Direct Connect, see Getting Started in the Direct Connect User Guide.
+Prerequisites
Your on-premises data center has been connected to your VPC using a VPN or Direct Connect connection.- The VPC subnet that needs to communicate with the on-premises data center over the VPN connection contains the OBS CIDR block 100.125.0.0/16.
For details about how to create a VPN connection, see Creating a VPN in the Virtual Private Network User Guide.
+ - The VPC subnet that needs to communicate with the on-premises data center over the Direct Connect gateway contains the OBS CIDR block 100.125.0.0/16.
For details about how to enable Direct Connect, see Getting Started in the Direct Connect User Guide.
Procedure
- In the VPC endpoint list, locate the target VPC endpoint and click the ID of the endpoint to view its details.Figure 1 Summary of the VPC endpoint-
- Add DNS records on the DNS server at your local data center to forward requests for resolving OBS domain names to the VPC endpoint for accessing DNS.
The methods of configuring DNS forwarding rules vary depending on operating systems. For details, see the DNS software operation documents.
-This step uses the common DNS software Bind as an example to configure forwarding rules in the UNIX operating system as follows:
+ - Add DNS records on the DNS server at your on-premises data center to forward requests for resolving OBS domain names to the VPC endpoint for accessing DNS.
The methods of configuring DNS forwarding rules vary depending on OSs. For details, see the DNS software operation guides.
+This step uses Bind, a common DNS software, as an example to configure forwarding rules in the UNIX.
In file /etc/named.conf, add the DNS forwarder configuration and set forwarders to the private IP address of the VPC endpoint for accessing DNS.
-options {
-forward only;
-forwarders{ xx.xx.xx.xx;};
-};
- - If no DNS server is available at your local data center, add the private IP address of the VPC endpoint in file /etc/resolv.conf.
- xx.xx.xx.xx is the private IP address obtained in step 1.
options { +forward only; +forwarders{ xx.xx.xx.xx;}; +};+- - If no DNS server is available at your on-premises data center, add the private IP address of the VPC endpoint in file /etc/resolv.conf.
- xx.xx.xx.xx is the VPC endpoint IP address obtained in 1.
- Configure a DNS route from your local data center to the VPN gateway or Direct Connect gateway.
xx.xx.xx.xx indicates the private IP address of the VPC endpoint. To access DNS using a VPN connection or a direct connection, you need to ensure that traffic from your local data center to DNS is directed to the VPN gateway or Direct Connect gateway.
-Configure a permanent route at your local data center and specify the IP address of the Direct Connect or VPN gateway as the next hop for accessing DNS.
-route -p add xx.xx.xx.xx mask 255.255.255.255 xxx.xxx.xxx.xxx
- - xx.xx.xx.xx is the private IP address obtained in step 1.
- xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your local data center.
- Configure a DNS route from your on-premises data center to the VPN gateway or Direct Connect gateway.
To access DNS over a VPN or Direct Connect connection, ensure that traffic from your on-premises data center to DNS is directed to the VPN gateway or Direct Connect gateway.
+Configure a permanent route at your on-premises data center and specify the IP address of the Direct Connect or VPN gateway as the next hop for accessing DNS. The following is the example command for configuring such a route:
+route -p add xx.xx.xx.xx mask 255.255.255.255 xxx.xxx.xxx.xxx
+- - xx.xx.xx.xx is the VPC endpoint IP address obtained in 1.
- xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your on-premises data center.
- The route command format varies depending on the OS. Use the route command format corresponding to the actual OS.
- Configure an OBS route from the local data center to the VPN or Direct Connect gateway.
The CIDR block of the VPC endpoint for accessing OBS is 100.125.0.0/16. To access OBS using a VPN connection or direct connection, you need to ensure that traffic from your local data center to OBS is directed to the VPN gateway or Direct Connect gateway.
-Configure a permanent route at your local data center and specify the Direct Connect or VPN gateway as the next hop for accessing OBS.
-route -p add 100.125.0.0 mask 255.255.0.0 xxx.xxx.xxx.xxx
- xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your local data center.
+- Configure an OBS route from the on-premises data center to the VPN or Direct Connect gateway.
The CIDR block of the VPC endpoint for accessing OBS is 100.125.0.0/16. To access OBS over a VPN or Direct Connect connection, ensure that traffic from your on-premises data center to OBS is directed to the VPN gateway or Direct Connect gateway.
+Configure a permanent route at your on-premises data center and specify the Direct Connect or VPN gateway as the next hop for accessing OBS. The following is the example command for configuring such a route:
+route -p add 100.125.0.0 mask 255.255.0.0 xxx.xxx.xxx.xxx
+- - xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your on-premises data center.
- The route command format varies depending on the OS. Use the route command format corresponding to the actual OS.
- At the local data center, run the following command to verify the connectivity with OBS: +
- At the on-premises data center, run the following command to verify the connectivity with OBS:
telnet bucket.endpoint
In the command:
-- bucket: indicates the bucket name.
- endpoint: indicates the endpoint information about OBS.
- bucket: indicates the bucket name.
- endpoint: indicates the OBS endpoint.
Example: telnet bucket.obs.eu-de.otc.t-systems.com
@@ -39,7 +39,7 @@diff --git a/docs/vpcep/umn/vpcep_02_0400.html b/docs/vpcep/umn/vpcep_02_0400.html index b9da0bcfe..87d3a191e 100644 --- a/docs/vpcep/umn/vpcep_02_0400.html +++ b/docs/vpcep/umn/vpcep_02_0400.html @@ -1,6 +1,6 @@ -Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address
+Configuring a VPC Endpoint for Accessing the Public IP Address of OBS over Public Networks
-
diff --git a/docs/vpcep/umn/vpcep_02_0401.html b/docs/vpcep/umn/vpcep_02_0401.html
index 2ab2ee0f7..08041fc36 100644
--- a/docs/vpcep/umn/vpcep_02_0401.html
+++ b/docs/vpcep/umn/vpcep_02_0401.html
@@ -17,7 +17,7 @@
diff --git a/docs/vpcep/umn/vpcep_02_0402.html b/docs/vpcep/umn/vpcep_02_0402.html index 6c4ce4f5d..fb1246810 100644 --- a/docs/vpcep/umn/vpcep_02_0402.html +++ b/docs/vpcep/umn/vpcep_02_0402.html @@ -1,16 +1,16 @@Step 1: Create a VPC Endpoint for Connecting to OBS
-Scenarios
This section describes how to create a VPC endpoint to access OBS from an IDC.
+-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 already exists.
+-Prerequisites
The required VPC endpoint service is available.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.
The Create VPC Endpoint page is displayed.
-Figure 1 Create VPC Endpoint+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- On the VPC Endpoints page, click Create VPC Endpoint.
The Create VPC Endpoint page is displayed.
+ - - Set the required parameters.
-
Table 1 Required parameters Parameter
+- Configure required parameters. +
-Table 1 VPC endpoint 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.
+Specifies the region where the VPC endpoint is to be located.
+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 services or Find a service by name.
+There are two options:
- 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
+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 operations people and you can use it without having to perform the creation operation.
+The VPC endpoint service has been created by the O&M personnel and you can directly use it.
Select com.t-systems.otc.eu-nl.obs-internet.
VPC
Specifies the VPC where the VPC endpoint is deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
+Subnet
+Specifies the subnet where the VPC endpoint is to be located.
Tag
@@ -62,18 +67,18 @@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 (_).
- 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 (@).
Value
- Cannot be left blank.
- Can contain a maximum of 43 Unicode characters.
- Can contain only letters, digits, hyphens (-), and underscores (_).
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
- 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.
- 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-nl.obs-internet is created.
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
@@ -81,7 +86,7 @@Figure 2 Summary of the VPC endpoint
diff --git a/docs/vpcep/umn/vpcep_02_0403.html b/docs/vpcep/umn/vpcep_02_0403.html index af2fdd8a1..fde728e31 100644 --- a/docs/vpcep/umn/vpcep_02_0403.html +++ b/docs/vpcep/umn/vpcep_02_0403.html @@ -1,24 +1,24 @@Step 2: Access OBS
-Scenarios
This section describes how to access OBS using a VPN connection or a direct connection.
+-Scenarios
This section describes how to access OBS using a VPN or Direct Connect connection.
Prerequisites
Your local data center has been connected to your VPC using a VPN or Direct Connect connection.- The local subnet of your VPC that interconnects with your VPN connection contains the OBS CIDR block.
For details about how to create a VPN connection, see Creating a VPN in the Virtual Private Network User Guide.
- - The VPC subnet associated with the virtual gateway contains the OBS CIDR block.
For details about how to enable Direct Connect, see Getting Started in the Direct Connect User Guide.
+-Prerequisites
Your on-premises data center has been connected to your VPC using a VPN or Direct Connect connection.- The VPC subnet associated with the VPN gateway contains the OBS CIDR block.
For details about how to create a VPN connection, see Creating a VPN in the Virtual Private Network User Guide.
+ - The VPC subnet associated with the Direct Connect gateway contains the OBS CIDR block.
For details about how to enable Direct Connect, see Getting Started in the Direct Connect User Guide.
Procedure
Configure an OBS route from the local data center to the VPN or Direct Connect gateway.
-The CIDR block of the VPC endpoint for accessing OBS is a public CIDR block. To access OBS using a VPN connection or direct connection, ensure that traffic from your local data center to OBS is directed to the VPN gateway or Direct Connect gateway.
-Configure a permanent route at your local data center and specify the Direct Connect or VPN gateway as the next hop for accessing OBS. The following is the example command for configuring such a route:
-route -p add Public IP address xxx.xxx.xxx.xxx
- - Public IP address indicates the address for accessing OBS.
- xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your local data center.
Procedure
Configure an OBS route from the on-premises data center to the VPN or Direct Connect gateway.
+The CIDR block of the VPC endpoint for accessing OBS is a public CIDR block. To access OBS over a VPN or Direct Connect connection, ensure that traffic from your on-premises data center to OBS is directed to the VPN gateway or Direct Connect gateway.
+Configure a permanent route at your on-premises data center and specify the Direct Connect or VPN gateway as the next hop for accessing OBS. The following is the example command for configuring such a route:
+route -p add Public IP address xxx.xxx.xxx.xxx
+ - Public IP address indicates the address for accessing OBS.
- xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your on-premises data center.
- The route command format varies depending on the OS. Use the route command format corresponding to the actual OS.
diff --git a/docs/vpcep/umn/vpcep_03_0100.html b/docs/vpcep/umn/vpcep_03_0100.html index 96c968fa8..f075fd428 100644 --- a/docs/vpcep/umn/vpcep_03_0100.html +++ b/docs/vpcep/umn/vpcep_03_0100.html @@ -8,7 +8,7 @@- Creating a VPC Endpoint Service
-
- Viewing Summary of a VPC Endpoint Service
+- Viewing the Summary of a VPC Endpoint Service
- Deleting a VPC Endpoint Service
diff --git a/docs/vpcep/umn/vpcep_03_0102.html b/docs/vpcep/umn/vpcep_03_0102.html index ab91d527b..86cc8a246 100644 --- a/docs/vpcep/umn/vpcep_03_0102.html +++ b/docs/vpcep/umn/vpcep_03_0102.html @@ -1,22 +1,22 @@ -
Viewing Summary of a VPC Endpoint Service
-Scenarios
This section describes how to query summary of a VPC endpoint service, including the name, ID, backend resource type, backend resource name, VPC, status, connection approval, service type, and creation time.
+Viewing the Summary of a VPC Endpoint Service
+-Scenarios
This section describes how to query the summary of a VPC endpoint service, including its name, ID, backend resource type, backend resource name, VPC, status, connection approval, service type, and creation time.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
Locate the target VPC endpoint service by entering a filter in the search box in the upper right corner:
-- Search by name or ID.
- Select Name or ID in the filter box.
- Enter a keyword in the search box.
- Click
to start the search.VPC endpoint services containing the keyword are displayed in the list.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
Locate the target VPC endpoint service by entering a filter in the search box in the upper right corner:
+- Search by name or ID.
- Select Name or ID in the filter box.
- Enter a keyword in the search box.
- Click to start the search.
VPC endpoint services containing the keyword are displayed.
- Search by preset tag.
- Click
in Search by Tag.Figure 1 Searching by tag-
- Enter a tag and a value.
Enter a key or value or select a key or value from the drop-down list.
+ - Search by tag.
- Click to the right of Search by Tag.Figure 1 Search by Tag+
- Enter a tag and a value.
You can also select a key or value from the drop-down list.
You can use a maximum of 20 tags to search for a VPC endpoint service.
- - Click Search.
The VPC endpoint service containing the specified tag is displayed in the list.
+ - Click Search.
VPC endpoint services containing the specified tag are displayed.
If you set multiple tags, VPC endpoint services containing all the specified tags will be displayed.
- Click
- Click
- Search by name or ID.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view the details.Figure 2 Summary of the VPC endpoint service+
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view its details.
Table 1 describes the parameters displayed on the VPC endpoint service details page.
-Table 1 Parameter description Tab
+Table 1 Parameters contained in details of a VPC endpoint service Tab
Parameter
VPC
Specifies the VPC where the VPC endpoint service is deployed.
+Specifies the VPC where the VPC endpoint service is to be deployed.
Status
@@ -66,7 +66,7 @@Specifies the type of the VPC endpoint service.
Creation
+Created
Specifies the creation time of the VPC endpoint service.
Status
Specifies the status of the VPC endpoint.
-For details about statuses of VPC endpoint services and VPC endpoints, see What Are Statuses of VPC Endpoint Services and VPC Endpoints?
+For details about statuses of VPC endpoint services and VPC endpoints, see What Statuses Are Available for a VPC Endpoint Service and VPC Endpoint?
Owner
@@ -94,7 +94,7 @@Specifies the domain ID of the VPC endpoint owner.
Creation
+Created
Specifies the creation time of the VPC endpoint.
Protocol
Specifies the protocol used for communications between the VPC endpoint service and VPC endpoint.
+Specifies the protocol used for communications between the VPC endpoint service and a VPC endpoint.
Service Port
@@ -135,7 +135,7 @@Specifies the port provided by the VPC endpoint, allowing you to access the VPC endpoint service.
Tag
+Tags
Key
Operation
Specifies the operation to be performed on the VPC endpoint service tag, for example, you can select Edit or Delete.
+Specifies the operation to be performed on the VPC endpoint service tag. You can click Edit or Delete.
- Deleted VPC endpoint services cannot be recovered. Exercise caution when performing this operation.
Constraints
- The VPC endpoint services configured from your private services can be deleted, but those configured by the system cannot.
- Any VPC endpoint service that has VPC endpoints in Accepted or Creating status cannot be deleted.
For statuses of a VPC endpoint, see What Are Statuses of VPC Endpoint Services and VPC Endpoints?
+-Constraints
- The VPC endpoint services configured from your private services can be deleted, but those configured by the system cannot.
- Any VPC endpoint service that has VPC endpoints in Accepted or Creating state cannot be deleted.
For statuses of a VPC endpoint, see What Statuses Are Available for a VPC Endpoint Service and VPC Endpoint?
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click Delete in the Operation column.Figure 1 Delete VPC Endpoint Service-
- Click Yes.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click Delete in the Operation column.Figure 1 Delete VPC Endpoint Service+
- In the displayed Delete VPC Endpoint Service dialog box, click Yes.
diff --git a/docs/vpcep/umn/vpcep_03_0104.html b/docs/vpcep/umn/vpcep_03_0104.html index 371512f1c..16904ee96 100644 --- a/docs/vpcep/umn/vpcep_03_0104.html +++ b/docs/vpcep/umn/vpcep_03_0104.html @@ -1,13 +1,13 @@Managing Connections of a VPC Endpoint Service
-Scenarios
To connect a VPC endpoint to a VPC endpoint service that has connection approval enabled, obtain the approval from the owner of the endpoint service.
-This section describes how to accept or reject connection of a VPC endpoint.
+Scenarios
To connect a VPC endpoint to a VPC endpoint service that has connection approval enabled, obtain the approval from the owner of the VPC endpoint service.
+This section describes how to accept or reject a connection from a VPC endpoint.
-Prerequisites
There is a VPC endpoint available for connecting to the target VPC endpoint service.
diff --git a/docs/vpcep/umn/vpcep_03_0105.html b/docs/vpcep/umn/vpcep_03_0105.html index 143b2ba08..74e2c0800 100644 --- a/docs/vpcep/umn/vpcep_03_0105.html +++ b/docs/vpcep/umn/vpcep_03_0105.html @@ -2,17 +2,17 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- Select the Connection Management tab.Figure 1 Connection Management-
- Accept or reject connection of a VPC endpoint in the list based on service requirements.
- If you click Accept, the VPC endpoint can connect to the VPC endpoint service.
- If you click Reject, the VPC endpoint cannot connect to the VPC endpoint service.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- Select the Connection Management tab.Figure 1 Connection Management+
- Accept or reject connection from a VPC endpoint in the list based on service requirements.
- If you click Accept, the VPC endpoint can connect to the VPC endpoint service.
- If you click Reject, the VPC endpoint cannot connect to the VPC endpoint service.
Managing Whitelist Records of a VPC Endpoint Service
-Scenarios
Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.
-After a VPC endpoint service is created, you can add an authorized domain ID to or delete it from the whitelist of the endpoint service.
+After a VPC endpoint service is created, you can add an authorized domain ID to or delete it from the whitelist of the VPC endpoint service.
- If the whitelist is empty, access from a VPC endpoint in another domain is not allowed.
- If an authorized domain ID is already in the whitelist, you can use this domain to create a VPC endpoint for connecting to the VPC endpoint service.
- If an authorized domain ID is not in the whitelist, you cannot use this domain to create a VPC endpoint for connecting to the VPC endpoint service.
This section describes how to add or delete a whitelist record for a VPC endpoint service.
Add a Whitelist Record
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab and click Add to Whitelist.
- Enter an authorized domain ID in the required format and click OK.Figure 1 Add to Whitelist+-
Add a Whitelist Record
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab and click Add to Whitelist.
- Enter an authorized domain ID in the required format and click OK.Figure 1 Add to Whitelist
- Your domain is in the whitelist of your VPC endpoint service by default.
- The authorized domain ID is in the iam:domain::domain_id format.
domain_id indicates the ID of the authorized domain, for example, iam:domain::1564ec50ef2a47c791ea5536353ed4b9
- Adding * to the whitelist means that all users can access the VPC endpoint service.
diff --git a/docs/vpcep/umn/vpcep_03_0106.html b/docs/vpcep/umn/vpcep_03_0106.html index 35e76ac18..221a5862c 100644 --- a/docs/vpcep/umn/vpcep_03_0106.html +++ b/docs/vpcep/umn/vpcep_03_0106.html @@ -3,9 +3,9 @@Delete a Whitelist Record
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab, locate the target domain ID, and click Delete in the Operation column.
To delete multiple whitelist records, select all the target domain IDs and click Delete in the upper left corner.
+Delete a Whitelist Record
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab, locate the target domain ID, and click Delete in the Operation column.
To delete multiple whitelist records, select all the target domain IDs and click Delete in the upper left corner.
- Click Yes.
Viewing Port Mappings of a VPC Endpoint Service
-Scenarios
After a VPC endpoint service is created, you can view the added port mappings.
A port mapping defines the protocol and ports used for communications between a VPC endpoint and a VPC endpoint service.
-- Protocol: A protocol both supported by the VPC endpoint and VPC endpoint service
- Service Port: A service port is provided by the backend service bound to the endpoint service.
- Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
- Protocol: a protocol both supported by the VPC endpoint and VPC endpoint service
- Service Port: provided by the backend resource bound to the VPC endpoint service.
- Terminal Port: provided by the VPC endpoint, allowing you to access the VPC endpoint service.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Choose Service List > Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Port Mapping tab.The port mapping configured for the VPC endpoint service is displayed.Figure 1 Port Mapping+
diff --git a/docs/vpcep/umn/vpcep_03_0107.html b/docs/vpcep/umn/vpcep_03_0107.html index 0fe24cdd5..0d1f0858d 100644 --- a/docs/vpcep/umn/vpcep_03_0107.html +++ b/docs/vpcep/umn/vpcep_03_0107.html @@ -4,11 +4,11 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the required region and project.
- Click Service List and choose Networking > VPC Endpoint.
- In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
- On the displayed page, select the Port Mapping tab.The port mappings configured for the VPC endpoint service are displayed.Figure 1 Port Mapping
A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.
There are two types of VPC endpoint services: gateway and interface.-- Gateway VPC endpoint services are created only for cloud services.
- Interface VPC endpoint services can be created for both cloud services and your private services. All VPC endpoint services for cloud services are created by default while those for private services need to be created by users themselves.
Supported cloud services vary in different regions. For details, see the list of services that can be configured on the management console.
+ Supported cloud services vary in different regions. For details, see the services that can be configured on the management console.
This section describes how to configure a VPC endpoint service (interface type) from your private service and how to manage it.
-Table 1 Management of VPC endpoint services
- Search by name or ID.
- The VPC subnet associated with the VPN gateway contains the OBS CIDR block.
- Configure required parameters. +
- The VPC subnet that needs to communicate with the on-premises data center over the VPN connection contains the OBS CIDR block 100.125.0.0/16.
- Configure VPC endpoint parameters. +
Overview
-Scenarios
If you want to access a cloud service like OBS from an IDC, you can connect the IDC to your VPC using a VPN connection or a direct connection and then connect your VPC to a cloud service using a VPC endpoint.
-This section describes how to configure a VPC endpoint to access OBS using its private address from an IDC.
- -Figure 1 shows the process of connecting an IDC to a VPC over VPN or Direct Connect to access DNS and OBS using two VPC endpoints, respectively.
+-Scenarios
If you want to access a cloud service like OBS from an on-premises data center, you can connect the on-premises data center to your VPC using a VPN connection or a Direct Connect connection, and then use a VPC endpoint to access the cloud service from your VPC.
+This section describes how to use a VPC endpoint to access OBS (private address) from an on-premises data center.
+ +Figure 1 shows the process of connecting the on-premise data center to a VPC over VPN or Direct Connect, and then using two VPC endpoints to access DNS and OBS, respectively.
A VPC endpoint comes with a VPC endpoint service. Before you create a VPC endpoint, ensure that the VPC endpoint service that you want to access is available.
The following VPC endpoint services are required:
-Configuration Process
Figure 2 shows the process for configuring a VPC endpoint to access OBS using its private address from an IDC.
+Configuration Process
Figure 2 shows the process for configuring a VPC endpoint to access OBS (private address) from the on-premises data center.
diff --git a/docs/vpcep/umn/vpcep_02_0302.html b/docs/vpcep/umn/vpcep_02_0302.html index b2fa8dd82..c50e7eda2 100644 --- a/docs/vpcep/umn/vpcep_02_0302.html +++ b/docs/vpcep/umn/vpcep_02_0302.html @@ -3,13 +3,13 @@Step 1: Create a VPC Endpoint for Connecting to DNS
-Scenarios
This section describes how to create a VPC endpoint for accessing a DNS server, in order to forward requests of resolving OBS domain names.
Prerequisites
The required VPC endpoint service already exists.
+-Prerequisites
The required VPC endpoint service is available.
Procedure
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
- Configure required parameters. +
- Configure required parameters. +
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
- Configure required parameters. +
- Configure required parameters. +
