No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specied in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every eort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
VPC Endpoint
User Guide (ME-Abu Dhabi Region)Contents
Contents
1 Service Overview..................................................................................................................... 1
1.1 What Is VPC Endpoint?..........................................................................................................................................................1
1.4.1 User Permissions.................................................................................................................................................................. 3
1.4.2 Region and AZ...................................................................................................................................................................... 3
3.1.6 Viewing Port Mappings................................................................................................................................................... 30
3.2.1 Creating a VPC Endpoint.................................................................................................................................................31
3.2.2 Querying and Accessing a VPC Endpoint.................................................................................................................. 33
3.2.3 Deleting a VPC Endpoint.................................................................................................................................................34
4.1 What Is a Quota?.................................................................................................................................................................. 36
4.2 How Can I Check Network Congurations of the ECS Hosting the VPC Endpoint Service?...................... 36
4.3 What Are Statuses of VPC Endpoint Services and VPC Endpoints?.....................................................................36
A Change History...................................................................................................................... 38
VPC Endpoint
User Guide (ME-Abu Dhabi Region)1 Service Overview
1 Service Overview
1.1 What Is VPC Endpoint?
The VPC Endpoint (VPCEP) service provides secure and private channels to connect
your VPC to VPC endpoint services (cloud services on the current platform or your
private services) without having to use EIPs.
VPCEP provides two types of resources: VPC endpoint services and VPC endpoints.
For details, see Application Scenarios.
VPC Endpoint Services
VPC endpoint services are cloud services or users' private services that are
congured in VPCEP. There are two types of VPC endpoint services: gateway and
interface.
●Gateway VPC endpoint services are cloud services that are
operations people and supported by VPCEP.
●Interface VPC endpoint services include cloud services
operations people and private services congured by users.
● The cloud service platform congures some cloud services as VPC endpoint services by
default. Users do not have the permission to congure such services but can select them
(which vary by region) when creating a VPC endpoint.
● Users can congure services or resources (such as elastic load balancers and ECSs) in
their own VPC as VPC endpoint services.
congured by
congured by
VPC Endpoints
VPC endpoints are channels for connecting VPCs to VPC endpoint services. You can
create an application in your VPC and
endpoint can be created in another VPC in the same region and used as a channel
to access the endpoint service. There are two types of VPC endpoints: interface
and gateway.
VPC Endpoint
User Guide (ME-Abu Dhabi Region)1 Service Overview
●An interface VPC endpoint is an elastic network interface with a private IP
address that serves as an entry point for trac destined to a VPC endpoint
service.
●A gateway VPC endpoint is a gateway that is a target for a specied route to
direct trac to a VPC endpoint service.
1.2 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 are easy to use
and can take
●Easy to Use: You can use VPC endpoints to access resources across VPCs
without having to use EIPs.
●High Security: VPC endpoints enable you to access VPC endpoint services
without exposing server information, helping you minimize risks.
eect a few seconds after being created.
1.3 Application Scenarios
VPCEP provides:
●High-speed cloud migration
Connect your local data center to cloud services using a Virtual Private
Network (VPN) connection or a high-speed Direct Connect connection over a
private network to improve access
Figure 1-1
Figure 1-1 High-speed cloud migration
briey illustrates this application scenario.
eciency and security with low costs.
●Cross-VPC connection
Dierent VPCs cannot communicate with each other. To solve this problem,
you can create an application in your VPC and congure it as a VPC endpoint
VPC Endpoint
User Guide (ME-Abu Dhabi Region)1 Service Overview
service. A VPC endpoint can be created in another VPC of the same region
and used as a channel to access the VPC endpoint service.
Figure 1-2 briey illustrates this application scenario.
Figure 1-2 Cross-VPC connection
1.4 Product Concepts
1.4.1 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.
1.4.2 Region and AZ
Concept
A region and availability zone (AZ) identify the location of a data center. You can
create resources in a
VPC Endpoint
User Guide (ME-Abu Dhabi Region)1 Service Overview
●A region is a physical data center, which is completely isolated to improve
fault tolerance and stability. The region that is selected during resource
creation cannot be changed after the resource is created.
●An AZ is a physical location where resources use independent power supplies
and networks. A region contains one or more AZs that are physically isolated
but interconnected through internal networks. Because AZs are isolated from
each other, any fault that occurs in an AZ will not
Figure 1-3 shows the relationship between regions and AZs.
Figure 1-3 Regions and AZs
aect other AZs.
Selecting a Region
Select a region closest to your target users for low network latency and quick
access.
Selecting an AZ
When deploying resources, consider your applications' requirements on disaster
recovery (DR) and network latency.
●For high DR capability, deploy resources in
region.
●For low 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.
VPC Endpoint
User Guide (ME-Abu Dhabi Region)2 Getting Started
2 Getting Started
2.1 Conguring a VPC Endpoint for Communication
Across VPCs
2.1.1 Overview
VPCEP supports cross-VPC communication. With VPCEP, two VPCs created by the
same domain or
a private IP address to access resources across the VPCs despite of network
isolation between them.
Figure 2-1 shows how an ECS in VPC1 accesses a VPC endpoint service in VPC2
using a VPC endpoint.
Figure 2-1
dierent domains can communicate with each other. You can use
Conguring a VPC endpoint for communication Across VPCs
The above is an example on how to congure VPC endpoints for communication across
VPCs in the same region.
VPC Endpoint
User Guide (ME-Abu Dhabi Region)2 Getting Started
Table 2-1 Required parameters
ParameterDescription
RegionSpecies the region where the VPC endpoint service is
located.
Resources in dierent regions cannot communicate with
each other over internal networks. Select the nearest region
for lower network latency and faster access to resources.
VPCSpecies the VPC where the VPC endpoint service is located.
Service TypeSpecies the type of the VPC endpoint service. The value
can only be Interface.
Connection
Approval
Species whether the connection between a VPC endpoint
and a VPC endpoint service requires approval from the
owner of the VPC endpoint service.
You can determine whether to enable or disable the
connection approval.
If connection approval is enabled, any VPC endpoint for
connecting to the VPC endpoint service needs to be
approved. For details, see step 5.
Port MappingSpecies the protocol and ports used for communication
between the VPC endpoint service and VPC endpoint. The
protocol is TCP.
● Service Port: A service port is provided by the backend
service bound to the endpoint service.
● Terminal Port: A terminal port is provided by the VPC
endpoint, allowing you to access the VPC endpoint
service.
The service and terminal port numbers range from 1 to
65535. A maximum of 50 port mappings can be added at a
time.
NOTE
Accessing a VPC endpoint service from a VPC endpoint is to access
the service port from the associated terminal port.
VPC Endpoint
User Guide (ME-Abu Dhabi Region)2 Getting Started
ParameterDescription
Backend
Resource
Type
Load
Balancer
Species the type of the backend resource that provides
services to be accessed.
This parameter can be set to Elastic load balancer or ECS.
● Elastic load balancer: Select this value if the backend
resource is an elastic load balancer. Backend resources of
this type suit services that receive high access
trac and
demand high reliability and disaster recovery (DR)
performance.
● ECS: Select this value if the backend resource is an
Elastic Cloud Server (ECS). Backend resources of this
type serve as servers.
Example: Elastic load balancer
NOTE
Security groups use the whitelist mechanism. For the security group
of the backend resource
you need to add an inbound rule for the whitelist, where the source
IP address is 198.19.128.0/20. For details, see Adding a Security
Group Rule in the
congured for the VPC endpoint service,
Virtual Private Cloud User Guide
.
When Backend Resource Type is set to Elastic loadbalancer, select the load balancer that provides services
from the drop-down list. Only elastic load balancers are
supported.
NOTE
If an elastic load balancer is used as the backend resource, the
source IP address received by the VPC endpoint service is not the
real address of the client.
TagThis parameter is optional.
Species the VPC endpoint service tag, which consists of a
key and a value. You can add a maximum of 10 tags to
each VPC endpoint service.
Tag keys and values must meet requirements listed in Table
2-2.
Table 2-2 Tag requirements for VPC endpoint services
Parameter
Requirement
Tag key● Cannot be left blank.
● Must be unique for each resource.
● Can contain a maximum of 36 characters.
● Cannot start or end with a space or contain special
characters =*<>\,|/