Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Edge Gateway Overview

Updated on 2024-11-26 GMT+08:00

What Is an Edge Gateway?

An edge gateway can connect subnets in the same VPC but from both edge and central AZs or from different edge AZs.

NOTE:

Edge gateways are supported in the AF-Johannesburg region.

Edge gateways are free of charge, but if there is a change, you will be notified in advance.

Application Scenarios

Figure 1 Edge gateway networking architecture

Table 1 lists the required two VPCs and 12 subnets in 12 AZs and five regions.

Table 1 VPC and subnet planning

VPC

Subnet

AZ

Region

VPC-EG1

Subnet1

Edge AZ1

Edge region A

Subnet2

Edge AZ2

Subnet3

Edge AZ3

Edge region B

Subnet4

Edge AZ4

Centre-Subnet1

Central AZ1

Central region A

Centre-Subnet2

Central AZ2

VPC-EG2

Subnet5

Edge AZ5

Edge region A

Subnet6

Edge AZ6

Subnet7

Edge AZ7

Edge region C

Subnet8

Edge AZ8

Centre-Subnet3

Central AZ3

Central region B

Centre-Subnet4

Central AZ4

Table 2 lists the required edge gateway and five edge connections in 12 AZs and five regions.

Table 2 Edge gateway and edge connection planning

Edge Gateway

AZ

Region

Edge Connection

Global Connection Bandwidth-HomeZones (CN East)

Edge gateway

  • Edge AZ1
  • Edge AZ2
  • Edge AZ5
  • Edge AZ6

Edge region A

Edge connection A

Global connection bandwidth A

  • Edge AZ3
  • Edge AZ4

Edge region B

Edge connection B

Global connection bandwidth B

  • Edge AZ7
  • Edge AZ8

Edge region C

Edge connection C

Global connection bandwidth C

  • Central AZ1
  • Central AZ2

Central region A

Edge connection A-Central

Global connection bandwidth A-Central

  • Central AZ3
  • Central AZ4

Central region B

Edge connection B-Central

Global connection bandwidth B-Central

The edge gateway is attached to both VPC-EG1 and VPC-EG2 and is used in the following scenarios.
Table 3 Edge gateway application scenarios

Scenario

Required Resource

Description

Reference

In VPC-EG1, connect subnets in edge and central AZs.

  • VPC
  • Subnet in an edge AZ
  • Edge connection in an edge region
  • Global connection bandwidth in an edge region
  • Subnet in a central AZ
  • Edge connection in a central region
  • Global connection bandwidth in a central region

In VPC-EG1, Subnet1 in the edge AZ (AZ1) and Centre-Subnet1 in the central AZ (AZ1) need to communicate with each other.

  • For the subnet in the edge AZ (AZ1), an edge connection (edge connection A) needs to be created in edge region A and has a global connection bandwidth (global connection bandwidth A) bound.
  • For the subnet in the central AZ (AZ1), an edge connection (edge connection A-Central) needs to be created in central region A and has a global connection bandwidth (global connection bandwidth A-Central) bound.
  1. Edge gateways: An edge gateway can have one or more VPCs attached.
  2. Associating VPCs with an Edge Gateway: The number of VPCs that an edge gateway can have vary by gateway edition.
  3. Creating an Edge Connection: An edge connection can be shared in all AZs of the same region.
  4. Binding a Global Connection Bandwidth to an Edge Connection: An edge connection can only have one global connection bandwidth bound.

In VPC-EG1, connect subnets in different edge AZs.

  • VPC
  • Subnet in an edge AZ
  • Edge connection in an edge region
  • Global connection bandwidth in an edge region
  • Edge connection in a central region
  • Global connection bandwidth in a central region

In VPC-EG1, Subnet1 in the edge AZ (AZ1) and Subnet3 in the edge AZ (AZ3) need to communicate with each other.

  • For the subnet in the edge AZ (AZ1), an edge connection (edge connection A) needs to be created in edge region A and has a global connection bandwidth (global connection bandwidth A) bound.
  • For the subnet in the edge AZ (AZ3), an edge connection (edge connection B) needs to be created in edge region B and has a global connection bandwidth (global connection bandwidth B) bound.
  • For both subnets, an edge connection (edge connection A-Central) needs to be created in central region A and has a global connection bandwidth (global connection bandwidth A-Central) bound.
NOTE:

To enable communications between a central region and an edge region or between different edge regions, you need to create an edge connection in the central region.

  1. Edge gateways: An edge gateway can have one or more VPCs attached.
  2. Associating VPCs with an Edge Gateway: The number of VPCs that an edge gateway can have vary by gateway edition.
  3. Creating an Edge Connection: This edge connection is used for communications between the edge regions and a central region.
  4. Binding a Global Connection Bandwidth to an Edge Connection: An edge connection can only have one global connection bandwidth bound.

In VPC-EG2, connect subnets in edge and central AZs.

  • VPC
  • Subnet in an edge AZ
  • Edge connection in an edge region
  • Global connection bandwidth in an edge region
  • Subnet in a central AZ
  • Edge connection in a central region
  • Global connection bandwidth in a central region

In VPC-EG2, Subnet5 in the edge AZ (AZ5) and Centre-Subnet3 in the central AZ (AZ3) need to communicate with each other.

  • For the subnet in the edge AZ (AZ5), an edge connection has been created in edge region A and has a global connection bandwidth bound. You can use this edge connection directly.
  • For the subnet in the central AZ (AZ3), an edge connection (edge connection B-Central) needs to be created in central region B and has a global connection bandwidth (global connection bandwidth B-Central) bound.
NOTE:

Edge connections can be reused because VPC-EG1 and VPC-EG2 are attached to the same edge gateway.

  1. Edge gateways: An edge gateway can have one or more VPCs attached.
  2. Associating VPCs with an Edge Gateway: The number of VPCs that an edge gateway can have vary by gateway edition.
  3. Creating an Edge Connection: VPCs attached to the same edge gateway can use one edge connection. In this example, only one edge connection needs to be created in the central region.
  4. Binding a Global Connection Bandwidth to an Edge Connection: An edge connection can only have one global connection bandwidth bound.

In VPC-EG2, connect subnets in different edge regions.

  • VPC
  • Subnet in an edge AZ
  • Edge connection in an edge region
  • Global connection bandwidth in an edge region
  • Edge connection in a central region
  • Global connection bandwidth in a central region

In VPC-EG2, Subnet5 in the edge AZ (AZ5) and the subnet in the edge AZ (AZ7) need to communicate with each other.

  • For the subnet in the edge AZ (AZ5), an edge connection has been created in edge region A and has a global connection bandwidth bound. You can use this edge connection directly.
  • For the subnet in the edge AZ (AZ7), an edge connection (edge connection C) needs to be created in edge region C and has a global connection bandwidth (global connection bandwidth C) bound.
  • For both subnets, an edge connection (edge connection B-Central) needs to be created in central region B and has a global connection bandwidth (global connection bandwidth B-Central) bound.
  1. Edge gateways: An edge gateway can have one or more VPCs attached.
  2. Associating VPCs with an Edge Gateway: The number of VPCs that an edge gateway can have vary by gateway edition.
  3. Creating an Edge Connection: VPCs attached to the same edge gateway can use one edge connection. In this example, one edge connection is required for the edge AZ (AZ7), and one edge connection needs to be created in the central region.
  4. Binding a Global Connection Bandwidth to an Edge Connection: An edge connection can only have one global connection bandwidth bound.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback