Scenarios
- 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.
Scenarios
- 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. Cloud services are configured as VPC endpoint services by the O&M personnel by default. However, you need to create VPC endpoint services for your private services.
This section describes how to configure a private service into an interface VPC endpoint service.
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.
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. BMS will be discarded. You are recommended to choose Elastic load balancer.
- 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 can have only one backend resource.
Prerequisites
There are available backend resources in the same VPC.
+Prerequisites
There is a load balancer in the VPC where you are going to create 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 upper right corner, click Create VPC Endpoint Service.The Create VPC Endpoint Service page is displayed.diff --git a/docs/vpcep/umn/en-us_topic_0131645189.html b/docs/vpcep/umn/en-us_topic_0131645189.html index 91b6b7ad..62ab9f02 100644 --- a/docs/vpcep/umn/en-us_topic_0131645189.html +++ b/docs/vpcep/umn/en-us_topic_0131645189.html @@ -3,13 +3,13 @@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 Parameters for creating a VPC endpoint service Parameter
@@ -65,8 +65,8 @@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.
+- 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. BMS will be discarded. You are recommended to choose Elastic load balancer.
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 Source 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 an ECS from the ECS list.
+When you select ECS for Backend Resource Type, select an ECS from the ECS list.
BMS List
When Backend Resource Type is set to BMS, select a BMS from the BMS list.
+When you select BMS for Backend Resource Type, select a BMS from the BMS list.
NOTE:The BMS type will be discarded. The ELB type is recommended.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.Figure 2 VPC endpoint service list+
- Click Create Now.
- Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.Figure 2 VPC endpoint service list
Creating a VPC Endpoint
Scenarios
VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.
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.
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 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.
- 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.
-
+
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 VPC endpoint parameters Parameter
Region
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.
+Specifies the region where the VPC endpoint is to be deployed. Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
Service Category
There are two options:
-- Cloud 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.
- Cloud service: Select this option if the VPC endpoint service to be accessed is a cloud service.
- Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
Service List
This parameter is available only when you select Cloud services for Service Category.
+This parameter is available only when you select Cloud service for Service Category.
The VPC endpoint service has been created by the O&M personnel and you can directly use it.
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 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.
You can enter the VPC endpoint service name recorded in Viewing 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 VPC endpoint service or whether the name entered is correct.
Create a Private 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.
-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.
If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name.
+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
@@ -56,7 +56,7 @@Subnet
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.
+Specifies the subnet where the VPC endpoint is to be deployed.
Private IP Address
@@ -70,8 +70,8 @@This parameter is optional.
Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint.
Tag keys and values must meet requirements listed in Table 2.
-NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
-For details about predefined tags, see Predefined Tag Overview.
+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.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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.
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)+
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 service)+
Figure 4 Create VPC Endpoint (Service Category set to Find a service by name)
-Table 3 VPC endpoint parameters Parameter
+-Table 3 VPC endpoint parameters Parameter
Description
+Description
Region
+Region
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.
+Specifies the region where the VPC endpoint is to be deployed. Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
Service Category
+Service Category
Specifies the type of services that are configured as gateway VPC endpoint services. Only cloud services are supported.
-Select Cloud services.
+There are two options:
+- Cloud service: Select this option if the VPC endpoint service to be accessed is a cloud service.
- Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
Service List
+Service List
This parameter is available only when you select Cloud services for Service Category.
+This parameter is available only when you select Cloud service 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 the O&M personnel and you can directly use it.
VPC
+VPC Endpoint Service Name
Specifies the VPC where the VPC endpoint is to be deployed.
+This parameter is available only when you select Find a service by name for Service Category.
+Enter the VPC endpoint service name recorded in 7 (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 VPC endpoint service or whether the name entered is correct.
Subnet
+VPC
Specifies the subnet where the VPC endpoint is to be located.
+Specifies the VPC where the VPC endpoint is to be deployed.
Tag
+Subnet
This parameter is optional.
+Specifies the subnet where the VPC endpoint is to be deployed.
+Route Table
+This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+Select a route table for the VPC where the VPC endpoint is to be deployed.
+Tag
+This parameter is optional.
Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint.
Tag keys and values must meet requirements listed in Table 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.
+NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
+For details about predefined tags, see Predefined Tag Overview.
Table 4 Tag requirements for VPC endpoints Parameter
+Table 4 Tag requirements for VPC endpoints Parameter
Requirement
+Requirement
Tag key
+Tag key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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
+Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Application Scenarios
-
- Constraints
+- Notes and Constraints
-
- VPCEP and Other Services
+- VPC Endpoint and Other Services
- Permissions
diff --git a/docs/vpcep/umn/en-us_topic_0131645194.html b/docs/vpcep/umn/en-us_topic_0131645194.html index edbaafb9..84a9c320 100644 --- a/docs/vpcep/umn/en-us_topic_0131645194.html +++ b/docs/vpcep/umn/en-us_topic_0131645194.html @@ -1,20 +1,19 @@
What Is VPC Endpoint?
-VPC Endpoint (VPCEP) is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services, including cloud services or your private services. It allows you to plan networks flexibly without having to use EIPs.
+VPC Endpoint is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services, including cloud services or your private services. It allows you to plan networks flexibly without having to use EIPs.
-Architecture
There are two types of resources: VPC endpoint services and VPC endpoints.
-- VPC endpoint services are cloud services or private services that you manually configure in VPCEP. You can access these endpoint services using VPC endpoints.
For more information, see VPC Endpoint Services.
+- VPC endpoint services are cloud services or private services that you manually configure in VPC Endpoint. You can access these endpoint services using VPC endpoints.
For more information, see VPC Endpoint Services.
- VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.
For more information, see VPC Endpoints.
Figure 1 shows the process of establishing channels for network communications between:
- VPC 1 (ECS 1) and VPC 3 (ECS 3)
- VPC 2 (ECS 2) and cloud services such as OBS and DNS
- IDC and VPC 2 over VPN or Direct Connect to finally access a cloud service such as OBS or DNS
For more information, see Application Scenarios.
- VPC endpoint services are cloud services or private services that you manually configure in VPC Endpoint. You can access these endpoint services using VPC endpoints.
diff --git a/docs/vpcep/umn/en-us_topic_0131645196.html b/docs/vpcep/umn/en-us_topic_0131645196.html index 759ec03f..9b60f477 100644 --- a/docs/vpcep/umn/en-us_topic_0131645196.html +++ b/docs/vpcep/umn/en-us_topic_0131645196.html @@ -1,32 +1,32 @@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
Use this method if you need to integrate VPCEP into a third-party system for secondary development. For details, see VPC Endpoint API Reference.
+Accessing VPC Endpoint
You can access VPC Endpoint using any of the following:
+- Management console
Upon a quick configuration on the management console, you can start using VPC Endpoint.
+ - APIs
Use this method if you need to integrate VPC Endpoint into a third-party system for secondary development. For details, see VPC Endpoint API Reference.
- Management console
Application Scenarios
-VPCEP establishes a secure and private channel between a VPC endpoint (cloud resources in a VPC) and a VPC endpoint service in the same region.
-You can use VPCEP in different scenarios.
+VPC Endpoint establishes a secure and private channel between a VPC endpoint (cloud resources in a VPC) and a VPC endpoint service in the same region.
+You can use VPC Endpoint 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 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:
+ +Figure 1 shows the process of connecting an IDC to VPC 1 over VPN or Direct Connect, for accessing:
+- OBS or DNS using VPC endpoint 1
- ECS 1 in VPC 1 using VPC endpoint 2
- ECS 2 in VPC 2 using VPC endpoint 3
For cloud migration, VPC Endpoint 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.
+- Low cost
With VPC Endpoint, 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 the Private IP Address of OBS over Private Networks.
- Low cost
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.
+Cross-VPC Connection
VPC Endpoint enables your resources in two different VPCs within a region to communicate with each other.
- -
VPC endpoints and VPC peering connections are different in security, communications methods, route configurations, and more.
-For details, see What Are the Differences Between VPC Endpoints and VPC Peering Connections?.
+For details, see What Are the Differences Between VPC Endpoints and VPC Peering Connections?
An ECS in VPC 1 uses a VPC endpoint to access a load balancer in VPC 2 over a private network. Figure 2 shows the connection process.
-VPCEP has the following advantages:
-- High performance
Each gateway supports up to 1 million concurrent connections.
+ +Figure 2 shows how an ECS in VPC 1 uses a VPC endpoint to access a load balancer in VPC 2 over a private network.
+VPC Endpoint has the following advantages:
+ -- Simplified operations
VPCEP resources can be created within seconds and take effect quickly.
+For details, see the following sections:
- +
- Simplified operations
diff --git a/docs/vpcep/umn/vpcep_01_0002.html b/docs/vpcep/umn/vpcep_01_0002.html index 0852aa52..d586454c 100644 --- a/docs/vpcep/umn/vpcep_01_0002.html +++ b/docs/vpcep/umn/vpcep_01_0002.html @@ -1,7 +1,7 @@Product Advantages
-- Excellent Performance: Each gateway supports up to 1 million concurrent connections in a variety of application scenarios.
- Immediately Ready for Use Upon Creation: VPC endpoints take effect a few seconds after they are created.
- Easy to Use: You can use VPC endpoints to access resources over private networks, without having to use EIPs.
- High Security: VPC endpoints enable you to access VPC endpoint services without exposing server information, minimizing security risks.
- Excellent Performance: Each gateway supports up to 1 million concurrent connections, meeting requirements in different service scenarios.
- Ready to Use: VPC endpoints take effect a few seconds after they are created.
- Easy to Use: You can use VPC endpoints to access resources over private networks, without having to use EIPs.
- High Security: VPC endpoints enable you to access VPC endpoint services without exposing server information, minimizing security risks.
diff --git a/docs/vpcep/umn/vpcep_01_0005.html b/docs/vpcep/umn/vpcep_01_0005.html index b8e10172..a20dc30c 100644 --- a/docs/vpcep/umn/vpcep_01_0005.html +++ b/docs/vpcep/umn/vpcep_01_0005.html @@ -1,33 +1,35 @@ -Constraints
-Constraints on Resource Quotas
Table 1 describes constraints on the VPCEP resource quota.
+Notes and Constraints
+Resource Quotas
Table 1 describes quotas and constraints on VPC Endpoint resources.
-Table 1 VPCEP resource quotas Resource
+-Table 1 VPC Endpoint resource quotas and constraints Resource
Quota
+Default Quota and Constraints
How to Increase Quota
VPC endpoint services per account
+VPC endpoint services per account in one region
20
+ VPC endpoints per account
+VPC endpoints per account in one region
50
+50
+Other Constraints
- When you create a VPC endpoint, ensure that the associated VPC endpoint service has been created and is in the same region as the VPC endpoint.
- One VPC endpoint can be used to connect to only one VPC endpoint service.
- A VPC endpoint supports a maximum of 3,000 concurrent requests.
- One VPC endpoint service can be connected by multiple VPC endpoints.
- One VPC endpoint service corresponds to only one backend resource.
Other Constraints
- When you create a VPC endpoint, ensure that the associated VPC endpoint service is deployed in the same region as the VPC endpoint.
- One VPC endpoint can connect to only one VPC endpoint service.
- A VPC endpoint supports a maximum of 3,000 concurrent connections.
- One VPC endpoint service can be connected by multiple VPC endpoints.
- One VPC endpoint service can have only one backend resource.
diff --git a/docs/vpcep/umn/vpcep_01_0006.html b/docs/vpcep/umn/vpcep_01_0006.html index b5ef9bf1..263cc832 100644 --- a/docs/vpcep/umn/vpcep_01_0006.html +++ b/docs/vpcep/umn/vpcep_01_0006.html @@ -3,7 +3,7 @@VPC Endpoints
VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.
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.
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.
diff --git a/docs/vpcep/umn/vpcep_01_0007.html b/docs/vpcep/umn/vpcep_01_0007.html index 258a1ffc..bd4e60f2 100644 --- a/docs/vpcep/umn/vpcep_01_0007.html +++ b/docs/vpcep/umn/vpcep_01_0007.html @@ -1,7 +1,7 @@ -VPCEP and Other Services
-Table 1 shows the relationship between VPCEP and other cloud services.
+VPC Endpoint and Other Services
+Table 1 shows the relationship between VPC Endpoint and other cloud services.
Table 1 Relationships with other services Interactive Function
VPC
- + Connecting an IDC to your VPC using a VPN connection and connecting your VPC to a cloud service through VPCEP
+Connecting your on-premises data center to your VPC using a VPN connection and connecting your on-premises data center to a cloud service in another VPC through VPC Endpoint
VPN
Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks
Connecting an IDC to your VPC using a Direct Connect connection and connecting your VPC to a cloud service through VPCEP
+Connecting your on-premises data center to your VPC using a Direct Connect connection and connecting your on-premises data center to a cloud service in another VPC through VPC Endpoint
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.
+Creating IAM users and controlling their access to VPC Endpoint resources
IAM
Configured as a gateway VPC endpoint service by default. You can create a VPC endpoint to access these VPC endpoint services.
+Configured as a gateway VPC endpoint service by default. You can create a VPC endpoint to access the VPC endpoint service.
OBS
Configured as an interface VPC endpoint service by default. You can create VPC endpoints to access these endpoint services.
+Only the eu-de region supports the API gateway VPC endpoint service.
+API Gateway
++ +Configuring a private service as a VPC endpoint service. You can create a VPC endpoint to access the VPC endpoint service.
ELB
diff --git a/docs/vpcep/umn/vpcep_01_0010.html b/docs/vpcep/umn/vpcep_01_0010.html index a57c59e6..b185c286 100644 --- a/docs/vpcep/umn/vpcep_01_0010.html +++ b/docs/vpcep/umn/vpcep_01_0010.html @@ -3,7 +3,7 @@User Permissions
The cloud system provides two types of user permissions by default, user management and resource management.-- User management refers to management of users, user groups, and user group permissions.
- Resource management refers to access control over cloud service resources.
VPCEP provides two types of resources: VPC endpoint services and VPC endpoints, both of which are region-level resources. The required permissions must be added for users in the project.
+VPC Endpoint provides two types of resources: VPC endpoint services and VPC endpoints, both of which are region-level resources. The required permissions must be added for users in the project.
diff --git a/docs/vpcep/umn/vpcep_01_0011.html b/docs/vpcep/umn/vpcep_01_0011.html index 4cd8056b..7eb2b8db 100644 --- a/docs/vpcep/umn/vpcep_01_0011.html +++ b/docs/vpcep/umn/vpcep_01_0011.html @@ -11,7 +11,7 @@-Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
diff --git a/docs/vpcep/umn/vpcep_01_0013.html b/docs/vpcep/umn/vpcep_01_0013.html index 120d84cd..269cb936 100644 --- a/docs/vpcep/umn/vpcep_01_0013.html +++ b/docs/vpcep/umn/vpcep_01_0013.html @@ -2,7 +2,7 @@VPC Endpoint Services
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.
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. Cloud services are configured as VPC endpoint services by the O&M personnel by default. However, you need to create VPC endpoint services for your private services.
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.
@@ -40,7 +40,7 @@-Interface VPC Endpoint Services
Interface VPC endpoint services are mainly configured from:
- 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.
+ 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
@@ -68,7 +68,20 @@Select the endpoint service ending with dns if you want to access DNS over private networks.
Load balancer
+API Gateway
+Cloud service
+Interface
+eu-de:
+com.t-systems.otc.eu-de.apig
+Select the endpoint service ending with apig if you want to access API Gateway using a VPC endpoint.
+Only the eu-de region supports the API gateway VPC endpoint service.
+ELB
Users' private service
- Operation Guide
- - Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain
+ - Configuring a VPC Endpoint for Communications Across VPCs of the Same Account
- - Configuring a VPC Endpoint for Communications Across VPCs of Different Domains
+ - Configuring a VPC Endpoint for Communications Across VPCs of Different Accounts
- Configuring a VPC Endpoint for Accessing the Private IP Address of OBS over Private Networks
diff --git a/docs/vpcep/umn/vpcep_02_0200.html b/docs/vpcep/umn/vpcep_02_0200.html
index d310a9d1..ee2d7166 100644
--- a/docs/vpcep/umn/vpcep_02_0200.html
+++ b/docs/vpcep/umn/vpcep_02_0200.html
@@ -1,6 +1,6 @@
- - 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.
- Only one-way communications from the VPC endpoint to the VPC endpoint service are supported.
- For details about communications between two VPCs of different accounts, see Configuring a VPC Endpoint for Communications Across VPCs of Different Accounts.
- 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- +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 required parameters.
-
Table 1 Parameters for creating a VPC endpoint service Parameter
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.
+- 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. BMS will be discarded. You are recommended to choose Elastic load balancer.
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 Source set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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 its 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 VPC endpoint service and click its name to view its details.Figure 2 Summary of the VPC endpoint service
- 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)+
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)
- Configure required parameters. +
- Configure VPC endpoint parameters.
Table 1 VPC endpoint parameters Parameter
Description
@@ -17,27 +17,28 @@Region
Specifies the region where the VPC endpoint is to be located. This region is the same as that of the VPC endpoint service.
+Specifies the region where the VPC endpoint is to be deployed. This region is the same as that of the VPC endpoint service.
Service Category
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.
- Cloud services: Select this option if the VPC endpoint service to be accessed is a cloud service.
- Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
In this example, select 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 name entered is correct.
Enter the VPC endpoint service name recorded in 8 (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 VPC endpoint service or whether the name entered is correct.
Create a Private 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.
If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name.
+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
@@ -47,7 +48,13 @@Subnet
Specifies the subnet where the VPC endpoint is to be located.
+Specifies the subnet where the VPC endpoint is to be deployed.
+Route Table
+This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+Select a route table for the VPC where the VPC endpoint is to be deployed.
Private IP Address
@@ -61,8 +68,8 @@This parameter is optional.
Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint.
Tag keys and values must meet requirements listed in Table 2.
-NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
-For details about predefined tags, see Predefined Tag Overview.
+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.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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 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.
- 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 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 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 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 during creation.Figure 2 Summary of the VPC endpoint+
- In the VPC endpoint list, click the ID of the 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 (for accessing an interface VPC endpoint service)
You can use the private IP address or private domain name to access the VPC endpoint service.
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 endpoint+
Figure 3 Logging in to an ECS to access the VPC endpoint
diff --git a/docs/vpcep/umn/vpcep_02_0203.html b/docs/vpcep/umn/vpcep_02_0203.html index 9e538b1c..56d30fde 100644 --- a/docs/vpcep/umn/vpcep_02_0203.html +++ b/docs/vpcep/umn/vpcep_02_0203.html @@ -1,6 +1,6 @@ -Configuring a VPC Endpoint for Communications Across VPCs of Different Domains
+Configuring a VPC Endpoint for Communications Across VPCs of Different Accounts
-
diff --git a/docs/vpcep/umn/vpcep_02_02031.html b/docs/vpcep/umn/vpcep_02_02031.html
index 07b6bebf..46ca5a4f 100644
--- a/docs/vpcep/umn/vpcep_02_02031.html
+++ b/docs/vpcep/umn/vpcep_02_02031.html
@@ -1,21 +1,21 @@
- 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.
- Only one-way communications from the VPC endpoint to the VPC endpoint service are supported.
- Before you create a VPC endpoint, add the authorized account 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 account, see Configuring a VPC Endpoint for Communications Across VPCs of the Same Account.
- 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- +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 required parameters.
-
Table 1 Parameters for creating a VPC endpoint service Parameter
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.
+- 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. BMS will be discarded. You are recommended to choose Elastic load balancer.
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 Source set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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 its 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 VPC endpoint service and click its name to view its details.Figure 2 Summary of the VPC endpoint service
- Log in to the management console.
- Click My Credentials under the domain.Figure 1 My Credentials+
Obtain the ID of Your Own Account
- Log in to the management console.
- Click My Credentials under the account.
-The My Credentials page is displayed. You can view and record the domain ID.-Figure 2 Domain ID+
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
+Add Account 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 VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab and click Add to Whitelist.
- Enter an authorized account ID in the required format and click OK.Figure 3 Add to Whitelist+
- Your account is in the whitelist of your VPC endpoint service by default.
- The authorized account ID is in the iam:domain::domain_id format.
domain_id indicates the ID of the authorized account, 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_02_02035.html b/docs/vpcep/umn/vpcep_02_02035.html index ce907319..70b8cb19 100644 --- a/docs/vpcep/umn/vpcep_02_02035.html +++ b/docs/vpcep/umn/vpcep_02_02035.html @@ -5,9 +5,9 @@ Select the same region and project as those of the VPC endpoint service.
- Click
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)+
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)
- Configure required parameters. +
- Configure VPC endpoint parameters.
Table 1 VPC endpoint parameters Parameter
Description
@@ -16,27 +16,28 @@Region
Specifies the region where the VPC endpoint is to be located. This region is the same as that of the VPC endpoint service.
+Specifies the region where the VPC endpoint is to be deployed. This region is the same as that of the VPC endpoint service.
Service Category
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.
- Cloud services: Select this option if the VPC endpoint service to be accessed is a cloud service.
- Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
In this example, select 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 name entered is correct.
Enter the VPC endpoint service name recorded in 8 (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 VPC endpoint service or whether the name entered is correct.
Create a Private 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.
If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name.
+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
@@ -46,7 +47,13 @@Subnet
Specifies the subnet where the VPC endpoint is to be located.
+Specifies the subnet where the VPC endpoint is to be deployed.
+Route Table
+This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+Select a route table for the VPC where the VPC endpoint is to be deployed.
Private IP Address
@@ -60,8 +67,8 @@This parameter is optional.
Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint.
Tag keys and values must meet requirements listed in Table 2.
-NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
-For details about predefined tags, see Predefined Tag Overview.
+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.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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 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.
- 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 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 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 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 during creation.Figure 2 Summary of the VPC endpoint+- In the VPC endpoint list, click the ID of the VPC endpoint to view its details.
@@ -100,7 +107,7 @@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 (for accessing an interface VPC endpoint service)You can use the private IP address or private domain name to access the VPC endpoint service.
diff --git a/docs/vpcep/umn/vpcep_02_0301.html b/docs/vpcep/umn/vpcep_02_0301.html index 71556cd5..3a7c76ca 100644 --- a/docs/vpcep/umn/vpcep_02_0301.html +++ b/docs/vpcep/umn/vpcep_02_0301.html @@ -3,8 +3,8 @@Overview
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.
+ +Figure 1 shows the process of connecting the on-premises data center to a VPC over VPN or Direct Connect, and then using two VPC endpoints to enable the on-premises data center 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 (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 c50e7eda..94fabbab 100644 --- a/docs/vpcep/umn/vpcep_02_0302.html +++ b/docs/vpcep/umn/vpcep_02_0302.html @@ -5,7 +5,7 @@-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.
- 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+
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. @@ -17,28 +17,28 @@
- Click
Overview
-Scenarios
With VPCEP, you can access resources across VPCs in the same region.
+Scenarios
With VPC Endpoint, 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.
-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 communications-
-This section describes how cloud resources in VPCs of different accounts in the same region can communicate with each other.
+VPC 1 and VPC 2 belong to different accounts. 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 a private IP address.
+Figure 1 Cross-VPC communications+
Cross-VPC Communications
Figure 2 shows how to enable communications between two VPCs of different domains using VPCEP.
- +Cross-VPC Communications
Figure 2 shows how to enable communications between two VPCs of different accounts using VPC Endpoint.
+diff --git a/docs/vpcep/umn/vpcep_02_02032.html b/docs/vpcep/umn/vpcep_02_02032.html index 79e2345d..cf7bf439 100644 --- a/docs/vpcep/umn/vpcep_02_02032.html +++ b/docs/vpcep/umn/vpcep_02_02032.html @@ -1,16 +1,13 @@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 describes how to create a VPC endpoint service by selecting an elastic load balancer as an example backend service in VPC 2 using domain B.
+-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 describes how to create a VPC endpoint service by selecting an elastic load balancer as an example backend service in VPC 2 using account B.
Prerequisites
There are available backend resources in the same VPC.
+-Prerequisites
There is a load balancer in the VPC where you are going to create the VPC endpoint service.
Procedure
diff --git a/docs/vpcep/umn/vpcep_02_02034.html b/docs/vpcep/umn/vpcep_02_02034.html index b21cec78..6de4af0a 100644 --- a/docs/vpcep/umn/vpcep_02_02034.html +++ b/docs/vpcep/umn/vpcep_02_02034.html @@ -1,20 +1,20 @@Step 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 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.
+-Scenarios
Permission management controls the access of a VPC endpoint in one account to a VPC endpoint service in another.
+After a VPC endpoint service is created, you can add or delete an authorized account ID to and from the whitelist of the VPC endpoint service.
+The following operations describe how to obtain your account ID and add it to the whitelist of another user's VPC endpoint services.
Prerequisites
There is a VPC endpoint service available.
+-Prerequisites
The required VPC endpoint service is available.
Obtain the ID of Your Own Domain
Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain
+Configuring a VPC Endpoint for Communications Across VPCs of the Same Account
-
diff --git a/docs/vpcep/umn/vpcep_02_02021.html b/docs/vpcep/umn/vpcep_02_02021.html
index 24c323ff..ba4b2b1a 100644
--- a/docs/vpcep/umn/vpcep_02_02021.html
+++ b/docs/vpcep/umn/vpcep_02_02021.html
@@ -1,21 +1,21 @@
Overview
-Scenarios
With VPCEP, you can access resources across VPCs in the same region.
+Scenarios
With VPC Endpoint, 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 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- -This section describes how cloud resources in VPCs of the same account in the same region can communicate with each other.
+VPC 1 and VPC 2 belong to the same account 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+ Configuration Process
Figure 2 shows how to enable communications between VPCs of the same domain using VPCEP. +Configuration Process
Figure 2 shows how to enable communications between VPCs of the same account using VPC Endpoint.diff --git a/docs/vpcep/umn/vpcep_02_02022.html b/docs/vpcep/umn/vpcep_02_02022.html index 171dca23..adbe3a62 100644 --- a/docs/vpcep/umn/vpcep_02_02022.html +++ b/docs/vpcep/umn/vpcep_02_02022.html @@ -2,15 +2,12 @@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 to describe how to create a VPC endpoint service.
+This section uses a load balancer as an example to describe how to create a VPC endpoint service.
-Prerequisites
There are available backend resources in the same VPC.
+-Prerequisites
There is a load balancer in the VPC where you are going to create the VPC endpoint service.
Procedure
diff --git a/docs/vpcep/umn/vpcep_02_02023.html b/docs/vpcep/umn/vpcep_02_02023.html index 3231fb0e..1b928e7b 100644 --- a/docs/vpcep/umn/vpcep_02_02023.html +++ b/docs/vpcep/umn/vpcep_02_02023.html @@ -6,9 +6,9 @@ Select the same region and project as those of the VPC endpoint service.
Procedure
Region
Specifies the region where the VPC endpoint is to be located.
+Specifies the region where the VPC endpoint is to be deployed.
Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
Service Category
There are two options:
-- Cloud 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 Cloud services.
+- Cloud service: Select this option if the VPC endpoint service to be accessed is a cloud service.
- Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
In this example, select Cloud service.
Service List
This parameter is available only when you select Cloud services for Service Category.
+This parameter is available only when you select Cloud service for Service Category.
The VPC endpoint service has been created by the O&M personnel and you can directly use it.
-In this example, select com.t-systems.otc.eu-de.dns.
+In this example, select com.t-systems.otc.eu-de.dns.
Create a Private 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.
-This parameter is only available for interface VPC endpoints, 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.
+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.
Subnet
Specifies the subnet where the VPC endpoint is to be located.
+Specifies the subnet where the VPC endpoint is to be deployed.
Private IP Address
@@ -63,8 +63,8 @@This parameter is optional.
Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint.
Tag keys and values must meet requirements listed in Table 2.
-NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
-For details about predefined tags, see Predefined Tag Overview.
+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.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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 assigned together with a private domain name if you select Create a Private Domain Name during creation.diff --git a/docs/vpcep/umn/vpcep_02_0303.html b/docs/vpcep/umn/vpcep_02_0303.html index 580a7d13..c132c47b 100644 --- a/docs/vpcep/umn/vpcep_02_0303.html +++ b/docs/vpcep/umn/vpcep_02_0303.html @@ -5,8 +5,8 @@Figure 2 Summary of the VPC endpoint+
- 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 VPC endpoint to view its details.
-Prerequisites
The required VPC endpoint service is available.
diff --git a/docs/vpcep/umn/vpcep_02_0304.html b/docs/vpcep/umn/vpcep_02_0304.html index 4a2a73c8..6aecc78f 100644 --- a/docs/vpcep/umn/vpcep_02_0304.html +++ b/docs/vpcep/umn/vpcep_02_0304.html @@ -8,7 +8,7 @@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+
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
Region
Specifies the region where the VPC endpoint is to be located.
+Specifies the region where the VPC endpoint is to be deployed.
Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
Service Category
There are two options:
-- Cloud 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 Cloud services.
+- Cloud service: Select this option if the VPC endpoint service to be accessed is a cloud service.
- Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
In this example, select Cloud service.
Service List
This parameter is available only when you select Cloud services for Service Category.
+This parameter is available only when you select Cloud service for Service Category.
The VPC endpoint service has been created by the O&M personnel and you can directly use it.
-Example: com.t-systems.otc.eu-de.obs
+Example: com.t-systems.otc.eu-de.obs
VPC
@@ -41,7 +41,13 @@Subnet
Specifies the subnet where the VPC endpoint is to be located.
+Specifies the subnet where the VPC endpoint is to be deployed.
+Route Table
+This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+Select a route table for the VPC where the VPC endpoint is to be deployed.
Tag
@@ -49,8 +55,8 @@This parameter is optional.
Specifies the VPC endpoint tag, which consists of a key and a value. You can add up to 20 tags to each VPC endpoint.
Tag keys and values must meet requirements listed in Table 2.
-NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
-For details about predefined tags, see Predefined Tag Overview.
+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.
Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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 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+
- 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 VPC endpoint to view its details.Figure 2 Summary of the VPC endpoint
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+
Procedure
- In the VPC endpoint list, locate the 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 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.
@@ -28,10 +28,10 @@ forwarders{ xx.xx.xx.xx;};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 on-premises data center, run the following command to verify the connectivity with OBS:
telnet bucket.endpoint
+ - At the on-premises data center, run the following command to verify the connectivity with OBS:
telnet bucketname.endpoint
In the command:
-- bucket: indicates the bucket name.
- endpoint: indicates the OBS endpoint.
Example: telnet bucket.obs.eu-de.otc.t-systems.com
+- bucketname: indicates the bucket name.
- endpoint: indicates the endpoint (domain name) of the region where the bucket is deployed.
Example: telnet bucketname.obs.eu-de.otc.t-systems.com
- Overview
- - Step 1: Create a VPC Endpoint for Connecting to OBS
+ - Step 1: Create a VPC Endpoint for Accessing OBS
- Step 2: Access OBS
diff --git a/docs/vpcep/umn/vpcep_02_0401.html b/docs/vpcep/umn/vpcep_02_0401.html
index 08041fc3..a66ea613 100644
--- a/docs/vpcep/umn/vpcep_02_0401.html
+++ b/docs/vpcep/umn/vpcep_02_0401.html
@@ -5,14 +5,14 @@
This section describes how to create such a VPC endpoint to access OBS.
- + This scenario is supported only in region eu-nl.
Figure 1 shows the process of connecting an IDC to a VPC over VPN or Direct Connect to access OBS using a VPC endpoint created in the VPC.
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:
eu-nl: com.t-systems.otc.eu-nl.obs-internet
Configuration Process
Figure 2 shows the process for configuring a VPC endpoint to access OBS using its public address from an IDC.
- + - In the VPC endpoint list, locate the VPC endpoint and click the ID of the endpoint to view its details.
diff --git a/docs/vpcep/umn/vpcep_02_0402.html b/docs/vpcep/umn/vpcep_02_0402.html index fb124681..4b8421d4 100644 --- a/docs/vpcep/umn/vpcep_02_0402.html +++ b/docs/vpcep/umn/vpcep_02_0402.html @@ -1,57 +1,63 @@ -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 on-premises data center.
+Step 1: Create a VPC Endpoint for Accessing OBS
+Scenarios
This section describes how to create a VPC endpoint to access OBS from an on-premises data center.
-Prerequisites
The required VPC endpoint service is available.
Procedure
- 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.
-+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.
+ - - - Configure required parameters.
-
Table 1 VPC endpoint parameters Parameter
+ +- Configure VPC endpoint parameters. +
-Table 1 VPC endpoint parameters Parameter
Description
+Description
Region
+Region
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.
+Specifies the region where the VPC endpoint is to be deployed.
+Resources in different regions cannot communicate with each other over an intranet. For lower latency and quicker access, select the nearest region.
Service Category
+Service Category
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 Cloud services.
+There are two options:
+- Cloud service: Select this option if the VPC endpoint service to be accessed is a cloud service.
- Find a service by name: Select this option if the VPC endpoint service to be accessed is a private service of your own.
In this example, select Cloud service.
Service List
+Service List
This parameter is available only when you select Cloud services for Service Category.
-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.
+This parameter is available only when you select Cloud service for Service Category.
+The VPC endpoint service has been created by the O&M personnel and you can directly use it.
+Select the VPC endpoint service for OBS, that is, com.t-systems.otc.eu-nl.obs-internet.
VPC
+VPC
Specifies the VPC where the VPC endpoint is to be deployed.
+Specifies the VPC where the VPC endpoint is to be deployed.
Subnet
Specifies the subnet where the VPC endpoint is to be located.
+Specifies the subnet where the VPC endpoint is to be deployed.
Tag
+Route Table
(Optional) Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.
-Tag keys and values must meet requirements listed in Table 2.
-NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
-For details about predefined tags, see Predefined Tag Overview.
+This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+Select a route table for the VPC where the VPC endpoint is to be deployed.
+Tag
+(Optional) Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.
+Tag keys and values must meet requirements listed in Table 2.
+NOTE:If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.
+For details about predefined tags, see Predefined Tag Overview.
Table 2 Tag requirements for VPC endpoints Parameter
+Table 2 Tag requirements for VPC endpoints Parameter
Requirement
+Requirement
Key
+Tag key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain a maximum of 36 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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
+Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- 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 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.
Figure 2 Summary of the VPC endpoint+
- 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 VPC endpoint to view its details.
diff --git a/docs/vpcep/umn/vpcep_03_0100.html b/docs/vpcep/umn/vpcep_03_0100.html index f075fd42..8920c64b 100644 --- a/docs/vpcep/umn/vpcep_03_0100.html +++ b/docs/vpcep/umn/vpcep_03_0100.html @@ -8,7 +8,7 @@Figure 2 Summary of the VPC endpoint
- Creating a VPC Endpoint Service
-
- Viewing the Summary of a VPC Endpoint Service
+- Viewing 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 86cc8a24..3d922968 100644 --- a/docs/vpcep/umn/vpcep_03_0102.html +++ b/docs/vpcep/umn/vpcep_03_0102.html @@ -1,22 +1,20 @@ -
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.
+Viewing a VPC Endpoint Service
+-Scenarios
This section describes how to query details 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.
- 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.
+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 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 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.
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.
+ - Search by tag.
- Click the filter box and select Tag from the drop-down list.Figure 1 Searching for VPC endpoint services by tag+
- Select tags.Figure 2 Selecting tags+
- Click OK to search.
VPC endpoint services containing the specified tags are displayed.
- Click the filter box and select Tag from the drop-down list.
- Click
- Search by name or ID.
- In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view its details. +
- In the VPC endpoint service list, locate the 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 Parameters contained in details of a VPC endpoint service Tab
+Table 1 Parameters contained in the details of a VPC endpoint service Tab
Parameter
Summary
+Summary
Name
Specifies the name of the VPC endpoint service.
ID
+Summary
Specifies the ID of the VPC endpoint service.
+ID
+Specifies the ID of the VPC endpoint service.
Backend Resource Type
+Summary
Specifies the type of the backend resource that provides services.
+Backend Resource Type
+Specifies the type of the backend resource that provides services.
Backend Resource Name
+Summary
Specifies the name of the backend resource that provides services to be accessed.
+Backend Resource Name
+Specifies the name of the backend resource that provides services to be accessed.
VPC
+Summary
Specifies the VPC where the VPC endpoint service is to be deployed.
+VPC
+Specifies the VPC where the VPC endpoint service is to be deployed.
Status
+Summary
Specifies the status of the VPC endpoint service.
+Status
+Specifies the status of the VPC endpoint service.
Connection Approval
+Summary
Specifies whether connection approval is required.
+Connection Approval
+Specifies whether connection approval is required.
Service Type
+Summary
Specifies the type of the VPC endpoint service.
+Service Type
+Specifies the type of the VPC endpoint service.
Created
+Summary
Specifies the creation time of the VPC endpoint service.
+Created
+Specifies the creation time of the VPC endpoint service.
Connection Management
+Connection Management
VPC Endpoint ID
Specifies the ID of the VPC endpoint.
Packet ID
+Connection Management
Specifies the identifier of the VPC endpoint ID.
+Packet ID
+Specifies the identifier of the VPC endpoint ID.
Status
+Connection Management
Specifies the status of the VPC endpoint.
-For details about statuses of VPC endpoint services and VPC endpoints, see What Statuses Are Available for a VPC Endpoint Service and VPC Endpoint?
+Status
+Specifies the status of the VPC endpoint.
+For details about the statuses of a VPC endpoint, see What Statuses Are Available for a VPC Endpoint Service and VPC Endpoint?
Owner
+Connection Management
Specifies the domain ID of the VPC endpoint owner.
+Owner
+Specifies the account ID of the VPC endpoint owner.
Created
+Connection Management
Specifies the creation time of the VPC endpoint.
+Created
+Specifies the creation time of the VPC endpoint.
Operation
+Connection Management
Specifies whether to allow a VPC endpoint to connect to a VPC endpoint service. The option can be Accept or Reject.
+Operation
+Specifies whether to allow a VPC endpoint to connect to a VPC endpoint service. The option can be Accept or Reject.
Permission Management
+Permission Management
Authorized Domain ID
+Authorized Account ID
Specifies the authorized domain ID for connecting to the VPC endpoint. The ID can also be *.
+Specifies the authorized account ID for connecting to the VPC endpoint. The ID can also be *.
If you add an asterisk (*) to the whitelist, it means that all users can access the VPC endpoint service.
Operation
+Permission Management
Specifies whether to delete an authorized domain from the whitelist.
+Operation
+Specifies whether to delete an authorized account from the whitelist.
Port Mapping
+Port Mapping
Protocol
@@ -125,31 +151,39 @@Specifies the protocol used for communications between the VPC endpoint service and a VPC endpoint.
Service Port
+Port Mapping
Specifies the port provided by the backend service bound to the VPC endpoint service.
+Service Port
+Specifies the port provided by the backend service bound to the VPC endpoint service.
Terminal Port
+Port Mapping
Specifies the port provided by the VPC endpoint, allowing you to access the VPC endpoint service.
+Terminal Port
+Specifies the port provided by the VPC endpoint, allowing you to access the VPC endpoint service.
Tags
+Tags
Key
Specifies the tag key of the VPC endpoint service.
Value
+Tags
Specifies the tag value of the VPC endpoint service.
+Value
+Specifies the tag value of the VPC endpoint service.
Operation
+Tags
Specifies the operation to be performed on the VPC endpoint service tag. You can click Edit or Delete.
+Operation
+Specifies the operation to be performed on the VPC endpoint service tag. You can click Edit or Delete.
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.
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.
diff --git a/docs/vpcep/umn/vpcep_03_0104.html b/docs/vpcep/umn/vpcep_03_0104.html index 16904ee9..2a836fe6 100644 --- a/docs/vpcep/umn/vpcep_03_0104.html +++ b/docs/vpcep/umn/vpcep_03_0104.html @@ -4,9 +4,9 @@-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.
+-Prerequisites
There is a VPC endpoint available for connecting to the target 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+
diff --git a/docs/vpcep/umn/vpcep_03_0105.html b/docs/vpcep/umn/vpcep_03_0105.html index 74e2c080..3a898bc2 100644 --- a/docs/vpcep/umn/vpcep_03_0105.html +++ b/docs/vpcep/umn/vpcep_03_0105.html @@ -1,19 +1,19 @@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 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 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.
-Scenarios
Permission management controls the access of a VPC endpoint in one account to a VPC endpoint service in another.
+After a VPC endpoint service is created, you can add or delete an authorized account ID to and from the whitelist of the VPC endpoint service.
+- If the whitelist is empty, access from a VPC endpoint in another account is not allowed.
- If an authorized account ID is already in the whitelist, you can use this account to create a VPC endpoint for connecting to the VPC endpoint service.
- If an authorized account ID is not in the whitelist, you cannot use this account 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.
- 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
+-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 VPC endpoint service and click its name.
- On the displayed page, select the Permission Management tab and click Add to Whitelist.
- Enter an authorized account ID in the required format and click OK.Figure 1 Add to Whitelist+
- Your account is in the whitelist of your VPC endpoint service by default.
- The authorized account ID is in the iam:domain::domain_id format.
domain_id indicates the ID of the authorized account, for example, iam:domain::1564ec50ef2a47c791ea5536353ed4b9
- Adding * to the whitelist means that all users can access the VPC endpoint service.
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.
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 VPC endpoint service and click its name.
- On the displayed page, click the Permission Management tab, locate the account ID, and click Delete in the Operation column.
To delete multiple whitelist records, select the account IDs to be deleted and click Delete in the upper left corner.
+ - Click Yes.
diff --git a/docs/vpcep/umn/vpcep_03_0106.html b/docs/vpcep/umn/vpcep_03_0106.html index 221a5862..5cdb59ef 100644 --- a/docs/vpcep/umn/vpcep_03_0106.html +++ b/docs/vpcep/umn/vpcep_03_0106.html @@ -3,9 +3,9 @@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: 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.
- 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.
- 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+
diff --git a/docs/vpcep/umn/vpcep_03_0107.html b/docs/vpcep/umn/vpcep_03_0107.html index 0d1f0858..1967e98c 100644 --- a/docs/vpcep/umn/vpcep_03_0107.html +++ b/docs/vpcep/umn/vpcep_03_0107.html @@ -2,7 +2,7 @@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 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
VPC Endpoint Service Overview
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.
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. Cloud services are configured as VPC endpoint services by the O&M personnel by default. However, you need to create VPC endpoint services for your private services.
@@ -20,14 +20,14 @@ Supported cloud services vary in different regions. For details, see the services that can be configured on the management console.
Describes how to configure a private service as a VPC endpoint service.
- 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.
- 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. BMS will be discarded. You are recommended to choose Elastic load balancer.
- 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 can have only one backend resource.
+ Describes how to query details about a VPC endpoint service.
+Describes how to query details of a VPC endpoint service.
None
Describes how to manage whitelist records of a VPC endpoint service to control across-account access between a VPC endpoint and a VPC endpoint service.
- The VPC endpoint must be in the same region as the VPC endpoint service.
- Before you configure the whitelist for a VPC endpoint service, obtain the domain ID of the associated VPC endpoint.
- The VPC endpoint and the VPC endpoint service must be deployed in the same region.
- Before you configure the whitelist for a VPC endpoint service, obtain the account ID of the associated VPC endpoint.
Viewing Port Mappings of a VPC Endpoint Service
diff --git a/docs/vpcep/umn/vpcep_03_0108.html b/docs/vpcep/umn/vpcep_03_0108.html index 804cbda2..7c8f99d1 100644 --- a/docs/vpcep/umn/vpcep_03_0108.html +++ b/docs/vpcep/umn/vpcep_03_0108.html @@ -8,7 +8,7 @@Add a Tag
Perform the following operations to tag an existing VPC endpoint service:
-- 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 Tags tab.
- Click Add Tag.
- In the displayed Add Tag dialog box, enter a key and a value.Table 1 describes the tag requirements. +
- 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 VPC endpoint service and click its name.
- On the displayed page, select the Tags tab.
- Click Add Tag.
- In the displayed Add Tag dialog box, enter a key and a value.Table 1 describes the tag requirements.
Table 1 Tag requirements for VPC endpoint services Parameter
Requirement
@@ -22,7 +22,7 @@Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Click OK.
Edit a Tag
Perform the following operations to edit a tag of a VPC endpoint service:
-- 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 Tags tab.
- In the tag list, locate the target tag and click Edit in the Operation column.
- Enter a new value.
You can only edit tag values.
+- 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 VPC endpoint service and click its name.
- On the displayed page, select the Tags tab.
- In the tag list, locate the tag and click Edit in the Operation column.
- Enter a new value.
You can only edit tag values.
- Click OK.
Delete a Tag
Perform the following operations to delete a tag of a VPC endpoint service:
-
Deleted tags cannot be recovered. Exercise caution when performing this operation.
- 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 Tags tab.
- In the tag list, locate the target tag and click Delete in the Operation column.
- Click Yes.
- 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 VPC endpoint service and click its name.
- On the displayed page, select the Tags tab.
- In the tag list, locate the tag and click Delete in the Operation column.
- Click Yes.
diff --git a/docs/vpcep/umn/vpcep_03_0202.html b/docs/vpcep/umn/vpcep_03_0202.html index 2c684556..9b7da239 100644 --- a/docs/vpcep/umn/vpcep_03_0202.html +++ b/docs/vpcep/umn/vpcep_03_0202.html @@ -3,85 +3,139 @@Querying and Accessing a VPC Endpoint
-Scenarios
After a VPC endpoint is created, you can query its details and access it.
Querying a VPC Endpoint
Perform the following operations to query details about a VPC endpoint, including its ID, associated VPC endpoint service name, VPC, and status.
-- 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 displayed page, locate the target VPC endpoint by entering a keyword in the search box in the upper right corner:
-- Search by VPC endpoint service name or VPC endpoint ID.
- Select ID or VPC Endpoint Service Name in the filter box.
- Enter a keyword in the search box.
- Click to start the search.
VPC endpoints containing the keyword are displayed in the VPC endpoint list.
++Constraints
One VPC endpoint supports up to 3,000 concurrent connections.
+Querying a VPC Endpoint
Perform the following operations to query details of a VPC endpoint, including its ID, associated VPC endpoint service name, VPC, and status.
+- 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 displayed page, locate the VPC endpoint by entering a keyword in the search box in the upper right corner:
+- Search by VPC endpoint service name or VPC endpoint ID.
- Select ID or VPC Endpoint Service Name in the filter box.
- Enter a keyword in the search box.
- Click to start the search.
VPC endpoints containing the keyword are displayed in the VPC endpoint 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.
- - Click Search.
VPC endpoints containing the specified tag are displayed in the VPC endpoint list.
-If you set multiple tags, VPC endpoints containing all the specified tags will be displayed.
+ - Search by tag.
- Click
- Search by VPC endpoint service name or VPC endpoint ID.
- In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.After an interface VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name. +
- In the VPC endpoint list, click the ID of the VPC endpoint to view its details.
After an interface 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 4 Summary of the VPC endpoint (for accessing a gateway VPC endpoint service)-
Table 1 Parameters contained in details of a VPC endpoint Tab
+Table 1 Parameters contained in the details of a VPC endpoint Tab
Parameter
+Parameter
Description
+Description
Summary
+Summary
ID
+ID
Specifies the ID of the VPC endpoint.
+Specifies the ID of the VPC endpoint.
VPC
+Summary
Specifies the VPC where the VPC endpoint is deployed.
+VPC
+Specifies the VPC where the VPC endpoint is deployed.
VPC Endpoint Service Name
+Summary
Specifies the name of the VPC endpoint service that the VPC endpoint is used to access.
+VPC Endpoint Service Name
+Specifies the name of the VPC endpoint service that the VPC endpoint is used to access.
Private IP Address
+Summary
Specifies the IP address for accessing the VPC endpoint.
+IPv4 Address
+Specifies the IPv4 address of the VPC endpoint.
Private Domain Name
+Summary
Specifies the private domain name for accessing the VPC endpoint.
+Private Domain Name
+Specifies the private domain name for accessing the VPC endpoint.
Status
+Summary
Specifies the status of the VPC endpoint.
+Status
+Specifies the status of the VPC endpoint.
Type
+Summary
Specifies the type of the VPC endpoint service that the VPC endpoint is used to access.
+Type
+Specifies the type of the VPC endpoint service that the VPC endpoint is used to access.
Assigned
+Summary
Specifies the creation time of the VPC endpoint.
+Created
+Specifies the creation time of the VPC endpoint.
Tags
+Route Tables
Key
+Name
Specifies the tag key of the VPC endpoint.
+Specifies the name of the route table.
Value
+Route Tables
Specifies the tag value of the VPC endpoint.
+VPC
+Specifies the VPC that the route table belongs to.
Operation
+Route Tables
Specifies the operation to be performed on the VPC endpoint tag. You can click Edit or Delete.
+Type
+Specifies the type of the route table, which can be Default and Custom.
+Route Tables
+Associated Subnets
+Specifies the number of subnets associated with the route table.
+Route Tables
+Operation
+Specifies the operation to be performed on the route table. The operation can be Disassociate or Associate.
+Tags
+Key
+Specifies the tag key of the VPC endpoint.
+Tags
+Value
+Specifies the tag value of the VPC endpoint.
+Tags
+Operation
+Specifies the operation to be performed on the VPC endpoint tag. You can click Edit or Delete.
Viewing the record set of the private domain name
- Log in to the management console.
- In the service list, choose Network > Domain Name Service.
The DNS console is displayed.
- In the navigation pane, choose Private Zones.
The Private Zones page is displayed.
-
- In the private zone list, click the name of the target private zone. -
- In the record set list, locate the target A record set and view its information.When Status changes to Normal, the resolution takes effect.-Figure 3 Record set of the private domain name+
- In the private zone list, click the name of the private zone. +
- In the record set list, locate the A record set and view its information.
Accessing a VPC endpoint via its private domain name
diff --git a/docs/vpcep/umn/vpcep_03_0203.html b/docs/vpcep/umn/vpcep_03_0203.html index 7c826f66..a890cd9a 100644 --- a/docs/vpcep/umn/vpcep_03_0203.html +++ b/docs/vpcep/umn/vpcep_03_0203.html @@ -5,8 +5,8 @@ Deleted VPC endpoints cannot be recovered. Exercise caution when performing this operation.
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 Endpoints.
- In the VPC endpoint list, locate the VPC endpoint to be deleted and click Delete in the Operation column.Figure 1 Delete VPC Endpoint-
- In the displayed Delete VPC Endpoint dialog box, 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 Endpoints.
- In the VPC endpoint list, locate the VPC endpoint and click Delete in the Operation column.Figure 1 Delete VPC Endpoint+
- In the Delete VPC Endpoint dialog box, click Yes.
diff --git a/docs/vpcep/umn/vpcep_03_0204.html b/docs/vpcep/umn/vpcep_03_0204.html index 16ebe800..83eb361e 100644 --- a/docs/vpcep/umn/vpcep_03_0204.html +++ b/docs/vpcep/umn/vpcep_03_0204.html @@ -17,14 +17,14 @@Describes how to create a VPC endpoint.
- VPC endpoints are region-level resources. Select a region and project when you create such a VPC endpoint.
- Each tenant can create a maximum of 50 VPC endpoints.
- When you create a VPC endpoint, ensure that the associated VPC endpoint service exists and is in the same region as the VPC endpoint.
- VPC endpoints are region-level resources. Select a region and project when you create such a VPC endpoint.
- Each tenant can create a maximum of 50 VPC endpoints.
- When you create a VPC endpoint, ensure that the associated VPC endpoint service is deployed in the same region as the VPC endpoint.
Describes how to query the summary of a VPC endpoint.
A VPC endpoint supports a maximum of 3,000 concurrent requests.
+One VPC endpoint supports up to 3,000 concurrent connections.
diff --git a/docs/vpcep/umn/vpcep_03_0206.html b/docs/vpcep/umn/vpcep_03_0206.html index 0a0a0e35..a54f9737 100644 --- a/docs/vpcep/umn/vpcep_03_0206.html +++ b/docs/vpcep/umn/vpcep_03_0206.html @@ -3,12 +3,12 @@ Managing Tags of a VPC Endpoint
Scenarios
After a VPC endpoint is created, you can view its tags, or add, edit, or delete a tag.
Tags help identify VPC endpoints. You can add up to 20 tags to each VPC endpoint.
- 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.
+ 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.
Add a Tag
Perform the following operations to tag an existing VPC endpoint:
-- 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 VPC endpoint list, locate the target VPC endpoint and click its ID.
- On the displayed page, select the Tags tab.
- Click Add Tag.
- In the displayed Add Tag dialog box, enter a key and a value.Table 1 describes the tag requirements. +
- 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 VPC endpoint list, locate the VPC endpoint and click its ID.
- On the displayed page, select the Tags tab.
- Click Add Tag.
- In the displayed Add Tag dialog box, enter a key and a value.Table 1 describes the tag requirements.
Table 1 Tag requirements for VPC endpoints Parameter
Requirement
@@ -22,7 +22,7 @@Tag value
- Cannot be left blank.
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Can contain a maximum of 43 characters.
- Can contain only digits, letters, hyphens (-), underscores (_), and at signs (@).
- Click OK.
Edit a Tag
Perform the following operations to edit a tag of a VPC endpoint:
-- 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 VPC endpoint list, locate the target VPC endpoint and click its ID.
- On the displayed page, select the Tags tab.
- In the tag list, locate the target tag and click Edit in the Operation column.
- Enter a new value. -
You can only edit tag values.
+- 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 VPC endpoint list, locate the VPC endpoint and click its ID.
- On the displayed page, select the Tags tab.
- In the tag list, locate the tag and click Edit in the Operation column.
- Enter a new value.
You can only edit tag values.
- Click OK.
Delete a Tag
Perform the following operations to delete a tag of a VPC endpoint:
-- Deleted tags cannot be recovered. Exercise caution when performing this operation.
-- 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 VPC endpoint list, locate the target VPC endpoint and click its ID.
- On the displayed page, select the Tags tab.
- In the tag list, locate the target tag and click Delete in the Operation column.
- Click Yes.
Delete a Tag
You can delete tags added to a VPC endpoint. Deleted tags cannot be restored. Exercise caution when performing this operation.
+- 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 VPC endpoint list, locate the VPC endpoint and click its ID.
- On the displayed page, select the Tags tab.
- In the tag list, locate the tag and click Delete in the Operation column.
- Click Yes.
diff --git a/docs/vpcep/umn/vpcep_03_0500.html b/docs/vpcep/umn/vpcep_03_0500.html index 8180f8f3..c6d5fdce 100644 --- a/docs/vpcep/umn/vpcep_03_0500.html +++ b/docs/vpcep/umn/vpcep_03_0500.html @@ -10,7 +10,7 @@diff --git a/docs/vpcep/umn/vpcep_04_0006.html b/docs/vpcep/umn/vpcep_04_0006.html index 95b454d1..1bf59b52 100644 --- a/docs/vpcep/umn/vpcep_04_0006.html +++ b/docs/vpcep/umn/vpcep_04_0006.html @@ -1,7 +1,7 @@ -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.
+- 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
- Domain name, project name, and project ID, which can be obtained by performing the following operations:
- What Statuses Are Available for a VPC Endpoint Service and VPC Endpoint?
- - Does VPCEP Support Cross-Region Access?
+ - Does VPC Endpoint Support Cross-Region Access?
Does VPCEP Support Cross-Region Access?
-VPC endpoint services cannot be accessed across regions. VPCEP supports only access to cloud services or users' private services in VPCs in the same region.
+Does VPC Endpoint Support Cross-Region Access?
+VPC endpoint services cannot be accessed across regions. VPC Endpoint supports only access to cloud services or users' private services in VPCs in the same region.
diff --git a/docs/vpcep/umn/vpcep_0_0002.html b/docs/vpcep/umn/vpcep_0_0002.html index 2243d9f5..c6bcaea4 100644 --- a/docs/vpcep/umn/vpcep_0_0002.html +++ b/docs/vpcep/umn/vpcep_0_0002.html @@ -2,22 +2,40 @@Change History
-Released On
+Released On
Description
2023-06-29
+2024-07-26
+This release incorporates the following changes:
+Updated the description of the Tag value in Step 1: Create a VPC Endpoint Service, Step 2: Create a VPC Endpoint, Step 1: Create a VPC Endpoint Service, Step 3: Create a VPC Endpoint, Step 1: Create a VPC Endpoint for Connecting to DNS, Step 2: Create a VPC Endpoint for Connecting to OBS, Step 1: Create a VPC Endpoint for Accessing OBS, Creating a VPC Endpoint Service, Managing Tags of a VPC Endpoint Service, Creating a VPC Endpoint, and Managing Tags of a VPC Endpoint.
+2024-07-24
+This release incorporates the following changes:
+- Added interaction with the API Gateway service to Table 1 in VPC Endpoint and Other Services.
- Optimized the description of parameter Create a Private Domain Name and added the Route Table parameter and its description in Step 2: Create a VPC Endpoint, Step 3: Create a VPC Endpoint, Step 1: Create a VPC Endpoint for Connecting to DNS, and Creating a VPC Endpoint.
- Updated Figure 1 and Figure 2 in Step 2: Add a Whitelist Record.
- Updated step 6 in Deleting a VPC Endpoint Service.
- Updated the screenshots and procedure related to search by tag in Viewing a VPC Endpoint Service.
- Added parameters and screenshots related to Route Tables and updated the screenshots and procedure related to search by tag in Querying and Accessing a VPC Endpoint.
2024-07-10
+This release incorporates the following change:
+- Updated Table 2 by adding the API gateway VPC endpoint service in the eu-de region.
- Updated the screenshots related to creating a VPC endpoint in Step 2: Create a VPC Endpoint, Step 3: Create a VPC Endpoint, Step 1: Create a VPC Endpoint for Connecting to DNS, Step 2: Create a VPC Endpoint for Connecting to OBS, Step 1: Create a VPC Endpoint for Accessing OBS, and Creating a VPC Endpoint.
- Added parameter VPC Endpoint Service Name in Table 3.
2023-06-29
This release incorporates the following changes:
-- Updated the step in Add Domain IDs to Be Authorized to the Whitelist of a VPC Endpoint Service.
- Updated Figure 1 and added parameter Subnet in Table 1.
- Updated the step in Add Account IDs to Be Authorized to the Whitelist of a VPC Endpoint Service.
- Updated Figure 1 and added parameter Subnet in Table 1.
2023-06-25
This release incorporates the following changes:
-- Added the interactions between VPCEP and Direct Connect, ECS, and BMS in Table 1.
- Added the description of the VPC endpoint service whose backend resource is a virtual IP address in Table 2.
- Updated the description of the scenario "Communications between cloud resources across VPCs in the same region" in Table 1.
- Updated the description of Subnet in Table 1 and Table 1.
- Updated the key and value rules in Table 2, Table 2, Table 2, Table 2, Table 1, Table 2, Table 4, and Table 1.
- Updated 6.
- Updated 6.
- Updated 6.
- Added the description of the VPC endpoint service whose backend resource is a virtual IP address in Table 1.
- Updated Figure 2.
- Updated the parameter Created and Tag in Table 1.
- Updated Figure 1, Figure 2, and 6.
- Updated Figure 2.
- Added the interactions between VPC Endpoint and Direct Connect, ECS, and BMS in Table 1.
- Added the description of the VPC endpoint service whose backend resource is a virtual IP address in Table 2.
- Updated the description of the scenario "Communications between cloud resources across VPCs in the same region" in Table 1.
- Updated the description of Subnet in Table 1 and Table 1.
- Updated the tag key and tag value rules of VPC endpoints and VPC endpoint services in Step 1: Create a VPC Endpoint for Connecting to DNS, Step 2: Create a VPC Endpoint for Connecting to OBS, Step 1: Create a VPC Endpoint for Accessing OBS, Creating a VPC Endpoint Service, Managing Tags of a VPC Endpoint Service, Creating a VPC Endpoint, and Managing Tags of a VPC Endpoint.
- Optimized 6 in Step 1: Create a VPC Endpoint for Connecting to DNS.
- Optimized 6 in Step 2: Create a VPC Endpoint for Connecting to OBS.
- Optimized 6 in Step 1: Create a VPC Endpoint for Accessing OBS.
- Added the description of the VPC endpoint service whose backend resource is a virtual IP address in Table 1.
- Updated Figure 3 in Procedure.
- Updated the parameter Created and Tag in Table 1.
- Updated Figure 1 and Figure 2 in Creating a VPC Endpoint for Accessing Interface VPC Endpoint Services and Creating a VPC Endpoint for Accessing Gateway VPC Endpoint Services and optimized 6.
- Updated Figure 3 in Querying a VPC Endpoint.
2023-06-13
@@ -35,7 +53,7 @@2020-11-02
This release incorporates the following changes:
+This release incorporates the following change:
Modified the format description of whitelist records in Step 2: Add a Whitelist Record and Managing Whitelist Records of a VPC Endpoint Service.
Permissions
-If you need to assign different permissions to personnel in your enterprise to access your VPCEP resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources.
-With IAM, you can use your account to create IAM users and assign permissions to control their access to specific cloud resources. For example, if you want website maintenance personnel in your enterprise to use VPCEP resources but do not want them to delete other cloud resources or perform any other high-risk operations, you can create IAM users and grant only permissions to use VPCEP resources.
+If you need to assign different permissions to employees in your enterprise to access your VPC Endpoint resources, you can use Identity and Access Management (IAM) to manage fine-grained permissions. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources.
+With IAM, you can use your account to create IAM users and assign permissions to control their access to specific cloud resources. For example, if you want website maintenance personnel in your enterprise to use VPC Endpoint resources but do not want them to delete other cloud resources or perform any other high-risk operations, you can create IAM users and grant only permissions to use VPC Endpoint resources.
If your account does not require individual IAM users for permissions management, you can skip this section.
IAM is a free service. You only pay for the resources in your account.
For more information about IAM, see IAM Service Overview.
-VPCEP Permissions
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
-VPCEP is a project-level service deployed for specific regions. You need to select a project for which the permissions will be granted. If you select All projects, the permissions will be granted for all the projects. When accessing the VPCEP service, the users need to switch to the authorized region.
-Table 1 lists all system-defined roles for VPCEP. -Table 1 System-defined roles for VPCEP Role
+VPC Endpoint Permissions
New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.
+VPC Endpoint is a project-level service deployed for specific regions. You need to select a project for which the permissions will be granted. If you select All projects, the permissions will be granted for all the projects. When accessing VPC Endpoint, the users need to switch to the authorized region.
+Table 1 lists all system-defined roles for VPC Endpoint. +-Table 1 System-defined roles for VPC Endpoint Role
Description
Category
+Type
Dependency
VPCEndpoint Administrator
Full permissions for VPCEP
+Full permissions for VPC Endpoint
System-defined role
This role depends on Server Administrator, VPC Administrator, and DNS Administrator roles in the same project.
+This role depends on DNS Administrator, Server Administrator, and VPC Administrator roles in the same project.
Table 2 lists the common operations supported by system-defined permissions for VPCEP.
+Table 2 lists the common operations supported by system-defined permissions for VPC Endpoint.
Table 2 Common operations supported by system-defined permissions Operation
Helpful Links
- +diff --git a/docs/vpcep/umn/vpcep_qs_0001.html b/docs/vpcep/umn/vpcep_qs_0001.html index 3079cab1..46c69856 100644 --- a/docs/vpcep/umn/vpcep_qs_0001.html +++ b/docs/vpcep/umn/vpcep_qs_0001.html @@ -1,9 +1,9 @@Operation Guide
-This section uses examples to describe how to use VPCEP.
-You can use VPCEP on the VPCEP console. For more information, see What Is VPC Endpoint?
-Application Scenarios
VPCEP can be used in different scenarios. For details, see Table 1.
+This section uses examples to describe how to use VPC Endpoint.
+You can use VPC Endpoint on the VPC Endpoint console. For more information, see What Is VPC Endpoint?
+Application Scenarios
VPC Endpoint can be used in different scenarios. For details, see Table 1.
Table 1 Application scenarios Scenario
Communications between cloud resources across VPCs in the same region
You can create a VPC endpoint service and a VPC endpoint to access cloud services across VPCs. For details, see the following sections:
- +You can create a VPC endpoint service and a VPC endpoint to access cloud services across VPCs. For details, see the following sections:
+Access to cloud resources from an on-premises data center
VPCEP allows you to access cloud resources from your on-premises data center. For details, see the following sections:
+VPC Endpoint allows you to access cloud resources from your on-premises data centers.
Permission Management
+Permissions Management
diff --git a/docs/vpcep/umn/vpcep_ug_0003.html b/docs/vpcep/umn/vpcep_ug_0003.html index ffe15897..941cd04d 100644 --- a/docs/vpcep/umn/vpcep_ug_0003.html +++ b/docs/vpcep/umn/vpcep_ug_0003.html @@ -1,22 +1,23 @@ -Creating a User and Granting Permissions
-Use IAM to implement fine-grained permissions control over your VPCEP resources. With IAM, you can:
-- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing VPCEP resources.
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Entrust an account or a cloud service to perform efficient O&M on your VPCEP resources.
If your account meets your permissions requirements, you can skip this section.
-Figure 1 shows the process flow of granting permissions.
-Prerequisites
Before granting permissions to user groups, learn about permissions (see Permissions) supported by VPCEP and choose policies or roles according to your requirements. To grant permissions for other services, learn about all Permissions supported by IAM.
+Creating a User and Granting VPC Endpoint Permissions
+Use IAM to implement fine-grained permissions control over your VPC Endpoint resources. With IAM, you can:
+- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user has their own security credentials for accessing VPC Endpoint resources.
- Grant only the permissions required for users to perform a specific task.
- Entrust an account or a cloud service to perform efficient O&M on your VPC Endpoint resources.
If your account does not need individual IAM users, skip this section.
+This section describes the process flow for granting permissions (see Figure 1).
+-Prerequisites
You must learn about permissions (see Permissions) supported by VPC Endpoint and choose policies or roles according to your requirements. To grant permissions for other services, learn about all Permissions supported by IAM.
Process Flow
-- Create a user group and assign it permissions.
On the IAM console, create a user group and assign the VPCEndpoint Administrator permissions to the group.
- - Create an IAM user and add it to the created user group.
- Log in as the IAM user and verify permissions.
In the authorized region, perform the following operations:
-- Click Service List> VPC Endpoint. Then click Create VPC Endpoint in the upper right corner. If you can create a VPC endpoint, the VPCEndpoint Administrator policy is in effect.
- Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the VPCEndpoint Administrator policy is in effect.
Process Flow
+- Create a user group and assign it permissions.
On the IAM console, create a user group and attach the VPCEndpoint Administrator policy to the group.
+ - Create an IAM user and add it to the created user group.
Create an IAM user and add it to the user group created in 1.
+ - Log in as the IAM user and verify permissions.
In the authorized region, perform the following operations:
+- On the Service List page, choose VPC Endpoint. Click Create VPC Endpoint in the upper right corner. If you can create a VPC endpoint, the VPCEndpoint Administrator policy has already taken effect.
- Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the VPCEndpoint Administrator policy has already taken effect.
-Parent topic: Permission Management+Parent topic: Permissions Management
- In the VPC endpoint list, click the ID of the VPC endpoint to view its details.
- Search by VPC endpoint service name or VPC endpoint ID.
- Search by name or ID.
- Configure VPC endpoint parameters. +
