2018-01-15
diff --git a/docs/natgw/umn/nat_nat_0000.html b/docs/natgw/umn/nat_nat_0000.html
index d42bf0d3..396fcfb5 100644
--- a/docs/natgw/umn/nat_nat_0000.html
+++ b/docs/natgw/umn/nat_nat_0000.html
@@ -4,13 +4,15 @@
diff --git a/docs/natgw/umn/nat_nat_0001.html b/docs/natgw/umn/nat_nat_0001.html
index abfb0ce3..a6c668c5 100644
--- a/docs/natgw/umn/nat_nat_0001.html
+++ b/docs/natgw/umn/nat_nat_0001.html
@@ -1,6 +1,6 @@
-Viewing a NAT Gateway
+Viewing a Public NAT Gateway
ScenariosAfter a NAT gateway is created, you can view details about the NAT gateway.
PrerequisitesA NAT gateway has been created.
diff --git a/docs/natgw/umn/nat_nat_0002.html b/docs/natgw/umn/nat_nat_0002.html
index 7a259691..0f50de0f 100644
--- a/docs/natgw/umn/nat_nat_0002.html
+++ b/docs/natgw/umn/nat_nat_0002.html
@@ -1,6 +1,6 @@
- Deleting a NAT Gateway
+ Deleting a Public NAT Gateway
ScenariosYou can delete NAT gateways to release resources, saving costs.
PrerequisitesAll SNAT rules created on the NAT gateway have been deleted.
diff --git a/docs/natgw/umn/nat_pro_0000.html b/docs/natgw/umn/nat_pro_0000.html
index 3c4fbabf..eb17fb8e 100644
--- a/docs/natgw/umn/nat_pro_0000.html
+++ b/docs/natgw/umn/nat_pro_0000.html
@@ -10,10 +10,12 @@
Application Scenarios
- NAT Gateway Types
+NAT Gateway Specifications
Notes and Constraints
+ Using NAT Gateway with Other Services
+
Region and AZ
Basic Concepts
diff --git a/docs/natgw/umn/nat_pro_0001.html b/docs/natgw/umn/nat_pro_0001.html
index 6501fb94..02069431 100644
--- a/docs/natgw/umn/nat_pro_0001.html
+++ b/docs/natgw/umn/nat_pro_0001.html
@@ -2,8 +2,8 @@
Product Advantages
The NAT Gateway service has the following highlights:
- - Flexibility
A NAT gateway can be deployed flexibly across subnets and AZs. Any fault in a single AZ does not affect the service continuity of a NAT gateway. The type and EIP of a NAT gateway can be adjusted at any time.
- - Easy of use
Multiple types of NAT gateways are available. You can use them after simple configuration. NAT Gateway supports easy operation and maintenance (O&M) and quick provisioning. They can run stably and reliably.
+- Flexibility
A NAT gateway is deployed across subnets and across two AZs. Any fault in a single AZ does not affect the service continuity of a NAT gateway. The specifications and EIP of a NAT gateway can be adjusted at any time.
+ - Easy of use
Multiple NAT gateway specifications are available. You can use them after simple configuration. NAT Gateway supports easy operation and maintenance (O&M) and quick provisioning. They can run stably and reliably.
- Cost-effectiveness
Multiple servers can share an EIP. When you send data through a private IP address or provide services accessible from the Internet using a NAT gateway, the NAT gateway translates the private IP address to a public IP address. The NAT Gateway service helps you save money on EIPs and bandwidth.
Application Scenarios
-Using SNAT to Access the InternetIf your servers in a VPC require Internet access, you can use SNAT to let the servers share one or more EIPs to access the Internet without exposing their IP addresses. In a VPC, each subnet corresponds to an SNAT rule, and each SNAT rule is configured with an EIP. NAT Gateway provides different types of NAT gateways that support different numbers of connections. You can create multiple SNAT rules to meet your service requirements.
+ Using SNAT to Enable Servers to Access the InternetIf your servers in a VPC require Internet access, you can use SNAT to let the servers share one or more EIPs to access the Internet without exposing their IP addresses. In a VPC, each subnet corresponds to an SNAT rule, and each SNAT rule is configured with an EIP. NAT Gateway provides different specifications to support different numbers of connections. You can create multiple SNAT rules to meet your service requirements.
Figure 1 shows how servers in a VPC access the Internet using SNAT.
- Figure 1 Using SNAT to access the Internet
+ Figure 1 Using SNAT to enable servers to access the Internet
Using DNAT to Allow Servers to Provide Services Accessible from the InternetTo allow your servers in a VPC to provide services accessible from the Internet, you can use DNAT.
You can associate an EIP with a DNAT rule. As requests with a specific protocol and port access the EIP, NAT Gateway only forwards requests to the port of the target server through the mapping between the ports. NAT Gateway can also forward requests on the EIP to your servers based on IP address mapping. NAT Gateway allows multiple servers to share an EIP, saving costs on bandwidth.
A DNAT rule is configured for one server. If there are multiple servers, you can create several DNAT rules to make the servers share one or more EIPs.
- Figure 2 shows how servers in a VPC use DNAT to provide services accessible from the Internet. The servers shown in the following figure can be an ECS or BMS.
+ Figure 2 shows how servers in a VPC use DNAT to provide services accessible from the Internet. Servers in the following figure can be an ECS or a BMS.
Figure 2 Using DNAT to allow servers to provide services accessible from the Internet
Using SNAT or DNAT to Communicate with the Internet at a High SpeedIf a large number of servers in a private cloud or those connect to a VPC through Direct Connect or VPN need secure, high-speed Internet access or need to provide services accessible from the Internet, SNAT and DNAT provide this access. Typical scenarios include Internet, games, e-commerce, and finance across clouds.
diff --git a/docs/natgw/umn/nat_pro_0003.html b/docs/natgw/umn/nat_pro_0003.html
new file mode 100644
index 00000000..43df2cb2
--- /dev/null
+++ b/docs/natgw/umn/nat_pro_0003.html
@@ -0,0 +1,45 @@
+
+
+ Using NAT Gateway with Other Services
+
+
+
diff --git a/docs/natgw/umn/nat_pro_0004.html b/docs/natgw/umn/nat_pro_0004.html
index 2e667e1d..116fe824 100644
--- a/docs/natgw/umn/nat_pro_0004.html
+++ b/docs/natgw/umn/nat_pro_0004.html
@@ -1,13 +1,14 @@
Basic Concepts
- EIPAn EIP can be directly accessed over the Internet. A private IP address is an IP address on a local area network (LAN) and cannot be routed through the Internet.
- An EIP is a static, public IP address. You can bind an EIP to an ECS in your subnet to enable the ECS in your VPC to communicate with the Internet through a fixed public IP address.
- Each EIP can be used by only one ECS at a time.
+ EIPEIP is a static, public IP address.
+ An EIP can be directly accessed over the Internet. A private IP address is an IP address on a local area network (LAN) and cannot be routed through the Internet.
+ You can bind an EIP to an ECS in your subnet so that the ECS will be able to communicate with the Internet through a fixed public IP address.
+ Each EIP can be used by only one ECS at a time. If you want multiple ECSs in the same VPC to share an EIP, you have to use a NAT gateway. For more information, see the NAT Gateway User Guide.
- SNAT ConnectionsAn SNAT connection consists of the source IP address, source port, destination IP address, destination port, and transmission-layer protocol. The source IP address refers to the EIP, and the source port refers to the EIP port. They will be used to access the destination IP address and port of the Internet. These five elements identify a connection as a unique session.
+ SNAT ConnectionsAn SNAT connection consists of the source IP address, source port, destination IP address, destination port, and a transport-layer protocol. The source IP address is the EIP, and the source port is the EIP port. An SNAT connection uniquely identifies a session.
- DNAT ConnectionsA DNAT connection enables servers in a VPC to share an EIP to provide services accessible from the Internet through IP address or port mapping.
+ DNAT ConnectionsA DNAT connection enables servers in a VPC to share an EIP to provide services accessible from the Internet.
diff --git a/docs/natgw/umn/nat_qs_0001.html b/docs/natgw/umn/nat_qs_0001.html
index 1c75fe70..016d2e9c 100644
--- a/docs/natgw/umn/nat_qs_0001.html
+++ b/docs/natgw/umn/nat_qs_0001.html
@@ -8,7 +8,7 @@
Step 1: Assign an EIP
- Step 2: Create a NAT Gateway
+Step 2: Create a Public NAT Gateway
Step 3: Add an SNAT Rule
diff --git a/docs/natgw/umn/nat_qs_0002.html b/docs/natgw/umn/nat_qs_0002.html
index ac099fb4..48048e2f 100644
--- a/docs/natgw/umn/nat_qs_0002.html
+++ b/docs/natgw/umn/nat_qs_0002.html
@@ -1,9 +1,9 @@
- Step 1: Assign an EIP
- ScenariosAssign an EIP and enable your servers in a VPC to access the Internet through a NAT gateway by sharing the EIP.
+ Step 1: Assign an EIP
+ ScenariosAssign an EIP and enable your servers in a VPC to access the Internet through a NAT gateway by sharing the EIP.
- ProcedureFor details, see the Elastic IP User Guide. After you assign an EIP, you do not need to bind it to a server here.
+ ProcedureFor details, see Assigning an EIP. After obtaining the EIP, you do not need to bind it to a server.
diff --git a/docs/natgw/umn/nat_qs_0003.html b/docs/natgw/umn/nat_qs_0003.html
index 02c98089..8bfdd6a5 100644
--- a/docs/natgw/umn/nat_qs_0003.html
+++ b/docs/natgw/umn/nat_qs_0003.html
@@ -1,31 +1,34 @@
- Step 2: Create a NAT Gateway
- ScenariosThis section guides you on how to create a NAT gateway to enable your servers to access the Internet or to provide services available from the Internet.
+ Step 2: Create a Public NAT Gateway
+ ScenariosThis section guides you on how to create a public NAT gateway to enable your servers to access the Internet or to provide services available from the Internet.
- Prerequisites- When creating a NAT gateway, you must specify its VPC, subnet, and type.
- Ensure that the VPC does not have the default route.
+ Prerequisites- When creating a public NAT gateway, you must specify its VPC and subnet.
- To allow traffic to pass through the public NAT gateway, a route to the public NAT gateway in the VPC is required. When you buy 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 buy 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.
- Procedure- Log in to the management console.
- Click
 in the upper left corner and select the desired region and project. - Under Network, choose NAT Gateway.
