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
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
Help Center/ NAT Gateway/ User Guide (Ankara Region)/ Getting Started/ Using a Public NAT Gateway to Enable Servers to Be Accessed by the Internet

Using a Public NAT Gateway to Enable Servers to Be Accessed by the Internet

Updated on 2025-01-10 GMT+08:00

Scenarios

When one or more servers in a VPC need to provide services accessible from the Internet, you can add DNAT rules for a public NAT gateway, as introduced in this section.

Operation Process

Procedure

Description

Step 1: Buy an EIP

Buy an EIP.

Step 2: Buy a Public NAT Gateway

Buy a public NAT gateway.

Step 3: Add a Default Route Pointing to the Public NAT Gateway

Add a route table.

Step 4: Add a DNAT Rule

Add DNAT rules for the public NAT gateway so that servers in specific CIDR blocks share EIPs to access the Internet.

Step 5: Verify that the DNAT Rule Has Been Added

Check whether the DNAT rule has been added.

Step 6: Verify that Servers in a VPC Can Be Accessed from the Internet Through the NAT Gateway

Verify that servers for which the DNAT rules are applied can be accessed by a client on the Internet.

Step 1: Buy an EIP

  1. On the Assign EIP page, set the EIP name to EIP-A.

    You can configure other EIP parameters as required. For details, see .

Step 2: Buy a Public NAT Gateway

  1. On the Create Public NAT Gateway page, configure required parameters.
    Table 1 Descriptions of public NAT gateway parameters

    Parameter

    Example

    Description

    Region

    CN North-Beijing4

    The region where the public NAT gateway is located.

    Specifications

    Small

    The specifications of the public NAT gateway.

    The value can be Extra-large, Large, Medium, or Small. To view more details about specifications, click Learn more on the page.

    Name

    public-nat-01

    The name of the public NAT gateway. Enter up to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed.

    VPC

    vpc-A

    The VPC that the public NAT gateway belongs to.

    The selected VPC cannot be changed after you create the public NAT gateway.

    NOTE:

    To allow traffic to pass through the public NAT gateway, a route to the public NAT gateway in the VPC is required. When you create a public NAT gateway, a default route 0.0.0.0/0 to the public NAT gateway is automatically added to the default route table of the VPC. If the default route 0.0.0.0/0 already exists in the default route table of the VPC before you create the public NAT gateway, the default route that points to the public NAT gateway will fail to be added automatically. In this case, perform the following operations after the public NAT gateway is successfully created: Manually add a different route that points to the gateway or create a default route 0.0.0.0/0 pointing to the gateway in the new routing table.

    Subnet

    Subnet-A01

    The subnet that the public NAT gateway belongs to.

    The subnet must have at least one available IP address.

    The selected subnet cannot be changed after you create the public NAT gateway.

    The NAT gateway will be deployed in the selected subnet. The NAT gateway works for the entire VPC where it is deployed. To enable communications over the Internet, add SNAT or DNAT rules.

    Advanced Settings (Optional)

    -

    Click the drop-down arrow to configure advanced parameters of the public NAT gateway.

    SNAT Connection TCP Timeout (s)

    900

    The timeout period of a TCP connection established using the SNAT rule. If no data is exchanged within this period, the TCP connection will be closed.

    Value range: 40 to 7200

    SNAT Connection UDP Timeout (s)

    300

    The timeout period of a UDP connection established using the SNAT rule. If no data is exchanged within this period, the UDP connection will be closed.

    Value range: 40 to 7200

    SNAT Connection ICMP Timeout (s)

    10

    The timeout period of an ICMP connection established using the SNAT rule. If no data is exchanged within this period, the ICMP connection will be closed.

    Value range: 10 to 7200

    TCP TIME_WAIT (s)

    5

    How long the side that actively closed the TCP connection is in the TIME_WAIT state.

    Value range: 0 to 1800

    Description

    Not required

    Supplementary information about the public NAT gateway. Enter up to 255 characters. Angle brackets (<>) are not allowed.

    Tag

    Not required

    The identifier of the public NAT gateway. A tag is a key-value pair. You can add up to 20 tags to each public NAT gateway.

  2. Click Create Now. On the page displayed, confirm the public NAT gateway specifications.
  3. If you do not need to modify the information, click Submit.

    On the Public NAT Gateways page, you can view the created public NAT gateway in the list.

Step 3: Add a Default Route Pointing to the Public NAT Gateway

  1. On the Route Tables page, click Create Route Table in the upper right corner.

    VPC: Select the VPC that the public NAT gateway belongs to.

  2. After the custom route table is created, click its name. The Summary page is displayed.
  3. Click Add Route and configure parameters as follows:

    Destination: Set it to 0.0.0.0/0.

    Next Hop Type: Select NAT gateway.

    Next Hop: Select the created NAT gateway.

    Figure 1 Add Route
  4. Click OK.

Step 4: Add a DNAT Rule

  1. On the displayed page, click the name of the public NAT gateway on which you need to add a DNAT rule.
  2. On the public NAT gateway details page, click the DNAT Rules tab.
  3. Click Add DNAT Rule.
  4. Configure required parameters. For details, see Table 2.
    Table 2 Descriptions of DNAT rule parameters

    Parameter

    Example

    Description

    Scenario

    VPC

    Select VPC if your servers in a VPC will use the DNAT rule to provide services accessible from the Internet.

    Different servers in a VPC can share the same EIP to provide services accessible from the Internet.

    Port Type

    Specific port

    The port type.

    • All ports: All requests received by the gateway through all ports over any protocol will be forwarded to the private IP address of your server.
    • Specific port: Only requests received from a specified port over a specified protocol will be forwarded to the specified port on the server.

    Protocol

    TCP

    The protocol can be TCP or UDP. This parameter is available if you select Specific port for Port Type. If you select All ports, this parameter is All by default.

    Public IP Address Type

    EIP

    The EIP of the public NAT gateway.

    Outside Port

    80-100

    The port of the EIP used by the NAT gateway. The port number ranges from 1 to 65535.

    You can enter a specific port number or a port range, for example, 80 or 80-100.

    Instance Type

    Server

    The instance type for which the DNAT rules are applied.

    NIC

    -

    The network interface of the server.

    Inside Port

    80-100

    The port of the server that provides services accessible from the Internet through the DNAT rule. This parameter is available if you select Specific port for Port Type. The port number ranges from 1 to 65535.

    You can enter a specific port number or a port range, for example, 80 or 80-100.

    Description

    Not required

    Supplementary information about the DNAT rule. Enter up to 255 characters. Angle brackets (<>) are not allowed.

  5. Click OK.
NOTICE:

After you add a DNAT rule, add rules to the security group associated with the servers to allow inbound or outbound traffic. Otherwise, the DNAT rule does not take effect. For details, see .

Step 5: Verify that the DNAT Rule Has Been Added

  1. In the DNAT Rules tab, view details of the DNAT rule and check whether the DNAT rule has been created.

    If Status of the SNAT rule is Running, the SNAT rule has been created.

Step 6: Verify that Servers in a VPC Can Be Accessed from the Internet Through the NAT Gateway

  1. Log in to ECS 02 with an EIP bound.
  2. On ECS 02, ping the EIP (120.46.131.153) to check whether ECS 01 on the private network can be accessed by ECS 02 on the public network through the NAT gateway.
    Figure 2 Verification result

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