Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
-
- In the navigation pane on the left, choose VPC Flow Logs.
- In the upper right corner, click Create VPC Flow Log. On the displayed page, configure parameters as prompted.Figure 1 Create VPC Flow Log+
- In the navigation pane on the left, choose VPC Flow Logs.
- In the upper right corner, click Create VPC Flow Log. On the displayed page, configure parameters as prompted.Figure 1 Create VPC Flow Log
Table 1 Parameter descriptions Parameter
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
-
- In the navigation pane on the left, choose VPC Flow Logs.
- Locate the row that contains the VPC flow log to be deleted and click Delete in the Operation column.Figure 1 Deleting a VPC flow log-
- Click Yes in the displayed dialog box.
- In the navigation pane on the left, choose VPC Flow Logs.
- Locate the row that contains the VPC flow log to be deleted and click Delete in the Operation column.Figure 1 Deleting a VPC flow log+
- Click OK in the displayed dialog box.
diff --git a/docs/vpc/umn/FlowLog_0006.html b/docs/vpc/umn/FlowLog_0006.html index 6895617d..618bbd79 100644 --- a/docs/vpc/umn/FlowLog_0006.html +++ b/docs/vpc/umn/FlowLog_0006.html @@ -6,7 +6,7 @@Notes and Constraints
- After a VPC flow log is enabled, the system starts to collect flow logs in the next log collection period.
- After a VPC flow log is disabled, the system stops collecting flow logs in the next log collection period. Generated flow logs will still be reported.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
-
- In the navigation pane on the left, choose VPC Flow Logs.
- Locate the VPC flow log to be enabled or disabled, and choose More > Enable or More > Disable in the Operation column.
- Click Yes.
- In the navigation pane on the left, choose VPC Flow Logs.
- Locate the VPC flow log to be enabled or disabled, and choose More > Enable or More > Disable in the Operation column.
- Click OK.
diff --git a/docs/vpc/umn/SecurityGroup_0004.html b/docs/vpc/umn/SecurityGroup_0004.html index a1966be4..13a64b97 100644 --- a/docs/vpc/umn/SecurityGroup_0004.html +++ b/docs/vpc/umn/SecurityGroup_0004.html @@ -5,9 +5,9 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- - Locate the row that contains the target security group and click Manage Rule in the Operation column.
The page for configuring security group rules is displayed.
+ - Locate the row that contains the target security group and click Manage Rules in the Operation column.
The page for configuring security group rules is displayed.
- On the Inbound Rules tab, click Fast-Add Rule.
The Fast-Add Inbound Rule dialog box is displayed.
- - Configure required parameters.Figure 1 Fast-Add Inbound Rule+
- Configure required parameters.
Figure 1 Fast-Add Inbound Rule
Table 1 Inbound rule parameter description Parameter
0.0.0.0/0
Action
+- If the Action is set to Allow, access from the source is allowed to ECSs in the security group over specified ports.
- If the Action is set to Deny, access from the source is denied to ECSs in the security group over specified ports.
Deny rules take precedence over allow rules of the same priority.
+Allow
+Priority
+Security group rule priority.
+The priority value is from 1 to 100. The default value is 1 and has the highest priority. The security group rule with a smaller value has a higher priority.
+1
+Description
(Optional) Supplementary information about the security group rule.
@@ -56,7 +73,7 @@- Click OK.
The inbound rule list is displayed and you can view your added rule.
- On the Outbound Rules tab, click Fast-Add Rule.
The Fast-Add Outbound Rule dialog box is displayed.
-- Configure required parameters.
Figure 2 Fast-Add Outbound Rule+
- Configure required parameters.
Figure 2 Fast-Add Outbound Rule
Table 2 Outbound rule parameter description Parameter
0.0.0.0/0
Priority
+Security group rule priority.
+The priority value is from 1 to 100. The default value is 1 and has the highest priority. The security group rule with a smaller value has a higher priority.
+1
+Action
+- If the Action is set to Allow, access from ECSs in the security group is allowed to the destination over specified ports.
- If the Action is set to Deny, access from ECSs in the security group is denied to the destination over specified ports.
Deny rules take precedence over allow rules of the same priority.
+Allow
+Description
(Optional) Supplementary information about the security group rule.
diff --git a/docs/vpc/umn/SecurityGroup_0005.html b/docs/vpc/umn/SecurityGroup_0005.html index 0a7ad1e2..1082c087 100644 --- a/docs/vpc/umn/SecurityGroup_0005.html +++ b/docs/vpc/umn/SecurityGroup_0005.html @@ -1,6 +1,6 @@ -Allowing Common Ports with A Few Clicks
+Allowing Common Ports with a Few Clicks
Scenarios
You can configure a security group to allow common ports with a few clicks. This function is suitable for the following scenarios:- Remotely log in to ECSs.
- Use the ping command to test ECS connectivity.
- ECSs functioning as web servers provide website access services.
Table 1 describes the common ports that can be opened with a few clicks.
diff --git a/docs/vpc/umn/SecurityGroup_0017.html b/docs/vpc/umn/SecurityGroup_0017.html index c921e385..89d698c3 100644 --- a/docs/vpc/umn/SecurityGroup_0017.html +++ b/docs/vpc/umn/SecurityGroup_0017.html @@ -9,15 +9,15 @@- In the security group list, locate the row that contains the security group and click Manage Instances in the Operation column.
The Associated Instances tab is displayed.
- Click an instance type.
- Click the Servers tab and click Add.
The Add Server dialog box is displayed.
-- In the server list, select one or more servers and click OK to add them to the current security group.
+- In the server list, select one or more servers and click OK to add them to the current security group.
Removing an Instance from a Security Group
An instance must be added to at least one security group. If you want to remove an instance from a security group, the instance must be associated with at least two security groups now.
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
+- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Virtual Private Cloud.
The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- In the security group list, locate the row that contains the security group and click Manage Instances in the Operation column.
The Associated Instances tab is displayed.
- Click an instance type.
- Click the Servers tab, select one or more servers, and click Remove in the upper left corner of the server list.
A confirmation dialog box is displayed.
- - Confirm the information and click Yes.
- Confirm the information and click OK.
diff --git a/docs/vpc/umn/acl_0001.html b/docs/vpc/umn/acl_0001.html index 9143fe65..92f1abfe 100644 --- a/docs/vpc/umn/acl_0001.html +++ b/docs/vpc/umn/acl_0001.html @@ -1,14 +1,14 @@ -Follow-Up Operations
You can delete the security groups that you no longer need. Deleting a security group will also delete all security group rules in the security group. For details, see Deleting a Security Group.
Firewall Overview
-A firewall is an optional layer of security for your subnets. After you associate one or more subnets with a firewall, you can control traffic in and out of the subnets.
-Figure 1 shows how a firewall works.
+Firewall Overview
+A firewall is an optional layer of security for your subnets. After you associate one or more subnets with a firewall, you can control traffic in and out of the subnets.
+For details, see Figure 1.
-Similar to security groups, firewalls control access to subnets and add an additional layer of defense to your subnets. Security groups only have the "allow" rules, but firewalls have both "allow" and "deny" rules. You can use firewalls together with security groups to implement comprehensive and fine-grained access control.
-Differences Between Security Groups and Firewalls summarizes the basic differences between security groups and firewalls.
-Firewall Basics
- Your VPC does not come with a firewall, but you can create a firewall and associate it with a VPC subnet if required. By default, each firewall denies all inbound traffic to and outbound traffic from the associated subnet until you add rules.
- You can associate a firewall with multiple subnets. However, a subnet can only be associated with one firewall at a time.
- Each newly created firewall is in the Inactive state until you associate subnets with it.
- Firewalls use connection tracking to track traffic to and from instances. Changes to inbound and outbound rules do not take effect immediately for the existing traffic.
If you add, modify, or delete a firewall rule, or associate or disassociate a subnet with or from a firewall, all the inbound and outbound persistent connections will not be disconnected. New rules will only be applied for the new connections.
+Similar to security groups, firewalls control access to subnets and add an additional layer of defense to your subnets. Security groups only have the "allow" rules, but firewalls have both "allow" and "deny" rules. You can use firewalls together with security groups to implement comprehensive and fine-grained access control.
+Differences Between Security Groups and Firewalls summarizes the basic differences between security groups and firewalls.
+Firewall Basics
- Your VPC does not come with a firewall, but you can create a firewall and associate it with a VPC subnet if required. By default, each firewall denies all inbound traffic to and outbound traffic from the associated subnet until you add rules.
- You can associate a firewall with multiple subnets. However, a subnet can only be associated with one firewall at a time.
- Each newly created firewall is in the Inactive state until you associate subnets with it.
- Firewalls use connection tracking to track traffic to and from instances. Changes to inbound and outbound rules do not take effect immediately for the existing traffic.
If you add, modify, or delete a firewall rule, or associate or disassociate a subnet with or from a firewall, all the inbound and outbound persistent connections will not be disconnected. New rules will only be applied for the new connections.
diff --git a/docs/vpc/umn/eip_0003.html b/docs/vpc/umn/eip_0003.html index ccebe0b1..d1889310 100644 --- a/docs/vpc/umn/eip_0003.html +++ b/docs/vpc/umn/eip_0003.html @@ -1,9 +1,11 @@ -After a persistent connection is disconnected, new connections will not be established immediately until the timeout period of connection tracking expires. For example, after an ICMP persistent connection is disconnected, a new connection will be established and a new rule will apply when the timeout period (30s) expires.
+ After a persistent connection is disconnected, new connections will not be established immediately until the timeout period of connection tracking expires. For example, after an ICMP persistent connection is disconnected, a new connection will be established and a new rule will be applied when the timeout period (30s) expires.
- The timeout period of connection tracking varies by protocol. The timeout period of a TCP connection in the established state is 600s, and that of an ICMP connection is 30s. For other protocols, if packets are received in both inbound and outbound directions, the connection tracking timeout period is 180s. If packets are received only in one direction, the connection tracking timeout period is 30s.
- The timeout period of TCP connections varies by connection status. The timeout period of a TCP connection in the established state is 600s, and that of a TCP connection in the FIN-WAIT state is 30s.
Exporting EIP Information
-Scenarios
The information of all EIPs under your account can be exported in an Excel file to a local directory. The file records the ID, status, type, bandwidth name, and bandwidth size of EIPs.
+Exporting EIPs
+-Scenarios
The information of all EIPs under your account can be exported in an Excel file to a local directory.
+The file records the EIP, EIP ID, status, type, bandwidth name, bandwidth size, bandwidth id, Instance Type, Instance Name, Instance ID, Tags and Created.
diff --git a/docs/vpc/umn/en-us_image_0000001818823050.png b/docs/vpc/umn/en-us_image_0000001818823050.png deleted file mode 100644 index f5a39cdd..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818823050.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818823074.png b/docs/vpc/umn/en-us_image_0000001818823074.png deleted file mode 100644 index df810e82..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818823074.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818823318.png b/docs/vpc/umn/en-us_image_0000001818823318.png deleted file mode 100644 index 0114f735..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818823318.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818823374.png b/docs/vpc/umn/en-us_image_0000001818823374.png deleted file mode 100644 index b20d87fc..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818823374.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818823514.png b/docs/vpc/umn/en-us_image_0000001818823514.png deleted file mode 100644 index a5876445..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818823514.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818823594.png b/docs/vpc/umn/en-us_image_0000001818823594.png deleted file mode 100644 index ebc4d6f2..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818823594.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818823602.png b/docs/vpc/umn/en-us_image_0000001818823602.png deleted file mode 100644 index 05e485d6..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818823602.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818982838.png b/docs/vpc/umn/en-us_image_0000001818982838.png deleted file mode 100644 index 0b463920..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818982838.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818983242.png b/docs/vpc/umn/en-us_image_0000001818983242.png deleted file mode 100644 index b1af5d2d..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818983242.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001818983398.png b/docs/vpc/umn/en-us_image_0000001818983398.png deleted file mode 100644 index f3053c06..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001818983398.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001832479012.png b/docs/vpc/umn/en-us_image_0000001832479012.png deleted file mode 100644 index 2fb3fb2d..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001832479012.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865582513.png b/docs/vpc/umn/en-us_image_0000001865582513.png deleted file mode 100644 index a235a332..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865582513.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865582617.png b/docs/vpc/umn/en-us_image_0000001865582617.png deleted file mode 100644 index ea33dfe0..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865582617.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865582629.png b/docs/vpc/umn/en-us_image_0000001865582629.png deleted file mode 100644 index 58647558..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865582629.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865582789.png b/docs/vpc/umn/en-us_image_0000001865582789.png deleted file mode 100644 index 92cd5049..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865582789.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865582793.png b/docs/vpc/umn/en-us_image_0000001865582793.png deleted file mode 100644 index 0587b67e..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865582793.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865582905.png b/docs/vpc/umn/en-us_image_0000001865582905.png deleted file mode 100644 index 671ce59f..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865582905.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865583269.png b/docs/vpc/umn/en-us_image_0000001865583269.png deleted file mode 100644 index f1f960fe..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865583269.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865662761.png b/docs/vpc/umn/en-us_image_0000001865662761.png deleted file mode 100644 index fc4cfb76..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865662761.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865662817.png b/docs/vpc/umn/en-us_image_0000001865662817.png deleted file mode 100644 index d46c18d8..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865662817.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865662885.png b/docs/vpc/umn/en-us_image_0000001865662885.png deleted file mode 100644 index 98634416..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865662885.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865662969.png b/docs/vpc/umn/en-us_image_0000001865662969.png deleted file mode 100644 index 5912989f..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865662969.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001865663453.png b/docs/vpc/umn/en-us_image_0000001865663453.png deleted file mode 100644 index 05e485d6..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001865663453.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001866046474.png b/docs/vpc/umn/en-us_image_0000001866046474.png deleted file mode 100644 index 8bbd5148..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001866046474.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001879005797.png b/docs/vpc/umn/en-us_image_0000001879005797.png deleted file mode 100644 index f6203273..00000000 Binary files a/docs/vpc/umn/en-us_image_0000001879005797.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000002027767176.png b/docs/vpc/umn/en-us_image_0000002027767176.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002027767176.png differ diff --git a/docs/vpc/umn/en-us_image_0000002027925628.png b/docs/vpc/umn/en-us_image_0000002027925628.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002027925628.png differ diff --git a/docs/vpc/umn/en-us_image_0000002027982768.png b/docs/vpc/umn/en-us_image_0000002027982768.png new file mode 100644 index 00000000..fa2ac362 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002027982768.png differ diff --git a/docs/vpc/umn/en-us_image_0000002028007756.png b/docs/vpc/umn/en-us_image_0000002028007756.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002028007756.png differ diff --git a/docs/vpc/umn/en-us_image_0000002028141064.png b/docs/vpc/umn/en-us_image_0000002028141064.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002028141064.png differ diff --git a/docs/vpc/umn/en-us_image_0000002028956040.png b/docs/vpc/umn/en-us_image_0000002028956040.png new file mode 100644 index 00000000..ef3a2b56 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002028956040.png differ diff --git a/docs/vpc/umn/en-us_image_0000002029014640.png b/docs/vpc/umn/en-us_image_0000002029014640.png new file mode 100644 index 00000000..d24385e5 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002029014640.png differ diff --git a/docs/vpc/umn/en-us_image_0000002029083886.png b/docs/vpc/umn/en-us_image_0000002029083886.png new file mode 100644 index 00000000..2a09eb3a Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002029083886.png differ diff --git a/docs/vpc/umn/en-us_image_0000002029088858.png b/docs/vpc/umn/en-us_image_0000002029088858.png new file mode 100644 index 00000000..75c1badb Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002029088858.png differ diff --git a/docs/vpc/umn/en-us_image_0000002029103832.png b/docs/vpc/umn/en-us_image_0000002029103832.png new file mode 100644 index 00000000..7e3ed983 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002029103832.png differ diff --git a/docs/vpc/umn/en-us_image_0000002029118468.png b/docs/vpc/umn/en-us_image_0000002029118468.png new file mode 100644 index 00000000..8470e552 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002029118468.png differ diff --git a/docs/vpc/umn/en-us_image_0000002029168046.png b/docs/vpc/umn/en-us_image_0000002029168046.png new file mode 100644 index 00000000..f4932145 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002029168046.png differ diff --git a/docs/vpc/umn/en-us_image_0000002029182980.png b/docs/vpc/umn/en-us_image_0000002029182980.png new file mode 100644 index 00000000..c5495044 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002029182980.png differ diff --git a/docs/vpc/umn/en-us_image_0000002033444204.png b/docs/vpc/umn/en-us_image_0000002033444204.png new file mode 100644 index 00000000..62cea1ba Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002033444204.png differ diff --git a/docs/vpc/umn/en-us_image_0000002048296164.png b/docs/vpc/umn/en-us_image_0000002048296164.png new file mode 100644 index 00000000..6a89604f Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002048296164.png differ diff --git a/docs/vpc/umn/en-us_image_0000002063982285.png b/docs/vpc/umn/en-us_image_0000002063982285.png new file mode 100644 index 00000000..b057ab1c Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002063982285.png differ diff --git a/docs/vpc/umn/en-us_image_0000002064000897.png b/docs/vpc/umn/en-us_image_0000002064000897.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002064000897.png differ diff --git a/docs/vpc/umn/en-us_image_0000002064022321.png b/docs/vpc/umn/en-us_image_0000002064022321.png new file mode 100644 index 00000000..d8f9804a Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002064022321.png differ diff --git a/docs/vpc/umn/en-us_image_0000002064122133.png b/docs/vpc/umn/en-us_image_0000002064122133.png new file mode 100644 index 00000000..4ef6e818 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002064122133.png differ diff --git a/docs/vpc/umn/en-us_image_0000002064973289.png b/docs/vpc/umn/en-us_image_0000002064973289.png new file mode 100644 index 00000000..10e6d8aa Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002064973289.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065082501.png b/docs/vpc/umn/en-us_image_0000002065082501.png new file mode 100644 index 00000000..161708bf Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065082501.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065091841.png b/docs/vpc/umn/en-us_image_0000002065091841.png new file mode 100644 index 00000000..5d841075 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065091841.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065093369.png b/docs/vpc/umn/en-us_image_0000002065093369.png new file mode 100644 index 00000000..3dadfc94 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065093369.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065101369.png b/docs/vpc/umn/en-us_image_0000002065101369.png new file mode 100644 index 00000000..315c5b96 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065101369.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065116093.png b/docs/vpc/umn/en-us_image_0000002065116093.png new file mode 100644 index 00000000..a8574fa8 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065116093.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065187445.png b/docs/vpc/umn/en-us_image_0000002065187445.png new file mode 100644 index 00000000..944a2290 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065187445.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065190509.png b/docs/vpc/umn/en-us_image_0000002065190509.png new file mode 100644 index 00000000..a87b705e Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065190509.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065200717.png b/docs/vpc/umn/en-us_image_0000002065200717.png new file mode 100644 index 00000000..42064e23 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065200717.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065202201.png b/docs/vpc/umn/en-us_image_0000002065202201.png new file mode 100644 index 00000000..fdce6ad1 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065202201.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065205609.png b/docs/vpc/umn/en-us_image_0000002065205609.png new file mode 100644 index 00000000..64ad10b4 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065205609.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065206257.png b/docs/vpc/umn/en-us_image_0000002065206257.png new file mode 100644 index 00000000..20d580e3 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065206257.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065209133.png b/docs/vpc/umn/en-us_image_0000002065209133.png new file mode 100644 index 00000000..24e32fe8 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065209133.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065211017.png b/docs/vpc/umn/en-us_image_0000002065211017.png new file mode 100644 index 00000000..80591145 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065211017.png differ diff --git a/docs/vpc/umn/en-us_image_0000002065222681.png b/docs/vpc/umn/en-us_image_0000002065222681.png new file mode 100644 index 00000000..10e6d8aa Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002065222681.png differ diff --git a/docs/vpc/umn/en-us_image_0000002084336681.png b/docs/vpc/umn/en-us_image_0000002084336681.png new file mode 100644 index 00000000..6a89604f Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000002084336681.png differ diff --git a/docs/vpc/umn/en-us_image_0141273034.png b/docs/vpc/umn/en-us_image_0141273034.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/vpc/umn/en-us_image_0141273034.png differ diff --git a/docs/vpc/umn/en-us_topic_0013748715.html b/docs/vpc/umn/en-us_topic_0013748715.html index d4614945..94076f20 100644 --- a/docs/vpc/umn/en-us_topic_0013748715.html +++ b/docs/vpc/umn/en-us_topic_0013748715.html @@ -155,7 +155,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner, and choose Network > Elastic IP. - On the EIP list page, select one or more EIPs and click Export in the upper left corner.
The system will automatically export all EIPs to an Excel file and download the file to a local directory.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the EIP list page, click Export in the upper left corner.
- Export selected data to an XLSX file: Select one or more EIPs and export the information about all the selected EIPs.
- Export all data to an XLSX file: Export information about all the EIPs in the current region.
The system automatically exports the information about the EIPs as an Excel file to a local directory.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- In the upper right corner, click Create Security Group.
The Create Security Group page is displayed.
- - Configure the parameters as prompted.Figure 1 Create Security Group+
- Configure the parameters as prompted.Figure 1 Create Security Group
Table 2 Parameter description Parameter
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
- Click Create Subnet.
The Create Subnet page is displayed.
- - Set the parameters as prompted.Figure 1 Create Subnet+
- Set the parameters as prompted.Figure 1 Creating a subnet
Table 1 Parameter descriptions Parameter
VPC
+Region
+The region where the VPC is located.
+-
+VPC
The VPC for which you want to create a subnet.
-
Name
+Subnet Name
The subnet name.
The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
diff --git a/docs/vpc/umn/en-us_topic_0013748738.html b/docs/vpc/umn/en-us_topic_0013748738.html index 24e9a602..cf6d82dc 100644 --- a/docs/vpc/umn/en-us_topic_0013748738.html +++ b/docs/vpc/umn/en-us_topic_0013748738.html @@ -26,7 +26,7 @@EIP Type
- Dynamic BGP: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.
- Mail BGP: EIPs with port 25, 465, or 587 enabled are used for email services.
- Dynamic BGP: Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.
- Mail BGP: EIPs with port 25, 465, or 587 enabled are used for email services.
The selected EIP type cannot be changed after the EIP is assigned.
Dynamic BGP
@@ -35,7 +35,7 @@Billed By
Two options are available:
-- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
- Dedicated: The bandwidth can be used by only one EIP.
- Shared: The bandwidth can be shared by multiple EIPs.
Dedicated
- Click Create Now.
- Click Submit.
-Binding an EIP
- On the EIPs page, locate the row that contains the target EIP, and click Bind.
- Select the instance that you want to bind the EIP to.
+diff --git a/docs/vpc/umn/en-us_topic_0013935842.html b/docs/vpc/umn/en-us_topic_0013935842.html index fe70c248..cdfb586f 100644 --- a/docs/vpc/umn/en-us_topic_0013935842.html +++ b/docs/vpc/umn/en-us_topic_0013935842.html @@ -6,15 +6,15 @@
Binding an EIP
- On the EIPs page, locate the row that contains the target EIP, and click Bind.
- Select the instance that you want to bind the EIP to.
+Figure 2 Bind EIP
- Click OK.
An IPv6 client on the internet can access the ECS that has an EIP bound in a VPC. For details, see How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- Click Create VPC.
- On the Create VPC page, set parameters as prompted.
A default subnet will be created together with a VPC and you can also click Add Subnet to create more subnets for the VPC.
-Figure 1 Create a VPC and subnet+
Figure 1 Creating a VPC and subnetTable 1 VPC parameter descriptions Category
Parameter
+Parameter
Description
+Description
Example Value
+Example Value
IPv6 CIDR Block
Specifies whether to set IPv6 CIDR Block to Enable.
+Specifies whether to set IPv6 CIDR Block to Enable.
After the IPv6 function is enabled, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created.
-
@@ -113,7 +113,7 @@Associated Route Table
The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
+The default route table to which the subnet will be associated. You can change the route table to a custom route table on the Subnets page.
Default
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- - Locate the row that contains the target security group, and click Manage Rule in the Operation column.
The page for configuring security group rules is displayed.
+ - Locate the row that contains the target security group and click Manage Rules in the Operation column.
The page for configuring security group rules is displayed.
- On the Inbound Rules tab, click Add Rule.
The Add Inbound Rule dialog box is displayed.
- Configure required parameters.
You can click + to add more inbound rules.
-Figure 1 Add Inbound Rule+
Figure 1 Add Inbound Rule
Table 1 Inbound rule parameter description Parameter
Protocol & Port
+Priority
+The security group rule priority.
+The priority value ranges from 1 to 100. The default value is 1 and has the highest priority. The security group rule with a smaller value has a higher priority.
+1
+Action
+- If the Action is set to Allow, access from the source is allowed to ECSs in the security group over specified ports.
- If the Action is set to Deny, access from the source is denied to ECSs in the security group over specified ports.
Deny rules take precedence over allow rules of the same priority.
+Allow
+Protocol
The network protocol used to match traffic in a security group rule.
Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
@@ -37,9 +54,11 @@TCP
Port: The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535.
+Port
22, or 22-30
+The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535.
+22, or 22-30
Type
@@ -74,18 +93,34 @@- Click OK.
The inbound rule list is displayed.
- On the Outbound Rules tab, click Add Rule.
The Add Outbound Rule dialog box is displayed.
- Configure required parameters.
You can click + to add more outbound rules.
-Figure 2 Add Outbound Rule+
Figure 2 Add Outbound Rule-
Table 2 Outbound rule parameter description Parameter
+Table 2 Outbound rule parameter description Parameter
Description
+Description
Example Value
Protocol & Port
- +Priority
+The security group rule priority.
+The priority value ranges from 1 to 100. The default value is 1 and has the highest priority. The security group rule with a smaller value has a higher priority.
+1
+Action
+- If the Action is set to Allow, access from ECSs in the security group is allowed to the destination over specified ports.
- If the Action is set to Deny, access from ECSs in the security group is denied to the destination over specified ports.
Deny rules take precedence over allow rules of the same priority.
+Allow
+Protocol
The network protocol used to match traffic in a security group rule.
Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.
@@ -93,9 +128,11 @@TCP
Port: The port or port range over which traffic can leave your ECS. The value can be from 1 to 65535.
+Port
22, or 22-30
+The port or port range over which traffic can leave your ECS. The value can be from 1 to 65535.
+22, or 22-30
Type
diff --git a/docs/vpc/umn/en-us_topic_0046655037.html b/docs/vpc/umn/en-us_topic_0046655037.html index bfb26de0..90690a1a 100644 --- a/docs/vpc/umn/en-us_topic_0046655037.html +++ b/docs/vpc/umn/en-us_topic_0046655037.html @@ -17,7 +17,7 @@Step 1: Create a VPC Peering Connection
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.
The VPC peering connection list is displayed.
- In the upper right corner of the page, click Create VPC Peering Connection.
The Create VPC Peering Connection dialog box is displayed.
- - Configure the parameters as prompted.For details, see Table 1.Figure 2 Create VPC Peering Connection+
- Configure the parameters as prompted.
For details, see Table 1.Figure 2 Create VPC Peering Connection
Table 1 Parameters for creating a VPC peering connection Parameter
- In the displayed dialog box, click Add Now. On the displayed page about the VPC peering connection details, go to Step 2: Add Routes for the VPC Peering Connection to add a route.
Step 2: Add Routes for the VPC Peering Connection
- In the lower part of the VPC peering connection details page, click Add Route.
The Add Route dialog box is displayed.
-Figure 3 Add Route+
Figure 3 Add Route
- Add routes to the route tables as prompted.
Table 2 describes the parameters.
Table 2 Parameter description Parameter
diff --git a/docs/vpc/umn/en-us_topic_0046655038.html b/docs/vpc/umn/en-us_topic_0046655038.html index 9f9d1eb1..56478861 100644 --- a/docs/vpc/umn/en-us_topic_0046655038.html +++ b/docs/vpc/umn/en-us_topic_0046655038.html @@ -22,7 +22,7 @@- In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.
The VPC peering connection list is displayed.
- In the upper right corner of the page, click Create VPC Peering Connection.
The Create VPC Peering Connection dialog box is displayed.
- Configure the parameters as prompted.
For details, see Table 1.
-Figure 2 Create VPC Peering Connection+
Figure 2 Create VPC Peering Connection
Table 1 Parameters for creating a VPC peering connection Parameter
@@ -109,7 +109,7 @@Both accounts need to add a route to the route table of their VPC. In this example, account A adds a route to the route table of VPC-A, and account B adds a route to the route table of VPC-B.
- Add routes to the route table of the local VPC:
- In the VPC peering connection list of the local account, click the name of the target VPC peering connection.
The page showing the VPC peering connection details is displayed.
- In the lower part of the VPC peering connection details page, click Add Route.
The Add Route dialog box is displayed.
-Figure 4 Add Route+
Figure 4 Add Route
- Add routes to the route tables as prompted.
Table 2 describes the parameters.
Table 2 Parameter description Parameter
@@ -165,7 +165,7 @@- Add routes to the route table of the peer VPC:
- In the VPC peering connection list of the peer account, click the name of the target VPC peering connection.
The page showing the VPC peering connection details is displayed.
- In the lower part of the VPC peering connection details page, click Add Route.
The Add Route dialog box is displayed.
-Figure 5 Add Route+
Figure 5 Add Route
- Add routes to the route table as prompted.
Table 3 describes the parameters.
Table 3 Parameter description Parameter
diff --git a/docs/vpc/umn/en-us_topic_0046809840.html b/docs/vpc/umn/en-us_topic_0046809840.html index 6a9c40f9..2a1ce3c5 100644 --- a/docs/vpc/umn/en-us_topic_0046809840.html +++ b/docs/vpc/umn/en-us_topic_0046809840.html @@ -22,17 +22,14 @@VPCs in the same region
+VPCs in the same region
- VPC CIDR blocks overlap.
- Some subnet CIDR blocks overlap.
- VPC CIDR blocks overlap.
- Some subnet CIDR blocks overlap.
You can create VPC peering connections to connect specific subnets or ECSs from different VPCs.
+You can create VPC peering connections to connect specific subnets or ECSs from different VPCs.
- To connect specific subnets from two VPCs, the subnet CIDR blocks cannot overlap.
- To connect specific ECSs from two VPCs, each ECS must have a unique private IP address.
- -+ VPCs in the same region
@@ -441,23 +438,23 @@Peering Two VPCs with Overlapping CIDR Blocks
As shown in Figure 4, VPC-A and VPC-B have overlapping CIDR blocks, and their Subnet-A01 and Subnet-B01 also have overlapping CIDR blocks. In this case, a VPC peering connection can connect their Subnet-A02 and Subnet-B02 that do not overlap with each other. -Table 8 Peering relationships (IPv4) Peering Relationship
+Table 8 Peering relationships (IPv4) Peering Relationship
Peering Connection Name
+Peering Connection Name
Local VPC
+Local VPC
Peer VPC
+Peer VPC
VPC-A is peered with VPC-B.
+VPC-A is peered with VPC-B.
Peering-AB
+Peering-AB
VPC-A
+VPC-A
VPC-B
+VPC-B
System
Local routes are automatically added for communications within a VPC.
+Local routes are added by the system for internal communication in a VPC.
10.0.1.0/24
@@ -647,7 +644,7 @@System
Local routes are automatically added for communications within a VPC.
+Local routes are added by the system for internal communication in a VPC.
10.0.1.0/24
diff --git a/docs/vpc/umn/en-us_topic_0051746676.html b/docs/vpc/umn/en-us_topic_0051746676.html index e96acf14..97927c4e 100644 --- a/docs/vpc/umn/en-us_topic_0051746676.html +++ b/docs/vpc/umn/en-us_topic_0051746676.html @@ -1,9 +1,9 @@Firewall
-A firewall is an optional layer of security for your subnets. After you associate one or more subnets with a firewall, you can control traffic in and out of the subnets.
+A firewall is an optional layer of security for your subnets. After you associate one or more subnets with a firewall, you can control traffic in and out of the subnets.
Figure 1 Security groups and firewalls-
Similar to security groups, firewalls control access to subnets and add an additional layer of defense to your subnets. Security groups only have the "allow" rules, but firewalls have both "allow" and "deny" rules. You can use firewalls together with security groups to implement comprehensive and fine-grained access control.
+Similar to security groups, firewalls control access to subnets and add an additional layer of defense to your subnets. Security groups only have the "allow" rules, but firewalls have both "allow" and "deny" rules. You can use firewalls together with security groups to implement comprehensive and fine-grained access control.
diff --git a/docs/vpc/umn/en-us_topic_0051746698.html b/docs/vpc/umn/en-us_topic_0051746698.html index a39ce748..575e515c 100644 --- a/docs/vpc/umn/en-us_topic_0051746698.html +++ b/docs/vpc/umn/en-us_topic_0051746698.html @@ -5,7 +5,7 @@By default, you can create a maximum of 200 firewalls in a region.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Access Control > Firewalls.
- In the right pane displayed, click Create Firewall.
- On the Create Firewall page, configure parameters as prompted.Figure 1 Create Firewall+
- In the navigation pane on the left, choose Access Control > Firewalls.
- In the right pane displayed, click Create Firewall.
- On the Create Firewall page, configure parameters as prompted.Figure 1 Create Firewall
Table 1 Parameter descriptions Parameter
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the Inbound Rules or Outbound Rules tab, click Add Rule to add an inbound or outbound rule.
- Click + to add more rules.
- Locate the row that contains the firewall rule and click Replicate in the Operation column to replicate an existing rule.
Figure 1 Add Inbound Rule+
Figure 1 Add Inbound Rule
-Table 1 Parameter descriptions Parameter
Procedure
Searching for EIPs by tag key and value on the page showing the EIP list- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner, and choose Network > Elastic IP. - In the search box above the EIP list, click anywhere in the box to set filters.
Click the tag key and then the value as required. The system filters resources based on the tag you select.
-Click anywhere in the search box to add the next tag key and value.
-You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for EIPs, the system will display only the EIPs that match all of the tags you specified.
+Procedure
Searching for EIPs by tag key and value on the page showing the EIP list-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the search box above the EIP list, click anywhere in the box to set filters.
- Click the tag key and then the value as required. The system filters resources based on the tag you select.
- Click anywhere in the search box to add the next tag key and value.
You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for EIPs, the system will display only the EIPs that match all of the tags you specified.
Adding, deleting, editing, and viewing tags on the Tags tab of an EIP- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the EIP whose tags you want to manage, and click the EIP name.
- On the page showing EIP details, click the Tags tab and perform desired operations on tags.
- View tags.
On the Tags tab, you can view details about tags added to the current EIP, including the number of tags and the key and value of each tag.
+Adding, deleting, editing, and viewing tags on the Tags tab of an EIPdiff --git a/docs/vpc/umn/faq_bandwidth.html b/docs/vpc/umn/faq_bandwidth.html index 422c6ed1..b591f7b3 100644 --- a/docs/vpc/umn/faq_bandwidth.html +++ b/docs/vpc/umn/faq_bandwidth.html @@ -8,7 +8,7 @@- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the EIP whose tags you want to manage, and click the EIP name.
- On the page showing EIP details, click the Tags tab and perform desired operations on tags.
- View tags.
On the Tags tab, you can view details about tags added to the current EIP, 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 Add Tag dialog box, enter the tag key and value, and click OK.
- Edit a tag.
Locate the row that contains the tag you want to edit, and click Edit in the Operation column. Enter the new tag value, and click OK.
The tag key cannot be modified.
- - Delete a tag.
Locate the row that contains the tag you want to delete, and click Delete in the Operation column. In the displayed dialog box, click Yes.
+ - Delete a tag.
Locate the row that contains the tag you want to delete, and click Delete in the Operation column. In the displayed dialog box, click OK.
- View tags.
- What Bandwidth Types Are Available?
- - What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth?
+ - What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth?
What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth?
+What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth?
A dedicated bandwidth can only be used by one EIP that is bound to one cloud resource, such as an ECS, a NAT gateway, or a load balancer.
A shared bandwidth can be shared by multiple EIPs. Adding an EIP to or removing an EIP from a shared bandwidth does not affect your services.
A dedicated bandwidth cannot be changed to a shared bandwidth or the other way around. You can purchase a shared bandwidth for your EIPs.
diff --git a/docs/vpc/umn/overview_region.html b/docs/vpc/umn/overview_region.html index 69e64fd9..fdad453b 100644 --- a/docs/vpc/umn/overview_region.html +++ b/docs/vpc/umn/overview_region.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/vpc/umn/vpc010005.html b/docs/vpc/umn/vpc010005.html index f84e4948..c1378904 100644 --- a/docs/vpc/umn/vpc010005.html +++ b/docs/vpc/umn/vpc010005.html @@ -3,44 +3,43 @@Assigning a Shared Bandwidth
-Scenarios
Assign a shared bandwidth for use with EIPs.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the upper right corner, click Assign Shared Bandwidth. On the displayed page, configure parameters as prompted.
-Figure 1 Assigning Shared Bandwidth+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the upper right corner, click Assign Shared Bandwidth. On the displayed page, configure parameters as prompted.Figure 1 Assigning Shared Bandwidth-
Table 1 Parameter descriptions Parameter
+Table 1 Parameter descriptions Parameter
Description
+Description
Example Value
+Example Value
Region
+Region
Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you.
+Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you.
eu-de
+eu-de
Bandwidth
+Bandwidth
The bandwidth size in Mbit/s. The minimum value is 5 Mbit/s. The maximum bandwidth can be 1000 Mbit/s.
+The bandwidth size in Mbit/s. The minimum value is 5 Mbit/s. The maximum bandwidth can be 1000 Mbit/s.
10
+10
Name
+Name
The name of the shared bandwidth.
+The name of the shared bandwidth.
Bandwidth-001
+Bandwidth-001
Enterprise Project
+Enterprise Project
The enterprise project that the EIP belongs to.
-An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.
+The enterprise project that the EIP belongs to.
+An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.
default
+default
-Notes and Constraints
- The type of EIPs must be the same as that of the shared bandwidth the EIPs to be added to.
- Do not add EIPs of the dedicated load balancer type (5_gray) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect.
diff --git a/docs/vpc/umn/vpc010007.html b/docs/vpc/umn/vpc010007.html index 42314110..9fd162dc 100644 --- a/docs/vpc/umn/vpc010007.html +++ b/docs/vpc/umn/vpc010007.html @@ -3,7 +3,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the target shared bandwidth that you want to add EIPs to. In the Operation column, choose Add Public IP Address, and select the EIPs or IPv6 addresses to be added.Figure 1 Adding EIPs or IPv6 addresses+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the target shared bandwidth that you want to add EIPs to. In the Operation column, choose Add Public IP Address, and select the EIPs or IPv6 addresses to be added.Figure 1 Adding an EIP+
Figure 2 Adding an IPv6 address+
+
- After an EIP is added to a shared bandwidth, the dedicated bandwidth used by the EIP will become invalid and the EIP will start to use the shared bandwidth. The EIP will be removed from the original dedicated bandwidth.
- Click OK.
Removing EIPs from a Shared Bandwidth
-Scenarios
Remove EIPs that are no longer required from a shared bandwidth if needed.
diff --git a/docs/vpc/umn/vpc010009.html b/docs/vpc/umn/vpc010009.html index ec96212a..24b6b34c 100644 --- a/docs/vpc/umn/vpc010009.html +++ b/docs/vpc/umn/vpc010009.html @@ -5,7 +5,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the target bandwidth from which you want to remove EIPs, choose More > Remove Public IP Address in the Operation column, and select the EIPs or IPv6 addresses to be removed in the displayed dialog box.Figure 1 Removing EIPs or IPv6 addresses+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the target bandwidth from which you want to remove EIPs, choose More > Remove Public IP Address in the Operation column, and select the EIPs or IPv6 addresses to be removed in the displayed dialog box.Figure 1 Removing EIPs or IPv6 addresses
- Click OK.
-Prerequisites
Before deleting a shared bandwidth, remove all the EIPs associated with it. For details, see Removing EIPs from a Shared Bandwidth.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the row that contains the shared bandwidth you want to delete, click More in the Operation column, and then click Delete.
- In the displayed dialog box, click OK.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the shared bandwidth list, locate the row that contains the shared bandwidth you want to delete, click More in the Operation column, and then click Delete.
- Enter DELETE as prompted and click OK.
diff --git a/docs/vpc/umn/vpc010010.html b/docs/vpc/umn/vpc010010.html index f4c78a2f..1a950672 100644 --- a/docs/vpc/umn/vpc010010.html +++ b/docs/vpc/umn/vpc010010.html @@ -1,9 +1,14 @@Exporting Shared Bandwidths
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- On the shared bandwidth list page, select one or more shared bandwidths and click Export in the upper left corner.
The system will automatically export information about all of your shared bandwidths as an Excel file to a local directory.
++Scenarios
You can export the information about the shared bandwidths as an Excel file to a local directory.
+The file records the Shared Bandwidth Name, Status, Shared bandwidthID, Bandwidth (Mbit/s),EIPs.
++Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
- In the upper left corner above the shared bandwidth list, click Export.
- Export selected data to an XLSX file: Select one or more shared bandwidths and export information about the selected shared bandwidths.
- Export all data to an XLSX file: Export information about all the shared bandwidths in the current region.
The system will automatically export information about the shared bandwidths as an Excel file to a local directory.
Parent topic: Shared Bandwidthdiff --git a/docs/vpc/umn/vpc010012.html b/docs/vpc/umn/vpc010012.html index 3ec11c64..fee32fdb 100644 --- a/docs/vpc/umn/vpc010012.html +++ b/docs/vpc/umn/vpc010012.html @@ -48,6 +48,34 @@1 minute
upstream_bandwidth_usage
+Outbound Bandwidth Usage
+Usage of outbound bandwidth in the unit of percent.
+Outbound bandwidth usage = Outbound bandwidth/Purchased bandwidth
+0% to 100%
+Bandwidth or EIP
+1 minute
+downstream_bandwidth_usage
+Inbound Bandwidth Usage
+Usage of inbound bandwidth in the unit of percent.
+Inbound bandwidth usage = Inbound bandwidth/Purchased bandwidth
+0% to 100%
+Bandwidth or EIP
+1 minute
+up_stream
Outbound Traffic
diff --git a/docs/vpc/umn/vpc_0002.html b/docs/vpc/umn/vpc_0002.html index 3df30e7d..ad8284fb 100644 --- a/docs/vpc/umn/vpc_0002.html +++ b/docs/vpc/umn/vpc_0002.html @@ -109,7 +109,7 @@Adding a Security Group Rule (IPv6)
Add a security group rule with Type set to IPv6 and Source or Destination set to an IPv6 address or IPv6 CIDR block.
Adding an IPv6 Firewall Rule
-Add a firewall rule with Type set to IPv6 and Source or Destination set to an IPv6 address or IPv6 CIDR block.
+Add a firewall rule with Type set to IPv6 and Source or Destination set to an IPv6 address or IPv6 CIDR block.
Adding a Route (IPv6)
Add a route with Destination and Next Hop set to an IPv4 or IPv6 CIDR block. For details about how to add a route, see Adding a Custom Route. If the destination is an IPv6 CIDR block, the next hop can only be an IP address in the same VPC as the IPv6 CIDR block.
If the destination is an IPv6 CIDR block, the next hop type can only be an ECS, extension NIC, or virtual IP address. The next hop must also have IPv6 addresses.
diff --git a/docs/vpc/umn/vpc_0003.html b/docs/vpc/umn/vpc_0003.html index 1d73290f..bd0ae692 100644 --- a/docs/vpc/umn/vpc_0003.html +++ b/docs/vpc/umn/vpc_0003.html @@ -16,7 +16,7 @@- Managing VPC Tags
-
- Exporting VPC List
+- Exporting VPCs
- Obtaining a VPC ID
diff --git a/docs/vpc/umn/vpc_0004.html b/docs/vpc/umn/vpc_0004.html index 6a78fdfd..a850432c 100644 --- a/docs/vpc/umn/vpc_0004.html +++ b/docs/vpc/umn/vpc_0004.html @@ -10,12 +10,14 @@
- Managing Subnet Tags
-
- Exporting Subnet List
+- Exporting Subnets
- Viewing and Deleting Resources in a Subnet
- Viewing IP Addresses in a Subnet
+
- Exporting IP Addresses in a Subnet
+- Deleting a Subnet
diff --git a/docs/vpc/umn/vpc_SecurityGroup_0006.html b/docs/vpc/umn/vpc_SecurityGroup_0006.html index 50c0bb48..60e13489 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0006.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0006.html @@ -10,7 +10,7 @@
- In the security group list, click the name of the security group.
- Click the Inbound Rules or Outbound Rules tab as required.
The security group rule list is displayed.
- In the security group rule list:
- To delete a single security group rule, locate the row that contains the rule and click Delete in the Operation column.
- To delete multiple security group rules, select multiple security group rules and click Delete in the upper left corner of the rule list.
- Click Yes.
+- Click OK.
diff --git a/docs/vpc/umn/vpc_SecurityGroup_0007.html b/docs/vpc/umn/vpc_SecurityGroup_0007.html index eecefd93..54d2ff1d 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0007.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0007.html @@ -9,7 +9,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- On the security group list, click the name of the target security group. -
- Export and import security group rules.
- Click
to export all rules of the current security group to an Excel file. - Click
to import security group rules from an Excel file into the current security group.Table 1 describes the parameters in the template for importing rules. +- Export and import security group rules.
- Click Export Rule to export all rules of the current security group to an Excel file.
- Click Import Rule to import security group rules from an Excel file into the current security group.Table 1 describes the parameters in the template for importing rules.diff --git a/docs/vpc/umn/vpc_SecurityGroup_0008.html b/docs/vpc/umn/vpc_SecurityGroup_0008.html index e819d5fa..043a5fa4 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0008.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0008.html @@ -10,7 +10,7 @@
Table 1 Template parameters Parameter
Description
@@ -26,6 +26,20 @@Inbound
Priority
+The priority value is from 1 to 100. The default value is 1 and has the highest priority. The security group rule with a smaller value has a higher priority.
+1
+Action
+Deny rules take precedence over allow rules of the same priority.
+Allow
+Protocol & Port
The network protocol used to match traffic in a security group rule.
@@ -71,6 +85,13 @@-
Last Modified
+The time when the security group was modified.
+-
+Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- Locate the row that contains the target security group, click More in the Operation column, and click Delete.
A confirmation dialog box is displayed.
- - Confirm the information and click Yes.
- Enter DELETE as prompted and click OK.
diff --git a/docs/vpc/umn/vpc_SecurityGroup_0009.html b/docs/vpc/umn/vpc_SecurityGroup_0009.html index 1f7ef4f8..8be65a82 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0009.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0009.html @@ -8,9 +8,9 @@-Notes and Constraints
- You can clone a security group from the same or a different region.
- If you want to clone a security group from the same region, you can clone all rules in the security group.
- If you want to clone a security group from a different region, the system will clone only rules whose source and destination are IP addresses and rules whose source and destination is the current security group.
- Cloning a security group clones its security group rules, but not the instances associated with the security group.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
+diff --git a/docs/vpc/umn/vpc_SecurityGroup_0012.html b/docs/vpc/umn/vpc_SecurityGroup_0012.html index 702af858..d8a0776f 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0012.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0012.html @@ -16,6 +16,8 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Virtual Private Cloud.
The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
- - Locate the row that contains the security group, click More in the Operation column, and click Clone.
- Select the region and name of the new security group as prompted.Figure 1 Clone Security Group+
- Locate the row that contains the security group, click More in the Operation column, and click Clone.
- Select the region and name of the new security group as prompted.Figure 1 Clone Security Group
- Click OK.
You can then switch to the required region to view the cloned security group in the security group list.
- Deleting a Security Group
+ - Exporting Security Groups
+ - Adding a Security Group Rule
- Fast-Adding Security Group Rules
- - Allowing Common Ports with A Few Clicks
+ - Allowing Common Ports with a Few Clicks
- Modifying a Security Group Rule
diff --git a/docs/vpc/umn/vpc_SecurityGroup_0015.html b/docs/vpc/umn/vpc_SecurityGroup_0015.html
new file mode 100644
index 00000000..f4c59a75
--- /dev/null
+++ b/docs/vpc/umn/vpc_SecurityGroup_0015.html
@@ -0,0 +1,19 @@
+
+
+ - Basic information about security groups, including the name, ID, and creation time.
- Number of security group rules.
- Number of the associated instances.
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click
in the upper left corner to display the service list and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
+ - In the navigation pane on the left, choose Access Control > Security Groups.
The security group list is displayed.
+ - In the upper left corner above the security group list, click Export.
- Export selected data to an XLSX file: Select one or more security groups and export information about the selected security groups.
- Export all data to an XLSX file: Export information about all the security groups in the current region.
The system will automatically export information about the security groups as an Excel file to a local directory.
+ - Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the displayed page, click the Associated Subnets tab.
- On the Associated Subnets page, locate the row that contains the target subnet and click Disassociate in the Operation column.
- Click Yes in the displayed dialog box.
- In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the displayed page, click the Associated Subnets tab.
- On the Associated Subnets page, locate the row that contains the target subnet and click Disassociate in the Operation column.
- Click OK.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the Inbound Rules or Outbound Rules tab, locate the row that contains the target rule, and click More and then Enable or Disable in the Operation column.
- Click Yes in the displayed dialog box.
The rule is enabled or disabled. The procedure for enabling or disabling an outbound rule is the same as that for enabling or disabling an inbound rule.
+ - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the Inbound Rules or Outbound Rules tab, locate the row that contains the target rule, and click More and then Enable or Disable in the Operation column.
- Click OK in the displayed dialog box.
The rule is enabled or disabled. The procedure for enabling or disabling an outbound rule is the same as that for enabling or disabling an inbound rule.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the Inbound Rules or Outbound Rules tab, locate the row that contains the target rule and click Delete in the Operation column.
- Click Yes in the displayed dialog box.
- In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the Inbound Rules or Outbound Rules tab, locate the row that contains the target rule and click Delete in the Operation column.
- Click OK.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the displayed page, click
on the right of Name and edit the firewall name. - Click √ to save the new firewall name.
- Click on the right of Description and edit the firewall description.
- Click √ to save the new firewall description.
- In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
- On the displayed page, click on the right of Name and edit the firewall name.
- Click
to save the new firewall name. - Click on the right of Description and edit the firewall description.
- Click
to save the new firewall description. - Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the row that contains the firewall, click More in the Operation column, and click Enable or Disable.
- Click Yes in the displayed dialog box.
- In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the row that contains the firewall, click More in the Operation column, and click Enable or Disable.
- Click OK in the displayed dialog box.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the firewall, click More in the Operation column, and click Delete.
- Click Yes. diff --git a/docs/vpc/umn/vpc_acl_0016.html b/docs/vpc/umn/vpc_acl_0016.html index 24bb8b82..7ebb5d8f 100644 --- a/docs/vpc/umn/vpc_acl_0016.html +++ b/docs/vpc/umn/vpc_acl_0016.html @@ -1,14 +1,15 @@
Deleting a firewall will also disassociate its associated subnets and delete the firewall rules.
+- In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the firewall, click More in the Operation column, and click Delete.
- Enter DELETE as prompted and click OK.
Deleting a firewall will also disassociate its associated subnets and delete the firewall rules.
Managing Subnets Associated with a Firewall
--+- Associating Subnets with a Firewall
- Disassociating Subnets from a Firewall
+ - Exporting the Information About Subnets Associated with a Firewall
+
diff --git a/docs/vpc/umn/vpc_acl_0017.html b/docs/vpc/umn/vpc_acl_0017.html new file mode 100644 index 00000000..3c762435 --- /dev/null +++ b/docs/vpc/umn/vpc_acl_0017.html @@ -0,0 +1,18 @@ + + +Exporting the Information About Subnets Associated with a Firewall
+++Scenarios
You can export the information about the subnets associated with a Firewall as an Excel file to a local directory. Each file records the subnet names, IDs, IPv4 CIDR blocks, IPv6 CIDR blocks, VPCs, and VPC IDs.
++Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
+ - In the navigation pane on the left, choose Access Control > Firewalls.
- Locate the target firewall and click its name.
- On the displayed page, click the Associated Subnets tab.
- In the upper left corner above the subnet list, click Export.
- Export selected data to an XLSX file: Select one or more subnets and export information about the selected subnets.
- Export all data to an XLSX file: Export information about all subnets associated with the current firewall.
The system will automatically export information about the subnets as an Excel file to a local directory.
+Figure 1 Exporting the subnets associated with a firewall+
++ diff --git a/docs/vpc/umn/vpc_eip_0000.html b/docs/vpc/umn/vpc_eip_0000.html index def4d04a..98aa6ca2 100644 --- a/docs/vpc/umn/vpc_eip_0000.html +++ b/docs/vpc/umn/vpc_eip_0000.html @@ -10,7 +10,7 @@++Parent topic: Managing Subnets Associated with a Firewall+- Modifying an EIP Bandwidth
-
- Exporting EIP Information
+- Exporting EIPs
- Managing EIP Tags
diff --git a/docs/vpc/umn/vpc_eip_0001.html b/docs/vpc/umn/vpc_eip_0001.html index 453a00b1..b02268dc 100644 --- a/docs/vpc/umn/vpc_eip_0001.html +++ b/docs/vpc/umn/vpc_eip_0001.html @@ -7,13 +7,13 @@
- EIP assigned together with your load balancers will also be displayed in the EIP list.
- Only EIPs with no instance bound can be released. If you want to release an EIP with an instance bound, you need to unbind EIP from the instance first.
Procedure
Unbinding a single EIP
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the EIP, and click Unbind.
- Click Yes in the displayed dialog box.
Releasing a single EIP- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the target EIP, click More and then Release in the Operation column.
- Click Yes in the displayed dialog box.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the EIP, and click Unbind.
- Click OK.
Releasing a single EIP- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, locate the row that contains the target EIP, click More and then Release in the Operation column.
- Click OK.
Unbinding multiple EIPs at once
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be unbound.
- Click the Unbind button located above the EIP list.
- Click Yes in the displayed dialog box.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be unbound.
- Click the Unbind button located above the EIP list.
- Click OK.
Releasing multiple EIPs at once
-- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be released.
- Click the Release button located above the EIP list.
- Click Yes in the displayed dialog box.
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner, and choose Network > Elastic IP.
- On the displayed page, select the EIPs to be released.
- Click the Release button located above the EIP list.
- Click OK.
diff --git a/docs/vpc/umn/vpc_faq_0011.html b/docs/vpc/umn/vpc_faq_0011.html index 20993484..47d1b7de 100644 --- a/docs/vpc/umn/vpc_faq_0011.html +++ b/docs/vpc/umn/vpc_faq_0011.html @@ -1,7 +1,7 @@What Is the Bandwidth Size Range?
-The bandwidth range is from 5Mbit/s to 1000Mbit/s.
+The bandwidth range is from 5 Mbit/s to 1000 Mbit/s.
diff --git a/docs/vpc/umn/vpc_faq_0103.html b/docs/vpc/umn/vpc_faq_0103.html index 9172f959..719ba3e8 100644 --- a/docs/vpc/umn/vpc_faq_0103.html +++ b/docs/vpc/umn/vpc_faq_0103.html @@ -2,13 +2,31 @@Change History
-Released On
+Released On
Description
2024-05-06
+2024-11-13
+This release incorporates the following changes:
+Modified the route type in VPC Peering Connection Usage Examples.
+2024-10-16
+This release incorporates the following changes:
+- Modified the operation procedure in Managing Subnet Tags, Modifying a Firewall, Unbinding a Virtual IP Address from an EIP, Unbinding an EIP from an ECS and Releasing the EIP, Exporting Routes, and Deleting a VPC Flow Log.
- Modified the description tables in Creating a Subnet for the VPC.
- Modified the figures in Creating a VPC Peering Connection with a VPC in Another Account.
- Modified the descriptions about exporting resource details in Exporting EIPs, Exporting VPCs, Exporting Subnets, Exporting Shared Bandwidths, and Exporting Routes.
- Added parameter Region in VPC Peering Connection Usage Examples.
- Added parameters Priority and Action in Adding a Security Group Rule, Fast-Adding Security Group Rules, Importing and Exporting Security Group Rules, Step 5: Add a Security Group Rule, and Step 4: Add a Security Group Rule.
2024-09-20
+This release incorporates the following changes:
+- Added Exporting IP Addresses in a Subnet to describe how to export virtual and private IP addresses in a subnet.
- Added Exporting Routes to describe how to export routes.
- Added Exporting the Information About Subnets Associated with a Firewall to describe how to export subnets associated with a firewall.
- Added Exporting Security Groups to describe how to export security groups.
- Modified the procedure for exporting resources in Exporting VPCs, Exporting Subnets, Importing and Exporting Security Group Rules, Exporting EIPs, Exporting Shared Bandwidths, and Exporting Route Tables.
- Modified the procedure for deleting resources in Deleting a Subnet, Deleting a Security Group, Deleting a Firewall, Deleting a Shared Bandwidth, Deleting a Route Table, and Deleting a VPC Peering Connection.
- Modified the console screenshots in Creating a Subnet for the VPC, Creating a Security Group, Cloning a Security Group, Adding a Security Group Rule, Fast-Adding Security Group Rules, Creating a Firewall, Adding a Firewall Rule, Assigning an EIP and Binding It to an ECS, Assigning a Shared Bandwidth, Adding EIPs to a Shared Bandwidth, Removing EIPs from a Shared Bandwidth, Creating a Custom Route Table, Associating a Route Table with a Subnet, Adding a Custom Route, Creating a VPC Peering Connection with Another VPC in Your Account, Creating a VPC Peering Connection with a VPC in Another Account, Creating a VPC Flow Log, and Assigning a Virtual IP Address.
2024-05-06
This release incorporates the following changes:
Removed step links in Configuring a VPC for ECSs That Do Not Require Internet Access and Configuring a VPC for ECSs That Access the Internet Using EIPs.
@@ -40,7 +58,7 @@2024-03-27
This release incorporates the following changes:- Changed VPCReadOnlyAccess and VPCFullAccess into VPC ReadOnlyAccess and VPC FullAccess.
- Modified the subnet description in Subnet.
- Deleted parameter Fast-add rule in Creating a Security Group.
- Added the description indicating that if the secondary IPv4 CIDR block function is available in a region, the CIDR block of a VPC in this region cannot be modified through the console in Modifying a VPC and Adding a Secondary IPv4 CIDR Block to a VPC.
- Added the procedure for exporting the list of shared bandwidths in Exporting Shared Bandwidths.
- Modified the operation procedure and figures in Adding EIPs to a Shared Bandwidth and Removing EIPs from a Shared Bandwidth.
- Modified the procedure for exporting the resource list in Exporting VPC List, Exporting Subnet List, Importing and Exporting Security Group Rules, Exporting EIP Information, and Exporting Route Table Information.
This release incorporates the following changes:- Changed VPCReadOnlyAccess and VPCFullAccess into VPC ReadOnlyAccess and VPC FullAccess.
- Modified the subnet description in Subnet.
- Deleted parameter Fast-add rule in Creating a Security Group.
- Added the description indicating that if the secondary IPv4 CIDR block function is available in a region, the CIDR block of a VPC in this region cannot be modified through the console in Modifying a VPC and Adding a Secondary IPv4 CIDR Block to a VPC.
- Added the procedure for exporting the list of shared bandwidths in Exporting Shared Bandwidths.
- Modified the operation procedure and figures in Adding EIPs to a Shared Bandwidth and Removing EIPs from a Shared Bandwidth.
- Modified the procedure for exporting the resource list in Exporting VPCs, Exporting Subnets, Importing and Exporting Security Group Rules, Exporting EIPs, and Exporting Route Tables.
This release incorporates the following changes:
Added the following content:
-Added description about allowing common ports with a few clicks in Allowing Common Ports with A Few Clicks.
+Added description about allowing common ports with a few clicks in Allowing Common Ports with a Few Clicks.
2023-10-10
@@ -245,7 +263,7 @@2021-03-16
Added the following FAQ:
- +2020-12-16
@@ -340,7 +358,7 @@2019-08-16
Added the following content:
-Added Exporting Route Table Information.
+Added Exporting Route Tables.
2019-08-09
@@ -506,7 +524,7 @@2019-01-30
Modified the following content:
-- Modified the table listing the parameters for creating a VPC in VPC and Subnet.
- Modified the table listing the parameters for modifying a security group rule in Adding a Security Group Rule.
- Added the link to the default security group rule introduction in Adding a Security Group Rule.
- Modified the format of the exported file to Excel in Exporting VPC List and Importing and Exporting Security Group Rules.
- Changed the number of characters allowed for the Description field to 255 in Creating a Firewall.
- Modified steps in Managing EIP Tags.
- Added the Monitoring Period column to the table listing metrics in Supported Metrics.
- Changed the maximum bandwidth size allowed to 1000 Mbit/s in What Is the Bandwidth Size Range?
- Modified the table listing subnet parameters in Modifying a Subnet.
- Updated the security group description in Security Group.
- Updated the VPC peering connection description in VPC Peering Connection.
- Updated firewall description in Firewall.
- Updated console screenshots in Adding a Firewall Rule.
- Updated console screenshots in Modifying a Firewall Rule.
- Modified the table listing the parameters for creating a VPC in VPC and Subnet.
- Modified the table listing the parameters for modifying a security group rule in Adding a Security Group Rule.
- Added the link to the default security group rule introduction in Adding a Security Group Rule.
- Modified the format of the exported file to Excel in Exporting VPCs and Importing and Exporting Security Group Rules.
- Changed the number of characters allowed for the Description field to 255 in Creating a Firewall.
- Modified steps in Managing EIP Tags.
- Added the Monitoring Period column to the table listing metrics in Supported Metrics.
- Changed the maximum bandwidth size allowed to 1000 Mbit/s in What Is the Bandwidth Size Range?
- Modified the table listing subnet parameters in Modifying a Subnet.
- Updated the security group description in Security Group.
- Updated the VPC peering connection description in VPC Peering Connection.
- Updated firewall description in Firewall.
- Updated console screenshots in Adding a Firewall Rule.
- Updated console screenshots in Modifying a Firewall Rule.
Added the following content:
- Added Security Group Configuration Examples.
- Added Modifying an EIP Bandwidth.
- Added description about disassociating and releasing multiple EIPs at a time in Unbinding an EIP from an ECS and Releasing the EIP.
Deleted the following content:
diff --git a/docs/vpc/umn/vpc_peering_0003.html b/docs/vpc/umn/vpc_peering_0003.html index 7a469007..711c6b30 100644 --- a/docs/vpc/umn/vpc_peering_0003.html +++ b/docs/vpc/umn/vpc_peering_0003.html @@ -9,7 +9,7 @@Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.
The VPC peering connection list is displayed.
- In the VPC peering connection list, locate the row that contains the target VPC peering connection and click Delete in the Operation column.
A confirmation dialog box is displayed.
- - Click Yes.
- Enter DELETE as prompted and click OK.
diff --git a/docs/vpc/umn/vpc_peering_0006.html b/docs/vpc/umn/vpc_peering_0006.html index ef31795a..ad606540 100644 --- a/docs/vpc/umn/vpc_peering_0006.html +++ b/docs/vpc/umn/vpc_peering_0006.html @@ -12,7 +12,7 @@Deleting Routes of a VPC Peering Connection Between VPCs in Different Accounts
Only the account owner of a VPC in a VPC peering connection can delete the routes added for the connection.
- Log in to the management console using the account of the local VPC and delete the route of the local VPC:
- Click in the upper left corner and select the desired region and project.
- Click
in the upper left corner and choose Network > Virtual Private Cloud.The Virtual Private Cloud page is displayed.
- - In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.
The VPC peering connection list is displayed.
+ - In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.
The VPC peering connection list is displayed.
- In the VPC peering connection list, click the name of the target VPC peering connection.
The page showing the VPC peering connection details is displayed.
- In the route list, locate the route and click Delete in the Operation column.
A confirmation dialog box is displayed.
- Confirm the information and click OK.
- Click
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click in the upper left corner and choose Network > Virtual Private Cloud.
The Virtual Private Cloud page is displayed.
- Click Create VPC.
- On the Create VPC page, set parameters as prompted.
A default subnet will be created together with a VPC and you can also click Add Subnet to create more subnets for the VPC.
-Figure 1 Create a VPC and subnet+Figure 1 Creating a VPC and subnet
diff --git a/docs/vpc/umn/vpc_SecurityGroup_0013.html b/docs/vpc/umn/vpc_SecurityGroup_0013.html index d0a538ee..69f22e02 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0013.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0013.html @@ -1,18 +1,14 @@ - -Managing Security Group Rules
- --- +Managing Security Group Rules
+Exporting Security Groups
+++Scenarios
You can export the details about security groups, including:++Procedure
++ diff --git a/docs/vpc/umn/vpc_acl_0000.html b/docs/vpc/umn/vpc_acl_0000.html index a14ca00e..e640631a 100644 --- a/docs/vpc/umn/vpc_acl_0000.html +++ b/docs/vpc/umn/vpc_acl_0000.html @@ -1,6 +1,6 @@ -++Parent topic: Managing a Security Group+Firewall
+Firewall
-
diff --git a/docs/vpc/umn/vpc_acl_0003.html b/docs/vpc/umn/vpc_acl_0003.html
index 867067e3..82f37b7e 100644
--- a/docs/vpc/umn/vpc_acl_0003.html
+++ b/docs/vpc/umn/vpc_acl_0003.html
@@ -4,7 +4,7 @@
Scenarios
You can disassociate a subnet from its firewall based on your network requirements.
diff --git a/docs/vpc/umn/vpc_acl_0006.html b/docs/vpc/umn/vpc_acl_0006.html index 734af51d..d12a5f6c 100644 --- a/docs/vpc/umn/vpc_acl_0006.html +++ b/docs/vpc/umn/vpc_acl_0006.html @@ -4,7 +4,7 @@Procedure
Disassociating subnets from a firewall
Select multiple subnets and click Disassociate above the subnet list to disassociate the subnets from the firewall at a time.
diff --git a/docs/vpc/umn/vpc_acl_0007.html b/docs/vpc/umn/vpc_acl_0007.html index dbbd20ef..42c9f9ba 100644 --- a/docs/vpc/umn/vpc_acl_0007.html +++ b/docs/vpc/umn/vpc_acl_0007.html @@ -4,7 +4,7 @@Scenarios
Enable or disable an inbound or outbound rule based on your network security requirements.
Procedure
Scenarios
Delete an inbound or outbound rule based on your network security requirements.
diff --git a/docs/vpc/umn/vpc_acl_0010.html b/docs/vpc/umn/vpc_acl_0010.html index 35bb603d..ed378fb0 100644 --- a/docs/vpc/umn/vpc_acl_0010.html +++ b/docs/vpc/umn/vpc_acl_0010.html @@ -4,7 +4,7 @@Procedure
Deleting Multiple Firewall Rules at a Time
You can also select multiple firewall rules and click Delete above the firewall rule list to delete multiple rules at a time.
Scenarios
Modify the name and description of a firewall.
Procedure
diff --git a/docs/vpc/umn/vpc_acl_0011.html b/docs/vpc/umn/vpc_acl_0011.html index 62f2f57d..7b32c35f 100644 --- a/docs/vpc/umn/vpc_acl_0011.html +++ b/docs/vpc/umn/vpc_acl_0011.html @@ -5,7 +5,7 @@When a firewall is disabled, custom rules will become invalid while default rules still take effect. Disabling a firewall may interrupt network traffic. For information about the default firewall rules, see Default Firewall Rules.
Procedure
diff --git a/docs/vpc/umn/vpc_acl_0012.html b/docs/vpc/umn/vpc_acl_0012.html index 251cfa26..9417f734 100644 --- a/docs/vpc/umn/vpc_acl_0012.html +++ b/docs/vpc/umn/vpc_acl_0012.html @@ -4,7 +4,7 @@Scenarios
Delete a firewall when it is no longer required.
Procedure
- Export and import security group rules.
- Click
- View tags.
- Add routes to the route table of the peer VPC:
- In the VPC peering connection list of the local account, click the name of the target VPC peering connection.
- In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.
- Configure the parameters as prompted.
- Configure required parameters.