- On the displayed page, click Create NAT Gateway.
- Configure the parameters as prompted. For details, see Table 1.
-
Table 1 Parameter descriptionsParameter
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click Create Public NAT Gateway.
Figure 1 Create NAT Gateway
+ - Configure the parameters as prompted. For details, see Table 1.
+
Table 1 Parameter descriptions of a public NAT gatewayParameter
|
Description
|
|---|
-Region
+ | Region
|
The region where the NAT gateway is located.
|
Name
|
-The name of the NAT gateway. The name can include up to 64 characters and can include digits, letters, underscores (_), and hyphens (-).
+ | The name of the NAT gateway. The name can contain a maximum of 64 characters and only digits, letters, underscores (_), and hyphens (-) are allowed.
|
VPC
|
The VPC that the NAT gateway belongs to. Select a VPC which is not used by any other NAT gateways and has no default route.
You can change the VPC only when you are creating the NAT gateway. After the NAT gateway is created, you cannot modify the VPC.
+ 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 buy 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 buy 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
@@ -35,10 +38,10 @@
You can change the subnet only when you are creating the NAT gateway. After the NAT gateway is created, you cannot change the subnet.
|
-Type
+ | Specifications
|
-The type of the NAT gateway.
-The value can be Small, Medium, Large, and Extra-large. You can click Learn more on the page to view details about each type.
+ | The specifications of the NAT gateway.
+The option can be Small, Medium, Large, and Extra-large. You can click Learn more on the page to view details about each specifications.
|
Description
@@ -64,14 +67,12 @@
| Key
|
-- Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
Value
|
-- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Can contain a maximum of 43 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
@@ -81,7 +82,7 @@
- In the NAT gateway list, view the NAT gateway status. For details about the NAT gateway status, see Table 3.
Table 3 NAT gateway statusStatus
|
-Description
+ | Description
|
|---|
@@ -118,8 +119,16 @@
After the public NAT gateway is created, check whether a default route (0.0.0.0/0) that points to the public NAT gateway exists in the default route table of the VPC where the public NAT gateway is. If no, add a route pointing to the public NAT gateway to the default route table, alternatively, create a custom route table and add the default route 0.0.0.0/0 pointing to the public NAT gateway to the table. The following describes how to add a route to a custom route table.
+Adding a Default Route Pointing to the Public NAT Gateway- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select Virtual Private Cloud.
- In the navigation pane on the left, choose Route Tables.
- On the Route Tables page, click Create Route Table in the upper right corner.
VPC: Select the VPC to which the public NAT gateway belongs.
+ - After the custom route table is created, click its name.
The Summary page is displayed.
+ - 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.
+ - Click OK.
+
diff --git a/docs/natgw/umn/nat_qs_0004.html b/docs/natgw/umn/nat_qs_0004.html
index 59889c70..f5b2be69 100644
--- a/docs/natgw/umn/nat_qs_0004.html
+++ b/docs/natgw/umn/nat_qs_0004.html
@@ -4,9 +4,9 @@
ScenariosAfter a NAT gateway is created, add SNAT rules. With an SNAT rule, your servers in a specified subnet can access the Internet by sharing the same EIP.
Each SNAT rule is configured for one subnet or CIDR block. If there are multiple subnets or CIDR blocks in a VPC, you can create several SNAT rules to allow multiple servers to share EIPs.
- PrerequisitesA NAT gateway has been created.
+ PrerequisitesA NAT gateway has been created.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, choose NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the SNAT rule.
- On the SNAT Rules tab, click Add SNAT Rule.
Figure 1 Add SNAT Rule
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the SNAT rule.
- On the SNAT Rules tab, click Add SNAT Rule.
Figure 1 Add SNAT Rule
- Configure the parameters as prompted. Table 1 describes the parameters.
Table 1 Parameter descriptionsParameter
|
@@ -20,32 +20,33 @@
N/A
|
-Select VPC if your servers in a VPC will use the SNAT rule to access the Internet.
-Different servers in a VPC can share the same EIP to access the Internet.
+ | The scenarios where the SNAT rule is used.
+Select VPC if your servers in a VPC need to access the Internet.
+Select Direct Connect if the servers that are connected to a VPC through Direct Connect in your data center need to access the Internet.
|
|---|
-Type
+ | CIDR Block
|
-This parameter is available only when you select VPC for Scenario.
+ | - Configure this parameter when you select VPC for Scenario and Custom for CIDR Block.
- This parameter is available only when you select VPC for Scenario and Custom for CIDR Block.
- Configure this parameter when you select VPC for Scenario.
+
|
-You can set it to Subnet or Custom based on service requirements.
-Select Subnet if all servers in a VPC subnet need to access the Internet through the SNAT rule.
-Select Custom if only specific servers in a VPC subnet need to access the Internet through the SNAT rule.
+ | - In a VPC scenario with CIDR Block as Custom, specify an IPv4 CIDR block, which must be a subset of the VPC subnets.
- In a VPC scenario with CIDR Block as Existing, specify a VPC subnet in which servers can access the Internet through the SNAT rule.
- In a Direct Connect scenario, specify a CIDR block of your data center to enable your on-premises servers to access the Internet through the SNAT rule.
|
-Subnet
- |
-This parameter is available only when you select VPC for Scenario, and Subnet for Type.
- |
-The subnet in which servers can access the Internet through the SNAT rule.
- |
-
-EIP
+ | EIP
|
N/A
|
The EIP used for accessing the Internet.
You can select an EIP that either is not bound to any resource, has been bound to a DNAT rule with Port Type set to Specific port of the current NAT gateway, or has been bound to an SNAT rule of the current NAT gateway.
+You can select multiple EIPs at once. Up to 20 EIPs can be selected for each SNAT rule. If you have selected multiple EIPs for an SNAT rule, one EIP will be chosen randomly.
+ |
+
+Description
+ |
+N/A
+ |
+Supplementary information about the SNAT rule. The description can contain up to 255 characters.
|
diff --git a/docs/natgw/umn/nat_qs_0005.html b/docs/natgw/umn/nat_qs_0005.html
index a1494127..144745bd 100644
--- a/docs/natgw/umn/nat_qs_0005.html
+++ b/docs/natgw/umn/nat_qs_0005.html
@@ -1,11 +1,13 @@
Step 4: Verify the Result
-ScenariosAfter you add an SNAT rule to a NAT gateway, you can verify that the SNAT rule has been added successfully.
+ Scenarios
+ After adding an SNAT rule, you can perform the following steps to verify the connection:
+ - Verify that the SNAT rule has been added for the public NAT gateway.
- Verify that servers that have no EIPs bound can access the Internet through the NAT gateway.
PrerequisitesAn SNAT rule has been added.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, click NAT Gateway.
- On the displayed page, click the name of the target NAT gateway.
- In the SNAT rule list, you can view details about the SNAT rule. If Status is Running, the SNAT rule has been added successfully.
+ Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click the name of the target NAT gateway.
- In the SNAT rule list, you can view details about the SNAT rule. If Status is Running, the SNAT rule has been added successfully.
diff --git a/docs/natgw/umn/nat_qs_0006.html b/docs/natgw/umn/nat_qs_0006.html
index 424673f7..4cb368b6 100644
--- a/docs/natgw/umn/nat_qs_0006.html
+++ b/docs/natgw/umn/nat_qs_0006.html
@@ -8,7 +8,7 @@
- Step 1: Assign an EIP
- - Step 2: Create a NAT Gateway
+ - Step 2: Create a Public NAT Gateway
- Step 3: Add a DNAT Rule
diff --git a/docs/natgw/umn/nat_qs_0007.html b/docs/natgw/umn/nat_qs_0007.html
index e56c3ebe..ce05b2ad 100644
--- a/docs/natgw/umn/nat_qs_0007.html
+++ b/docs/natgw/umn/nat_qs_0007.html
@@ -1,7 +1,7 @@
- Overview
- When one or more servers (ECSs and BMSs) in a VPC are required to provide services accessible from the Internet, you can add DNAT rules. Figure 1 illustrates the process.
+ Overview
+ When one or more servers (ECSs and BMSs) in a VPC are required to provide services accessible from the Internet, you can add DNAT rules. Figure 1 illustrates the process.
Figure 1 Flowchart
diff --git a/docs/natgw/umn/nat_qs_0008.html b/docs/natgw/umn/nat_qs_0008.html
index b37e43bb..18f43e98 100644
--- a/docs/natgw/umn/nat_qs_0008.html
+++ b/docs/natgw/umn/nat_qs_0008.html
@@ -3,7 +3,7 @@
Step 1: Assign an EIP
ScenariosAssign an EIP and enable servers in a VPC to provide services accessible from the Internet using a NAT gateway by sharing the EIP.
- ProcedureFor details, see the Elastic IP User Guide. After you assign an EIP, you do not need to bind it to a server here.
+ ProcedureFor details, see Assigning an EIP. After obtaining the EIP, you do not need to bind it to a server.
diff --git a/docs/natgw/umn/nat_qs_0009.html b/docs/natgw/umn/nat_qs_0009.html
index 971ae2a5..cd2d6b40 100644
--- a/docs/natgw/umn/nat_qs_0009.html
+++ b/docs/natgw/umn/nat_qs_0009.html
@@ -1,31 +1,34 @@
- Step 2: Create a NAT Gateway
- ScenariosThis section guides you on how to create a NAT gateway to enable your servers to access the Internet or to provide services available from the Internet.
+ Step 2: Create a Public NAT Gateway
+ ScenariosThis section guides you on how to create a public NAT gateway to enable your servers to access the Internet or to provide services available from the Internet.
- Prerequisites- When creating a NAT gateway, you must specify its VPC, subnet, and type.
- Ensure that the VPC does not have the default route.
+ Prerequisites- When creating a public NAT gateway, you must specify its VPC and subnet.
- To allow traffic to pass through the public NAT gateway, a route to the public NAT gateway in the VPC is required. When you buy 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 buy 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.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, choose NAT Gateway.
- On the displayed page, click Create NAT Gateway.
- Configure the parameters as prompted. For details, see Table 1.
-
Table 1 Parameter descriptionsParameter
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click Create Public NAT Gateway.
Figure 1 Create NAT Gateway
+ - Configure the parameters as prompted. For details, see Table 1.
+
Table 1 Parameter descriptions of a public NAT gatewayParameter
|
Description
|
|---|
-Region
+ | Region
|
The region where the NAT gateway is located.
|
Name
|
-The name of the NAT gateway. The name can include up to 64 characters and can include digits, letters, underscores (_), and hyphens (-).
+ | The name of the NAT gateway. The name can contain a maximum of 64 characters and only digits, letters, underscores (_), and hyphens (-) are allowed.
|
VPC
|
The VPC that the NAT gateway belongs to. Select a VPC which is not used by any other NAT gateways and has no default route.
You can change the VPC only when you are creating the NAT gateway. After the NAT gateway is created, you cannot modify the VPC.
+ 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 buy 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 buy 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
@@ -35,10 +38,10 @@
You can change the subnet only when you are creating the NAT gateway. After the NAT gateway is created, you cannot change the subnet.
|
-Type
+ | Specifications
|
-The type of the NAT gateway.
-The value can be Small, Medium, Large, and Extra-large. You can click Learn more on the page to view details about each type.
+ | The specifications of the NAT gateway.
+The option can be Small, Medium, Large, and Extra-large. You can click Learn more on the page to view details about each specifications.
|
Description
@@ -64,14 +67,12 @@
| Key
|
-- Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
Value
|
-- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Can contain a maximum of 43 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
@@ -81,7 +82,7 @@
- In the NAT gateway list, view the NAT gateway status. For details about the NAT gateway status, see Table 3.
Table 3 NAT gateway statusStatus
|
-Description
+ | Description
|
|---|
@@ -118,8 +119,16 @@
After the public NAT gateway is created, check whether a default route (0.0.0.0/0) that points to the public NAT gateway exists in the default route table of the VPC where the public NAT gateway is. If no, add a route pointing to the public NAT gateway to the default route table, alternatively, create a custom route table and add the default route 0.0.0.0/0 pointing to the public NAT gateway to the table. The following describes how to add a route to a custom route table.
+Adding a Default Route Pointing to the Public NAT Gateway- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select Virtual Private Cloud.
- In the navigation pane on the left, choose Route Tables.
- On the Route Tables page, click Create Route Table in the upper right corner.
VPC: Select the VPC to which the public NAT gateway belongs.
+ - After the custom route table is created, click its name.
The Summary page is displayed.
+ - 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.
+ - Click OK.
+
diff --git a/docs/natgw/umn/nat_qs_0010.html b/docs/natgw/umn/nat_qs_0010.html
index 45131e4e..eeb4b4df 100644
--- a/docs/natgw/umn/nat_qs_0010.html
+++ b/docs/natgw/umn/nat_qs_0010.html
@@ -6,7 +6,7 @@
PrerequisitesA NAT gateway has been created.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, choose NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the DNAT rule.
- On the NAT gateway details page, click the DNAT Rules tab.
- Click Add DNAT Rule.
Figure 1 Add DNAT Rule
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the DNAT rule.
- On the NAT gateway details page, click the DNAT Rules tab.
- Click Add DNAT Rule.
Figure 1 Add DNAT Rule
- Configure the parameters as prompted. For details, see Table 1.
Table 1 Parameter descriptionsParameter
@@ -32,7 +32,7 @@
| The protocol can be TCP or UDP. This parameter is available if you select Specific port for Port Type. If you select All ports, the value of this parameter will be All by default.
|
|---|
-EIP
+ | EIP
|
The EIP that will be used by the server to provide services accessible from the Internet.
You can select an EIP that either is not bound to any resource, has been bound to a DNAT rule with Port Type set to Specific port of the current NAT gateway, or has been bound to an SNAT rule of the current NAT gateway.
@@ -40,7 +40,7 @@
|
Outside Port
|
-The port of the EIP. This parameter is available if you select Specific port for Port Type. The value ranges from 1 to 65535.
+ | The port of the EIP. This parameter is available if you select Specific port for Port Type. The value ranges from 1 to 65535.
You can enter a single port number, for example, 80.
|
@@ -49,12 +49,28 @@
The private IP address of the server that provides services accessible from the Internet through the DNAT rule.
|
+Instance Type
+ |
+The type of the instance that will be providing services accessible from on-premises data centers or remote VPCs. Possible values are:
+- Server
- Virtual IP address
- Custom
+ |
+
+NIC
+ |
+The NIC of the server. This parameter is available when you set Instance Type to Server.
+ |
+
Inside Port
|
-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 value ranges from 1 to 65535.
+ | 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 value ranges from 1 to 65535.
You can enter a single port number, for example, 80.
|
+Description
+ |
+Supplementary information about the DNAT rule. The description can contain up to 255 characters.
+ |
+
Step 4: Verify the Result
-ScenariosAfter you add a DNAT rule to a NAT gateway, you can verify that the DNAT rule has been added successfully.
+ Scenarios
+ After adding a DNAT rule, you can perform the following steps to verify the connection:
+ - Verify that the DNAT rule has been added for the public NAT gateway.
- Check whether ECS 01 in the private network can be accessed by ECS 02 from the Internet through the NAT gateway (EIP 120.46.131.153 bound to the DNAT rule).
PrerequisitesA DNAT rule has been added.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, click NAT Gateway.
- On the displayed page, click the name of the target NAT gateway.
- In the DNAT rule list, you can view details about the DNAT rule. If Status is Running, the DNAT rule has been added successfully.
+ Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click the name of the target NAT gateway.
- In the DNAT rule list, you can view details about the DNAT rule. If Status is Running, the DNAT rule has been added successfully.
+
+ Verifying that Servers in a VPC Can Be Accessed from the Internet Through the NAT Gateway- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Hover on
 in the upper left corner to display Service List and choose Computing > Elastic Cloud Server. - Log in to ECS 02 with an EIP bound.
- 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.
+
diff --git a/docs/natgw/umn/nat_qs_0012.html b/docs/natgw/umn/nat_qs_0012.html
index 03337e06..c3ebc00b 100644
--- a/docs/natgw/umn/nat_qs_0012.html
+++ b/docs/natgw/umn/nat_qs_0012.html
@@ -1,6 +1,6 @@
- Using SNAT and DNAT Rules to Allow On-premises Servers to Communicate Over the Internet
+ Allowing On-Premises Servers to Communicate with the Internet
diff --git a/docs/natgw/umn/nat_qs_0014.html b/docs/natgw/umn/nat_qs_0014.html
index fa4223fd..c1e26384 100644
--- a/docs/natgw/umn/nat_qs_0014.html
+++ b/docs/natgw/umn/nat_qs_0014.html
@@ -3,12 +3,12 @@
Step 1: Create a Direct Connect Connection
ScenariosCreate a Direct Connect connection for connecting a VPC to your data center before enabling your servers in the data center to access the Internet or to provide services accessible from the Internet through NAT gateways.
- ProcedureFor details on how to enable Direct Connect, see the Enabling Direct Connect in the Direct Connect User Guide. If you enable Direct Connect in self-service mode, you are advised to set the VPC CIDR block to 0.0.0.0/0.
+ ProcedureFor details on how to enable Direct Connect, see the Enabling Direct Connect in the Direct Connect User Guide. If you enable Direct Connect in self-service mode, you are advised to set the VPC CIDR block to 0.0.0.0/0.
diff --git a/docs/natgw/umn/nat_qs_0015.html b/docs/natgw/umn/nat_qs_0015.html
index 725d727d..243df786 100644
--- a/docs/natgw/umn/nat_qs_0015.html
+++ b/docs/natgw/umn/nat_qs_0015.html
@@ -1,14 +1,14 @@
Step 2: Assign an EIP
- ScenariosYou can assign an EIP, which can work together with a NAT gateway to allow servers that are connected to public cloud system using Direct Connect or VPN to access the Internet or to provide services accessible from the Internet.
+ ScenariosYou can assign an EIP, which can work together with a NAT gateway to allow servers that are connected to a public cloud system using Direct Connect or VPN to access the Internet or to provide services accessible from the Internet.
- ProcedureFor details, see the Elastic IP User Guide. After you assign an EIP, you do not need to bind it to a server here.
+ ProcedureFor details, see Assigning an EIP. After obtaining the EIP, you do not need to bind it to a server.
diff --git a/docs/natgw/umn/nat_qs_0016.html b/docs/natgw/umn/nat_qs_0016.html
index 28fd848a..908a7623 100644
--- a/docs/natgw/umn/nat_qs_0016.html
+++ b/docs/natgw/umn/nat_qs_0016.html
@@ -1,129 +1,138 @@
- Step 3: Create a NAT Gateway
- ScenariosThis section guides you on how to create a NAT gateway to enable your servers to access the Internet or to provide services available from the Internet.
+ Step 3: Create a Public NAT Gateway
+ ScenariosThis section guides you on how to create a public NAT gateway to enable your servers to access the Internet or to provide services available from the Internet.
- Prerequisites- When creating a NAT gateway, you must specify its VPC, subnet, and type.
- Ensure that the VPC does not have the default route.
+ Prerequisites- When creating a public NAT gateway, you must specify its VPC and subnet.
- To allow traffic to pass through the public NAT gateway, a route to the public NAT gateway in the VPC is required. When you buy 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 buy 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.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List in the upper left corner. Under Networking, select NAT Gateway.
- On the displayed page, click Create NAT Gateway.
- Configure the parameters as prompted. For details, see Table 1.
-
Table 1 Parameter descriptionsParameter
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click Create Public NAT Gateway.
Figure 1 Create NAT Gateway
+ - Configure the parameters as prompted. For details, see Table 1.
+
Table 1 Parameter descriptions of a public NAT gatewayParameter
|
-Description
+ | Description
|
|---|
-Region
+ | Region
|
-The region where the NAT gateway is located.
+ | The region where the NAT gateway is located.
|
-Name
+ | Name
|
-The name of the NAT gateway. The name can contain up to 64 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.
+ | The name of the NAT gateway. The name can contain a maximum of 64 characters and only digits, letters, underscores (_), and hyphens (-) are allowed.
|
-VPC
+ | VPC
|
-The VPC that the NAT gateway belongs to. Select a VPC which is not used by any other NAT gateways and has no default route.
-You can change the VPC only when you are creating the NAT gateway.
+ | The VPC that the NAT gateway belongs to. Select a VPC which is not used by any other NAT gateways and has no default route.
+You can change the VPC only when you are creating the NAT gateway. After the NAT gateway is created, you cannot modify the VPC.
+ 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 buy 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 buy 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
|
-The subnet of the VPC that the NAT gateway belongs to.
-The subnet must have at least one available IP address.
-You can change the subnet only when you are creating the NAT gateway.
+ | The subnet of the VPC that the NAT gateway belongs to.
+The subnet must have at least one available IP address.
+You can change the subnet only when you are creating the NAT gateway. After the NAT gateway is created, you cannot change the subnet.
|
-Type
+ | Specifications
|
-The type of the NAT gateway.
-The value can be Small, Medium, Large, and Extra-large. You can click Learn more on the page to view details about each type.
+ | The specifications of the NAT gateway.
+The option can be Small, Medium, Large, and Extra-large. You can click Learn more on the page to view details about each specifications.
|
-Description
+ | Description
|
-Supplementary information about the NAT gateway. The description can contain up to 255 characters.
+ | Supplementary information about the NAT gateway. The description can contain up to 255 characters.
|
-Tag
+ | Tag
|
-The NAT gateway tag, which consists of a key and value pair. You can add a maximum of 20 tags to each NAT gateway.
-The tag key and value must meet the requirements listed in Table 2.
+ | The NAT gateway tag, which consists of a key and value pair. You can add a maximum of 20 tags to each NAT gateway.
+The tag key and value must meet the requirements listed in Table 2.
|
Table 2 Tag requirementsParameter
+Table 2 Tag requirementsParameter
|
-Requirement
+ | Requirement
|
|---|
-Key
+ | Key
|
-- Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
-Value
+ | Value
|
-- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Can contain a maximum of 43 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
- Click Create Now. Confirm the NAT gateway information on the displayed page.
- If you do not need to modify the information, click Submit.
It takes 1 to 5 minutes to create a NAT gateway.
- - In the NAT gateway list, view the NAT gateway status. For details about the NAT gateway status, see Table 3.
-
Table 3 NAT gateway statusStatus
+- Click Create Now. Confirm the NAT gateway information on the displayed page.
- If you do not need to modify the information, click Submit.
It takes 1 to 5 minutes to create a NAT gateway.
+ - In the NAT gateway list, view the NAT gateway status. For details about the NAT gateway status, see Table 3.
+
Table 3 NAT gateway statusStatus
|
-Description
+ | Description
|
|---|
-Running
+ | Running
|
-The NAT gateway is running.
+ | The NAT gateway is running.
|
-Creating
+ | Creating
|
-The NAT gateway is being created.
+ | The NAT gateway is being created.
|
-Updating
+ | Updating
|
-The NAT gateway is being updated.
+ | The NAT gateway is being updated.
|
-Deleting
+ | Deleting
|
-The NAT gateway is being deleted.
+ | The NAT gateway is being deleted.
|
-Frozen
+ | Frozen
|
-The NAT gateway has been frozen.
+ | The NAT gateway has been frozen.
|
-Abnormal
+ | Abnormal
|
-The NAT gateway is abnormal.
+ | The NAT gateway is abnormal.
|
After the public NAT gateway is created, check whether a default route (0.0.0.0/0) that points to the public NAT gateway exists in the default route table of the VPC where the public NAT gateway is. If no, add a route pointing to the public NAT gateway to the default route table, alternatively, create a custom route table and add the default route 0.0.0.0/0 pointing to the public NAT gateway to the table. The following describes how to add a route to a custom route table.
+Adding a Default Route Pointing to the Public NAT Gateway- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select Virtual Private Cloud.
- In the navigation pane on the left, choose Route Tables.
- On the Route Tables page, click Create Route Table in the upper right corner.
VPC: Select the VPC to which the public NAT gateway belongs.
+ - After the custom route table is created, click its name.
The Summary page is displayed.
+ - 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.
+ - Click OK.
+ Step 4: Add an SNAT Rule
-ScenariosAfter a NAT gateway is created, you can add SNAT rules for it. With SNAT rules, servers that are connected to a VPC using Direct Connect can access the Internet by sharing an EIP.
+ ScenariosAfter a NAT gateway is created, you can add SNAT rules for it. With SNAT rules, servers that are connected to a VPC using Direct Connect can access the Internet by sharing an EIP.
An SNAT rule is configured for one CIDR block. If servers that are connected to a VPC using Direct Connect are in multiple CIDR blocks, you can create several SNAT rules to make the servers share one or more EIPs.
PrerequisitesA NAT gateway has been created.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, choose NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the SNAT rule.
- On the SNAT Rules tab, click Add SNAT Rule.
Figure 1 Add SNAT Rule
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the SNAT rule.
- On the SNAT Rules tab, click Add SNAT Rule.
Figure 1 Add SNAT Rule
- Configure the parameters as prompted. For details, see Table 1.
Table 1 Parameter descriptionsParameter
|
@@ -25,12 +25,17 @@
On-premises servers whose IP address in this CIDR block can access the Internet through the SNAT rule.
|
|---|
-EIP
+ | EIP
|
The EIP used for accessing the Internet.
You can select an EIP that either is not bound to any resource, has been bound to a DNAT rule with Port Type set to Specific port of the current NAT gateway, or has been bound to an SNAT rule of the current NAT gateway.
|
+Description
+ |
+Supplementary information about the SNAT rule. The description can contain up to 255 characters.
+ |
+
PrerequisitesA NAT gateway has been created.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, choose NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the DNAT rule.
- On the NAT gateway details page, click the DNAT Rules tab.
- Click Add DNAT Rule.
Figure 1 Add DNAT Rule
+Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click the name of the NAT gateway for which you want to add the DNAT rule.
- On the NAT gateway details page, click the DNAT Rules tab.
- Click Add DNAT Rule.
Figure 1 Add DNAT Rule
- Configure the parameters as prompted. For details, see Table 1.
Table 1 Parameter descriptionsParameter
@@ -32,7 +32,7 @@
| The protocol can be TCP or UDP. This parameter is available if you select Specific port for Port Type. If you select All ports, the value of this parameter will be All by default.
|
|---|
-EIP
+ | EIP
|
The EIP that will be used by the server to provide services accessible from the Internet.
You can select an EIP that either is not bound to any resource, has been bound to a DNAT rule with Port Type set to Specific port of the current NAT gateway, or has been bound to an SNAT rule of the current NAT gateway.
@@ -49,12 +49,28 @@
| The IP address of the server in the local data center or the user's private IP address. With DNAT, a server using this private IP address in your data center that is connected to a VPC through Direct Connect or VPN can provide services accessible from the Internet.
|
+Instance Type
+ |
+The type of the instance that will be providing services accessible from on-premises data centers or remote VPCs. Possible values are:
+- Server
- Virtual IP address
- Custom
+ |
+
+NIC
+ |
+The NIC of the server. This parameter is available when you set Instance Type to Server.
+ |
+
Inside Port
|
-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 value ranges from 1 to 65535.
+ | 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 value ranges from 1 to 65535.
You can enter a single port number, for example, 80.
|
+Description
+ |
+Supplementary information about the DNAT rule. The description can contain up to 255 characters.
+ |
+
- Viewing an SNAT Rule
+- Modifying an SNAT Rule
+
- Deleting an SNAT Rule
diff --git a/docs/natgw/umn/nat_snat_0002.html b/docs/natgw/umn/nat_snat_0002.html
new file mode 100644
index 00000000..30465c12
--- /dev/null
+++ b/docs/natgw/umn/nat_snat_0002.html
@@ -0,0 +1,17 @@
+
+
+Modifying an SNAT Rule
+ScenariosAfter an SNAT rule is added, you can modify parameters in the SNAT rule as required.
+
+ PrerequisitesAn SNAT rule has been added for the NAT gateway.
+
+ Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, choose NAT Gateway.
- On the displayed page, click the name of the target NAT gateway.
- On the SNAT Rules tab, locate the row that contains the SNAT rule you want to modify.
- Click Modify in the Operation column.
- In the displayed dialog box, modify the required parameters.
Figure 1 Modify SNAT Rule
+ - Click OK.
+
+
PrerequisitesAn SNAT rule has been added for the NAT gateway.
- Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, choose NAT Gateway.
- On the displayed page, click the name of the target NAT gateway.
- In the SNAT rule list, locate the row that contains the target SNAT rule and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
+ Procedure- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, select NAT Gateway.
- On the displayed page, click the name of the target NAT gateway.
- In the SNAT rule list, locate the row that contains the target SNAT rule and click Delete in the Operation column.
- In the displayed dialog box, click Yes.
diff --git a/docs/natgw/umn/nat_tag_0000.html b/docs/natgw/umn/nat_tag_0000.html
index 4422b9ec..2b28829d 100644
--- a/docs/natgw/umn/nat_tag_0000.html
+++ b/docs/natgw/umn/nat_tag_0000.html
@@ -11,14 +11,12 @@
|
|---|
Key
|
-- Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Cannot be left blank.
- Must be unique for each NAT gateway.
- Contains a maximum of 36 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
Value
|
-- Can contain a maximum of 43 characters.
- Can contain only the following character types:
- Letter
- Digits
- Special characters, including hyphens (-) and underscores (_)
-
+ | - Can contain a maximum of 43 characters.
- Contains only letters, digits, hyphens (-), underscores (_), and at signs (@).
|
@@ -27,12 +25,12 @@
ProcedureSearch for NAT gateways by tag key and value on the page showing the NAT gateway List.
- - Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, click NAT Gateway.
- In the upper right corner of the NAT gateway list, click Search by Tag.
- In the displayed area, enter the tag key and value of the NAT gateway you are looking for. Both the tag key and value must be specified.
- Click + to specify additional tag keys and values.
You can add a maximum of ten tags to refine your search results. If you add more than one tag to search for NAT gateways, the tags are automatically joined with AND.
+- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, click NAT Gateway.
- In the upper right corner of the NAT gateway list, click Search by Tag.
- In the displayed area, enter the tag key and value of the NAT gateway you are looking for. Both the tag key and value must be specified.
- Click + to specify additional tag keys and values.
You can add a maximum of 20 tags to refine your search results. If you add more than one tag to search for NAT gateways, the tags are automatically joined with AND.
- Click Search.
The system displays the NAT gateways you are looking for based on the entered tag keys and values.
Add, delete, edit, and view tags on the Tags tab of a NAT gateway.- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Under Network, click NAT Gateway.
- On the displayed page, locate the NAT gateway whose tags are to be managed and click the NAT gateway name. The page showing details about the NAT gateway is displayed.
- Click the Tags tab and perform desired operations on tags.
- View a tag.
On the Tags tab, you can view details about tags added to the current VPC, including the number of tags and the key and value of each tag.
- Add a tag.
Click Add Tag in the upper left corner. In the displayed dialog box, enter the key and value of the tag to be added, and click OK.
- You can use the predefined tags as prompted to simplify tag adding operations. For details, see the Tag Management Service User Guide.
+ You can use the predefined tags as prompted to simplify tag adding operations. For more information about predefined tags, see the Tag Management Service User Guide.
- Modify a tag.
Locate the row that contains the tag to be edited and click Edit in the Operation column. In the Edit Tag dialog box, change the tag value and click OK.
- Delete a tag.
Locate the row that contains the tag to be deleted and click Delete in the Operation column. In the displayed Delete Tag dialog box, click Yes.
diff --git a/docs/natgw/umn/public_sys-resources/icon-arrowdn.gif b/docs/natgw/umn/public_sys-resources/icon-arrowdn.gif
index 84eec9be..37942803 100644
Binary files a/docs/natgw/umn/public_sys-resources/icon-arrowdn.gif and b/docs/natgw/umn/public_sys-resources/icon-arrowdn.gif differ
diff --git a/docs/natgw/umn/public_sys-resources/icon-arrowrt.gif b/docs/natgw/umn/public_sys-resources/icon-arrowrt.gif
index 39583d16..6aaaa11c 100644
Binary files a/docs/natgw/umn/public_sys-resources/icon-arrowrt.gif and b/docs/natgw/umn/public_sys-resources/icon-arrowrt.gif differ
|
|---|
|
|---|
|
|---|
|
|---|
|
