diff --git a/docs/vpc/umn/ALL_META.TXT.json b/docs/vpc/umn/ALL_META.TXT.json index d1b978a4b..1392b3696 100644 --- a/docs/vpc/umn/ALL_META.TXT.json +++ b/docs/vpc/umn/ALL_META.TXT.json @@ -14,7 +14,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Service Overview", @@ -32,7 +33,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Is Virtual Private Cloud?", @@ -50,7 +52,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Product Advantages", @@ -68,7 +71,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Application Scenarios", @@ -86,7 +90,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Connectivity", @@ -104,7 +109,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC and Other Services", @@ -122,7 +128,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Permissions", @@ -140,7 +147,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Basic Concepts", @@ -158,7 +166,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Subnet", @@ -176,7 +185,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Elastic IP", @@ -194,7 +204,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Route Table", @@ -212,7 +223,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"SNAT", @@ -230,7 +242,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Security Group", @@ -248,7 +261,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Shared SNAT", @@ -266,7 +280,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Peering Connection", @@ -277,14 +292,15 @@ "node_id":"en-us_topic_0051746676.xml", "product_code":"vpc", "code":"16", - "des":"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.", + "des":"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.S", "doc_type":"usermanual", "kw":"Firewall,Basic Concepts,User Guide", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Firewall", @@ -295,14 +311,15 @@ "node_id":"vpc_concepts_0012.xml", "product_code":"vpc", "code":"17", - "des":"A virtual IP address can be shared among multiple ECSs. An ECS can have both private and virtual IP addresses, and you can access the ECS through either IP address. A vir", + "des":"You can use either IP address to enable layer 2 and layer 3 communications in a VPC, access a different VPC using peering connections, and access cloud servers through EI", "doc_type":"usermanual", "kw":"Virtual IP Address,Basic Concepts,User Guide", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Virtual IP Address", @@ -315,12 +332,13 @@ "code":"18", "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", "doc_type":"usermanual", - "kw":"Region and AZ,Basic Concepts,User Guide", + "kw":"Region and AZ,Service Overview,User Guide", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Region and AZ", @@ -338,7 +356,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Document Usage Instructions", @@ -356,7 +375,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Getting Started", @@ -374,7 +394,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Typical Application Scenarios", @@ -392,7 +413,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Configuring a VPC for ECSs That Do Not Require Internet Access", @@ -410,7 +432,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Overview", @@ -428,7 +451,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 1: Create a VPC", @@ -446,7 +470,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 2: Create a Subnet for the VPC", @@ -464,7 +489,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 3: Create a Security Group", @@ -482,7 +508,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 4: Add a Security Group Rule", @@ -500,7 +527,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Configuring a VPC for ECSs That Access the Internet Using EIPs", @@ -518,7 +546,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Overview", @@ -536,7 +565,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 1: Create a VPC", @@ -554,7 +584,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 2: Create a Subnet for the VPC", @@ -572,7 +603,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 3: Assign an EIP and Bind It to an ECS", @@ -590,7 +622,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 4: Create a Security Group", @@ -608,7 +641,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Step 5: Add a Security Group Rule", @@ -625,9 +659,9 @@ "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC and Subnet", @@ -644,9 +678,9 @@ "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC", @@ -663,9 +697,9 @@ "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a VPC", @@ -676,34 +710,72 @@ "node_id":"en-us_topic_0030969462.xml", "product_code":"vpc", "code":"38", - "des":"You can modify the following information about a VPC:Modifying the Name and Description of a VPCModifying the CIDR Block of a VPCModifying the Name and Description of a V", + "des":"You can modify the following information about a VPC:Modifying the Name and Description of a VPCModifying the CIDR Block of a VPCIf the secondary IPv4 CIDR block function", "doc_type":"usermanual", "kw":"Modifying a VPC,VPC,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a VPC", "githuburl":"" }, + { + "uri":"vpc_vpc_0007.html", + "node_id":"vpc_vpc_0007.xml", + "product_code":"vpc", + "code":"39", + "des":"When you create a VPC, you specify a primary IPv4 CIDR block for the VPC, which cannot be changed. To extend the IP address range of your VPC, you can add a secondary CID", + "doc_type":"usermanual", + "kw":"Adding a Secondary IPv4 CIDR Block to a VPC,VPC,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Adding a Secondary IPv4 CIDR Block to a VPC", + "githuburl":"" + }, + { + "uri":"vpc_vpc_0008.html", + "node_id":"vpc_vpc_0008.xml", + "product_code":"vpc", + "code":"40", + "des":"If a secondary CIDR block of a VPC is no longer required, you can delete it.A secondary IPv4 CIDR block of a VPC can be deleted, but the primary CIDR block cannot be dele", + "doc_type":"usermanual", + "kw":"Deleting a Secondary IPv4 CIDR Block from a VPC,VPC,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Deleting a Secondary IPv4 CIDR Block from a VPC", + "githuburl":"" + }, { "uri":"vpc_vpc_0003.html", "node_id":"vpc_vpc_0003.xml", "product_code":"vpc", - "code":"39", + "code":"41", "des":"This section describes how to delete a VPC.If you want to delete a VPC that has subnets, custom routes, or other resources, you need to delete these resources as prompted", "doc_type":"usermanual", "kw":"Deleting a VPC,VPC,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a VPC", @@ -713,16 +785,16 @@ "uri":"vpc_vpc_0004.html", "node_id":"vpc_vpc_0004.xml", "product_code":"vpc", - "code":"40", + "code":"42", "des":"You can add tags to VPCs to help you identify and organize them.You can add a tag to a VPC when creating the VPC, or you can add a tag to a created VPC on the VPC details", "doc_type":"usermanual", "kw":"Managing VPC Tags,VPC,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Managing VPC Tags", @@ -732,16 +804,16 @@ "uri":"vpc_vpc_0006.html", "node_id":"vpc_vpc_0006.xml", "product_code":"vpc", - "code":"41", + "code":"43", "des":"Information about all VPCs under your account can be exported as an Excel file to a local directory.This file records the names, ID, status, CIDR blocks, and the number o", "doc_type":"usermanual", "kw":"Exporting VPC List,VPC,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Exporting VPC List", @@ -751,16 +823,16 @@ "uri":"vpc_vpc_0013.html", "node_id":"vpc_vpc_0013.xml", "product_code":"vpc", - "code":"42", + "code":"44", "des":"This section describes how to view and obtain a VPC ID.If you create a VPC peering connection between two VPCs in different accounts, you need to obtain the project ID of", "doc_type":"usermanual", "kw":"Obtaining a VPC ID,VPC,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Obtaining a VPC ID", @@ -770,16 +842,16 @@ "uri":"vpc_vpc_0009.html", "node_id":"vpc_vpc_0009.xml", "product_code":"vpc", - "code":"43", + "code":"45", "des":"This section describes how to view the topology of a VPC. The topology displays the subnets in a VPC and the ECSs in the subnets.Log in to the management console.Click i", "doc_type":"usermanual", "kw":"Viewing a VPC Topology,VPC,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing a VPC Topology", @@ -789,16 +861,16 @@ "uri":"vpc_0004.html", "node_id":"vpc_0004.xml", "product_code":"vpc", - "code":"44", + "code":"46", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Subnet", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Subnet", @@ -808,16 +880,16 @@ "uri":"en-us_topic_0013748726.html", "node_id":"en-us_topic_0013748726.xml", "product_code":"vpc", - "code":"45", + "code":"47", "des":"A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.A subnet is configured with DHCP by default. When an ECS in thi", "doc_type":"usermanual", "kw":"Creating a Subnet for the VPC,Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a Subnet for the VPC", @@ -827,16 +899,16 @@ "uri":"vpc_vpc_0001.html", "node_id":"vpc_vpc_0001.xml", "product_code":"vpc", - "code":"46", + "code":"48", "des":"Modify the subnet name, NTP server address, and DNS server address.Log in to the management console.Click in the upper left corner and select the desired region and proj", "doc_type":"usermanual", "kw":"Modifying a Subnet,Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a Subnet", @@ -846,16 +918,16 @@ "uri":"vpc_vpc_0005.html", "node_id":"vpc_vpc_0005.xml", "product_code":"vpc", - "code":"47", + "code":"49", "des":"You can add tags to subnets to help you identify and organize them.You can add a tag to a subnet when creating the subnet, or you can add a tag to a created subnet on the", "doc_type":"usermanual", "kw":"Managing Subnet Tags,Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Managing Subnet Tags", @@ -865,16 +937,16 @@ "uri":"vpc_vpc_0010.html", "node_id":"vpc_vpc_0010.xml", "product_code":"vpc", - "code":"48", + "code":"50", "des":"Information about all subnets under your account can be exported as an Excel file to a local directory. This file records the name, ID, VPC, CIDR block, and associated ro", "doc_type":"usermanual", "kw":"Exporting Subnet List,Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Exporting Subnet List", @@ -884,16 +956,16 @@ "uri":"vpc_vpc_0011.html", "node_id":"vpc_vpc_0011.xml", "product_code":"vpc", - "code":"49", + "code":"51", "des":"VPC subnets have private IP addresses used by cloud resources. This section describes how to view resources that are using private IP addresses of subnets. If these resou", "doc_type":"usermanual", "kw":"Viewing and Deleting Resources in a Subnet,Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing and Deleting Resources in a Subnet", @@ -903,16 +975,16 @@ "uri":"vpc_vpc_0012.html", "node_id":"vpc_vpc_0012.xml", "product_code":"vpc", - "code":"50", + "code":"52", "des":"A subnet is an IP address range in a VPC. This section describes how to view the used IP addresses in a subnet.Virtual IP addressesPrivate IP addressesUsed by the subnet ", "doc_type":"usermanual", "kw":"Viewing IP Addresses in a Subnet,Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing IP Addresses in a Subnet", @@ -922,16 +994,16 @@ "uri":"vpc_vpc_0002.html", "node_id":"vpc_vpc_0002.xml", "product_code":"vpc", - "code":"51", + "code":"53", "des":"This section describes how to delete a subnet.If you want to delete a subnet that has custom routes, virtual IP addresses, or other resources, you need to delete these re", "doc_type":"usermanual", "kw":"Deleting a Subnet,Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a Subnet", @@ -941,16 +1013,16 @@ "uri":"vpc_0002.html", "node_id":"vpc_0002.xml", "product_code":"vpc", - "code":"52", + "code":"54", "des":"IPv4 and IPv6 dual-stack allows your resources, such as ECSs, to use both IPv4 and IPv6 addresses for private and public network communications. For example, if ECSs use ", "doc_type":"usermanual", "kw":"IPv4 and IPv6 Dual-Stack Network,VPC and Subnet,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"IPv4 and IPv6 Dual-Stack Network", @@ -960,16 +1032,16 @@ "uri":"vpc_SecurityGroup_0000.html", "node_id":"vpc_securitygroup_0000.xml", "product_code":"vpc", - "code":"53", + "code":"55", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Access Control", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Access Control", @@ -979,16 +1051,16 @@ "uri":"en-us_topic_0052003963.html", "node_id":"en-us_topic_0052003963.xml", "product_code":"vpc", - "code":"54", - "des":"You can configure security groups and firewalls to increase the security of ECSs in your VPC.Security groups operate at the ECS level.Firewalls protect associated subnets", + "code":"56", + "des":"You can configure firewall and security group rules to protect the instances in your VPC, such as ECSs and databases.A security group protects the instances in it.A firew", "doc_type":"usermanual", "kw":"Differences Between Security Groups and Firewalls,Access Control,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Differences Between Security Groups and Firewalls", @@ -998,16 +1070,16 @@ "uri":"vpc_SecurityGroup_0001.html", "node_id":"vpc_securitygroup_0001.xml", "product_code":"vpc", - "code":"55", + "code":"57", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security Group", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Security Group", @@ -1017,16 +1089,16 @@ "uri":"en-us_topic_0073379079.html", "node_id":"en-us_topic_0073379079.xml", "product_code":"vpc", - "code":"56", + "code":"58", "des":"A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection req", "doc_type":"usermanual", "kw":"Security Groups and Security Group Rules,Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Security Groups and Security Group Rules", @@ -1036,16 +1108,16 @@ "uri":"SecurityGroup_0003.html", "node_id":"securitygroup_0003.xml", "product_code":"vpc", - "code":"57", - "des":"If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) wh", + "code":"59", + "des":"If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance when you create it.", "doc_type":"usermanual", "kw":"Default Security Group and Its Rules,Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Default Security Group and Its Rules", @@ -1055,35 +1127,54 @@ "uri":"en-us_topic_0081124350.html", "node_id":"en-us_topic_0081124350.xml", "product_code":"vpc", - "code":"58", + "code":"60", "des":"Here are some common security group configuration examples for different scenarios, including remote login to ECSs, website access, and internal communication between ins", "doc_type":"usermanual", "kw":"Security Group Configuration Examples,Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Security Group Configuration Examples", "githuburl":"" }, { - "uri":"en-us_topic_0013748715.html", - "node_id":"en-us_topic_0013748715.xml", + "uri":"vpc_SecurityGroup_0012.html", + "node_id":"vpc_securitygroup_0012.xml", "product_code":"vpc", - "code":"59", - "des":"A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The clo", + "code":"61", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Creating a Security Group,Security Group,User Guide", + "kw":"Managing a Security Group", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Managing a Security Group", + "githuburl":"" + }, + { + "uri":"en-us_topic_0013748715.html", + "node_id":"en-us_topic_0013748715.xml", + "product_code":"vpc", + "code":"62", + "des":"A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The clo", + "doc_type":"usermanual", + "kw":"Creating a Security Group,Managing a Security Group,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a Security Group", @@ -1093,16 +1184,16 @@ "uri":"vpc_SecurityGroup_0009.html", "node_id":"vpc_securitygroup_0009.xml", "product_code":"vpc", - "code":"60", + "code":"63", "des":"You can clone a security group from one region to another to quickly apply the security group rules to ECSs in another region.You can clone a security group in the follow", "doc_type":"usermanual", - "kw":"Cloning a Security Group,Security Group,User Guide", + "kw":"Cloning a Security Group,Managing a Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Cloning a Security Group", @@ -1112,16 +1203,16 @@ "uri":"vpc_SecurityGroup_0010.html", "node_id":"vpc_securitygroup_0010.xml", "product_code":"vpc", - "code":"61", + "code":"64", "des":"After a security group is created, you can change its name and description.Log in to the management console.Click in the upper left corner and select the desired region ", "doc_type":"usermanual", - "kw":"Modifying a Security Group,Security Group,User Guide", + "kw":"Modifying a Security Group,Managing a Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a Security Group", @@ -1131,35 +1222,54 @@ "uri":"vpc_SecurityGroup_0008.html", "node_id":"vpc_securitygroup_0008.xml", "product_code":"vpc", - "code":"62", + "code":"65", "des":"If your security group is no longer required, you can delete it.The default security group is named default and cannot be deleted.If you want to delete a security group t", "doc_type":"usermanual", - "kw":"Deleting a Security Group,Security Group,User Guide", + "kw":"Deleting a Security Group,Managing a Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a Security Group", "githuburl":"" }, { - "uri":"en-us_topic_0030969470.html", - "node_id":"en-us_topic_0030969470.xml", + "uri":"vpc_SecurityGroup_0013.html", + "node_id":"vpc_securitygroup_0013.xml", "product_code":"vpc", - "code":"63", - "des":"A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The clo", + "code":"66", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Adding a Security Group Rule,Security Group,User Guide", + "kw":"Managing Security Group Rules", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Managing Security Group Rules", + "githuburl":"" + }, + { + "uri":"en-us_topic_0030969470.html", + "node_id":"en-us_topic_0030969470.xml", + "product_code":"vpc", + "code":"67", + "des":"A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The clo", + "doc_type":"usermanual", + "kw":"Adding a Security Group Rule,Managing Security Group Rules,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" } ], "title":"Adding a Security Group Rule", @@ -1169,16 +1279,16 @@ "uri":"SecurityGroup_0004.html", "node_id":"securitygroup_0004.xml", "product_code":"vpc", - "code":"64", + "code":"68", "des":"The fast-adding rule function of security groups allows you to quickly add rules with common ports and protocols for remote login, ping tests, common web services, and da", "doc_type":"usermanual", - "kw":"Fast-Adding Security Group Rules,Security Group,User Guide", + "kw":"Fast-Adding Security Group Rules,Managing Security Group Rules,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Fast-Adding Security Group Rules", @@ -1188,16 +1298,16 @@ "uri":"SecurityGroup_0005.html", "node_id":"securitygroup_0005.xml", "product_code":"vpc", - "code":"65", + "code":"69", "des":"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 com", "doc_type":"usermanual", - "kw":"Allowing Common Ports with A Few Clicks,Security Group,User Guide", + "kw":"Allowing Common Ports with A Few Clicks,Managing Security Group Rules,User Guide", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Allowing Common Ports with A Few Clicks", @@ -1207,16 +1317,16 @@ "uri":"vpc_SecurityGroup_0005.html", "node_id":"vpc_securitygroup_0005.xml", "product_code":"vpc", - "code":"66", + "code":"70", "des":"You can modify the port, protocol, and IP address of your security group rules as required to ensure the security of your instances.Log in to the management console.Click", "doc_type":"usermanual", - "kw":"Modifying a Security Group Rule,Security Group,User Guide", + "kw":"Modifying a Security Group Rule,Managing Security Group Rules,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a Security Group Rule", @@ -1226,16 +1336,16 @@ "uri":"vpc_SecurityGroup_0004.html", "node_id":"vpc_securitygroup_0004.xml", "product_code":"vpc", - "code":"67", + "code":"71", "des":"You can replicate an existing security group rule and modify it to quickly generate a new rule.Log in to the management console.Click in the upper left corner and select", "doc_type":"usermanual", - "kw":"Replicating a Security Group Rule,Security Group,User Guide", + "kw":"Replicating a Security Group Rule,Managing Security Group Rules,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Replicating a Security Group Rule", @@ -1245,16 +1355,16 @@ "uri":"vpc_SecurityGroup_0007.html", "node_id":"vpc_securitygroup_0007.xml", "product_code":"vpc", - "code":"68", + "code":"72", "des":"You can configure security group rules in an Excel file and import the rules to the security group. You can also export security group rules to an Excel file. You are adv", "doc_type":"usermanual", - "kw":"Importing and Exporting Security Group Rules,Security Group,User Guide", + "kw":"Importing and Exporting Security Group Rules,Managing Security Group Rules,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Importing and Exporting Security Group Rules", @@ -1264,35 +1374,54 @@ "uri":"vpc_SecurityGroup_0006.html", "node_id":"vpc_securitygroup_0006.xml", "product_code":"vpc", - "code":"69", + "code":"73", "des":"If your security group rule is no longer required, you can delete it.Security group rules use whitelists. Deleting a security group rule may result in ECS access failures", "doc_type":"usermanual", - "kw":"Deleting a Security Group Rule,Security Group,User Guide", + "kw":"Deleting a Security Group Rule,Managing Security Group Rules,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a Security Group Rule", "githuburl":"" }, { - "uri":"SecurityGroup_0017.html", - "node_id":"securitygroup_0017.xml", + "uri":"vpc_SecurityGroup_0014.html", + "node_id":"vpc_securitygroup_0014.xml", "product_code":"vpc", - "code":"70", - "des":"When you create an instance, the system automatically adds the instance to a security group for protection.If one security group cannot meet your requirements, you can ad", + "code":"74", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Adding an Instance to or Removing an Instance from a Security Group,Security Group,User Guide", + "kw":"Managing Instances Associated with a Security Group", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Managing Instances Associated with a Security Group", + "githuburl":"" + }, + { + "uri":"SecurityGroup_0017.html", + "node_id":"securitygroup_0017.xml", + "product_code":"vpc", + "code":"75", + "des":"When you create an instance, the system automatically adds the instance to a security group for protection.If one security group cannot meet your requirements, you can ad", + "doc_type":"usermanual", + "kw":"Adding an Instance to or Removing an Instance from a Security Group,Managing Instances Associated wi", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" } ], "title":"Adding an Instance to or Removing an Instance from a Security Group", @@ -1302,16 +1431,16 @@ "uri":"vpc_SecurityGroup_0011.html", "node_id":"vpc_securitygroup_0011.xml", "product_code":"vpc", - "code":"71", + "code":"76", "des":"View inbound and outbound rules of a security group used by an ECS.Log in to the management console.Click in the upper left corner and select the desired region and proj", "doc_type":"usermanual", - "kw":"Viewing the Security Group of an ECS,Security Group,User Guide", + "kw":"Viewing the Security Group of an ECS,Managing Instances Associated with a Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing the Security Group of an ECS", @@ -1321,16 +1450,16 @@ "uri":"SecurityGroup_0006.html", "node_id":"securitygroup_0006.xml", "product_code":"vpc", - "code":"72", - "des":"Change the security group associated with an ECS NIC.Log in to the management console.Click in the upper left corner and select your region and project.Under Computing, ", + "code":"77", + "des":"Change the security group associated with an ECS NIC.Log in to the management console.Click in the upper left corner and select your region and project.Click and choose", "doc_type":"usermanual", - "kw":"Changing the Security Group of an ECS,Security Group,User Guide", + "kw":"Changing the Security Group of an ECS,Managing Instances Associated with a Security Group,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Changing the Security Group of an ECS", @@ -1340,16 +1469,16 @@ "uri":"vpc_acl_0000.html", "node_id":"vpc_acl_0000.xml", "product_code":"vpc", - "code":"73", + "code":"78", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Firewall", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Firewall", @@ -1359,16 +1488,16 @@ "uri":"acl_0001.html", "node_id":"acl_0001.xml", "product_code":"vpc", - "code":"74", + "code":"79", "des":"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.F", "doc_type":"usermanual", "kw":"Firewall Overview,Firewall,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Firewall Overview", @@ -1378,206 +1507,73 @@ "uri":"acl_0002.html", "node_id":"acl_0002.xml", "product_code":"vpc", - "code":"75", + "code":"80", "des":"This section provides examples for configuring firewalls.Denying Access from a Specific PortAllowing Access from Specific Ports and ProtocolsYou might want to block TCP p", "doc_type":"usermanual", "kw":"Firewall Configuration Examples,Firewall,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Firewall Configuration Examples", "githuburl":"" }, { - "uri":"en-us_topic_0051746698.html", - "node_id":"en-us_topic_0051746698.xml", + "uri":"vpc_acl_0014.html", + "node_id":"vpc_acl_0014.xml", "product_code":"vpc", - "code":"76", - "des":"You can create a custom firewall. By default, a newly created firewall is disabled and has no inbound or outbound rules, or any subnets associated.By default, you can cre", + "code":"81", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Creating a Firewall,Firewall,User Guide", + "kw":"Managing Firewalls", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Managing Firewalls", + "githuburl":"" + }, + { + "uri":"en-us_topic_0051746698.html", + "node_id":"en-us_topic_0051746698.xml", + "product_code":"vpc", + "code":"82", + "des":"You can create a custom firewall. By default, a newly created firewall is disabled and has no inbound or outbound rules, or any subnets associated.By default, you can cre", + "doc_type":"usermanual", + "kw":"Creating a Firewall,Managing Firewalls,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a Firewall", "githuburl":"" }, - { - "uri":"en-us_topic_0051746702.html", - "node_id":"en-us_topic_0051746702.xml", - "product_code":"vpc", - "code":"77", - "des":"Add an inbound or outbound rule based on your network security requirements.A firewall can contain no more than 20 rules in one direction, or performance will deteriorate", - "doc_type":"usermanual", - "kw":"Adding a Firewall Rule,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Adding a Firewall Rule", - "githuburl":"" - }, - { - "uri":"en-us_topic_0051746700.html", - "node_id":"en-us_topic_0051746700.xml", - "product_code":"vpc", - "code":"78", - "des":"You can associate a firewall with a subnet to protect resources in the subnet.You can associate a firewall with multiple subnets. However, a subnet can only be associated", - "doc_type":"usermanual", - "kw":"Associating Subnets with a Firewall,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Associating Subnets with a Firewall", - "githuburl":"" - }, - { - "uri":"vpc_acl_0003.html", - "node_id":"vpc_acl_0003.xml", - "product_code":"vpc", - "code":"79", - "des":"You can disassociate a subnet from its firewall based on your network requirements.Log in to the management console.Click in the upper left corner and select the desired", - "doc_type":"usermanual", - "kw":"Disassociating Subnets from a Firewall,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Disassociating Subnets from a Firewall", - "githuburl":"" - }, - { - "uri":"vpc_acl_0004.html", - "node_id":"vpc_acl_0004.xml", - "product_code":"vpc", - "code":"80", - "des":"If you need a rule to take effect before or after a specific rule, you can insert that rule before or after the specific rule.If multiple firewall rules conflict, only th", - "doc_type":"usermanual", - "kw":"Changing the Sequence of a Firewall Rule,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Changing the Sequence of a Firewall Rule", - "githuburl":"" - }, - { - "uri":"vpc_acl_0005.html", - "node_id":"vpc_acl_0005.xml", - "product_code":"vpc", - "code":"81", - "des":"Modify an inbound or outbound firewall rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the de", - "doc_type":"usermanual", - "kw":"Modifying a Firewall Rule,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Modifying a Firewall Rule", - "githuburl":"" - }, - { - "uri":"vpc_acl_0006.html", - "node_id":"vpc_acl_0006.xml", - "product_code":"vpc", - "code":"82", - "des":"Enable or disable an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the ", - "doc_type":"usermanual", - "kw":"Enabling or Disabling a Firewall Rule,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Enabling or Disabling a Firewall Rule", - "githuburl":"" - }, - { - "uri":"vpc_acl_0007.html", - "node_id":"vpc_acl_0007.xml", - "product_code":"vpc", - "code":"83", - "des":"Delete an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the desired reg", - "doc_type":"usermanual", - "kw":"Deleting a Firewall Rule,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Deleting a Firewall Rule", - "githuburl":"" - }, - { - "uri":"vpc_acl_0009.html", - "node_id":"vpc_acl_0009.xml", - "product_code":"vpc", - "code":"84", - "des":"View details about a firewall.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 a", - "doc_type":"usermanual", - "kw":"Viewing a Firewall,Firewall,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Viewing a Firewall", - "githuburl":"" - }, { "uri":"vpc_acl_0010.html", "node_id":"vpc_acl_0010.xml", "product_code":"vpc", - "code":"85", + "code":"83", "des":"Modify the name and description of a firewall.Log in to the management console.Click in the upper left corner and select the desired region and project.Click in the upp", "doc_type":"usermanual", - "kw":"Modifying a Firewall,Firewall,User Guide", + "kw":"Modifying a Firewall,Managing Firewalls,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a Firewall", @@ -1587,45 +1583,235 @@ "uri":"vpc_acl_0011.html", "node_id":"vpc_acl_0011.xml", "product_code":"vpc", - "code":"86", + "code":"84", "des":"After a firewall is created, you may need to enable it based on network security requirements. You can also disable an enabled firewall if needed. Before enabling a firew", "doc_type":"usermanual", - "kw":"Enabling or Disabling a Firewall,Firewall,User Guide", + "kw":"Enabling or Disabling a Firewall,Managing Firewalls,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Enabling or Disabling a Firewall", "githuburl":"" }, { - "uri":"vpc_acl_0012.html", - "node_id":"vpc_acl_0012.xml", + "uri":"vpc_acl_0009.html", + "node_id":"vpc_acl_0009.xml", "product_code":"vpc", - "code":"87", - "des":"Delete a firewall when it is no longer required.Log in to the management console.Click in the upper left corner and select the desired region and project.Click in the u", + "code":"85", + "des":"View details about a firewall.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 a", "doc_type":"usermanual", - "kw":"Deleting a Firewall,Firewall,User Guide", + "kw":"Viewing a Firewall,Managing Firewalls,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Viewing a Firewall", + "githuburl":"" + }, + { + "uri":"vpc_acl_0012.html", + "node_id":"vpc_acl_0012.xml", + "product_code":"vpc", + "code":"86", + "des":"Delete a firewall when it is no longer required.Log in to the management console.Click in the upper left corner and select the desired region and project.Click in the u", + "doc_type":"usermanual", + "kw":"Deleting a Firewall,Managing Firewalls,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a Firewall", "githuburl":"" }, + { + "uri":"vpc_acl_0015.html", + "node_id":"vpc_acl_0015.xml", + "product_code":"vpc", + "code":"87", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Management Firewall Rules", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Management Firewall Rules", + "githuburl":"" + }, + { + "uri":"en-us_topic_0051746702.html", + "node_id":"en-us_topic_0051746702.xml", + "product_code":"vpc", + "code":"88", + "des":"Add an inbound or outbound rule based on your network security requirements.A firewall can contain no more than 20 rules in one direction, or performance will deteriorate", + "doc_type":"usermanual", + "kw":"Adding a Firewall Rule,Management Firewall Rules,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Adding a Firewall Rule", + "githuburl":"" + }, + { + "uri":"vpc_acl_0005.html", + "node_id":"vpc_acl_0005.xml", + "product_code":"vpc", + "code":"89", + "des":"Modify an inbound or outbound firewall rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the de", + "doc_type":"usermanual", + "kw":"Modifying a Firewall Rule,Management Firewall Rules,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Modifying a Firewall Rule", + "githuburl":"" + }, + { + "uri":"vpc_acl_0004.html", + "node_id":"vpc_acl_0004.xml", + "product_code":"vpc", + "code":"90", + "des":"If you need a rule to take effect before or after a specific rule, you can insert that rule before or after the specific rule.If multiple firewall rules conflict, only th", + "doc_type":"usermanual", + "kw":"Changing the Sequence of a Firewall Rule,Management Firewall Rules,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Changing the Sequence of a Firewall Rule", + "githuburl":"" + }, + { + "uri":"vpc_acl_0006.html", + "node_id":"vpc_acl_0006.xml", + "product_code":"vpc", + "code":"91", + "des":"Enable or disable an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the ", + "doc_type":"usermanual", + "kw":"Enabling or Disabling a Firewall Rule,Management Firewall Rules,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Enabling or Disabling a Firewall Rule", + "githuburl":"" + }, + { + "uri":"vpc_acl_0007.html", + "node_id":"vpc_acl_0007.xml", + "product_code":"vpc", + "code":"92", + "des":"Delete an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the desired reg", + "doc_type":"usermanual", + "kw":"Deleting a Firewall Rule,Management Firewall Rules,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Deleting a Firewall Rule", + "githuburl":"" + }, + { + "uri":"vpc_acl_0016.html", + "node_id":"vpc_acl_0016.xml", + "product_code":"vpc", + "code":"93", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing Subnets Associated with a Firewall", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Managing Subnets Associated with a Firewall", + "githuburl":"" + }, + { + "uri":"en-us_topic_0051746700.html", + "node_id":"en-us_topic_0051746700.xml", + "product_code":"vpc", + "code":"94", + "des":"You can associate a firewall with a subnet to protect resources in the subnet.You can associate a firewall with multiple subnets. However, a subnet can only be associated", + "doc_type":"usermanual", + "kw":"Associating Subnets with a Firewall,Managing Subnets Associated with a Firewall,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Associating Subnets with a Firewall", + "githuburl":"" + }, + { + "uri":"vpc_acl_0003.html", + "node_id":"vpc_acl_0003.xml", + "product_code":"vpc", + "code":"95", + "des":"You can disassociate a subnet from its firewall based on your network requirements.Log in to the management console.Click in the upper left corner and select the desired", + "doc_type":"usermanual", + "kw":"Disassociating Subnets from a Firewall,Managing Subnets Associated with a Firewall,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Disassociating Subnets from a Firewall", + "githuburl":"" + }, { "uri":"vpc_eip_0000.html", "node_id":"vpc_eip_0000.xml", "product_code":"vpc", - "code":"88", + "code":"96", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Elastic IP", @@ -1633,7 +1819,7 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc", + "prodname":"eip", "opensource":"false" } ], @@ -1644,16 +1830,16 @@ "uri":"en-us_topic_0013748738.html", "node_id":"en-us_topic_0013748738.xml", "product_code":"vpc", - "code":"89", + "code":"97", "des":"You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.Note the following when you use EIPs of the Dedicated Load Balancer (5_gray) type:In e", "doc_type":"usermanual", "kw":"Assigning an EIP and Binding It to an ECS,Elastic IP,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Assigning an EIP and Binding It to an ECS", @@ -1663,16 +1849,16 @@ "uri":"vpc_eip_0001.html", "node_id":"vpc_eip_0001.xml", "product_code":"vpc", - "code":"90", + "code":"98", "des":"If you no longer need an EIP, unbind it from the ECS and release the EIP to avoid wasting network resources.In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type ca", "doc_type":"usermanual", "kw":"Unbinding an EIP from an ECS and Releasing the EIP,Elastic IP,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Unbinding an EIP from an ECS and Releasing the EIP", @@ -1682,16 +1868,16 @@ "uri":"en-us_topic_0013748743.html", "node_id":"en-us_topic_0013748743.xml", "product_code":"vpc", - "code":"91", + "code":"99", "des":"Modify the EIP bandwidth name or size.This section describes how to modify the dedicated bandwidth or shared bandwidth of an EIP. For details about how to modify a shared", "doc_type":"usermanual", "kw":"Modifying an EIP Bandwidth,Elastic IP,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying an EIP Bandwidth", @@ -1701,16 +1887,16 @@ "uri":"eip_0003.html", "node_id":"eip_0003.xml", "product_code":"vpc", - "code":"92", + "code":"100", "des":"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", "doc_type":"usermanual", "kw":"Exporting EIP Information,Elastic IP,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Exporting EIP Information", @@ -1720,16 +1906,16 @@ "uri":"en-us_topic_0068145818.html", "node_id":"en-us_topic_0068145818.xml", "product_code":"vpc", - "code":"93", + "code":"101", "des":"Tags can be added to EIPs to facilitate EIP identification and administration. You can add a tag to an EIP when assigning the EIP. Alternatively, you can add a tag to an ", "doc_type":"usermanual", "kw":"Managing EIP Tags,Elastic IP,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Managing EIP Tags", @@ -1739,16 +1925,16 @@ "uri":"vpc010003.html", "node_id":"vpc010003.xml", "product_code":"vpc", - "code":"94", + "code":"102", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Shared Bandwidth", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Shared Bandwidth", @@ -1758,16 +1944,16 @@ "uri":"vpc010004.html", "node_id":"vpc010004.xml", "product_code":"vpc", - "code":"95", + "code":"103", "des":"A shared bandwidth can be shared by multiple EIPs and controls the data transfer rate on these EIPs in a centralized manner. All ECSs, BMSs, and load balancers that have ", "doc_type":"usermanual", "kw":"Shared Bandwidth Overview,Shared Bandwidth,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Shared Bandwidth Overview", @@ -1777,16 +1963,16 @@ "uri":"vpc010005.html", "node_id":"vpc010005.xml", "product_code":"vpc", - "code":"96", + "code":"104", "des":"Assign a shared bandwidth for use with EIPs.Log in to the management console.Click in the upper left corner and select the desired region and project.Click in the upper", "doc_type":"usermanual", "kw":"Assigning a Shared Bandwidth,Shared Bandwidth,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Assigning a Shared Bandwidth", @@ -1796,16 +1982,16 @@ "uri":"vpc010006.html", "node_id":"vpc010006.xml", "product_code":"vpc", - "code":"97", + "code":"105", "des":"Add EIPs to a shared bandwidth and the EIPs can then share that bandwidth. You can add multiple EIPs to a shared bandwidth at the same time.The type of EIPs must be the s", "doc_type":"usermanual", "kw":"Adding EIPs to a Shared Bandwidth,Shared Bandwidth,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Adding EIPs to a Shared Bandwidth", @@ -1815,16 +2001,16 @@ "uri":"vpc010007.html", "node_id":"vpc010007.xml", "product_code":"vpc", - "code":"98", + "code":"106", "des":"Remove EIPs that are no longer required from a shared bandwidth if needed.Log in to the management console.Click in the upper left corner and select the desired region a", "doc_type":"usermanual", "kw":"Removing EIPs from a Shared Bandwidth,Shared Bandwidth,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Removing EIPs from a Shared Bandwidth", @@ -1834,16 +2020,16 @@ "uri":"vpc010008.html", "node_id":"vpc010008.xml", "product_code":"vpc", - "code":"99", + "code":"107", "des":"You can modify the name and size of a shared bandwidth as required.Log in to the management console.Click in the upper left corner and select the desired region and proj", "doc_type":"usermanual", "kw":"Modifying a Shared Bandwidth,Shared Bandwidth,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a Shared Bandwidth", @@ -1853,35 +2039,54 @@ "uri":"vpc010009.html", "node_id":"vpc010009.xml", "product_code":"vpc", - "code":"100", + "code":"108", "des":"Delete a shared bandwidth when it is no longer required.Before deleting a shared bandwidth, remove all the EIPs associated with it. For details, see Removing EIPs from a ", "doc_type":"usermanual", "kw":"Deleting a Shared Bandwidth,Shared Bandwidth,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a Shared Bandwidth", "githuburl":"" }, + { + "uri":"vpc010010.html", + "node_id":"vpc010010.xml", + "product_code":"vpc", + "code":"109", + "des":"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 I", + "doc_type":"usermanual", + "kw":"Exporting Shared Bandwidths,Shared Bandwidth,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Exporting Shared Bandwidths", + "githuburl":"" + }, { "uri":"vpc_route01_0000.html", "node_id":"vpc_route01_0000.xml", "product_code":"vpc", - "code":"101", + "code":"110", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Route Tables", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Route Tables", @@ -1891,35 +2096,54 @@ "uri":"vpc_route01_0001.html", "node_id":"vpc_route01_0001.xml", "product_code":"vpc", - "code":"102", + "code":"111", "des":"A route table contains a set of routes that are used to determine where network traffic from your subnets in a VPC is directed. Each subnet must be associated with a rout", "doc_type":"usermanual", "kw":"Route Tables and Routes,Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Route Tables and Routes", "githuburl":"" }, { - "uri":"vpc_route01_0005.html", - "node_id":"vpc_route01_0005.xml", + "uri":"vpc_route01_0016.html", + "node_id":"vpc_route01_0016.xml", "product_code":"vpc", - "code":"103", - "des":"A VPC automatically comes with a default route table. If your default route table cannot meet your service requirements, you can create a custom route table.By default, e", + "code":"112", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Creating a Custom Route Table,Route Tables,User Guide", + "kw":"Managing Route Tables", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Managing Route Tables", + "githuburl":"" + }, + { + "uri":"vpc_route01_0005.html", + "node_id":"vpc_route01_0005.xml", + "product_code":"vpc", + "code":"113", + "des":"A VPC automatically comes with a default route table. If your default route table cannot meet your service requirements, you can create a custom route table.By default, e", + "doc_type":"usermanual", + "kw":"Creating a Custom Route Table,Managing Route Tables,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a Custom Route Table", @@ -1929,16 +2153,16 @@ "uri":"vpc_route01_0007.html", "node_id":"vpc_route01_0007.xml", "product_code":"vpc", - "code":"104", + "code":"114", "des":"After a subnet is created, the system associates the subnet with the default route table of its VPC. If you want to use specific routes for a subnet, you can associate th", "doc_type":"usermanual", - "kw":"Associating a Route Table with a Subnet,Route Tables,User Guide", + "kw":"Associating a Route Table with a Subnet,Managing Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Associating a Route Table with a Subnet", @@ -1948,16 +2172,16 @@ "uri":"vpc_route01_0008.html", "node_id":"vpc_route01_0008.xml", "product_code":"vpc", - "code":"105", + "code":"115", "des":"You can change the route table for a subnet. If the route table for a subnet is changed, routes in the new route table will apply to all cloud resources in the subnet.Log", "doc_type":"usermanual", - "kw":"Changing the Route Table Associated with a Subnet,Route Tables,User Guide", + "kw":"Changing the Route Table Associated with a Subnet,Managing Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Changing the Route Table Associated with a Subnet", @@ -1967,16 +2191,16 @@ "uri":"vpc_route01_0015.html", "node_id":"vpc_route01_0015.xml", "product_code":"vpc", - "code":"106", + "code":"116", "des":"This section describes how to view the route table associated with a subnet.Log in to the management console.Click in the upper left corner and select the desired region", "doc_type":"usermanual", - "kw":"Viewing the Route Table Associated with a Subnet,Route Tables,User Guide", + "kw":"Viewing the Route Table Associated with a Subnet,Managing Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing the Route Table Associated with a Subnet", @@ -1986,16 +2210,16 @@ "uri":"vpc_route01_0009.html", "node_id":"vpc_route01_0009.xml", "product_code":"vpc", - "code":"107", + "code":"117", "des":"This section describes how to view detailed information about a route table, including:Basic information, such as name, type (default or custom), and ID of the route tabl", "doc_type":"usermanual", - "kw":"Viewing Route Table Information,Route Tables,User Guide", + "kw":"Viewing Route Table Information,Managing Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing Route Table Information", @@ -2005,16 +2229,16 @@ "uri":"vpc_route01_0014.html", "node_id":"vpc_route01_0014.xml", "product_code":"vpc", - "code":"108", + "code":"118", "des":"Information about all route tables under your account can be exported as an Excel file to a local directory. This file records the name, ID, VPC, type, and number of asso", "doc_type":"usermanual", - "kw":"Exporting Route Table Information,Route Tables,User Guide", + "kw":"Exporting Route Table Information,Managing Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Exporting Route Table Information", @@ -2024,35 +2248,54 @@ "uri":"vpc_route01_0010.html", "node_id":"vpc_route01_0010.xml", "product_code":"vpc", - "code":"109", + "code":"119", "des":"This section describes how to delete a custom route table.The default route table cannot be deleted.A custom route table with a subnet associated cannot be deleted direct", "doc_type":"usermanual", - "kw":"Deleting a Route Table,Route Tables,User Guide", + "kw":"Deleting a Route Table,Managing Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a Route Table", "githuburl":"" }, { - "uri":"vpc_route01_0006.html", - "node_id":"vpc_route01_0006.xml", + "uri":"vpc_route01_0017.html", + "node_id":"vpc_route01_0017.xml", "product_code":"vpc", - "code":"110", - "des":"Each route table contains a default system route, which indicates that ECSs in a VPC can communicate with each other. You can also add custom routes as required to forwar", + "code":"120", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Adding a Custom Route,Route Tables,User Guide", + "kw":"Managing Routes", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Managing Routes", + "githuburl":"" + }, + { + "uri":"vpc_route01_0006.html", + "node_id":"vpc_route01_0006.xml", + "product_code":"vpc", + "code":"121", + "des":"Each route table contains a default system route, which indicates that ECSs in a VPC can communicate with each other. You can also add custom routes as required to forwar", + "doc_type":"usermanual", + "kw":"Adding a Custom Route,Managing Routes,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" } ], "title":"Adding a Custom Route", @@ -2062,16 +2305,16 @@ "uri":"vpc_route01_0011.html", "node_id":"vpc_route01_0011.xml", "product_code":"vpc", - "code":"111", + "code":"122", "des":"This section describes how to modify a custom route in a route table.System routes cannot be modified.When you create a VPC endpoint, VPN or Direct Connect connection, th", "doc_type":"usermanual", - "kw":"Modifying a Route,Route Tables,User Guide", + "kw":"Modifying a Route,Managing Routes,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a Route", @@ -2081,16 +2324,16 @@ "uri":"vpc_route01_0013.html", "node_id":"vpc_route01_0013.xml", "product_code":"vpc", - "code":"112", + "code":"123", "des":"This section describes how to replicate routes among all route tables of a VPC. VPC route tables include the default and custom route tables.Table 1 shows whether routes ", "doc_type":"usermanual", - "kw":"Replicating a Route,Route Tables,User Guide", + "kw":"Replicating a Route,Managing Routes,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Replicating a Route", @@ -2100,16 +2343,16 @@ "uri":"vpc_route01_0012.html", "node_id":"vpc_route01_0012.xml", "product_code":"vpc", - "code":"113", + "code":"124", "des":"This section describes how to delete a custom route from a route table.System routes cannot be deleted.The routes automatically delivered by VPN or Direct Connect to the ", "doc_type":"usermanual", - "kw":"Deleting a Route,Route Tables,User Guide", + "kw":"Deleting a Route,Managing Routes,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a Route", @@ -2119,16 +2362,16 @@ "uri":"vpc_route_0004.html", "node_id":"vpc_route_0004.xml", "product_code":"vpc", - "code":"114", + "code":"125", "des":"Together with VPC route tables, you can configure SNAT on an ECS to enable other ECSs that have no EIPs bound in the same VPC to access the Internet through this ECS.The ", "doc_type":"usermanual", "kw":"Configuring an SNAT Server,Route Tables,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Configuring an SNAT Server", @@ -2138,16 +2381,16 @@ "uri":"vpc_peering_0000.html", "node_id":"vpc_peering_0000.xml", "product_code":"vpc", - "code":"115", + "code":"126", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"VPC Peering Connection", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Peering Connection", @@ -2157,16 +2400,16 @@ "uri":"en-us_topic_0046655036.html", "node_id":"en-us_topic_0046655036.xml", "product_code":"vpc", - "code":"116", + "code":"127", "des":"A VPC peering connection is a networking connection that connects two VPCs for them to communicate using private IP addresses. The VPCs to be peered can be in the same ac", "doc_type":"usermanual", "kw":"VPC Peering Connection Overview,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Peering Connection Overview", @@ -2176,16 +2419,16 @@ "uri":"en-us_topic_0046809840.html", "node_id":"en-us_topic_0046809840.xml", "product_code":"vpc", - "code":"117", + "code":"128", "des":"A VPC peering connection is a networking connection between two VPCs in the same region and enables them to communicate. Table 1 lists different scenarios of using VPC pe", "doc_type":"usermanual", "kw":"VPC Peering Connection Usage Examples,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Peering Connection Usage Examples", @@ -2195,16 +2438,16 @@ "uri":"en-us_topic_0046655037.html", "node_id":"en-us_topic_0046655037.xml", "product_code":"vpc", - "code":"118", + "code":"129", "des":"If two VPCs from the same region cannot communicate with each other, you can use a VPC peering connection. This section describes how to create a VPC peering connection b", "doc_type":"usermanual", "kw":"Creating a VPC Peering Connection with Another VPC in Your Account,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a VPC Peering Connection with Another VPC in Your Account", @@ -2214,16 +2457,16 @@ "uri":"en-us_topic_0046655038.html", "node_id":"en-us_topic_0046655038.xml", "product_code":"vpc", - "code":"119", + "code":"130", "des":"If two VPCs from the same region cannot communicate with each other, you can use a VPC peering connection. This section describes how to create a VPC peering connection b", "doc_type":"usermanual", "kw":"Creating a VPC Peering Connection with a VPC in Another Account,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a VPC Peering Connection with a VPC in Another Account", @@ -2233,16 +2476,16 @@ "uri":"vpc_peering_0005.html", "node_id":"vpc_peering_0005.xml", "product_code":"vpc", - "code":"120", + "code":"131", "des":"If you create a VPC peering connection between two VPCs in different accounts, you can refer to this section to obtain the project ID of the region that the peer VPC resi", "doc_type":"usermanual", "kw":"Obtaining the Peer Project ID of a VPC Peering Connection,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Obtaining the Peer Project ID of a VPC Peering Connection", @@ -2252,16 +2495,16 @@ "uri":"vpc_peering_0002.html", "node_id":"vpc_peering_0002.xml", "product_code":"vpc", - "code":"121", + "code":"132", "des":"This section describes how to modify the name of a VPC peering connection.Either owner of a VPC in a peering connection can modify the VPC peering connection in any state", "doc_type":"usermanual", "kw":"Modifying a VPC Peering Connection,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying a VPC Peering Connection", @@ -2271,16 +2514,16 @@ "uri":"vpc_peering_0001.html", "node_id":"vpc_peering_0001.xml", "product_code":"vpc", - "code":"122", + "code":"133", "des":"This section describes how to view basic information about a VPC peering connection, including the connection name, status, and information about the local and peer VPCs.", "doc_type":"usermanual", "kw":"Viewing VPC Peering Connections,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing VPC Peering Connections", @@ -2290,16 +2533,16 @@ "uri":"vpc_peering_0003.html", "node_id":"vpc_peering_0003.xml", "product_code":"vpc", - "code":"123", + "code":"134", "des":"This section describes how to delete a VPC peering connection.Either owner of a VPC in a peering connection can delete the VPC peering connection in any state.The owner o", "doc_type":"usermanual", "kw":"Deleting a VPC Peering Connection,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a VPC Peering Connection", @@ -2309,16 +2552,16 @@ "uri":"vpc_peering_0007.html", "node_id":"vpc_peering_0007.xml", "product_code":"vpc", - "code":"124", + "code":"135", "des":"This section describes how to modify the routes added for a VPC peering connection in the route tables of the local and peer VPCs.Modifying Routes of a VPC Peering Connec", "doc_type":"usermanual", "kw":"Modifying Routes Configured for a VPC Peering Connection,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Modifying Routes Configured for a VPC Peering Connection", @@ -2328,16 +2571,16 @@ "uri":"vpc_peering_0004.html", "node_id":"vpc_peering_0004.xml", "product_code":"vpc", - "code":"125", + "code":"136", "des":"This section describes how to view the routes added to the route tables of local and peer VPCs of a VPC peering connection.Viewing Routes of a VPC Peering Connection Betw", "doc_type":"usermanual", "kw":"Viewing Routes Configured for a VPC Peering Connection,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing Routes Configured for a VPC Peering Connection", @@ -2347,16 +2590,16 @@ "uri":"vpc_peering_0006.html", "node_id":"vpc_peering_0006.xml", "product_code":"vpc", - "code":"126", + "code":"137", "des":"This section describes how to delete routes from the route tables of the local and peer VPCs connected by a VPC peering connection.Deleting Routes of a VPC Peering Connec", "doc_type":"usermanual", "kw":"Deleting Routes Configured for a VPC Peering Connection,VPC Peering Connection,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting Routes Configured for a VPC Peering Connection", @@ -2366,16 +2609,16 @@ "uri":"FlowLog_0001.html", "node_id":"flowlog_0001.xml", "product_code":"vpc", - "code":"127", + "code":"138", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"VPC Flow Log", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Flow Log", @@ -2385,16 +2628,16 @@ "uri":"FlowLog_0002.html", "node_id":"flowlog_0002.xml", "product_code":"vpc", - "code":"128", + "code":"139", "des":"A VPC flow log records information about the traffic going to and from a VPC. VPC flow logs help you monitor network traffic, analyze network attacks, and determine wheth", "doc_type":"usermanual", "kw":"VPC Flow Log Overview,VPC Flow Log,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Flow Log Overview", @@ -2404,16 +2647,16 @@ "uri":"FlowLog_0003.html", "node_id":"flowlog_0003.xml", "product_code":"vpc", - "code":"129", + "code":"140", "des":"A VPC flow log records information about the traffic going to and from a VPC.Ensure that the following operations have been performed on the LTS console:Create a log grou", "doc_type":"usermanual", "kw":"Creating a VPC Flow Log,VPC Flow Log,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a VPC Flow Log", @@ -2423,16 +2666,16 @@ "uri":"FlowLog_0004.html", "node_id":"flowlog_0004.xml", "product_code":"vpc", - "code":"130", + "code":"141", "des":"View information about your flow log record.The capture window is approximately 10 minutes, which indicates that a flow log record will be generated every 10 minutes. Aft", "doc_type":"usermanual", "kw":"Viewing a VPC Flow Log,VPC Flow Log,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing a VPC Flow Log", @@ -2442,16 +2685,16 @@ "uri":"FlowLog_0006.html", "node_id":"flowlog_0006.xml", "product_code":"vpc", - "code":"131", + "code":"142", "des":"After a VPC flow log is created, the VPC flow log is automatically enabled. If you do not need to record flow log data, you can disable the corresponding VPC flow log. A ", "doc_type":"usermanual", "kw":"Enabling or Disabling VPC Flow Log,VPC Flow Log,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Enabling or Disabling VPC Flow Log", @@ -2461,16 +2704,16 @@ "uri":"FlowLog_0005.html", "node_id":"flowlog_0005.xml", "product_code":"vpc", - "code":"132", + "code":"143", "des":"Delete a VPC flow log that is not required. Deleting a VPC flow log will not delete the existing flow log records in LTS.If a NIC that uses a VPC flow log is deleted, the", "doc_type":"usermanual", "kw":"Deleting a VPC Flow Log,VPC Flow Log,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Deleting a VPC Flow Log", @@ -2480,16 +2723,16 @@ "uri":"vpc_dc_0000.html", "node_id":"vpc_dc_0000.xml", "product_code":"vpc", - "code":"133", + "code":"144", "des":"Direct Connect allows you to establish a dedicated network connection between your data center and the cloud platform. With Direct Connect, you can establish a private co", "doc_type":"usermanual", "kw":"Direct Connect,User Guide", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Direct Connect", @@ -2499,7 +2742,7 @@ "uri":"vpc_vip_0000.html", "node_id":"vpc_vip_0000.xml", "product_code":"vpc", - "code":"134", + "code":"145", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Virtual IP Address", @@ -2507,7 +2750,7 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc", + "prodname":"eip", "opensource":"false" } ], @@ -2518,16 +2761,16 @@ "uri":"vpc_vip_0001.html", "node_id":"vpc_vip_0001.xml", "product_code":"vpc", - "code":"135", + "code":"146", "des":"A virtual IP address can be shared among multiple ECSs. An ECS can have both private and virtual IP addresses, and you can access the ECS through either IP address. A vir", "doc_type":"usermanual", "kw":"Virtual IP Address Overview,Virtual IP Address,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Virtual IP Address Overview", @@ -2537,16 +2780,16 @@ "uri":"vpc_vip_0002.html", "node_id":"vpc_vip_0002.xml", "product_code":"vpc", - "code":"136", + "code":"147", "des":"If an ECS requires a virtual IP address or if a virtual IP address needs to be reserved, you can assign a virtual IP address from the subnet.Log in to the management cons", "doc_type":"usermanual", "kw":"Assigning a Virtual IP Address,Virtual IP Address,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Assigning a Virtual IP Address", @@ -2556,16 +2799,16 @@ "uri":"en-us_topic_0067802474.html", "node_id":"en-us_topic_0067802474.xml", "product_code":"vpc", - "code":"137", + "code":"148", "des":"You can use a virtual IP address and an EIP together.If you bind a virtual IP address to ECSs that work in active/standby pairs and bind an EIP to the virtual IP address,", "doc_type":"usermanual", "kw":"Binding a Virtual IP Address to an EIP or ECS,Virtual IP Address,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Binding a Virtual IP Address to an EIP or ECS", @@ -2575,130 +2818,35 @@ "uri":"vpc_vip_0003.html", "node_id":"vpc_vip_0003.xml", "product_code":"vpc", - "code":"138", + "code":"149", "des":"This section describes how to bind a virtual IP address to an EIP.You have assigned an EIP.Log in to the management console.Click in the upper left corner and select the", "doc_type":"usermanual", "kw":"Binding a Virtual IP Address to an EIP,Virtual IP Address,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Binding a Virtual IP Address to an EIP", "githuburl":"" }, - { - "uri":"vpc_vip_0004.html", - "node_id":"vpc_vip_0004.xml", - "product_code":"vpc", - "code":"139", - "des":"Configure the ECS networking based on Networking.Create a VPN.The VPN can be used to access the virtual IP address of the ECS.", - "doc_type":"usermanual", - "kw":"Using a VPN to Access a Virtual IP Address,Virtual IP Address,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Using a VPN to Access a Virtual IP Address", - "githuburl":"" - }, - { - "uri":"vpc_vip_0005.html", - "node_id":"vpc_vip_0005.xml", - "product_code":"vpc", - "code":"140", - "des":"Configure the ECS networking based on Networking.Create a Direct Connect connection.The created Direct Connect connection can be used to access the virtual IP address of ", - "doc_type":"usermanual", - "kw":"Using a Direct Connect Connection to Access the Virtual IP Address,Virtual IP Address,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Using a Direct Connect Connection to Access the Virtual IP Address", - "githuburl":"" - }, - { - "uri":"vpc_vip_0006.html", - "node_id":"vpc_vip_0006.xml", - "product_code":"vpc", - "code":"141", - "des":"Configure the ECS networking based on Networking.Create a VPC peering connection.You can access the virtual IP address of the ECS through the VPC peering connection.", - "doc_type":"usermanual", - "kw":"Using a VPC Peering Connection to Access the Virtual IP Address,Virtual IP Address,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Using a VPC Peering Connection to Access the Virtual IP Address", - "githuburl":"" - }, - { - "uri":"vpc_vip_0007.html", - "node_id":"vpc_vip_0007.xml", - "product_code":"vpc", - "code":"142", - "des":"If a virtual IP address is used in an active/standby scenario, disable IP forwarding on the standby ECS.Log in to the ECS.Run the following command to switch to user root", - "doc_type":"usermanual", - "kw":"Disabling IP Forwarding on the Standby ECS,Virtual IP Address,User Guide", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Disabling IP Forwarding on the Standby ECS", - "githuburl":"" - }, - { - "uri":"vpc_vip_0008.html", - "node_id":"vpc_vip_0008.xml", - "product_code":"vpc", - "code":"143", - "des":"If a virtual IP address is used in an HA load balancing cluster, you need to disable source/destination check for ECS NICs.Log in to the management console.Click in the ", - "doc_type":"usermanual", - "kw":"Disabling Source and Destination Check (HA Load Balancing Cluster Scenario),Virtual IP Address,User ", - "search_title":"", - "metedata":[ - { - "opensource":"true", - "documenttype":"usermanual", - "prodname":"vpc" - } - ], - "title":"Disabling Source and Destination Check (HA Load Balancing Cluster Scenario)", - "githuburl":"" - }, { "uri":"vpc_vip_0010.html", "node_id":"vpc_vip_0010.xml", "product_code":"vpc", - "code":"144", + "code":"150", "des":"This section describes how to unbind a virtual IP address from an ECS.Log in to the management console.Click in the upper left corner and select the desired region and p", "doc_type":"usermanual", "kw":"Unbinding a Virtual IP Address from an Instance,Virtual IP Address,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Unbinding a Virtual IP Address from an Instance", @@ -2708,16 +2856,16 @@ "uri":"vpc_vip_0011.html", "node_id":"vpc_vip_0011.xml", "product_code":"vpc", - "code":"145", + "code":"151", "des":"This section describes how to unbind a virtual IP address from an EIP.Log in to the management console.Click in the upper left corner and select the desired region and p", "doc_type":"usermanual", "kw":"Unbinding a Virtual IP Address from an EIP,Virtual IP Address,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Unbinding a Virtual IP Address from an EIP", @@ -2727,35 +2875,130 @@ "uri":"vpc_vip_0009.html", "node_id":"vpc_vip_0009.xml", "product_code":"vpc", - "code":"146", + "code":"152", "des":"If you no longer need a virtual IP address or a reserved virtual IP address, you can release it to avoid wasting resources.If you want to release a virtual IP address tha", "doc_type":"usermanual", "kw":"Releasing a Virtual IP Address,Virtual IP Address,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Releasing a Virtual IP Address", "githuburl":"" }, + { + "uri":"vpc_vip_0007.html", + "node_id":"vpc_vip_0007.xml", + "product_code":"vpc", + "code":"153", + "des":"If a virtual IP address is used in an active/standby scenario, disable IP forwarding on the standby ECS.Log in to the ECS.Run the following command to switch to user root", + "doc_type":"usermanual", + "kw":"Disabling IP Forwarding on the Standby ECS,Virtual IP Address,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Disabling IP Forwarding on the Standby ECS", + "githuburl":"" + }, + { + "uri":"vpc_vip_0008.html", + "node_id":"vpc_vip_0008.xml", + "product_code":"vpc", + "code":"154", + "des":"If a virtual IP address is used in an HA load balancing cluster, you need to disable source/destination check for ECS NICs.Log in to the management console.Click in the ", + "doc_type":"usermanual", + "kw":"Disabling Source and Destination Check (HA Load Balancing Cluster Scenario),Virtual IP Address,User ", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Disabling Source and Destination Check (HA Load Balancing Cluster Scenario)", + "githuburl":"" + }, + { + "uri":"vpc_vip_0004.html", + "node_id":"vpc_vip_0004.xml", + "product_code":"vpc", + "code":"155", + "des":"Configure the ECS networking based on Networking.Create a VPN.The VPN can be used to access the virtual IP address of the ECS.", + "doc_type":"usermanual", + "kw":"Using a VPN to Access a Virtual IP Address,Virtual IP Address,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Using a VPN to Access a Virtual IP Address", + "githuburl":"" + }, + { + "uri":"vpc_vip_0005.html", + "node_id":"vpc_vip_0005.xml", + "product_code":"vpc", + "code":"156", + "des":"Configure the ECS networking based on Networking.Create a Direct Connect connection.The created Direct Connect connection can be used to access the virtual IP address of ", + "doc_type":"usermanual", + "kw":"Using a Direct Connect Connection to Access the Virtual IP Address,Virtual IP Address,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Using a Direct Connect Connection to Access the Virtual IP Address", + "githuburl":"" + }, + { + "uri":"vpc_vip_0006.html", + "node_id":"vpc_vip_0006.xml", + "product_code":"vpc", + "code":"157", + "des":"Configure the ECS networking based on Networking.Create a VPC peering connection.You can access the virtual IP address of the ECS through the VPC peering connection.", + "doc_type":"usermanual", + "kw":"Using a VPC Peering Connection to Access the Virtual IP Address,Virtual IP Address,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"Using a VPC Peering Connection to Access the Virtual IP Address", + "githuburl":"" + }, { "uri":"vpc010011.html", "node_id":"vpc010011.xml", "product_code":"vpc", - "code":"147", + "code":"158", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitoring", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Monitoring", @@ -2765,16 +3008,16 @@ "uri":"vpc010012.html", "node_id":"vpc010012.xml", "product_code":"vpc", - "code":"148", + "code":"159", "des":"This section describes the namespace, list, and measurement dimensions of EIP and bandwidth metrics that you can check on Cloud Eye. You can use APIs or the Cloud Eye con", "doc_type":"usermanual", "kw":"Supported Metrics,Monitoring,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Supported Metrics", @@ -2784,16 +3027,16 @@ "uri":"vpc010013.html", "node_id":"vpc010013.xml", "product_code":"vpc", - "code":"149", + "code":"160", "des":"You can view the bandwidth and EIP usage on the Elastic IP and Bandwidth or Cloud Eye console.You can view the inbound bandwidth, outbound bandwidth, inbound bandwidth us", "doc_type":"usermanual", "kw":"Viewing Metrics,Monitoring,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Viewing Metrics", @@ -2803,16 +3046,16 @@ "uri":"vpc010014.html", "node_id":"vpc010014.xml", "product_code":"vpc", - "code":"150", + "code":"161", "des":"You can configure alarm rules to customize the monitored objects and notification policies. You can learn your resource statuses at any time.Log in to the management cons", "doc_type":"usermanual", "kw":"Creating an Alarm Rule,Monitoring,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Creating an Alarm Rule", @@ -2822,7 +3065,7 @@ "uri":"permission_0001.html", "node_id":"permission_0001.xml", "product_code":"vpc", - "code":"151", + "code":"162", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Permissions Management", @@ -2830,7 +3073,7 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc", + "prodname":"eip", "opensource":"false" } ], @@ -2841,16 +3084,16 @@ "uri":"permission_0003.html", "node_id":"permission_0003.xml", "product_code":"vpc", - "code":"152", + "code":"163", "des":"This section describes how to use IAM to implement fine-grained permissions control for your VPC resources. With IAM, you can:Create IAM users for employees based on your", "doc_type":"usermanual", "kw":"Creating a User and Granting VPC Permissions,Permissions Management,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Creating a User and Granting VPC Permissions", @@ -2860,16 +3103,16 @@ "uri":"permission_0004.html", "node_id":"permission_0004.xml", "product_code":"vpc", - "code":"153", + "code":"164", "des":"Custom policies can be created to supplement the system-defined policies of VPC. For the actions supported for custom policies, see Permissions Policies and Supported Act", "doc_type":"usermanual", "kw":"VPC Custom Policies,Permissions Management,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Custom Policies", @@ -2879,7 +3122,7 @@ "uri":"vpc_faq_0000.html", "node_id":"vpc_faq_0000.xml", "product_code":"vpc", - "code":"154", + "code":"165", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQ", @@ -2887,7 +3130,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"FAQ", @@ -2897,7 +3141,7 @@ "uri":"faq_common.html", "node_id":"faq_common.xml", "product_code":"vpc", - "code":"155", + "code":"166", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"General Questions", @@ -2905,7 +3149,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"General Questions", @@ -2915,7 +3160,7 @@ "uri":"vpc_faq_0051.html", "node_id":"vpc_faq_0051.xml", "product_code":"vpc", - "code":"156", + "code":"167", "des":"A quota limits the quantity of a resource available to users, thereby preventing spikes in the usage of the resource. For example, a VPC quota limits the number of VPCs t", "doc_type":"usermanual", "kw":"What Is a Quota?,General Questions,User Guide", @@ -2923,7 +3168,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Is a Quota?", @@ -2933,7 +3179,7 @@ "uri":"faq_vpc.html", "node_id":"faq_vpc.xml", "product_code":"vpc", - "code":"157", + "code":"168", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"VPCs and Subnets", @@ -2941,7 +3187,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPCs and Subnets", @@ -2951,15 +3198,16 @@ "uri":"vpc_faq_0001.html", "node_id":"vpc_faq_0001.xml", "product_code":"vpc", - "code":"158", - "des":"The Virtual Private Cloud (VPC) service enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security a", + "code":"169", + "des":"Virtual Private Cloud (VPC) enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security and simplifyi", "doc_type":"usermanual", "kw":"What Is Virtual Private Cloud?,VPCs and Subnets,User Guide", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Is Virtual Private Cloud?", @@ -2969,7 +3217,7 @@ "uri":"vpc_faq_0004.html", "node_id":"vpc_faq_0004.xml", "product_code":"vpc", - "code":"159", + "code":"170", "des":"The following table lists the private CIDR blocks that you can specify when creating a VPC. Consider the following when selecting a VPC CIDR block:Number of IP addresses:", "doc_type":"usermanual", "kw":"Which CIDR Blocks Are Available for the VPC Service?,VPCs and Subnets,User Guide", @@ -2977,7 +3225,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Which CIDR Blocks Are Available for the VPC Service?", @@ -2987,7 +3236,7 @@ "uri":"vpc_faq_0005.html", "node_id":"vpc_faq_0005.xml", "product_code":"vpc", - "code":"160", + "code":"171", "des":"Subnets in the same VPC can communicate with each other by default.VPCs are isolated from each other. Subnets from different VPCs cannot communicate with each other. You ", "doc_type":"usermanual", "kw":"Can Subnets Communicate with Each Other?,VPCs and Subnets,User Guide", @@ -2995,7 +3244,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Can Subnets Communicate with Each Other?", @@ -3005,7 +3255,7 @@ "uri":"vpc_faq_0006.html", "node_id":"vpc_faq_0006.xml", "product_code":"vpc", - "code":"161", + "code":"172", "des":"A subnet is an IP address range from a VPC. The VPC service supports CIDR blocks 10.0.0.0/8-24, 172.16.0.0/12-24, and 192.168.0.0/16-24.Subnets must reside within your VP", "doc_type":"usermanual", "kw":"What Subnet CIDR Blocks Are Available?,VPCs and Subnets,User Guide", @@ -3013,7 +3263,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Subnet CIDR Blocks Are Available?", @@ -3023,7 +3274,7 @@ "uri":"vpc_faq_0009.html", "node_id":"vpc_faq_0009.xml", "product_code":"vpc", - "code":"162", + "code":"173", "des":"Each account can have a maximum of 100 subnets. If the number of subnets cannot meet your service requirements, request a quota increase. For details, see What Is a Quota", "doc_type":"usermanual", "kw":"How Many Subnets Can I Create?,VPCs and Subnets,User Guide", @@ -3031,7 +3282,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"How Many Subnets Can I Create?", @@ -3041,7 +3293,7 @@ "uri":"vpc_faq_0094.html", "node_id":"vpc_faq_0094.xml", "product_code":"vpc", - "code":"163", + "code":"174", "des":"The network ID of the subnet is the neutron_network_id in the subnet fields in Subnet > Creating a Subnet in the Virtual Private Cloud API Reference.Parameter neutron_net", "doc_type":"usermanual", "kw":"What Are the Differences Between the Network ID and Subnet ID of a Subnet?,VPCs and Subnets,User Gui", @@ -3049,7 +3301,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Are the Differences Between the Network ID and Subnet ID of a Subnet?", @@ -3059,7 +3312,7 @@ "uri":"vpc_faq_0075.html", "node_id":"vpc_faq_0075.xml", "product_code":"vpc", - "code":"164", + "code":"175", "des":"If VPCs and subnets are being used by other resources, you need to delete these resources first based on the prompts on the console before deleting the VPCs and subnets. ", "doc_type":"usermanual", "kw":"Why Can't I Delete My VPCs and Subnets?,VPCs and Subnets,User Guide", @@ -3067,7 +3320,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Why Can't I Delete My VPCs and Subnets?", @@ -3077,7 +3331,7 @@ "uri":"faq_eip.html", "node_id":"faq_eip.xml", "product_code":"vpc", - "code":"165", + "code":"176", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"EIPs", @@ -3085,7 +3339,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"EIPs", @@ -3095,7 +3350,7 @@ "uri":"vpc_faq_0013.html", "node_id":"vpc_faq_0013.xml", "product_code":"vpc", - "code":"166", + "code":"177", "des":"The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to ", "doc_type":"usermanual", "kw":"What Is an EIP?,EIPs,User Guide", @@ -3103,7 +3358,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Is an EIP?", @@ -3113,15 +3369,16 @@ "uri":"vpc_faq_0019.html", "node_id":"vpc_faq_0019.xml", "product_code":"vpc", - "code":"167", - "des":"Each EIP can be bound to only one ECS at a time.Multiple ECSs cannot share the same EIP. An ECS and its bound EIP must be in the same region. If you want multiple ECSs in", + "code":"178", + "des":"Each EIP can be bound to only one ECS at a time.Multiple ECSs cannot share the same EIP. An ECS and its EIP must be in the same region. To enable ECSs across AZs in a VPC", "doc_type":"usermanual", "kw":"Can I Bind an EIP to Multiple ECSs?,EIPs,User Guide", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Can I Bind an EIP to Multiple ECSs?", @@ -3131,7 +3388,7 @@ "uri":"vpc_faq_0020.html", "node_id":"vpc_faq_0020.xml", "product_code":"vpc", - "code":"168", + "code":"179", "des":"Each ECS is automatically added to a security group after being created to ensure its security. The security group denies access traffic from the Internet by default. To ", "doc_type":"usermanual", "kw":"How Do I Access an ECS with an EIP Bound from the Internet?,EIPs,User Guide", @@ -3139,7 +3396,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"How Do I Access an ECS with an EIP Bound from the Internet?", @@ -3149,7 +3407,7 @@ "uri":"faq_eip_0012.html", "node_id":"faq_eip_0012.xml", "product_code":"vpc", - "code":"169", + "code":"180", "des":"No. EIPs and their associated cloud resources must be in the same region.", "doc_type":"usermanual", "kw":"Can I Bind an EIP to a Cloud Resource in Another Region?,EIPs,User Guide", @@ -3157,7 +3415,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Can I Bind an EIP to a Cloud Resource in Another Region?", @@ -3167,7 +3426,7 @@ "uri":"faq_eip_0014.html", "node_id":"faq_eip_0014.xml", "product_code":"vpc", - "code":"170", + "code":"181", "des":"The region of an EIP cannot be changed.If you assigned an EIP in region A but need an EIP in region B, you cannot directly change the region of the assigned EIP from A to", "doc_type":"usermanual", "kw":"Can I Change the Region of My EIP?,EIPs,User Guide", @@ -3175,17 +3434,37 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Can I Change the Region of My EIP?", "githuburl":"" }, + { + "uri":"en-us_topic_0000001818822858.html", + "node_id":"en-us_topic_0000001818822858.xml", + "product_code":"vpc", + "code":"182", + "des":"Table 1 lists the differences between 5_bgp, 5_mailbgp, and 5_gray EIPs.", + "doc_type":"usermanual", + "kw":"What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?,EIPs,User Guide", + "search_title":"", + "metedata":[ + { + "documenttype":"usermanual", + "prodname":"eip", + "opensource":"false" + } + ], + "title":"What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?", + "githuburl":"" + }, { "uri":"faq_peer_0000.html", "node_id":"faq_peer_0000.xml", "product_code":"vpc", - "code":"171", + "code":"183", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"VPC Peering Connections", @@ -3193,7 +3472,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"VPC Peering Connections", @@ -3203,7 +3483,7 @@ "uri":"vpc_faq_0070.html", "node_id":"vpc_faq_0070.xml", "product_code":"vpc", - "code":"172", + "code":"184", "des":"Each account can have a maximum of 50 VPC peering connections in each region by default.Number of VPC peering connections that you can create in each region between VPCs ", "doc_type":"usermanual", "kw":"How Many VPC Peering Connections Can I Create in an Account?,VPC Peering Connections,User Guide", @@ -3211,7 +3491,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"How Many VPC Peering Connections Can I Create in an Account?", @@ -3221,7 +3502,7 @@ "uri":"faq_connection_0001.html", "node_id":"faq_connection_0001.xml", "product_code":"vpc", - "code":"173", + "code":"185", "des":"A VPC peering connection only can connect VPCs in the same region.Figure 1 shows an application scenario of VPC peering connections.There are two VPCs (VPC-A and VPC-B) i", "doc_type":"usermanual", "kw":"Can a VPC Peering Connection Connect VPCs in Different Regions?,VPC Peering Connections,User Guide", @@ -3229,7 +3510,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Can a VPC Peering Connection Connect VPCs in Different Regions?", @@ -3239,7 +3521,7 @@ "uri":"vpc_faq_0069.html", "node_id":"vpc_faq_0069.xml", "product_code":"vpc", - "code":"174", + "code":"186", "des":"After a VPC peering connection is created, the local and peer VPCs cannot communicate with each other.The issues here are described in order of how likely they are to occ", "doc_type":"usermanual", "kw":"Why Did Communication Fail Between VPCs That Were Connected by a VPC Peering Connection?,VPC Peering", @@ -3247,7 +3529,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Why Did Communication Fail Between VPCs That Were Connected by a VPC Peering Connection?", @@ -3257,7 +3540,7 @@ "uri":"faq_bandwidth.html", "node_id":"faq_bandwidth.xml", "product_code":"vpc", - "code":"175", + "code":"187", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Bandwidth", @@ -3265,7 +3548,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Bandwidth", @@ -3275,15 +3559,16 @@ "uri":"vpc_faq_0011.html", "node_id":"vpc_faq_0011.xml", "product_code":"vpc", - "code":"176", - "des":"The bandwidth range is from 5 Mbit/s to 1000 Mbit/s.", + "code":"188", + "des":"The bandwidth range is from 5Mbit/s to 1000Mbit/s.", "doc_type":"usermanual", "kw":"What Is the Bandwidth Size Range?,Bandwidth,User Guide", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Is the Bandwidth Size Range?", @@ -3293,7 +3578,7 @@ "uri":"vpc_faq_0012.html", "node_id":"vpc_faq_0012.xml", "product_code":"vpc", - "code":"177", + "code":"189", "des":"There are dedicated bandwidths and shared bandwidths. A dedicated bandwidth can only be used by one EIP, but a shared bandwidth can be used by multiple EIPs.", "doc_type":"usermanual", "kw":"What Bandwidth Types Are Available?,Bandwidth,User Guide", @@ -3301,7 +3586,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Bandwidth Types Are Available?", @@ -3311,25 +3597,26 @@ "uri":"faq_bandwidth_0003.html", "node_id":"faq_bandwidth_0003.xml", "product_code":"vpc", - "code":"178", - "des":"A dedicated bandwidth can only be used by one EIP. An EIP can only be used by one cloud resource, such as an ECS, a NAT gateway, or a load balancer.A shared bandwidth can", + "code":"190", + "des":"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 ", "doc_type":"usermanual", - "kw":"What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandw", + "kw":"What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth?,Bandwidth,User Guide", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], - "title":"What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth or the Other Way Around?", + "title":"What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth?", "githuburl":"" }, { "uri":"faq_connection.html", "node_id":"faq_connection.xml", "product_code":"vpc", - "code":"179", + "code":"191", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Connectivity", @@ -3337,7 +3624,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Connectivity", @@ -3347,7 +3635,7 @@ "uri":"vpc_faq_0058.html", "node_id":"vpc_faq_0058.xml", "product_code":"vpc", - "code":"180", + "code":"192", "des":"If the two VPCs are in the same region, you can use a VPC peering connection to enable communication between them.If the two VPCs are in different regions, you can use a ", "doc_type":"usermanual", "kw":"Does a VPN Allow Communication Between Two VPCs?,Connectivity,User Guide", @@ -3355,7 +3643,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Does a VPN Allow Communication Between Two VPCs?", @@ -3365,15 +3654,16 @@ "uri":"vpc_faq_0060.html", "node_id":"vpc_faq_0060.xml", "product_code":"vpc", - "code":"181", - "des":"When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access the Internet or domain names i", + "code":"193", + "des":"When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access public websites or internal do", "doc_type":"usermanual", "kw":"Why Are Internet or Internal Domain Names in the Cloud Inaccessible Through Domain Names When My ECS", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Why Are Internet or Internal Domain Names in the Cloud Inaccessible Through Domain Names When My ECS Has Multiple NICs?", @@ -3383,7 +3673,7 @@ "uri":"vpc_faq_0073.html", "node_id":"vpc_faq_0073.xml", "product_code":"vpc", - "code":"182", + "code":"194", "des":"The priority of an EIP is higher than that of a custom route in a VPC route table. For example:The VPC route table of an ECS has a custom route with 0.0.0.0/0 as the dest", "doc_type":"usermanual", "kw":"What Are the Priorities of the Custom Route and EIP If Both Are Configured for an ECS to Enable the ", @@ -3391,7 +3681,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Are the Priorities of the Custom Route and EIP If Both Are Configured for an ECS to Enable the ECS to Access the Internet?", @@ -3401,7 +3692,7 @@ "uri":"vpc_faq_00002.html", "node_id":"vpc_faq_00002.xml", "product_code":"vpc", - "code":"183", + "code":"195", "des":"The priority of a custom route is higher than that of shared SNAT.", "doc_type":"usermanual", "kw":"What Are the Priorities of the Shared SNAT and Custom Route If Both Are Configured for an ECS to Ena", @@ -3409,7 +3700,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"What Are the Priorities of the Shared SNAT and Custom Route If Both Are Configured for an ECS to Enable the ECS to Access the Internet?", @@ -3419,7 +3711,7 @@ "uri":"vpc_faq_0076.html", "node_id":"vpc_faq_0076.xml", "product_code":"vpc", - "code":"184", + "code":"196", "des":"Users with IPv6 clients can call APIs to assign IPv6 EIPs and bind the EIPs to ECSs. Then, the users can use the EIP to access the ECSs in the VPC over the Internet.For d", "doc_type":"usermanual", "kw":"How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?,Connectivity,", @@ -3427,7 +3719,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?", @@ -3437,7 +3730,7 @@ "uri":"faq_route.html", "node_id":"faq_route.xml", "product_code":"vpc", - "code":"185", + "code":"197", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Routing", @@ -3445,7 +3738,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Routing", @@ -3455,7 +3749,7 @@ "uri":"vpc_faq_0063.html", "node_id":"vpc_faq_0063.xml", "product_code":"vpc", - "code":"186", + "code":"198", "des":"Currently, a route table can contain 100 routes.", "doc_type":"usermanual", "kw":"How Many Routes Can a Route Table Contain?,Routing,User Guide", @@ -3463,7 +3757,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"How Many Routes Can a Route Table Contain?", @@ -3473,7 +3768,7 @@ "uri":"vpc_faq_0064.html", "node_id":"vpc_faq_0064.xml", "product_code":"vpc", - "code":"187", + "code":"199", "des":"An ECS providing SNAT must have Unbind IP from MAC enabled.The destination of each route in a route table must be unique. The next hop must be a private IP address or a v", "doc_type":"usermanual", "kw":"Are There Any Restrictions on Using a Route Table?,Routing,User Guide", @@ -3481,7 +3776,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Are There Any Restrictions on Using a Route Table?", @@ -3491,7 +3787,7 @@ "uri":"vpc_faq_0066.html", "node_id":"vpc_faq_0066.xml", "product_code":"vpc", - "code":"188", + "code":"200", "des":"No. Direct Connect connections and custom routes are used in different scenarios, so the routing priorities are different.", "doc_type":"usermanual", "kw":"Do the Same Routing Priorities Apply to Direct Connect Connections and Custom Routes in the Same VPC", @@ -3499,7 +3795,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Do the Same Routing Priorities Apply to Direct Connect Connections and Custom Routes in the Same VPC?", @@ -3509,7 +3806,7 @@ "uri":"vpc_faq_00001.html", "node_id":"vpc_faq_00001.xml", "product_code":"vpc", - "code":"189", + "code":"201", "des":"No. The routing priority of custom routes and that of VPNs are the same.", "doc_type":"usermanual", "kw":"Are There Different Routing Priorities of the VPN and Custom Routes in the Same VPC?,Routing,User Gu", @@ -3517,7 +3814,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Are There Different Routing Priorities of the VPN and Custom Routes in the Same VPC?", @@ -3527,7 +3825,7 @@ "uri":"faq_security.html", "node_id":"faq_security.xml", "product_code":"vpc", - "code":"190", + "code":"202", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Security", @@ -3535,7 +3833,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Security", @@ -3545,7 +3844,7 @@ "uri":"faq_security_0003.html", "node_id":"faq_security_0003.xml", "product_code":"vpc", - "code":"191", + "code":"203", "des":"The default security group is named default and cannot be deleted.If you want to delete a security group that is associated with instances, such as cloud servers, contain", "doc_type":"usermanual", "kw":"Why Can't I Delete a Security Group?,Security,User Guide", @@ -3553,7 +3852,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Why Can't I Delete a Security Group?", @@ -3563,7 +3863,7 @@ "uri":"vpc_faq_0039.html", "node_id":"vpc_faq_0039.xml", "product_code":"vpc", - "code":"192", + "code":"204", "des":"Yes. Log in to the ECS console, switch to the page showing ECS details, and change the security group of the ECS.", "doc_type":"usermanual", "kw":"Can I Change the Security Group of an ECS?,Security,User Guide", @@ -3571,7 +3871,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Can I Change the Security Group of an ECS?", @@ -3581,7 +3882,7 @@ "uri":"vpc_faq_0059.html", "node_id":"vpc_faq_0059.xml", "product_code":"vpc", - "code":"193", + "code":"205", "des":"The TFTP daemon determines whether a configuration file specifies the port range. If you use a TFTP configuration file that allows the data channel ports to be configurab", "doc_type":"usermanual", "kw":"How Do I Configure a Security Group for Multi-Channel Protocols?,Security,User Guide", @@ -3589,7 +3890,8 @@ "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"How Do I Configure a Security Group for Multi-Channel Protocols?", @@ -3599,52 +3901,54 @@ "uri":"vpc_faq_0074.html", "node_id":"vpc_faq_0074.xml", "product_code":"vpc", - "code":"194", - "des":"Security groups are stateful. Responses to outbound traffic are allowed to go in to the instance regardless of inbound security group rules, and vice versa. Security grou", + "code":"206", + "des":"Security groups use connection tracking to track traffic to and from instances. If an inbound rule is modified, the modified rule immediately takes effect for the existin", "doc_type":"usermanual", - "kw":"Does a Security Group Rule or a Firewall Rule Immediately Take Effect for Existing Connections After", + "kw":"Does a Modified Security Group Rule or a Firewall Rule Take Effect Immediately for Existing Connecti", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], - "title":"Does a Security Group Rule or a Firewall Rule Immediately Take Effect for Existing Connections After It Is Modified?", + "title":"Does a Modified Security Group Rule or a Firewall Rule Take Effect Immediately for Existing Connections?", "githuburl":"" }, { "uri":"vpc_faq_0077.html", "node_id":"vpc_faq_0077.xml", "product_code":"vpc", - "code":"195", + "code":"207", "des":"Security group rules use the whitelist mechanism. If multiple security group rules conflict, the rules are aggregated to take effect.", "doc_type":"usermanual", - "kw":"Which Security Group Rule Has Priority When Multiple Security Group Rules Conflict?,Security,User Gu", + "kw":"Which Security Group Rule Has a High Priority When Multiple Security Group Rules Conflict?,Security,", "search_title":"", "metedata":[ { "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], - "title":"Which Security Group Rule Has Priority When Multiple Security Group Rules Conflict?", + "title":"Which Security Group Rule Has a High Priority When Multiple Security Group Rules Conflict?", "githuburl":"" }, { "uri":"vpc_faq_0103.html", "node_id":"vpc_faq_0103.xml", "product_code":"vpc", - "code":"196", + "code":"208", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", "search_title":"", "metedata":[ { - "opensource":"false", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Change History", @@ -3654,16 +3958,16 @@ "uri":"vpc_faq_0106.html", "node_id":"vpc_faq_0106.xml", "product_code":"vpc", - "code":"197", - "des":"For details about the terms involved in this document, see Glossary.", + "code":"209", + "des":"For details about the glossaries in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", "search_title":"", "metedata":[ { - "opensource":"true", "documenttype":"usermanual", - "prodname":"vpc" + "prodname":"eip", + "opensource":"false" } ], "title":"Glossary", diff --git a/docs/vpc/umn/CLASS.TXT.json b/docs/vpc/umn/CLASS.TXT.json index f4fcd523a..fa32acd51 100644 --- a/docs/vpc/umn/CLASS.TXT.json +++ b/docs/vpc/umn/CLASS.TXT.json @@ -135,7 +135,7 @@ "code":"15" }, { - "desc":"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.", + "desc":"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.S", "product_code":"vpc", "title":"Firewall", "uri":"en-us_topic_0051746676.html", @@ -144,7 +144,7 @@ "code":"16" }, { - "desc":"A virtual IP address can be shared among multiple ECSs. An ECS can have both private and virtual IP addresses, and you can access the ECS through either IP address. A vir", + "desc":"You can use either IP address to enable layer 2 and layer 3 communications in a VPC, access a different VPC using peering connections, and access cloud servers through EI", "product_code":"vpc", "title":"Virtual IP Address", "uri":"vpc_Concepts_0012.html", @@ -158,7 +158,7 @@ "title":"Region and AZ", "uri":"overview_region.html", "doc_type":"usermanual", - "p_code":"8", + "p_code":"1", "code":"18" }, { @@ -333,7 +333,7 @@ "code":"37" }, { - "desc":"You can modify the following information about a VPC:Modifying the Name and Description of a VPCModifying the CIDR Block of a VPCModifying the Name and Description of a V", + "desc":"You can modify the following information about a VPC:Modifying the Name and Description of a VPCModifying the CIDR Block of a VPCIf the secondary IPv4 CIDR block function", "product_code":"vpc", "title":"Modifying a VPC", "uri":"en-us_topic_0030969462.html", @@ -341,6 +341,24 @@ "p_code":"36", "code":"38" }, + { + "desc":"When you create a VPC, you specify a primary IPv4 CIDR block for the VPC, which cannot be changed. To extend the IP address range of your VPC, you can add a secondary CID", + "product_code":"vpc", + "title":"Adding a Secondary IPv4 CIDR Block to a VPC", + "uri":"vpc_vpc_0007.html", + "doc_type":"usermanual", + "p_code":"36", + "code":"39" + }, + { + "desc":"If a secondary CIDR block of a VPC is no longer required, you can delete it.A secondary IPv4 CIDR block of a VPC can be deleted, but the primary CIDR block cannot be dele", + "product_code":"vpc", + "title":"Deleting a Secondary IPv4 CIDR Block from a VPC", + "uri":"vpc_vpc_0008.html", + "doc_type":"usermanual", + "p_code":"36", + "code":"40" + }, { "desc":"This section describes how to delete a VPC.If you want to delete a VPC that has subnets, custom routes, or other resources, you need to delete these resources as prompted", "product_code":"vpc", @@ -348,7 +366,7 @@ "uri":"vpc_vpc_0003.html", "doc_type":"usermanual", "p_code":"36", - "code":"39" + "code":"41" }, { "desc":"You can add tags to VPCs to help you identify and organize them.You can add a tag to a VPC when creating the VPC, or you can add a tag to a created VPC on the VPC details", @@ -357,7 +375,7 @@ "uri":"vpc_vpc_0004.html", "doc_type":"usermanual", "p_code":"36", - "code":"40" + "code":"42" }, { "desc":"Information about all VPCs under your account can be exported as an Excel file to a local directory.This file records the names, ID, status, CIDR blocks, and the number o", @@ -366,7 +384,7 @@ "uri":"vpc_vpc_0006.html", "doc_type":"usermanual", "p_code":"36", - "code":"41" + "code":"43" }, { "desc":"This section describes how to view and obtain a VPC ID.If you create a VPC peering connection between two VPCs in different accounts, you need to obtain the project ID of", @@ -375,7 +393,7 @@ "uri":"vpc_vpc_0013.html", "doc_type":"usermanual", "p_code":"36", - "code":"42" + "code":"44" }, { "desc":"This section describes how to view the topology of a VPC. The topology displays the subnets in a VPC and the ECSs in the subnets.Log in to the management console.Click i", @@ -384,7 +402,7 @@ "uri":"vpc_vpc_0009.html", "doc_type":"usermanual", "p_code":"36", - "code":"43" + "code":"45" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -393,7 +411,7 @@ "uri":"vpc_0004.html", "doc_type":"usermanual", "p_code":"35", - "code":"44" + "code":"46" }, { "desc":"A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.A subnet is configured with DHCP by default. When an ECS in thi", @@ -401,8 +419,8 @@ "title":"Creating a Subnet for the VPC", "uri":"en-us_topic_0013748726.html", "doc_type":"usermanual", - "p_code":"44", - "code":"45" + "p_code":"46", + "code":"47" }, { "desc":"Modify the subnet name, NTP server address, and DNS server address.Log in to the management console.Click in the upper left corner and select the desired region and proj", @@ -410,8 +428,8 @@ "title":"Modifying a Subnet", "uri":"vpc_vpc_0001.html", "doc_type":"usermanual", - "p_code":"44", - "code":"46" + "p_code":"46", + "code":"48" }, { "desc":"You can add tags to subnets to help you identify and organize them.You can add a tag to a subnet when creating the subnet, or you can add a tag to a created subnet on the", @@ -419,8 +437,8 @@ "title":"Managing Subnet Tags", "uri":"vpc_vpc_0005.html", "doc_type":"usermanual", - "p_code":"44", - "code":"47" + "p_code":"46", + "code":"49" }, { "desc":"Information about all subnets under your account can be exported as an Excel file to a local directory. This file records the name, ID, VPC, CIDR block, and associated ro", @@ -428,8 +446,8 @@ "title":"Exporting Subnet List", "uri":"vpc_vpc_0010.html", "doc_type":"usermanual", - "p_code":"44", - "code":"48" + "p_code":"46", + "code":"50" }, { "desc":"VPC subnets have private IP addresses used by cloud resources. This section describes how to view resources that are using private IP addresses of subnets. If these resou", @@ -437,8 +455,8 @@ "title":"Viewing and Deleting Resources in a Subnet", "uri":"vpc_vpc_0011.html", "doc_type":"usermanual", - "p_code":"44", - "code":"49" + "p_code":"46", + "code":"51" }, { "desc":"A subnet is an IP address range in a VPC. This section describes how to view the used IP addresses in a subnet.Virtual IP addressesPrivate IP addressesUsed by the subnet ", @@ -446,8 +464,8 @@ "title":"Viewing IP Addresses in a Subnet", "uri":"vpc_vpc_0012.html", "doc_type":"usermanual", - "p_code":"44", - "code":"50" + "p_code":"46", + "code":"52" }, { "desc":"This section describes how to delete a subnet.If you want to delete a subnet that has custom routes, virtual IP addresses, or other resources, you need to delete these re", @@ -455,8 +473,8 @@ "title":"Deleting a Subnet", "uri":"vpc_vpc_0002.html", "doc_type":"usermanual", - "p_code":"44", - "code":"51" + "p_code":"46", + "code":"53" }, { "desc":"IPv4 and IPv6 dual-stack allows your resources, such as ECSs, to use both IPv4 and IPv6 addresses for private and public network communications. For example, if ECSs use ", @@ -465,7 +483,7 @@ "uri":"vpc_0002.html", "doc_type":"usermanual", "p_code":"35", - "code":"52" + "code":"54" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -474,16 +492,16 @@ "uri":"vpc_SecurityGroup_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"53" + "code":"55" }, { - "desc":"You can configure security groups and firewalls to increase the security of ECSs in your VPC.Security groups operate at the ECS level.Firewalls protect associated subnets", + "desc":"You can configure firewall and security group rules to protect the instances in your VPC, such as ECSs and databases.A security group protects the instances in it.A firew", "product_code":"vpc", "title":"Differences Between Security Groups and Firewalls", "uri":"en-us_topic_0052003963.html", "doc_type":"usermanual", - "p_code":"53", - "code":"54" + "p_code":"55", + "code":"56" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -491,8 +509,8 @@ "title":"Security Group", "uri":"vpc_SecurityGroup_0001.html", "doc_type":"usermanual", - "p_code":"53", - "code":"55" + "p_code":"55", + "code":"57" }, { "desc":"A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection req", @@ -500,17 +518,17 @@ "title":"Security Groups and Security Group Rules", "uri":"en-us_topic_0073379079.html", "doc_type":"usermanual", - "p_code":"55", - "code":"56" + "p_code":"57", + "code":"58" }, { - "desc":"If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) wh", + "desc":"If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance when you create it.", "product_code":"vpc", "title":"Default Security Group and Its Rules", "uri":"SecurityGroup_0003.html", "doc_type":"usermanual", - "p_code":"55", - "code":"57" + "p_code":"57", + "code":"59" }, { "desc":"Here are some common security group configuration examples for different scenarios, including remote login to ECSs, website access, and internal communication between ins", @@ -518,8 +536,17 @@ "title":"Security Group Configuration Examples", "uri":"en-us_topic_0081124350.html", "doc_type":"usermanual", - "p_code":"55", - "code":"58" + "p_code":"57", + "code":"60" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Managing a Security Group", + "uri":"vpc_SecurityGroup_0012.html", + "doc_type":"usermanual", + "p_code":"57", + "code":"61" }, { "desc":"A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The clo", @@ -527,8 +554,8 @@ "title":"Creating a Security Group", "uri":"en-us_topic_0013748715.html", "doc_type":"usermanual", - "p_code":"55", - "code":"59" + "p_code":"61", + "code":"62" }, { "desc":"You can clone a security group from one region to another to quickly apply the security group rules to ECSs in another region.You can clone a security group in the follow", @@ -536,8 +563,8 @@ "title":"Cloning a Security Group", "uri":"vpc_SecurityGroup_0009.html", "doc_type":"usermanual", - "p_code":"55", - "code":"60" + "p_code":"61", + "code":"63" }, { "desc":"After a security group is created, you can change its name and description.Log in to the management console.Click in the upper left corner and select the desired region ", @@ -545,8 +572,8 @@ "title":"Modifying a Security Group", "uri":"vpc_SecurityGroup_0010.html", "doc_type":"usermanual", - "p_code":"55", - "code":"61" + "p_code":"61", + "code":"64" }, { "desc":"If your security group is no longer required, you can delete it.The default security group is named default and cannot be deleted.If you want to delete a security group t", @@ -554,8 +581,17 @@ "title":"Deleting a Security Group", "uri":"vpc_SecurityGroup_0008.html", "doc_type":"usermanual", - "p_code":"55", - "code":"62" + "p_code":"61", + "code":"65" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Managing Security Group Rules", + "uri":"vpc_SecurityGroup_0013.html", + "doc_type":"usermanual", + "p_code":"57", + "code":"66" }, { "desc":"A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The clo", @@ -563,8 +599,8 @@ "title":"Adding a Security Group Rule", "uri":"en-us_topic_0030969470.html", "doc_type":"usermanual", - "p_code":"55", - "code":"63" + "p_code":"66", + "code":"67" }, { "desc":"The fast-adding rule function of security groups allows you to quickly add rules with common ports and protocols for remote login, ping tests, common web services, and da", @@ -572,8 +608,8 @@ "title":"Fast-Adding Security Group Rules", "uri":"SecurityGroup_0004.html", "doc_type":"usermanual", - "p_code":"55", - "code":"64" + "p_code":"66", + "code":"68" }, { "desc":"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 com", @@ -581,8 +617,8 @@ "title":"Allowing Common Ports with A Few Clicks", "uri":"SecurityGroup_0005.html", "doc_type":"usermanual", - "p_code":"55", - "code":"65" + "p_code":"66", + "code":"69" }, { "desc":"You can modify the port, protocol, and IP address of your security group rules as required to ensure the security of your instances.Log in to the management console.Click", @@ -590,8 +626,8 @@ "title":"Modifying a Security Group Rule", "uri":"vpc_SecurityGroup_0005.html", "doc_type":"usermanual", - "p_code":"55", - "code":"66" + "p_code":"66", + "code":"70" }, { "desc":"You can replicate an existing security group rule and modify it to quickly generate a new rule.Log in to the management console.Click in the upper left corner and select", @@ -599,8 +635,8 @@ "title":"Replicating a Security Group Rule", "uri":"vpc_SecurityGroup_0004.html", "doc_type":"usermanual", - "p_code":"55", - "code":"67" + "p_code":"66", + "code":"71" }, { "desc":"You can configure security group rules in an Excel file and import the rules to the security group. You can also export security group rules to an Excel file. You are adv", @@ -608,8 +644,8 @@ "title":"Importing and Exporting Security Group Rules", "uri":"vpc_SecurityGroup_0007.html", "doc_type":"usermanual", - "p_code":"55", - "code":"68" + "p_code":"66", + "code":"72" }, { "desc":"If your security group rule is no longer required, you can delete it.Security group rules use whitelists. Deleting a security group rule may result in ECS access failures", @@ -617,8 +653,17 @@ "title":"Deleting a Security Group Rule", "uri":"vpc_SecurityGroup_0006.html", "doc_type":"usermanual", - "p_code":"55", - "code":"69" + "p_code":"66", + "code":"73" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Managing Instances Associated with a Security Group", + "uri":"vpc_SecurityGroup_0014.html", + "doc_type":"usermanual", + "p_code":"57", + "code":"74" }, { "desc":"When you create an instance, the system automatically adds the instance to a security group for protection.If one security group cannot meet your requirements, you can ad", @@ -626,8 +671,8 @@ "title":"Adding an Instance to or Removing an Instance from a Security Group", "uri":"SecurityGroup_0017.html", "doc_type":"usermanual", - "p_code":"55", - "code":"70" + "p_code":"74", + "code":"75" }, { "desc":"View inbound and outbound rules of a security group used by an ECS.Log in to the management console.Click in the upper left corner and select the desired region and proj", @@ -635,17 +680,17 @@ "title":"Viewing the Security Group of an ECS", "uri":"vpc_SecurityGroup_0011.html", "doc_type":"usermanual", - "p_code":"55", - "code":"71" + "p_code":"74", + "code":"76" }, { - "desc":"Change the security group associated with an ECS NIC.Log in to the management console.Click in the upper left corner and select your region and project.Under Computing, ", + "desc":"Change the security group associated with an ECS NIC.Log in to the management console.Click in the upper left corner and select your region and project.Click and choose", "product_code":"vpc", "title":"Changing the Security Group of an ECS", "uri":"SecurityGroup_0006.html", "doc_type":"usermanual", - "p_code":"55", - "code":"72" + "p_code":"74", + "code":"77" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -653,8 +698,8 @@ "title":"Firewall", "uri":"vpc_acl_0000.html", "doc_type":"usermanual", - "p_code":"53", - "code":"73" + "p_code":"55", + "code":"78" }, { "desc":"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.F", @@ -662,8 +707,8 @@ "title":"Firewall Overview", "uri":"acl_0001.html", "doc_type":"usermanual", - "p_code":"73", - "code":"74" + "p_code":"78", + "code":"79" }, { "desc":"This section provides examples for configuring firewalls.Denying Access from a Specific PortAllowing Access from Specific Ports and ProtocolsYou might want to block TCP p", @@ -671,8 +716,17 @@ "title":"Firewall Configuration Examples", "uri":"acl_0002.html", "doc_type":"usermanual", - "p_code":"73", - "code":"75" + "p_code":"78", + "code":"80" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Managing Firewalls", + "uri":"vpc_acl_0014.html", + "doc_type":"usermanual", + "p_code":"78", + "code":"81" }, { "desc":"You can create a custom firewall. By default, a newly created firewall is disabled and has no inbound or outbound rules, or any subnets associated.By default, you can cre", @@ -680,89 +734,17 @@ "title":"Creating a Firewall", "uri":"en-us_topic_0051746698.html", "doc_type":"usermanual", - "p_code":"73", - "code":"76" - }, - { - "desc":"Add an inbound or outbound rule based on your network security requirements.A firewall can contain no more than 20 rules in one direction, or performance will deteriorate", - "product_code":"vpc", - "title":"Adding a Firewall Rule", - "uri":"en-us_topic_0051746702.html", - "doc_type":"usermanual", - "p_code":"73", - "code":"77" - }, - { - "desc":"You can associate a firewall with a subnet to protect resources in the subnet.You can associate a firewall with multiple subnets. However, a subnet can only be associated", - "product_code":"vpc", - "title":"Associating Subnets with a Firewall", - "uri":"en-us_topic_0051746700.html", - "doc_type":"usermanual", - "p_code":"73", - "code":"78" - }, - { - "desc":"You can disassociate a subnet from its firewall based on your network requirements.Log in to the management console.Click in the upper left corner and select the desired", - "product_code":"vpc", - "title":"Disassociating Subnets from a Firewall", - "uri":"vpc_acl_0003.html", - "doc_type":"usermanual", - "p_code":"73", - "code":"79" - }, - { - "desc":"If you need a rule to take effect before or after a specific rule, you can insert that rule before or after the specific rule.If multiple firewall rules conflict, only th", - "product_code":"vpc", - "title":"Changing the Sequence of a Firewall Rule", - "uri":"vpc_acl_0004.html", - "doc_type":"usermanual", - "p_code":"73", - "code":"80" - }, - { - "desc":"Modify an inbound or outbound firewall rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the de", - "product_code":"vpc", - "title":"Modifying a Firewall Rule", - "uri":"vpc_acl_0005.html", - "doc_type":"usermanual", - "p_code":"73", - "code":"81" - }, - { - "desc":"Enable or disable an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the ", - "product_code":"vpc", - "title":"Enabling or Disabling a Firewall Rule", - "uri":"vpc_acl_0006.html", - "doc_type":"usermanual", - "p_code":"73", + "p_code":"81", "code":"82" }, - { - "desc":"Delete an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the desired reg", - "product_code":"vpc", - "title":"Deleting a Firewall Rule", - "uri":"vpc_acl_0007.html", - "doc_type":"usermanual", - "p_code":"73", - "code":"83" - }, - { - "desc":"View details about a firewall.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 a", - "product_code":"vpc", - "title":"Viewing a Firewall", - "uri":"vpc_acl_0009.html", - "doc_type":"usermanual", - "p_code":"73", - "code":"84" - }, { "desc":"Modify the name and description of a firewall.Log in to the management console.Click in the upper left corner and select the desired region and project.Click in the upp", "product_code":"vpc", "title":"Modifying a Firewall", "uri":"vpc_acl_0010.html", "doc_type":"usermanual", - "p_code":"73", - "code":"85" + "p_code":"81", + "code":"83" }, { "desc":"After a firewall is created, you may need to enable it based on network security requirements. You can also disable an enabled firewall if needed. Before enabling a firew", @@ -770,8 +752,17 @@ "title":"Enabling or Disabling a Firewall", "uri":"vpc_acl_0011.html", "doc_type":"usermanual", - "p_code":"73", - "code":"86" + "p_code":"81", + "code":"84" + }, + { + "desc":"View details about a firewall.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 a", + "product_code":"vpc", + "title":"Viewing a Firewall", + "uri":"vpc_acl_0009.html", + "doc_type":"usermanual", + "p_code":"81", + "code":"85" }, { "desc":"Delete a firewall when it is no longer required.Log in to the management console.Click in the upper left corner and select the desired region and project.Click in the u", @@ -779,9 +770,90 @@ "title":"Deleting a Firewall", "uri":"vpc_acl_0012.html", "doc_type":"usermanual", - "p_code":"73", + "p_code":"81", + "code":"86" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Management Firewall Rules", + "uri":"vpc_acl_0015.html", + "doc_type":"usermanual", + "p_code":"78", "code":"87" }, + { + "desc":"Add an inbound or outbound rule based on your network security requirements.A firewall can contain no more than 20 rules in one direction, or performance will deteriorate", + "product_code":"vpc", + "title":"Adding a Firewall Rule", + "uri":"en-us_topic_0051746702.html", + "doc_type":"usermanual", + "p_code":"87", + "code":"88" + }, + { + "desc":"Modify an inbound or outbound firewall rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the de", + "product_code":"vpc", + "title":"Modifying a Firewall Rule", + "uri":"vpc_acl_0005.html", + "doc_type":"usermanual", + "p_code":"87", + "code":"89" + }, + { + "desc":"If you need a rule to take effect before or after a specific rule, you can insert that rule before or after the specific rule.If multiple firewall rules conflict, only th", + "product_code":"vpc", + "title":"Changing the Sequence of a Firewall Rule", + "uri":"vpc_acl_0004.html", + "doc_type":"usermanual", + "p_code":"87", + "code":"90" + }, + { + "desc":"Enable or disable an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the ", + "product_code":"vpc", + "title":"Enabling or Disabling a Firewall Rule", + "uri":"vpc_acl_0006.html", + "doc_type":"usermanual", + "p_code":"87", + "code":"91" + }, + { + "desc":"Delete an inbound or outbound rule based on your network security requirements.Log in to the management console.Click in the upper left corner and select the desired reg", + "product_code":"vpc", + "title":"Deleting a Firewall Rule", + "uri":"vpc_acl_0007.html", + "doc_type":"usermanual", + "p_code":"87", + "code":"92" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Managing Subnets Associated with a Firewall", + "uri":"vpc_acl_0016.html", + "doc_type":"usermanual", + "p_code":"78", + "code":"93" + }, + { + "desc":"You can associate a firewall with a subnet to protect resources in the subnet.You can associate a firewall with multiple subnets. However, a subnet can only be associated", + "product_code":"vpc", + "title":"Associating Subnets with a Firewall", + "uri":"en-us_topic_0051746700.html", + "doc_type":"usermanual", + "p_code":"93", + "code":"94" + }, + { + "desc":"You can disassociate a subnet from its firewall based on your network requirements.Log in to the management console.Click in the upper left corner and select the desired", + "product_code":"vpc", + "title":"Disassociating Subnets from a Firewall", + "uri":"vpc_acl_0003.html", + "doc_type":"usermanual", + "p_code":"93", + "code":"95" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"vpc", @@ -789,7 +861,7 @@ "uri":"vpc_eip_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"88" + "code":"96" }, { "desc":"You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.Note the following when you use EIPs of the Dedicated Load Balancer (5_gray) type:In e", @@ -797,8 +869,8 @@ "title":"Assigning an EIP and Binding It to an ECS", "uri":"en-us_topic_0013748738.html", "doc_type":"usermanual", - "p_code":"88", - "code":"89" + "p_code":"96", + "code":"97" }, { "desc":"If you no longer need an EIP, unbind it from the ECS and release the EIP to avoid wasting network resources.In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type ca", @@ -806,8 +878,8 @@ "title":"Unbinding an EIP from an ECS and Releasing the EIP", "uri":"vpc_eip_0001.html", "doc_type":"usermanual", - "p_code":"88", - "code":"90" + "p_code":"96", + "code":"98" }, { "desc":"Modify the EIP bandwidth name or size.This section describes how to modify the dedicated bandwidth or shared bandwidth of an EIP. For details about how to modify a shared", @@ -815,8 +887,8 @@ "title":"Modifying an EIP Bandwidth", "uri":"en-us_topic_0013748743.html", "doc_type":"usermanual", - "p_code":"88", - "code":"91" + "p_code":"96", + "code":"99" }, { "desc":"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", @@ -824,8 +896,8 @@ "title":"Exporting EIP Information", "uri":"eip_0003.html", "doc_type":"usermanual", - "p_code":"88", - "code":"92" + "p_code":"96", + "code":"100" }, { "desc":"Tags can be added to EIPs to facilitate EIP identification and administration. You can add a tag to an EIP when assigning the EIP. Alternatively, you can add a tag to an ", @@ -833,8 +905,8 @@ "title":"Managing EIP Tags", "uri":"en-us_topic_0068145818.html", "doc_type":"usermanual", - "p_code":"88", - "code":"93" + "p_code":"96", + "code":"101" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -843,7 +915,7 @@ "uri":"vpc010003.html", "doc_type":"usermanual", "p_code":"", - "code":"94" + "code":"102" }, { "desc":"A shared bandwidth can be shared by multiple EIPs and controls the data transfer rate on these EIPs in a centralized manner. All ECSs, BMSs, and load balancers that have ", @@ -851,8 +923,8 @@ "title":"Shared Bandwidth Overview", "uri":"vpc010004.html", "doc_type":"usermanual", - "p_code":"94", - "code":"95" + "p_code":"102", + "code":"103" }, { "desc":"Assign a shared bandwidth for use with EIPs.Log in to the management console.Click in the upper left corner and select the desired region and project.Click in the upper", @@ -860,8 +932,8 @@ "title":"Assigning a Shared Bandwidth", "uri":"vpc010005.html", "doc_type":"usermanual", - "p_code":"94", - "code":"96" + "p_code":"102", + "code":"104" }, { "desc":"Add EIPs to a shared bandwidth and the EIPs can then share that bandwidth. You can add multiple EIPs to a shared bandwidth at the same time.The type of EIPs must be the s", @@ -869,8 +941,8 @@ "title":"Adding EIPs to a Shared Bandwidth", "uri":"vpc010006.html", "doc_type":"usermanual", - "p_code":"94", - "code":"97" + "p_code":"102", + "code":"105" }, { "desc":"Remove EIPs that are no longer required from a shared bandwidth if needed.Log in to the management console.Click in the upper left corner and select the desired region a", @@ -878,8 +950,8 @@ "title":"Removing EIPs from a Shared Bandwidth", "uri":"vpc010007.html", "doc_type":"usermanual", - "p_code":"94", - "code":"98" + "p_code":"102", + "code":"106" }, { "desc":"You can modify the name and size of a shared bandwidth as required.Log in to the management console.Click in the upper left corner and select the desired region and proj", @@ -887,8 +959,8 @@ "title":"Modifying a Shared Bandwidth", "uri":"vpc010008.html", "doc_type":"usermanual", - "p_code":"94", - "code":"99" + "p_code":"102", + "code":"107" }, { "desc":"Delete a shared bandwidth when it is no longer required.Before deleting a shared bandwidth, remove all the EIPs associated with it. For details, see Removing EIPs from a ", @@ -896,8 +968,17 @@ "title":"Deleting a Shared Bandwidth", "uri":"vpc010009.html", "doc_type":"usermanual", - "p_code":"94", - "code":"100" + "p_code":"102", + "code":"108" + }, + { + "desc":"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 I", + "product_code":"vpc", + "title":"Exporting Shared Bandwidths", + "uri":"vpc010010.html", + "doc_type":"usermanual", + "p_code":"102", + "code":"109" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -906,7 +987,7 @@ "uri":"vpc_route01_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"101" + "code":"110" }, { "desc":"A route table contains a set of routes that are used to determine where network traffic from your subnets in a VPC is directed. Each subnet must be associated with a rout", @@ -914,8 +995,17 @@ "title":"Route Tables and Routes", "uri":"vpc_route01_0001.html", "doc_type":"usermanual", - "p_code":"101", - "code":"102" + "p_code":"110", + "code":"111" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Managing Route Tables", + "uri":"vpc_route01_0016.html", + "doc_type":"usermanual", + "p_code":"110", + "code":"112" }, { "desc":"A VPC automatically comes with a default route table. If your default route table cannot meet your service requirements, you can create a custom route table.By default, e", @@ -923,8 +1013,8 @@ "title":"Creating a Custom Route Table", "uri":"vpc_route01_0005.html", "doc_type":"usermanual", - "p_code":"101", - "code":"103" + "p_code":"112", + "code":"113" }, { "desc":"After a subnet is created, the system associates the subnet with the default route table of its VPC. If you want to use specific routes for a subnet, you can associate th", @@ -932,8 +1022,8 @@ "title":"Associating a Route Table with a Subnet", "uri":"vpc_route01_0007.html", "doc_type":"usermanual", - "p_code":"101", - "code":"104" + "p_code":"112", + "code":"114" }, { "desc":"You can change the route table for a subnet. If the route table for a subnet is changed, routes in the new route table will apply to all cloud resources in the subnet.Log", @@ -941,8 +1031,8 @@ "title":"Changing the Route Table Associated with a Subnet", "uri":"vpc_route01_0008.html", "doc_type":"usermanual", - "p_code":"101", - "code":"105" + "p_code":"112", + "code":"115" }, { "desc":"This section describes how to view the route table associated with a subnet.Log in to the management console.Click in the upper left corner and select the desired region", @@ -950,8 +1040,8 @@ "title":"Viewing the Route Table Associated with a Subnet", "uri":"vpc_route01_0015.html", "doc_type":"usermanual", - "p_code":"101", - "code":"106" + "p_code":"112", + "code":"116" }, { "desc":"This section describes how to view detailed information about a route table, including:Basic information, such as name, type (default or custom), and ID of the route tabl", @@ -959,8 +1049,8 @@ "title":"Viewing Route Table Information", "uri":"vpc_route01_0009.html", "doc_type":"usermanual", - "p_code":"101", - "code":"107" + "p_code":"112", + "code":"117" }, { "desc":"Information about all route tables under your account can be exported as an Excel file to a local directory. This file records the name, ID, VPC, type, and number of asso", @@ -968,8 +1058,8 @@ "title":"Exporting Route Table Information", "uri":"vpc_route01_0014.html", "doc_type":"usermanual", - "p_code":"101", - "code":"108" + "p_code":"112", + "code":"118" }, { "desc":"This section describes how to delete a custom route table.The default route table cannot be deleted.A custom route table with a subnet associated cannot be deleted direct", @@ -977,8 +1067,17 @@ "title":"Deleting a Route Table", "uri":"vpc_route01_0010.html", "doc_type":"usermanual", - "p_code":"101", - "code":"109" + "p_code":"112", + "code":"119" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"vpc", + "title":"Managing Routes", + "uri":"vpc_route01_0017.html", + "doc_type":"usermanual", + "p_code":"110", + "code":"120" }, { "desc":"Each route table contains a default system route, which indicates that ECSs in a VPC can communicate with each other. You can also add custom routes as required to forwar", @@ -986,8 +1085,8 @@ "title":"Adding a Custom Route", "uri":"vpc_route01_0006.html", "doc_type":"usermanual", - "p_code":"101", - "code":"110" + "p_code":"120", + "code":"121" }, { "desc":"This section describes how to modify a custom route in a route table.System routes cannot be modified.When you create a VPC endpoint, VPN or Direct Connect connection, th", @@ -995,8 +1094,8 @@ "title":"Modifying a Route", "uri":"vpc_route01_0011.html", "doc_type":"usermanual", - "p_code":"101", - "code":"111" + "p_code":"120", + "code":"122" }, { "desc":"This section describes how to replicate routes among all route tables of a VPC. VPC route tables include the default and custom route tables.Table 1 shows whether routes ", @@ -1004,8 +1103,8 @@ "title":"Replicating a Route", "uri":"vpc_route01_0013.html", "doc_type":"usermanual", - "p_code":"101", - "code":"112" + "p_code":"120", + "code":"123" }, { "desc":"This section describes how to delete a custom route from a route table.System routes cannot be deleted.The routes automatically delivered by VPN or Direct Connect to the ", @@ -1013,8 +1112,8 @@ "title":"Deleting a Route", "uri":"vpc_route01_0012.html", "doc_type":"usermanual", - "p_code":"101", - "code":"113" + "p_code":"120", + "code":"124" }, { "desc":"Together with VPC route tables, you can configure SNAT on an ECS to enable other ECSs that have no EIPs bound in the same VPC to access the Internet through this ECS.The ", @@ -1022,8 +1121,8 @@ "title":"Configuring an SNAT Server", "uri":"vpc_route_0004.html", "doc_type":"usermanual", - "p_code":"101", - "code":"114" + "p_code":"110", + "code":"125" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1032,7 +1131,7 @@ "uri":"vpc_peering_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"115" + "code":"126" }, { "desc":"A VPC peering connection is a networking connection that connects two VPCs for them to communicate using private IP addresses. The VPCs to be peered can be in the same ac", @@ -1040,8 +1139,8 @@ "title":"VPC Peering Connection Overview", "uri":"en-us_topic_0046655036.html", "doc_type":"usermanual", - "p_code":"115", - "code":"116" + "p_code":"126", + "code":"127" }, { "desc":"A VPC peering connection is a networking connection between two VPCs in the same region and enables them to communicate. Table 1 lists different scenarios of using VPC pe", @@ -1049,8 +1148,8 @@ "title":"VPC Peering Connection Usage Examples", "uri":"en-us_topic_0046809840.html", "doc_type":"usermanual", - "p_code":"115", - "code":"117" + "p_code":"126", + "code":"128" }, { "desc":"If two VPCs from the same region cannot communicate with each other, you can use a VPC peering connection. This section describes how to create a VPC peering connection b", @@ -1058,8 +1157,8 @@ "title":"Creating a VPC Peering Connection with Another VPC in Your Account", "uri":"en-us_topic_0046655037.html", "doc_type":"usermanual", - "p_code":"115", - "code":"118" + "p_code":"126", + "code":"129" }, { "desc":"If two VPCs from the same region cannot communicate with each other, you can use a VPC peering connection. This section describes how to create a VPC peering connection b", @@ -1067,8 +1166,8 @@ "title":"Creating a VPC Peering Connection with a VPC in Another Account", "uri":"en-us_topic_0046655038.html", "doc_type":"usermanual", - "p_code":"115", - "code":"119" + "p_code":"126", + "code":"130" }, { "desc":"If you create a VPC peering connection between two VPCs in different accounts, you can refer to this section to obtain the project ID of the region that the peer VPC resi", @@ -1076,8 +1175,8 @@ "title":"Obtaining the Peer Project ID of a VPC Peering Connection", "uri":"vpc_peering_0005.html", "doc_type":"usermanual", - "p_code":"115", - "code":"120" + "p_code":"126", + "code":"131" }, { "desc":"This section describes how to modify the name of a VPC peering connection.Either owner of a VPC in a peering connection can modify the VPC peering connection in any state", @@ -1085,8 +1184,8 @@ "title":"Modifying a VPC Peering Connection", "uri":"vpc_peering_0002.html", "doc_type":"usermanual", - "p_code":"115", - "code":"121" + "p_code":"126", + "code":"132" }, { "desc":"This section describes how to view basic information about a VPC peering connection, including the connection name, status, and information about the local and peer VPCs.", @@ -1094,8 +1193,8 @@ "title":"Viewing VPC Peering Connections", "uri":"vpc_peering_0001.html", "doc_type":"usermanual", - "p_code":"115", - "code":"122" + "p_code":"126", + "code":"133" }, { "desc":"This section describes how to delete a VPC peering connection.Either owner of a VPC in a peering connection can delete the VPC peering connection in any state.The owner o", @@ -1103,8 +1202,8 @@ "title":"Deleting a VPC Peering Connection", "uri":"vpc_peering_0003.html", "doc_type":"usermanual", - "p_code":"115", - "code":"123" + "p_code":"126", + "code":"134" }, { "desc":"This section describes how to modify the routes added for a VPC peering connection in the route tables of the local and peer VPCs.Modifying Routes of a VPC Peering Connec", @@ -1112,8 +1211,8 @@ "title":"Modifying Routes Configured for a VPC Peering Connection", "uri":"vpc_peering_0007.html", "doc_type":"usermanual", - "p_code":"115", - "code":"124" + "p_code":"126", + "code":"135" }, { "desc":"This section describes how to view the routes added to the route tables of local and peer VPCs of a VPC peering connection.Viewing Routes of a VPC Peering Connection Betw", @@ -1121,8 +1220,8 @@ "title":"Viewing Routes Configured for a VPC Peering Connection", "uri":"vpc_peering_0004.html", "doc_type":"usermanual", - "p_code":"115", - "code":"125" + "p_code":"126", + "code":"136" }, { "desc":"This section describes how to delete routes from the route tables of the local and peer VPCs connected by a VPC peering connection.Deleting Routes of a VPC Peering Connec", @@ -1130,8 +1229,8 @@ "title":"Deleting Routes Configured for a VPC Peering Connection", "uri":"vpc_peering_0006.html", "doc_type":"usermanual", - "p_code":"115", - "code":"126" + "p_code":"126", + "code":"137" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1140,7 +1239,7 @@ "uri":"FlowLog_0001.html", "doc_type":"usermanual", "p_code":"", - "code":"127" + "code":"138" }, { "desc":"A VPC flow log records information about the traffic going to and from a VPC. VPC flow logs help you monitor network traffic, analyze network attacks, and determine wheth", @@ -1148,8 +1247,8 @@ "title":"VPC Flow Log Overview", "uri":"FlowLog_0002.html", "doc_type":"usermanual", - "p_code":"127", - "code":"128" + "p_code":"138", + "code":"139" }, { "desc":"A VPC flow log records information about the traffic going to and from a VPC.Ensure that the following operations have been performed on the LTS console:Create a log grou", @@ -1157,8 +1256,8 @@ "title":"Creating a VPC Flow Log", "uri":"FlowLog_0003.html", "doc_type":"usermanual", - "p_code":"127", - "code":"129" + "p_code":"138", + "code":"140" }, { "desc":"View information about your flow log record.The capture window is approximately 10 minutes, which indicates that a flow log record will be generated every 10 minutes. Aft", @@ -1166,8 +1265,8 @@ "title":"Viewing a VPC Flow Log", "uri":"FlowLog_0004.html", "doc_type":"usermanual", - "p_code":"127", - "code":"130" + "p_code":"138", + "code":"141" }, { "desc":"After a VPC flow log is created, the VPC flow log is automatically enabled. If you do not need to record flow log data, you can disable the corresponding VPC flow log. A ", @@ -1175,8 +1274,8 @@ "title":"Enabling or Disabling VPC Flow Log", "uri":"FlowLog_0006.html", "doc_type":"usermanual", - "p_code":"127", - "code":"131" + "p_code":"138", + "code":"142" }, { "desc":"Delete a VPC flow log that is not required. Deleting a VPC flow log will not delete the existing flow log records in LTS.If a NIC that uses a VPC flow log is deleted, the", @@ -1184,8 +1283,8 @@ "title":"Deleting a VPC Flow Log", "uri":"FlowLog_0005.html", "doc_type":"usermanual", - "p_code":"127", - "code":"132" + "p_code":"138", + "code":"143" }, { "desc":"Direct Connect allows you to establish a dedicated network connection between your data center and the cloud platform. With Direct Connect, you can establish a private co", @@ -1194,7 +1293,7 @@ "uri":"vpc_dc_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"133" + "code":"144" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1203,7 +1302,7 @@ "uri":"vpc_vip_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"134" + "code":"145" }, { "desc":"A virtual IP address can be shared among multiple ECSs. An ECS can have both private and virtual IP addresses, and you can access the ECS through either IP address. A vir", @@ -1211,8 +1310,8 @@ "title":"Virtual IP Address Overview", "uri":"vpc_vip_0001.html", "doc_type":"usermanual", - "p_code":"134", - "code":"135" + "p_code":"145", + "code":"146" }, { "desc":"If an ECS requires a virtual IP address or if a virtual IP address needs to be reserved, you can assign a virtual IP address from the subnet.Log in to the management cons", @@ -1220,8 +1319,8 @@ "title":"Assigning a Virtual IP Address", "uri":"vpc_vip_0002.html", "doc_type":"usermanual", - "p_code":"134", - "code":"136" + "p_code":"145", + "code":"147" }, { "desc":"You can use a virtual IP address and an EIP together.If you bind a virtual IP address to ECSs that work in active/standby pairs and bind an EIP to the virtual IP address,", @@ -1229,8 +1328,8 @@ "title":"Binding a Virtual IP Address to an EIP or ECS", "uri":"en-us_topic_0067802474.html", "doc_type":"usermanual", - "p_code":"134", - "code":"137" + "p_code":"145", + "code":"148" }, { "desc":"This section describes how to bind a virtual IP address to an EIP.You have assigned an EIP.Log in to the management console.Click in the upper left corner and select the", @@ -1238,53 +1337,8 @@ "title":"Binding a Virtual IP Address to an EIP", "uri":"vpc_vip_0003.html", "doc_type":"usermanual", - "p_code":"134", - "code":"138" - }, - { - "desc":"Configure the ECS networking based on Networking.Create a VPN.The VPN can be used to access the virtual IP address of the ECS.", - "product_code":"vpc", - "title":"Using a VPN to Access a Virtual IP Address", - "uri":"vpc_vip_0004.html", - "doc_type":"usermanual", - "p_code":"134", - "code":"139" - }, - { - "desc":"Configure the ECS networking based on Networking.Create a Direct Connect connection.The created Direct Connect connection can be used to access the virtual IP address of ", - "product_code":"vpc", - "title":"Using a Direct Connect Connection to Access the Virtual IP Address", - "uri":"vpc_vip_0005.html", - "doc_type":"usermanual", - "p_code":"134", - "code":"140" - }, - { - "desc":"Configure the ECS networking based on Networking.Create a VPC peering connection.You can access the virtual IP address of the ECS through the VPC peering connection.", - "product_code":"vpc", - "title":"Using a VPC Peering Connection to Access the Virtual IP Address", - "uri":"vpc_vip_0006.html", - "doc_type":"usermanual", - "p_code":"134", - "code":"141" - }, - { - "desc":"If a virtual IP address is used in an active/standby scenario, disable IP forwarding on the standby ECS.Log in to the ECS.Run the following command to switch to user root", - "product_code":"vpc", - "title":"Disabling IP Forwarding on the Standby ECS", - "uri":"vpc_vip_0007.html", - "doc_type":"usermanual", - "p_code":"134", - "code":"142" - }, - { - "desc":"If a virtual IP address is used in an HA load balancing cluster, you need to disable source/destination check for ECS NICs.Log in to the management console.Click in the ", - "product_code":"vpc", - "title":"Disabling Source and Destination Check (HA Load Balancing Cluster Scenario)", - "uri":"vpc_vip_0008.html", - "doc_type":"usermanual", - "p_code":"134", - "code":"143" + "p_code":"145", + "code":"149" }, { "desc":"This section describes how to unbind a virtual IP address from an ECS.Log in to the management console.Click in the upper left corner and select the desired region and p", @@ -1292,8 +1346,8 @@ "title":"Unbinding a Virtual IP Address from an Instance", "uri":"vpc_vip_0010.html", "doc_type":"usermanual", - "p_code":"134", - "code":"144" + "p_code":"145", + "code":"150" }, { "desc":"This section describes how to unbind a virtual IP address from an EIP.Log in to the management console.Click in the upper left corner and select the desired region and p", @@ -1301,8 +1355,8 @@ "title":"Unbinding a Virtual IP Address from an EIP", "uri":"vpc_vip_0011.html", "doc_type":"usermanual", - "p_code":"134", - "code":"145" + "p_code":"145", + "code":"151" }, { "desc":"If you no longer need a virtual IP address or a reserved virtual IP address, you can release it to avoid wasting resources.If you want to release a virtual IP address tha", @@ -1310,8 +1364,53 @@ "title":"Releasing a Virtual IP Address", "uri":"vpc_vip_0009.html", "doc_type":"usermanual", - "p_code":"134", - "code":"146" + "p_code":"145", + "code":"152" + }, + { + "desc":"If a virtual IP address is used in an active/standby scenario, disable IP forwarding on the standby ECS.Log in to the ECS.Run the following command to switch to user root", + "product_code":"vpc", + "title":"Disabling IP Forwarding on the Standby ECS", + "uri":"vpc_vip_0007.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"153" + }, + { + "desc":"If a virtual IP address is used in an HA load balancing cluster, you need to disable source/destination check for ECS NICs.Log in to the management console.Click in the ", + "product_code":"vpc", + "title":"Disabling Source and Destination Check (HA Load Balancing Cluster Scenario)", + "uri":"vpc_vip_0008.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"154" + }, + { + "desc":"Configure the ECS networking based on Networking.Create a VPN.The VPN can be used to access the virtual IP address of the ECS.", + "product_code":"vpc", + "title":"Using a VPN to Access a Virtual IP Address", + "uri":"vpc_vip_0004.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"155" + }, + { + "desc":"Configure the ECS networking based on Networking.Create a Direct Connect connection.The created Direct Connect connection can be used to access the virtual IP address of ", + "product_code":"vpc", + "title":"Using a Direct Connect Connection to Access the Virtual IP Address", + "uri":"vpc_vip_0005.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"156" + }, + { + "desc":"Configure the ECS networking based on Networking.Create a VPC peering connection.You can access the virtual IP address of the ECS through the VPC peering connection.", + "product_code":"vpc", + "title":"Using a VPC Peering Connection to Access the Virtual IP Address", + "uri":"vpc_vip_0006.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"157" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1320,7 +1419,7 @@ "uri":"vpc010011.html", "doc_type":"usermanual", "p_code":"", - "code":"147" + "code":"158" }, { "desc":"This section describes the namespace, list, and measurement dimensions of EIP and bandwidth metrics that you can check on Cloud Eye. You can use APIs or the Cloud Eye con", @@ -1328,8 +1427,8 @@ "title":"Supported Metrics", "uri":"vpc010012.html", "doc_type":"usermanual", - "p_code":"147", - "code":"148" + "p_code":"158", + "code":"159" }, { "desc":"You can view the bandwidth and EIP usage on the Elastic IP and Bandwidth or Cloud Eye console.You can view the inbound bandwidth, outbound bandwidth, inbound bandwidth us", @@ -1337,8 +1436,8 @@ "title":"Viewing Metrics", "uri":"vpc010013.html", "doc_type":"usermanual", - "p_code":"147", - "code":"149" + "p_code":"158", + "code":"160" }, { "desc":"You can configure alarm rules to customize the monitored objects and notification policies. You can learn your resource statuses at any time.Log in to the management cons", @@ -1346,8 +1445,8 @@ "title":"Creating an Alarm Rule", "uri":"vpc010014.html", "doc_type":"usermanual", - "p_code":"147", - "code":"150" + "p_code":"158", + "code":"161" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1356,7 +1455,7 @@ "uri":"permission_0001.html", "doc_type":"usermanual", "p_code":"", - "code":"151" + "code":"162" }, { "desc":"This section describes how to use IAM to implement fine-grained permissions control for your VPC resources. With IAM, you can:Create IAM users for employees based on your", @@ -1364,8 +1463,8 @@ "title":"Creating a User and Granting VPC Permissions", "uri":"permission_0003.html", "doc_type":"usermanual", - "p_code":"151", - "code":"152" + "p_code":"162", + "code":"163" }, { "desc":"Custom policies can be created to supplement the system-defined policies of VPC. For the actions supported for custom policies, see Permissions Policies and Supported Act", @@ -1373,8 +1472,8 @@ "title":"VPC Custom Policies", "uri":"permission_0004.html", "doc_type":"usermanual", - "p_code":"151", - "code":"153" + "p_code":"162", + "code":"164" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1383,7 +1482,7 @@ "uri":"vpc_faq_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"154" + "code":"165" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1391,8 +1490,8 @@ "title":"General Questions", "uri":"faq_common.html", "doc_type":"usermanual", - "p_code":"154", - "code":"155" + "p_code":"165", + "code":"166" }, { "desc":"A quota limits the quantity of a resource available to users, thereby preventing spikes in the usage of the resource. For example, a VPC quota limits the number of VPCs t", @@ -1400,8 +1499,8 @@ "title":"What Is a Quota?", "uri":"vpc_faq_0051.html", "doc_type":"usermanual", - "p_code":"155", - "code":"156" + "p_code":"166", + "code":"167" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1409,17 +1508,17 @@ "title":"VPCs and Subnets", "uri":"faq_vpc.html", "doc_type":"usermanual", - "p_code":"154", - "code":"157" + "p_code":"165", + "code":"168" }, { - "desc":"The Virtual Private Cloud (VPC) service enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security a", + "desc":"Virtual Private Cloud (VPC) enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security and simplifyi", "product_code":"vpc", "title":"What Is Virtual Private Cloud?", "uri":"vpc_faq_0001.html", "doc_type":"usermanual", - "p_code":"157", - "code":"158" + "p_code":"168", + "code":"169" }, { "desc":"The following table lists the private CIDR blocks that you can specify when creating a VPC. Consider the following when selecting a VPC CIDR block:Number of IP addresses:", @@ -1427,8 +1526,8 @@ "title":"Which CIDR Blocks Are Available for the VPC Service?", "uri":"vpc_faq_0004.html", "doc_type":"usermanual", - "p_code":"157", - "code":"159" + "p_code":"168", + "code":"170" }, { "desc":"Subnets in the same VPC can communicate with each other by default.VPCs are isolated from each other. Subnets from different VPCs cannot communicate with each other. You ", @@ -1436,8 +1535,8 @@ "title":"Can Subnets Communicate with Each Other?", "uri":"vpc_faq_0005.html", "doc_type":"usermanual", - "p_code":"157", - "code":"160" + "p_code":"168", + "code":"171" }, { "desc":"A subnet is an IP address range from a VPC. The VPC service supports CIDR blocks 10.0.0.0/8-24, 172.16.0.0/12-24, and 192.168.0.0/16-24.Subnets must reside within your VP", @@ -1445,8 +1544,8 @@ "title":"What Subnet CIDR Blocks Are Available?", "uri":"vpc_faq_0006.html", "doc_type":"usermanual", - "p_code":"157", - "code":"161" + "p_code":"168", + "code":"172" }, { "desc":"Each account can have a maximum of 100 subnets. If the number of subnets cannot meet your service requirements, request a quota increase. For details, see What Is a Quota", @@ -1454,8 +1553,8 @@ "title":"How Many Subnets Can I Create?", "uri":"vpc_faq_0009.html", "doc_type":"usermanual", - "p_code":"157", - "code":"162" + "p_code":"168", + "code":"173" }, { "desc":"The network ID of the subnet is the neutron_network_id in the subnet fields in Subnet > Creating a Subnet in the Virtual Private Cloud API Reference.Parameter neutron_net", @@ -1463,8 +1562,8 @@ "title":"What Are the Differences Between the Network ID and Subnet ID of a Subnet?", "uri":"vpc_faq_0094.html", "doc_type":"usermanual", - "p_code":"157", - "code":"163" + "p_code":"168", + "code":"174" }, { "desc":"If VPCs and subnets are being used by other resources, you need to delete these resources first based on the prompts on the console before deleting the VPCs and subnets. ", @@ -1472,8 +1571,8 @@ "title":"Why Can't I Delete My VPCs and Subnets?", "uri":"vpc_faq_0075.html", "doc_type":"usermanual", - "p_code":"157", - "code":"164" + "p_code":"168", + "code":"175" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1481,8 +1580,8 @@ "title":"EIPs", "uri":"faq_eip.html", "doc_type":"usermanual", - "p_code":"154", - "code":"165" + "p_code":"165", + "code":"176" }, { "desc":"The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to ", @@ -1490,17 +1589,17 @@ "title":"What Is an EIP?", "uri":"vpc_faq_0013.html", "doc_type":"usermanual", - "p_code":"165", - "code":"166" + "p_code":"176", + "code":"177" }, { - "desc":"Each EIP can be bound to only one ECS at a time.Multiple ECSs cannot share the same EIP. An ECS and its bound EIP must be in the same region. If you want multiple ECSs in", + "desc":"Each EIP can be bound to only one ECS at a time.Multiple ECSs cannot share the same EIP. An ECS and its EIP must be in the same region. To enable ECSs across AZs in a VPC", "product_code":"vpc", "title":"Can I Bind an EIP to Multiple ECSs?", "uri":"vpc_faq_0019.html", "doc_type":"usermanual", - "p_code":"165", - "code":"167" + "p_code":"176", + "code":"178" }, { "desc":"Each ECS is automatically added to a security group after being created to ensure its security. The security group denies access traffic from the Internet by default. To ", @@ -1508,8 +1607,8 @@ "title":"How Do I Access an ECS with an EIP Bound from the Internet?", "uri":"vpc_faq_0020.html", "doc_type":"usermanual", - "p_code":"165", - "code":"168" + "p_code":"176", + "code":"179" }, { "desc":"No. EIPs and their associated cloud resources must be in the same region.", @@ -1517,8 +1616,8 @@ "title":"Can I Bind an EIP to a Cloud Resource in Another Region?", "uri":"faq_eip_0012.html", "doc_type":"usermanual", - "p_code":"165", - "code":"169" + "p_code":"176", + "code":"180" }, { "desc":"The region of an EIP cannot be changed.If you assigned an EIP in region A but need an EIP in region B, you cannot directly change the region of the assigned EIP from A to", @@ -1526,8 +1625,17 @@ "title":"Can I Change the Region of My EIP?", "uri":"faq_eip_0014.html", "doc_type":"usermanual", - "p_code":"165", - "code":"170" + "p_code":"176", + "code":"181" + }, + { + "desc":"Table 1 lists the differences between 5_bgp, 5_mailbgp, and 5_gray EIPs.", + "product_code":"vpc", + "title":"What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?", + "uri":"en-us_topic_0000001818822858.html", + "doc_type":"usermanual", + "p_code":"176", + "code":"182" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1535,8 +1643,8 @@ "title":"VPC Peering Connections", "uri":"faq_peer_0000.html", "doc_type":"usermanual", - "p_code":"154", - "code":"171" + "p_code":"165", + "code":"183" }, { "desc":"Each account can have a maximum of 50 VPC peering connections in each region by default.Number of VPC peering connections that you can create in each region between VPCs ", @@ -1544,8 +1652,8 @@ "title":"How Many VPC Peering Connections Can I Create in an Account?", "uri":"vpc_faq_0070.html", "doc_type":"usermanual", - "p_code":"171", - "code":"172" + "p_code":"183", + "code":"184" }, { "desc":"A VPC peering connection only can connect VPCs in the same region.Figure 1 shows an application scenario of VPC peering connections.There are two VPCs (VPC-A and VPC-B) i", @@ -1553,8 +1661,8 @@ "title":"Can a VPC Peering Connection Connect VPCs in Different Regions?", "uri":"faq_connection_0001.html", "doc_type":"usermanual", - "p_code":"171", - "code":"173" + "p_code":"183", + "code":"185" }, { "desc":"After a VPC peering connection is created, the local and peer VPCs cannot communicate with each other.The issues here are described in order of how likely they are to occ", @@ -1562,8 +1670,8 @@ "title":"Why Did Communication Fail Between VPCs That Were Connected by a VPC Peering Connection?", "uri":"vpc_faq_0069.html", "doc_type":"usermanual", - "p_code":"171", - "code":"174" + "p_code":"183", + "code":"186" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1571,17 +1679,17 @@ "title":"Bandwidth", "uri":"faq_bandwidth.html", "doc_type":"usermanual", - "p_code":"154", - "code":"175" + "p_code":"165", + "code":"187" }, { - "desc":"The bandwidth range is from 5 Mbit/s to 1000 Mbit/s.", + "desc":"The bandwidth range is from 5Mbit/s to 1000Mbit/s.", "product_code":"vpc", "title":"What Is the Bandwidth Size Range?", "uri":"vpc_faq_0011.html", "doc_type":"usermanual", - "p_code":"175", - "code":"176" + "p_code":"187", + "code":"188" }, { "desc":"There are dedicated bandwidths and shared bandwidths. A dedicated bandwidth can only be used by one EIP, but a shared bandwidth can be used by multiple EIPs.", @@ -1589,17 +1697,17 @@ "title":"What Bandwidth Types Are Available?", "uri":"vpc_faq_0012.html", "doc_type":"usermanual", - "p_code":"175", - "code":"177" + "p_code":"187", + "code":"189" }, { - "desc":"A dedicated bandwidth can only be used by one EIP. An EIP can only be used by one cloud resource, such as an ECS, a NAT gateway, or a load balancer.A shared bandwidth can", + "desc":"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 ", "product_code":"vpc", - "title":"What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth or the Other Way Around?", + "title":"What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth?", "uri":"faq_bandwidth_0003.html", "doc_type":"usermanual", - "p_code":"175", - "code":"178" + "p_code":"187", + "code":"190" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1607,8 +1715,8 @@ "title":"Connectivity", "uri":"faq_connection.html", "doc_type":"usermanual", - "p_code":"154", - "code":"179" + "p_code":"165", + "code":"191" }, { "desc":"If the two VPCs are in the same region, you can use a VPC peering connection to enable communication between them.If the two VPCs are in different regions, you can use a ", @@ -1616,17 +1724,17 @@ "title":"Does a VPN Allow Communication Between Two VPCs?", "uri":"vpc_faq_0058.html", "doc_type":"usermanual", - "p_code":"179", - "code":"180" + "p_code":"191", + "code":"192" }, { - "desc":"When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access the Internet or domain names i", + "desc":"When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access public websites or internal do", "product_code":"vpc", "title":"Why Are Internet or Internal Domain Names in the Cloud Inaccessible Through Domain Names When My ECS Has Multiple NICs?", "uri":"vpc_faq_0060.html", "doc_type":"usermanual", - "p_code":"179", - "code":"181" + "p_code":"191", + "code":"193" }, { "desc":"The priority of an EIP is higher than that of a custom route in a VPC route table. For example:The VPC route table of an ECS has a custom route with 0.0.0.0/0 as the dest", @@ -1634,8 +1742,8 @@ "title":"What Are the Priorities of the Custom Route and EIP If Both Are Configured for an ECS to Enable the ECS to Access the Internet?", "uri":"vpc_faq_0073.html", "doc_type":"usermanual", - "p_code":"179", - "code":"182" + "p_code":"191", + "code":"194" }, { "desc":"The priority of a custom route is higher than that of shared SNAT.", @@ -1643,8 +1751,8 @@ "title":"What Are the Priorities of the Shared SNAT and Custom Route If Both Are Configured for an ECS to Enable the ECS to Access the Internet?", "uri":"vpc_faq_00002.html", "doc_type":"usermanual", - "p_code":"179", - "code":"183" + "p_code":"191", + "code":"195" }, { "desc":"Users with IPv6 clients can call APIs to assign IPv6 EIPs and bind the EIPs to ECSs. Then, the users can use the EIP to access the ECSs in the VPC over the Internet.For d", @@ -1652,8 +1760,8 @@ "title":"How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?", "uri":"vpc_faq_0076.html", "doc_type":"usermanual", - "p_code":"179", - "code":"184" + "p_code":"191", + "code":"196" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1661,8 +1769,8 @@ "title":"Routing", "uri":"faq_route.html", "doc_type":"usermanual", - "p_code":"154", - "code":"185" + "p_code":"165", + "code":"197" }, { "desc":"Currently, a route table can contain 100 routes.", @@ -1670,8 +1778,8 @@ "title":"How Many Routes Can a Route Table Contain?", "uri":"vpc_faq_0063.html", "doc_type":"usermanual", - "p_code":"185", - "code":"186" + "p_code":"197", + "code":"198" }, { "desc":"An ECS providing SNAT must have Unbind IP from MAC enabled.The destination of each route in a route table must be unique. The next hop must be a private IP address or a v", @@ -1679,8 +1787,8 @@ "title":"Are There Any Restrictions on Using a Route Table?", "uri":"vpc_faq_0064.html", "doc_type":"usermanual", - "p_code":"185", - "code":"187" + "p_code":"197", + "code":"199" }, { "desc":"No. Direct Connect connections and custom routes are used in different scenarios, so the routing priorities are different.", @@ -1688,8 +1796,8 @@ "title":"Do the Same Routing Priorities Apply to Direct Connect Connections and Custom Routes in the Same VPC?", "uri":"vpc_faq_0066.html", "doc_type":"usermanual", - "p_code":"185", - "code":"188" + "p_code":"197", + "code":"200" }, { "desc":"No. The routing priority of custom routes and that of VPNs are the same.", @@ -1697,8 +1805,8 @@ "title":"Are There Different Routing Priorities of the VPN and Custom Routes in the Same VPC?", "uri":"vpc_faq_00001.html", "doc_type":"usermanual", - "p_code":"185", - "code":"189" + "p_code":"197", + "code":"201" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1706,8 +1814,8 @@ "title":"Security", "uri":"faq_security.html", "doc_type":"usermanual", - "p_code":"154", - "code":"190" + "p_code":"165", + "code":"202" }, { "desc":"The default security group is named default and cannot be deleted.If you want to delete a security group that is associated with instances, such as cloud servers, contain", @@ -1715,8 +1823,8 @@ "title":"Why Can't I Delete a Security Group?", "uri":"faq_security_0003.html", "doc_type":"usermanual", - "p_code":"190", - "code":"191" + "p_code":"202", + "code":"203" }, { "desc":"Yes. Log in to the ECS console, switch to the page showing ECS details, and change the security group of the ECS.", @@ -1724,8 +1832,8 @@ "title":"Can I Change the Security Group of an ECS?", "uri":"vpc_faq_0039.html", "doc_type":"usermanual", - "p_code":"190", - "code":"192" + "p_code":"202", + "code":"204" }, { "desc":"The TFTP daemon determines whether a configuration file specifies the port range. If you use a TFTP configuration file that allows the data channel ports to be configurab", @@ -1733,26 +1841,26 @@ "title":"How Do I Configure a Security Group for Multi-Channel Protocols?", "uri":"vpc_faq_0059.html", "doc_type":"usermanual", - "p_code":"190", - "code":"193" + "p_code":"202", + "code":"205" }, { - "desc":"Security groups are stateful. Responses to outbound traffic are allowed to go in to the instance regardless of inbound security group rules, and vice versa. Security grou", + "desc":"Security groups use connection tracking to track traffic to and from instances. If an inbound rule is modified, the modified rule immediately takes effect for the existin", "product_code":"vpc", - "title":"Does a Security Group Rule or a Firewall Rule Immediately Take Effect for Existing Connections After It Is Modified?", + "title":"Does a Modified Security Group Rule or a Firewall Rule Take Effect Immediately for Existing Connections?", "uri":"vpc_faq_0074.html", "doc_type":"usermanual", - "p_code":"190", - "code":"194" + "p_code":"202", + "code":"206" }, { "desc":"Security group rules use the whitelist mechanism. If multiple security group rules conflict, the rules are aggregated to take effect.", "product_code":"vpc", - "title":"Which Security Group Rule Has Priority When Multiple Security Group Rules Conflict?", + "title":"Which Security Group Rule Has a High Priority When Multiple Security Group Rules Conflict?", "uri":"vpc_faq_0077.html", "doc_type":"usermanual", - "p_code":"190", - "code":"195" + "p_code":"202", + "code":"207" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1761,15 +1869,15 @@ "uri":"vpc_faq_0103.html", "doc_type":"usermanual", "p_code":"", - "code":"196" + "code":"208" }, { - "desc":"For details about the terms involved in this document, see Glossary.", + "desc":"For details about the glossaries in this document, see Glossary.", "product_code":"vpc", "title":"Glossary", "uri":"vpc_faq_0106.html", "doc_type":"usermanual", "p_code":"", - "code":"197" + "code":"209" } ] \ No newline at end of file diff --git a/docs/vpc/umn/FlowLog_0002.html b/docs/vpc/umn/FlowLog_0002.html index 451626a86..4f6c93f2a 100644 --- a/docs/vpc/umn/FlowLog_0002.html +++ b/docs/vpc/umn/FlowLog_0002.html @@ -3,7 +3,7 @@

VPC Flow Log Overview

What Is a VPC Flow Log?

A VPC flow log records information about the traffic going to and from a VPC. VPC flow logs help you monitor network traffic, analyze network attacks, and determine whether security group and firewall rules require modification.

VPC flow logs must be used together with the Log Tank Service (LTS). Before you create a VPC flow log, you need to create a log group and a log topic in LTS. Figure 1 shows the process for configuring VPC flow logs.

-
Figure 1 Configuring VPC flow logs
+
Figure 1 Configuring VPC flow logs

Notes and Constraints

diff --git a/docs/vpc/umn/FlowLog_0003.html b/docs/vpc/umn/FlowLog_0003.html index 225ec997f..10ca8d762 100644 --- a/docs/vpc/umn/FlowLog_0003.html +++ b/docs/vpc/umn/FlowLog_0003.html @@ -7,68 +7,68 @@

For more information about the LTS service, see the Log Tank Service User Guide.

-

Procedure

  1. Log in to the management console.
  1. Click in the upper left corner and select the desired region and project.
  1. Click in the upper left corner and choose Network > Virtual Private Cloud.

    The Virtual Private Cloud page is displayed.

    -
  1. In the navigation pane on the left, choose VPC Flow Logs.
  2. In the upper right corner, click Create VPC Flow Log. On the displayed page, configure parameters as prompted.
    Figure 1 Create VPC Flow Log
    +

    Procedure

    1. Log in to the management console.
    1. Click in the upper left corner and select the desired region and project.
    1. Click in the upper left corner and choose Network > Virtual Private Cloud.

      The Virtual Private Cloud page is displayed.

      +
    1. In the navigation pane on the left, choose VPC Flow Logs.
    2. 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

      +
      - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/vpc/umn/FlowLog_0004.html b/docs/vpc/umn/FlowLog_0004.html index d548bdeb1..08462706a 100644 --- a/docs/vpc/umn/FlowLog_0004.html +++ b/docs/vpc/umn/FlowLog_0004.html @@ -6,9 +6,9 @@

      If an ECS is in the stopped state, its flow log records will not be displayed.

      -

      Procedure

      1. Log in to the management console.
      1. Click in the upper left corner and select the desired region and project.
      1. Click in the upper left corner and choose Network > Virtual Private Cloud.

        The Virtual Private Cloud page is displayed.

        -
      1. In the navigation pane on the left, choose VPC Flow Logs.
      2. Locate the target VPC flow log and click View Log Record in the Operation column to view information about the flow log record in LTS.
        Figure 1 Viewing a log record
        -
        Figure 2 Flow log record
        +

        Procedure

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        1. Click in the upper left corner and choose Network > Virtual Private Cloud.

          The Virtual Private Cloud page is displayed.

          +
        1. In the navigation pane on the left, choose VPC Flow Logs.
        2. Locate the target VPC flow log and click View Log Record in the Operation column to view information about the flow log record in LTS.
          Figure 1 Viewing a log record
          +
          Figure 2 Flow log record

          The flow log record is in the following format:

          <version> <project-id> <interface-id> <srcaddr> <dstaddr> <srcport> <dstport> <protocol> <packets> <bytes> <start> <end> <action> <log-status>

          Example 1: The following is an example of a flow log record in which data was recorded during the capture window:

          @@ -19,114 +19,114 @@

          Example 3: The following is an example of a flow log record in which data was skipped during the capture window:

          1 5f67944957444bd6bb4fe3b367de8f3d 1d515d18-1b36-47dc-a983-bd6512aed4bd - - - - - - - 1431280876 1431280934 - SKIPDATA
          Table 1 describes the fields of a flow log record. -
      Table 1 Parameter descriptions

      Parameter

      Description

      +

      Description

      Example Value

      +

      Example Value

      Name

      +

      Name

      The VPC flow log name.

      +

      The VPC flow log 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.

      flowlog-495d

      +

      flowlog-495d

      Resource Type

      +

      Resource Type

      The type of resources whose traffic is to be logged. You can select NIC, Subnet, or VPC.

      +

      The type of resources whose traffic is to be logged. You can select NIC, Subnet, or VPC.

      NIC

      +

      NIC

      Resource

      +

      Resource

      The specific NIC whose traffic is to be logged.

      +

      The specific NIC whose traffic is to be logged.

      NOTE:

      We recommend that you select an ECS that is in the running state. If an ECS in the stopped state is selected, restart the ECS after creating the VPC flow log for accurately recording the information about the traffic going to and from the ECS NIC.

      N/A

      +

      N/A

      Filter

      +

      Filter

      • All traffic: specifies that both accepted and rejected traffic of the specified resource will be logged.
      • Accepted traffic: specifies that only accepted traffic of the specified resource will be logged. Accepted traffic refers to the traffic permitted by the security group or firewall.
      • Rejected traffic: specifies that only rejected traffic of the specified resource will be logged. Rejected traffic refers to the traffic denied by the firewall.
      +
      • All traffic: specifies that both accepted and rejected traffic of the specified resource will be logged.
      • Accepted traffic: specifies that only accepted traffic of the specified resource will be logged. Accepted traffic refers to the traffic permitted by the security group or firewall.
      • Rejected traffic: specifies that only rejected traffic of the specified resource will be logged. Rejected traffic refers to the traffic denied by the firewall.

      All

      +

      All

      Log Group

      +

      Log Group

      The log group created in LTS.

      +

      The log group created in LTS.

      lts-group-abc

      +

      lts-group-abc

      Log Topic

      +

      Log Topic

      The log topic created in LTS.

      +

      The log topic created in LTS.

      LogTopic1

      +

      LogTopic1

      Description

      +

      Description

      Supplementary information about the VPC flow log. This parameter is optional.

      +

      Supplementary information about the VPC flow log. This parameter is optional.

      The VPC flow log description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

      N/A

      +

      N/A
      Table 1 Log field description

      Field

      +
      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/vpc/umn/FlowLog_0005.html b/docs/vpc/umn/FlowLog_0005.html index 3c0d17118..1ab57e16a 100644 --- a/docs/vpc/umn/FlowLog_0005.html +++ b/docs/vpc/umn/FlowLog_0005.html @@ -5,8 +5,8 @@

      If a NIC that uses a VPC flow log is deleted, the flow log will be automatically deleted. However, the flow log records are not deleted.

      -

      Procedure

      1. Log in to the management console.
      1. Click in the upper left corner and select the desired region and project.
      1. Click in the upper left corner and choose Network > Virtual Private Cloud.

        The Virtual Private Cloud page is displayed.

        -
      1. In the navigation pane on the left, choose VPC Flow Logs.
      2. 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
        +

        Procedure

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        1. Click in the upper left corner and choose Network > Virtual Private Cloud.

          The Virtual Private Cloud page is displayed.

          +
        1. In the navigation pane on the left, choose VPC Flow Logs.
        2. 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
        3. Click Yes in the displayed dialog box.
      diff --git a/docs/vpc/umn/FlowLog_0006.html b/docs/vpc/umn/FlowLog_0006.html index 6c43ad674..6895617d7 100644 --- a/docs/vpc/umn/FlowLog_0006.html +++ b/docs/vpc/umn/FlowLog_0006.html @@ -5,7 +5,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

      1. Log in to the management console.
      1. Click in the upper left corner and select the desired region and project.
      1. Click in the upper left corner and choose Network > Virtual Private Cloud.

        The Virtual Private Cloud page is displayed.

        +

        Procedure

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        1. Click in the upper left corner and choose Network > Virtual Private Cloud.

          The Virtual Private Cloud page is displayed.

        1. In the navigation pane on the left, choose VPC Flow Logs.
        2. Locate the VPC flow log to be enabled or disabled, and choose More > Enable or More > Disable in the Operation column.
        3. Click Yes.
      diff --git a/docs/vpc/umn/SecurityGroup_0003.html b/docs/vpc/umn/SecurityGroup_0003.html index ef1d17bc3..3c4ccf4f2 100644 --- a/docs/vpc/umn/SecurityGroup_0003.html +++ b/docs/vpc/umn/SecurityGroup_0003.html @@ -1,10 +1,10 @@

      Default Security Group and Its Rules

      -
      If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when you create it. A default security group has the following rules:
      • Inbound rules control incoming traffic to instances in a security group. Only instances in the same security group can communicate with each other, and all inbound requests are denied.
      • Outbound rules allow all outbound traffic and response traffic to the outbound requests.
      +
      If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance when you create it. A default security group has the following rules:
      • Inbound rules control incoming traffic to instances in a security group. Only instances in the same security group can communicate with each other, and all inbound requests are denied.
      • Outbound rules allow all outbound traffic and response traffic to the outbound requests.
      -
      Figure 1 Default security group
      -
      • You cannot delete the default security group, but you can modify existing rules or add rules to the group.
      • The default security group is automatically created to simplify the process of creating an instance for the first time. The default security group denies all external requests. To log in to an instance, add a security group rule by referring to Remotely Logging In to an ECS from a Local Server.
      +
      Figure 1 Default security group
      +
      • You cannot delete the default security group, but you can modify existing rules or add rules to the group.
      • The default security group denies all external requests. To log in to an instance associated with this security group, add a security group rule by referring to Remotely Logging In to an ECS from a Local Server.

      Table 1 describes the default rules for the default security group.

      diff --git a/docs/vpc/umn/SecurityGroup_0004.html b/docs/vpc/umn/SecurityGroup_0004.html index 5129c7078..056b4160d 100644 --- a/docs/vpc/umn/SecurityGroup_0004.html +++ b/docs/vpc/umn/SecurityGroup_0004.html @@ -3,11 +3,11 @@

      Fast-Adding Security Group Rules

      Scenarios

      The fast-adding rule function of security groups allows you to quickly add rules with common ports and protocols for remote login, ping tests, common web services, and database services.

      -

      Procedure

      1. Log in to the management console.
      1. Click in the upper left corner and select the desired region and project.
      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

        The Virtual Private Cloud page is displayed.

        +

        Procedure

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

          The Virtual Private Cloud page is displayed.

        3. In the navigation pane on the left, choose Access Control > Security Groups.

          The security group list is displayed.

        4. 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.

        5. On the Inbound Rules tab, click Fast-Add Rule.

          The Fast-Add Inbound Rule dialog box is displayed.

          -
        6. Configure required parameters.
          Figure 1 Fast-Add Inbound Rule
          +
        7. Configure required parameters.
          Figure 1 Fast-Add Inbound Rule
      Table 1 Log field description

      Field

      Description

      +

      Description

      Example Value

      +

      Example Value

      version

      +

      version

      The VPC flow log version.

      +

      The VPC flow log version.

      1

      +

      1

      project-id

      +

      project-id

      The project ID.

      +

      The project ID.

      5f67944957444bd6bb4fe3b367de8f3d

      +

      5f67944957444bd6bb4fe3b367de8f3d

      interface-id

      +

      interface-id

      The ID of the NIC for which the traffic is recorded.

      +

      The ID of the NIC for which the traffic is recorded.

      1d515d18-1b36-47dc-a983-bd6512aed4bd

      +

      1d515d18-1b36-47dc-a983-bd6512aed4bd

      srcaddr

      +

      srcaddr

      The source IP address.

      +

      The source IP address.

      192.168.0.154

      +

      192.168.0.154

      dstaddr

      +

      dstaddr

      The destination IP address.

      +

      The destination IP address.

      192.168.3.25

      +

      192.168.3.25

      srcport

      +

      srcport

      The source port.

      +

      The source port.

      38929

      +

      38929

      dstport

      +

      dstport

      The destination port.

      +

      The destination port.

      53

      +

      53

      protocol

      +

      protocol

      The Internet Assigned Numbers Authority (IANA) protocol number of the traffic. For details, see Assigned Internet Protocol Numbers.

      +

      The Internet Assigned Numbers Authority (IANA) protocol number of the traffic. For details, see Assigned Internet Protocol Numbers.

      17

      +

      17

      packets

      +

      packets

      The number of packets transferred during the capture window.

      +

      The number of packets transferred during the capture window.

      1

      +

      1

      bytes

      +

      bytes

      The number of bytes transferred during the capture window.

      +

      The number of bytes transferred during the capture window.

      96

      +

      96

      start

      +

      start

      The time, in Unix seconds, of the start of the capture window.

      +

      The time, in Unix seconds, of the start of the capture window.

      1548752136

      +

      1548752136

      end

      +

      end

      The time, in Unix seconds, of the end of the capture window.

      +

      The time, in Unix seconds, of the end of the capture window.

      1548752736

      +

      1548752736

      action

      +

      action

      The action associated with the traffic:

      +

      The action associated with the traffic:

      • ACCEPT: The recorded traffic was allowed by the security groups or firewalls.
      • REJECT: The recorded traffic was denied by the security groups or firewalls.

      ACCEPT

      +

      ACCEPT

      log-status

      +

      log-status

      The logging status of the VPC flow log:

      +

      The logging status of the VPC flow log:

      • OK: Data is logging normally to the chosen destinations.
      • NODATA: There was no traffic of the Filter setting to or from the NIC during the capture window.
      • SKIPDATA: Some flow log records were skipped during the capture window. This may be caused by an internal capacity constraint or an internal error.

      Example:

      When Filter is set to Accepted traffic, if there is accepted traffic, the value of log-status is OK. If there is no accepted traffic, the value of log-status is NODATA regardless of whether there is rejected traffic. If some accepted traffic is abnormally skipped, the value of log-status is SKIPDATA.

      OK

      +

      OK
      @@ -56,7 +56,7 @@
    3. Click OK.

      The inbound rule list is displayed and you can view your added rule.

    4. On the Outbound Rules tab, click Fast-Add Rule.

      The Fast-Add Outbound Rule dialog box is displayed.

      -
    5. Configure required parameters.
      Figure 2 Fast-Add Outbound Rule
      +
    6. Configure required parameters.
      Figure 2 Fast-Add Outbound Rule
      7. Table 1 Inbound rule parameter description

      Parameter
      @@ -108,7 +108,7 @@
      -
      Parent topic: Security Group
      +
      Parent topic: Managing Security Group Rules
      diff --git a/docs/vpc/umn/SecurityGroup_0005.html b/docs/vpc/umn/SecurityGroup_0005.html index c356ac4cd..0a7ad1e29 100644 --- a/docs/vpc/umn/SecurityGroup_0005.html +++ b/docs/vpc/umn/SecurityGroup_0005.html @@ -1,7 +1,7 @@

      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.
      +

      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.

      @@ -74,7 +74,7 @@
      Table 2 Outbound rule parameter description

      Parameter
      -

      Procedure

      1. Log in to the management console.
      2. Click in the upper left corner and select the desired region and project.
      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

        The Virtual Private Cloud page is displayed.

        +

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select the desired region and project.
        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

          The Virtual Private Cloud page is displayed.

        4. In the navigation pane on the left, choose Access Control > Security Groups.

          The security group list is displayed.

        5. In the security group list, click the name of the security group.

          The security group details page is displayed.

        6. Click the Inbound Rules or Outbound Rules tab, and then click Allow Common Ports.

          The Allow Common Ports page is displayed.

          @@ -84,7 +84,7 @@
        -
        Parent topic: Security Group
        +
        Parent topic: Managing Security Group Rules
        diff --git a/docs/vpc/umn/SecurityGroup_0006.html b/docs/vpc/umn/SecurityGroup_0006.html index f6fbcb1bd..01fc74cb6 100644 --- a/docs/vpc/umn/SecurityGroup_0006.html +++ b/docs/vpc/umn/SecurityGroup_0006.html @@ -3,18 +3,18 @@

        Changing the Security Group of an ECS

        Scenarios

        Change the security group associated with an ECS NIC.

        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select your region and project.
        3. Under Computing, click Elastic Cloud Server.
        4. In the ECS list, locate the row that contains the target ECS. Click More in the Operation column and select Manage Network > Change Security Group.

          The Change Security Group dialog box is displayed.

          -
          Figure 1 Change Security Group
          -
        5. Select the target NIC and security groups.

          You can select multiple security groups. In such a case, the rules of all the selected security groups will be aggregated to apply on the ECS.

          -

          To create a security group, click Create Security Group.

          -

          Using multiple security groups may deteriorate ECS network performance. You are suggested to select no more than five security groups.

          +

          Procedure

          1. Log in to the management console.
          2. Click in the upper left corner and select your region and project.
          3. Click and choose Computing > Elastic Cloud Server.
          4. In the ECS list, choose More > Manage Network > Change Security Group in the Operation column.

            The Change Security Group dialog box is displayed.

            +
            Figure 1 Changing a security group
            +
          5. Select the target NIC and security groups.

            You can select multiple security groups. In such a case, the access rules of all the selected security groups apply to the ECS.

            +

            To create a security group, click Create Security Group.

            +

            Using multiple security groups may deteriorate ECS network performance. We recommend that you associate no more than five security groups with each ECS.

            -
          6. Click OK.
          +
        6. Click OK.
        diff --git a/docs/vpc/umn/SecurityGroup_0017.html b/docs/vpc/umn/SecurityGroup_0017.html index c9f7f6d80..c921e3851 100644 --- a/docs/vpc/umn/SecurityGroup_0017.html +++ b/docs/vpc/umn/SecurityGroup_0017.html @@ -4,7 +4,7 @@

        Scenarios

        When you create an instance, the system automatically adds the instance to a security group for protection.
        • If one security group cannot meet your requirements, you can add an instance to multiple security groups.
        • An instance must be added to at least one security group. If you want to change the security group for an instance, you can add the instance to a new security group and then remove the instance from the original security group.
        -

        Adding an Instance to a Security Group

        1. Log in to the management console.
        2. Click in the upper left corner and select the desired region and project.
        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

          The Virtual Private Cloud page is displayed.

          +

          Adding an Instance to a Security Group

          1. Log in to the management console.
          2. Click in the upper left corner and select the desired region and project.
          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

            The Virtual Private Cloud page is displayed.

          4. In the navigation pane on the left, choose Access Control > Security Groups.

            The security group list is displayed.

          5. 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.

          6. Click an instance type.

            The following operations use Servers as an example.

            @@ -12,7 +12,7 @@
          7. 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.

          -
          1. Log in to the management console.
          2. Click in the upper left corner and select the desired region and project.
          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

            The Virtual Private Cloud page is displayed.

            +
            1. Log in to the management console.
            2. Click in the upper left corner and select the desired region and project.
            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

              The Virtual Private Cloud page is displayed.

            4. In the navigation pane on the left, choose Access Control > Security Groups.

              The security group list is displayed.

            5. 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.

            6. Click an instance type.

              The following operations use Servers as an example.

              @@ -24,7 +24,7 @@
          diff --git a/docs/vpc/umn/acl_0001.html b/docs/vpc/umn/acl_0001.html index d06e25397..9143fe657 100644 --- a/docs/vpc/umn/acl_0001.html +++ b/docs/vpc/umn/acl_0001.html @@ -3,10 +3,14 @@

          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.

          -
          Figure 1 Security groups and firewalls
          +
          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.

          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.
          +

          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.

            +
          +

          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.

          +
          • 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.
          +

          Default Firewall Rules

          By default, each firewall has preset rules that allow the following packets:

          • Packets whose source and destination are in the same subnet.
          • Broadcast packets with the destination 255.255.255.255/32, which is used to configure host startup information.
          • Multicast packets with the destination 224.0.0.0/24, which is used by routing protocols.
          • Metadata packets with the destination 169.254.169.254/32 and TCP port number 80, which is used to obtain metadata.
          • Packets from CIDR blocks that are reserved for public services (for example, packets with the destination 100.125.0.0/16).
          • A firewall denies all traffic in and out of a subnet excepting the preceding packets. Table 1 shows the default rules. You cannot modify or delete the default rules. @@ -61,7 +65,7 @@
        -

        Rule Priorities

        • Each firewall rule has a priority value where a smaller value corresponds to a higher priority. Any time two rules conflict, the rule with the higher priority is the one that gets applied. The rule whose priority value is an asterisk (*) has the lowest priority.
        • If multiple firewall rules conflict, only the rule with the highest priority takes effect. If you need a rule to take effect before or after a specific rule, you can insert that rule before or after the specific rule.
        +

        How Traffic Matches Firewall Rules

        • Each firewall rule has a priority value where a smaller value corresponds to a higher priority. Any time two rules conflict, the rule with the higher priority is the one that gets applied. The rule whose priority value is an asterisk (*) has the lowest priority.
        • If multiple firewall rules conflict, only the rule with the highest priority takes effect. If you need a rule to take effect before or after a specific rule, you can insert that rule before or after the specific rule.

        Application Scenarios

        • If the application layer needs to provide services for users, traffic must be allowed to reach the application layer from all IP addresses. However, you also need to prevent illegal access from malicious users.

          Solution: You can add firewall rules to deny access from suspect IP addresses.

        • How can I isolate ports with identified vulnerabilities? For example, how do I isolate port 445 that can be exploited by WannaCry worm?

          Solution: You can add firewall rules to deny access traffic from a specific port and protocol, for example, TCP port 445.

          @@ -70,7 +74,7 @@

        Configuration Procedure

        Figure 2 shows the procedure for configuring a firewall.

        -
        Figure 2 firewall configuration procedure
        +
        Figure 2 firewall configuration procedure
        1. Create a firewall by following the steps described in Creating a Firewall.
        2. Add firewall rules by following the steps described in Adding a Firewall Rule.
        3. Associate subnets with the firewall by following the steps described in Associating Subnets with a Firewall. After subnets are associated with the firewall, the subnets will be protected by the configured firewall rules.

        Notes and Constraints

        • By default, each account can have up to 200 firewalls in a region.
        • A firewall can contain no more than 20 rules in one direction, or performance will deteriorate.
        diff --git a/docs/vpc/umn/acl_0002.html b/docs/vpc/umn/acl_0002.html index b42ec1355..214c0cfb9 100644 --- a/docs/vpc/umn/acl_0002.html +++ b/docs/vpc/umn/acl_0002.html @@ -1,6 +1,6 @@ -

        Firewall Configuration Examples

        +

        Firewall Configuration Examples

        This section provides examples for configuring firewalls.

        Denying Access from a Specific Port

        You might want to block TCP port 445 to protect against the WannaCry ransomware attacks. You can add a firewall rule to deny all incoming traffic from TCP port 445.

        diff --git a/docs/vpc/umn/eip_0003.html b/docs/vpc/umn/eip_0003.html index 0ffc2de4f..ccebe0b12 100644 --- a/docs/vpc/umn/eip_0003.html +++ b/docs/vpc/umn/eip_0003.html @@ -3,7 +3,7 @@

        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.

        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select the desired region and project.
        3. Click in the upper left corner and choose Network > Elastic IP.
        4. On the displayed page, click in the upper right corner of the EIP list.

          The system will automatically export all EIPs in the current region of your account to an Excel file and download the file to a local directory.

          +

          Procedure

          1. Log in to the management console.
          2. Click in the upper left corner and select the desired region and project.
          3. Click in the upper left corner, and choose Network > Elastic IP.
          4. 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.

        diff --git a/docs/vpc/umn/en-us_image_0000001197228903.png b/docs/vpc/umn/en-us_image_0000001197228903.png deleted file mode 100644 index 6ef66ec65..000000000 Binary files a/docs/vpc/umn/en-us_image_0000001197228903.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001211006359.png b/docs/vpc/umn/en-us_image_0000001211006359.png deleted file mode 100644 index 66686f7e6..000000000 Binary files a/docs/vpc/umn/en-us_image_0000001211006359.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001211445065.png b/docs/vpc/umn/en-us_image_0000001211445065.png deleted file mode 100644 index a86f5c5dd..000000000 Binary files a/docs/vpc/umn/en-us_image_0000001211445065.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001540725521.png b/docs/vpc/umn/en-us_image_0000001540725521.png deleted file mode 100644 index 2f6a7cfb8..000000000 Binary files a/docs/vpc/umn/en-us_image_0000001540725521.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001627493158.png b/docs/vpc/umn/en-us_image_0000001627493158.png deleted file mode 100644 index 29a235127..000000000 Binary files a/docs/vpc/umn/en-us_image_0000001627493158.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001627653972.png b/docs/vpc/umn/en-us_image_0000001627653972.png deleted file mode 100644 index be2f35cda..000000000 Binary files a/docs/vpc/umn/en-us_image_0000001627653972.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0000001454059512.png b/docs/vpc/umn/en-us_image_0000001649841616.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001454059512.png rename to docs/vpc/umn/en-us_image_0000001649841616.png diff --git a/docs/vpc/umn/en-us_image_0000001490118666.png b/docs/vpc/umn/en-us_image_0000001818822962.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001490118666.png rename to docs/vpc/umn/en-us_image_0000001818822962.png diff --git a/docs/vpc/umn/en-us_image_0162332046.png b/docs/vpc/umn/en-us_image_0000001818823006.png similarity index 100% rename from docs/vpc/umn/en-us_image_0162332046.png rename to docs/vpc/umn/en-us_image_0000001818823006.png diff --git a/docs/vpc/umn/en-us_image_0000001678437642.png b/docs/vpc/umn/en-us_image_0000001818823010.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001678437642.png rename to docs/vpc/umn/en-us_image_0000001818823010.png diff --git a/docs/vpc/umn/en-us_image_0000001221790501.png b/docs/vpc/umn/en-us_image_0000001818823030.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001221790501.png rename to docs/vpc/umn/en-us_image_0000001818823030.png diff --git a/docs/vpc/umn/en-us_image_0000001117669274.png b/docs/vpc/umn/en-us_image_0000001818823034.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001117669274.png rename to docs/vpc/umn/en-us_image_0000001818823034.png diff --git a/docs/vpc/umn/en-us_image_0142359884.png b/docs/vpc/umn/en-us_image_0000001818823038.png similarity index 100% rename from docs/vpc/umn/en-us_image_0142359884.png rename to docs/vpc/umn/en-us_image_0000001818823038.png diff --git a/docs/vpc/umn/en-us_image_0209583952.png b/docs/vpc/umn/en-us_image_0000001818823042.png similarity index 100% rename from docs/vpc/umn/en-us_image_0209583952.png rename to docs/vpc/umn/en-us_image_0000001818823042.png diff --git a/docs/vpc/umn/en-us_image_0000001221842468.png b/docs/vpc/umn/en-us_image_0000001818823050.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001221842468.png rename to docs/vpc/umn/en-us_image_0000001818823050.png diff --git a/docs/vpc/umn/en-us_image_0000001520717193.png b/docs/vpc/umn/en-us_image_0000001818823058.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001520717193.png rename to docs/vpc/umn/en-us_image_0000001818823058.png diff --git a/docs/vpc/umn/en-us_image_0211552164.png b/docs/vpc/umn/en-us_image_0000001818823074.png similarity index 100% rename from docs/vpc/umn/en-us_image_0211552164.png rename to docs/vpc/umn/en-us_image_0000001818823074.png diff --git a/docs/vpc/umn/en-us_image_0000001572300492.png b/docs/vpc/umn/en-us_image_0000001818823082.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001572300492.png rename to docs/vpc/umn/en-us_image_0000001818823082.png diff --git a/docs/vpc/umn/en-us_image_0000001208260576.png b/docs/vpc/umn/en-us_image_0000001818823110.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001208260576.png rename to docs/vpc/umn/en-us_image_0000001818823110.png diff --git a/docs/vpc/umn/en-us_image_0000001209442636.png b/docs/vpc/umn/en-us_image_0000001818823118.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001209442636.png rename to docs/vpc/umn/en-us_image_0000001818823118.png diff --git a/docs/vpc/umn/en-us_image_0000001237013856.png b/docs/vpc/umn/en-us_image_0000001818823138.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001237013856.png rename to docs/vpc/umn/en-us_image_0000001818823138.png diff --git a/docs/vpc/umn/en-us_image_0000001179761510.png b/docs/vpc/umn/en-us_image_0000001818823142.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001179761510.png rename to docs/vpc/umn/en-us_image_0000001818823142.png diff --git a/docs/vpc/umn/en-us_image_0000001626574358.png b/docs/vpc/umn/en-us_image_0000001818823162.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626574358.png rename to docs/vpc/umn/en-us_image_0000001818823162.png diff --git a/docs/vpc/umn/en-us_image_0000001626574362.png b/docs/vpc/umn/en-us_image_0000001818823166.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626574362.png rename to docs/vpc/umn/en-us_image_0000001818823166.png diff --git a/docs/vpc/umn/en-us_image_0000001626574366.png b/docs/vpc/umn/en-us_image_0000001818823186.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626574366.png rename to docs/vpc/umn/en-us_image_0000001818823186.png diff --git a/docs/vpc/umn/en-us_image_0000001515644737.png b/docs/vpc/umn/en-us_image_0000001818823194.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001515644737.png rename to docs/vpc/umn/en-us_image_0000001818823194.png diff --git a/docs/vpc/umn/en-us_image_0000001626574370.png b/docs/vpc/umn/en-us_image_0000001818823210.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626574370.png rename to docs/vpc/umn/en-us_image_0000001818823210.png diff --git a/docs/vpc/umn/en-us_image_0214585341.png b/docs/vpc/umn/en-us_image_0000001818823214.png similarity index 100% rename from docs/vpc/umn/en-us_image_0214585341.png rename to docs/vpc/umn/en-us_image_0000001818823214.png diff --git a/docs/vpc/umn/en-us_image_0000001626575750.png b/docs/vpc/umn/en-us_image_0000001818823254.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626575750.png rename to docs/vpc/umn/en-us_image_0000001818823254.png diff --git a/docs/vpc/umn/en-us_image_0000001818823258.png b/docs/vpc/umn/en-us_image_0000001818823258.png new file mode 100644 index 000000000..a3ec979c4 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001818823258.png differ diff --git a/docs/vpc/umn/en-us_image_0000001626576382.png b/docs/vpc/umn/en-us_image_0000001818823270.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626576382.png rename to docs/vpc/umn/en-us_image_0000001818823270.png diff --git a/docs/vpc/umn/en-us_image_0214585309.png b/docs/vpc/umn/en-us_image_0000001818823278.png similarity index 100% rename from docs/vpc/umn/en-us_image_0214585309.png rename to docs/vpc/umn/en-us_image_0000001818823278.png diff --git a/docs/vpc/umn/en-us_image_0000001626576858.png b/docs/vpc/umn/en-us_image_0000001818823286.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626576858.png rename to docs/vpc/umn/en-us_image_0000001818823286.png diff --git a/docs/vpc/umn/en-us_image_0000001626578706.png b/docs/vpc/umn/en-us_image_0000001818823302.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626578706.png rename to docs/vpc/umn/en-us_image_0000001818823302.png diff --git a/docs/vpc/umn/en-us_image_0129304042.png b/docs/vpc/umn/en-us_image_0000001818823318.png similarity index 100% rename from docs/vpc/umn/en-us_image_0129304042.png rename to docs/vpc/umn/en-us_image_0000001818823318.png diff --git a/docs/vpc/umn/en-us_image_0000001626734158.png b/docs/vpc/umn/en-us_image_0000001818823338.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626734158.png rename to docs/vpc/umn/en-us_image_0000001818823338.png diff --git a/docs/vpc/umn/en-us_image_0152727234.png b/docs/vpc/umn/en-us_image_0000001818823370.png similarity index 100% rename from docs/vpc/umn/en-us_image_0152727234.png rename to docs/vpc/umn/en-us_image_0000001818823370.png diff --git a/docs/vpc/umn/en-us_image_0274115599.png b/docs/vpc/umn/en-us_image_0000001818823374.png similarity index 100% rename from docs/vpc/umn/en-us_image_0274115599.png rename to docs/vpc/umn/en-us_image_0000001818823374.png diff --git a/docs/vpc/umn/en-us_image_0000001626734162.png b/docs/vpc/umn/en-us_image_0000001818823378.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626734162.png rename to docs/vpc/umn/en-us_image_0000001818823378.png diff --git a/docs/vpc/umn/en-us_image_0152668782.png b/docs/vpc/umn/en-us_image_0000001818823386.png similarity index 100% rename from docs/vpc/umn/en-us_image_0152668782.png rename to docs/vpc/umn/en-us_image_0000001818823386.png diff --git a/docs/vpc/umn/en-us_image_0000001627174280.png b/docs/vpc/umn/en-us_image_0000001818823394.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627174280.png rename to docs/vpc/umn/en-us_image_0000001818823394.png diff --git a/docs/vpc/umn/en-us_image_0000001626734166.png b/docs/vpc/umn/en-us_image_0000001818823402.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626734166.png rename to docs/vpc/umn/en-us_image_0000001818823402.png diff --git a/docs/vpc/umn/en-us_image_0000001626734174.png b/docs/vpc/umn/en-us_image_0000001818823406.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626734174.png rename to docs/vpc/umn/en-us_image_0000001818823406.png diff --git a/docs/vpc/umn/en-us_image_0191588554.png b/docs/vpc/umn/en-us_image_0000001818823446.png similarity index 100% rename from docs/vpc/umn/en-us_image_0191588554.png rename to docs/vpc/umn/en-us_image_0000001818823446.png diff --git a/docs/vpc/umn/en-us_image_0000001626735566.png b/docs/vpc/umn/en-us_image_0000001818823450.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626735566.png rename to docs/vpc/umn/en-us_image_0000001818823450.png diff --git a/docs/vpc/umn/en-us_image_0000001818823514.png b/docs/vpc/umn/en-us_image_0000001818823514.png new file mode 100644 index 000000000..a58764452 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001818823514.png differ diff --git a/docs/vpc/umn/en-us_image_0171311823.png b/docs/vpc/umn/en-us_image_0000001818823522.png similarity index 100% rename from docs/vpc/umn/en-us_image_0171311823.png rename to docs/vpc/umn/en-us_image_0000001818823522.png diff --git a/docs/vpc/umn/en-us_image_0000001818823594.png b/docs/vpc/umn/en-us_image_0000001818823594.png new file mode 100644 index 000000000..ebc4d6f2c Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001818823594.png differ diff --git a/docs/vpc/umn/en-us_image_0000001464757610.png b/docs/vpc/umn/en-us_image_0000001818823598.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001464757610.png rename to docs/vpc/umn/en-us_image_0000001818823598.png diff --git a/docs/vpc/umn/en-us_image_0167839112.png b/docs/vpc/umn/en-us_image_0000001818823602.png similarity index 100% rename from docs/vpc/umn/en-us_image_0167839112.png rename to docs/vpc/umn/en-us_image_0000001818823602.png diff --git a/docs/vpc/umn/en-us_image_0162336264.png b/docs/vpc/umn/en-us_image_0000001818823626.png similarity index 100% rename from docs/vpc/umn/en-us_image_0162336264.png rename to docs/vpc/umn/en-us_image_0000001818823626.png diff --git a/docs/vpc/umn/en-us_image_0000001512701025.png b/docs/vpc/umn/en-us_image_0000001818823678.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001512701025.png rename to docs/vpc/umn/en-us_image_0000001818823678.png diff --git a/docs/vpc/umn/en-us_image_0000001209321492.png b/docs/vpc/umn/en-us_image_0000001818823702.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001209321492.png rename to docs/vpc/umn/en-us_image_0000001818823702.png diff --git a/docs/vpc/umn/en-us_image_0000001626735570.png b/docs/vpc/umn/en-us_image_0000001818823714.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626735570.png rename to docs/vpc/umn/en-us_image_0000001818823714.png diff --git a/docs/vpc/umn/en-us_image_0000001626736198.png b/docs/vpc/umn/en-us_image_0000001818823738.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626736198.png rename to docs/vpc/umn/en-us_image_0000001818823738.png diff --git a/docs/vpc/umn/en-us_image_0162329244.png b/docs/vpc/umn/en-us_image_0000001818823762.png similarity index 100% rename from docs/vpc/umn/en-us_image_0162329244.png rename to docs/vpc/umn/en-us_image_0000001818823762.png diff --git a/docs/vpc/umn/en-us_image_0000001626736678.png b/docs/vpc/umn/en-us_image_0000001818823766.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626736678.png rename to docs/vpc/umn/en-us_image_0000001818823766.png diff --git a/docs/vpc/umn/en-us_image_0000001796404809.png b/docs/vpc/umn/en-us_image_0000001818823770.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001796404809.png rename to docs/vpc/umn/en-us_image_0000001818823770.png diff --git a/docs/vpc/umn/en-us_image_0000001626736794.png b/docs/vpc/umn/en-us_image_0000001818823798.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626736794.png rename to docs/vpc/umn/en-us_image_0000001818823798.png diff --git a/docs/vpc/umn/en-us_image_0000001117669524.png b/docs/vpc/umn/en-us_image_0000001818823830.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001117669524.png rename to docs/vpc/umn/en-us_image_0000001818823830.png diff --git a/docs/vpc/umn/en-us_image_0093507575.png b/docs/vpc/umn/en-us_image_0000001818982734.png similarity index 100% rename from docs/vpc/umn/en-us_image_0093507575.png rename to docs/vpc/umn/en-us_image_0000001818982734.png diff --git a/docs/vpc/umn/en-us_image_0000001570070841.png b/docs/vpc/umn/en-us_image_0000001818982758.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001570070841.png rename to docs/vpc/umn/en-us_image_0000001818982758.png diff --git a/docs/vpc/umn/en-us_image_0000001626738526.png b/docs/vpc/umn/en-us_image_0000001818982762.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626738526.png rename to docs/vpc/umn/en-us_image_0000001818982762.png diff --git a/docs/vpc/umn/en-us_image_0000001461263993.png b/docs/vpc/umn/en-us_image_0000001818982794.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001461263993.png rename to docs/vpc/umn/en-us_image_0000001818982794.png diff --git a/docs/vpc/umn/en-us_image_0000001626894086.png b/docs/vpc/umn/en-us_image_0000001818982798.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626894086.png rename to docs/vpc/umn/en-us_image_0000001818982798.png diff --git a/docs/vpc/umn/en-us_image_0000001626894090.png b/docs/vpc/umn/en-us_image_0000001818982822.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626894090.png rename to docs/vpc/umn/en-us_image_0000001818982822.png diff --git a/docs/vpc/umn/en-us_image_0000001626894094.png b/docs/vpc/umn/en-us_image_0000001818982826.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626894094.png rename to docs/vpc/umn/en-us_image_0000001818982826.png diff --git a/docs/vpc/umn/en-us_image_0000001626894098.png b/docs/vpc/umn/en-us_image_0000001818982830.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626894098.png rename to docs/vpc/umn/en-us_image_0000001818982830.png diff --git a/docs/vpc/umn/en-us_image_0142360094.png b/docs/vpc/umn/en-us_image_0000001818982838.png similarity index 100% rename from docs/vpc/umn/en-us_image_0142360094.png rename to docs/vpc/umn/en-us_image_0000001818982838.png diff --git a/docs/vpc/umn/en-us_image_0000001626894106.png b/docs/vpc/umn/en-us_image_0000001818982846.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626894106.png rename to docs/vpc/umn/en-us_image_0000001818982846.png diff --git a/docs/vpc/umn/en-us_image_0000001626894110.png b/docs/vpc/umn/en-us_image_0000001818982858.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626894110.png rename to docs/vpc/umn/en-us_image_0000001818982858.png diff --git a/docs/vpc/umn/en-us_image_0000001626895486.png b/docs/vpc/umn/en-us_image_0000001818982866.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626895486.png rename to docs/vpc/umn/en-us_image_0000001818982866.png diff --git a/docs/vpc/umn/en-us_image_0000001254335981.png b/docs/vpc/umn/en-us_image_0000001818982898.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001254335981.png rename to docs/vpc/umn/en-us_image_0000001818982898.png diff --git a/docs/vpc/umn/en-us_image_0000001207699446.png b/docs/vpc/umn/en-us_image_0000001818982906.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001207699446.png rename to docs/vpc/umn/en-us_image_0000001818982906.png diff --git a/docs/vpc/umn/en-us_image_0000001626896590.png b/docs/vpc/umn/en-us_image_0000001818982918.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626896590.png rename to docs/vpc/umn/en-us_image_0000001818982918.png diff --git a/docs/vpc/umn/en-us_image_0000001281210233.png b/docs/vpc/umn/en-us_image_0000001818982930.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001281210233.png rename to docs/vpc/umn/en-us_image_0000001818982930.png diff --git a/docs/vpc/umn/en-us_image_0000001225081545.png b/docs/vpc/umn/en-us_image_0000001818982934.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001225081545.png rename to docs/vpc/umn/en-us_image_0000001818982934.png diff --git a/docs/vpc/umn/en-us_image_0000001699135873.png b/docs/vpc/umn/en-us_image_0000001818982946.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001699135873.png rename to docs/vpc/umn/en-us_image_0000001818982946.png diff --git a/docs/vpc/umn/en-us_image_0162335382.png b/docs/vpc/umn/en-us_image_0000001818982962.png similarity index 100% rename from docs/vpc/umn/en-us_image_0162335382.png rename to docs/vpc/umn/en-us_image_0000001818982962.png diff --git a/docs/vpc/umn/en-us_image_0000001626897562.png b/docs/vpc/umn/en-us_image_0000001818982974.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001626897562.png rename to docs/vpc/umn/en-us_image_0000001818982974.png diff --git a/docs/vpc/umn/en-us_image_0000001512591549.png b/docs/vpc/umn/en-us_image_0000001818983018.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001512591549.png rename to docs/vpc/umn/en-us_image_0000001818983018.png diff --git a/docs/vpc/umn/en-us_image_0000001627052380.png b/docs/vpc/umn/en-us_image_0000001818983026.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627052380.png rename to docs/vpc/umn/en-us_image_0000001818983026.png diff --git a/docs/vpc/umn/en-us_image_0000001818983038.png b/docs/vpc/umn/en-us_image_0000001818983038.png new file mode 100644 index 000000000..d6154bac1 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001818983038.png differ diff --git a/docs/vpc/umn/en-us_image_0000001627054054.png b/docs/vpc/umn/en-us_image_0000001818983042.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627054054.png rename to docs/vpc/umn/en-us_image_0000001818983042.png diff --git a/docs/vpc/umn/en-us_image_0141273034.png b/docs/vpc/umn/en-us_image_0000001818983054.png similarity index 100% rename from docs/vpc/umn/en-us_image_0141273034.png rename to docs/vpc/umn/en-us_image_0000001818983054.png diff --git a/docs/vpc/umn/en-us_image_0214585308.png b/docs/vpc/umn/en-us_image_0000001818983066.png similarity index 100% rename from docs/vpc/umn/en-us_image_0214585308.png rename to docs/vpc/umn/en-us_image_0000001818983066.png diff --git a/docs/vpc/umn/en-us_image_0000001627054058.png b/docs/vpc/umn/en-us_image_0000001818983162.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627054058.png rename to docs/vpc/umn/en-us_image_0000001818983162.png diff --git a/docs/vpc/umn/en-us_image_0118499140.png b/docs/vpc/umn/en-us_image_0000001818983170.png similarity index 100% rename from docs/vpc/umn/en-us_image_0118499140.png rename to docs/vpc/umn/en-us_image_0000001818983170.png diff --git a/docs/vpc/umn/en-us_image_0000001627054062.png b/docs/vpc/umn/en-us_image_0000001818983174.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627054062.png rename to docs/vpc/umn/en-us_image_0000001818983174.png diff --git a/docs/vpc/umn/en-us_image_0000001627334080.png b/docs/vpc/umn/en-us_image_0000001818983186.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627334080.png rename to docs/vpc/umn/en-us_image_0000001818983186.png diff --git a/docs/vpc/umn/en-us_image_0000001627054082.png b/docs/vpc/umn/en-us_image_0000001818983190.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627054082.png rename to docs/vpc/umn/en-us_image_0000001818983190.png diff --git a/docs/vpc/umn/en-us_image_0000001465124712.png b/docs/vpc/umn/en-us_image_0000001818983194.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001465124712.png rename to docs/vpc/umn/en-us_image_0000001818983194.png diff --git a/docs/vpc/umn/en-us_image_0000001627055450.png b/docs/vpc/umn/en-us_image_0000001818983198.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627055450.png rename to docs/vpc/umn/en-us_image_0000001818983198.png diff --git a/docs/vpc/umn/en-us_image_0209577986.png b/docs/vpc/umn/en-us_image_0000001818983218.png similarity index 100% rename from docs/vpc/umn/en-us_image_0209577986.png rename to docs/vpc/umn/en-us_image_0000001818983218.png diff --git a/docs/vpc/umn/en-us_image_0191594527.png b/docs/vpc/umn/en-us_image_0000001818983242.png similarity index 100% rename from docs/vpc/umn/en-us_image_0191594527.png rename to docs/vpc/umn/en-us_image_0000001818983242.png diff --git a/docs/vpc/umn/en-us_image_0000001627055454.png b/docs/vpc/umn/en-us_image_0000001818983298.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627055454.png rename to docs/vpc/umn/en-us_image_0000001818983298.png diff --git a/docs/vpc/umn/en-us_image_0000001627056086.png b/docs/vpc/umn/en-us_image_0000001818983374.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627056086.png rename to docs/vpc/umn/en-us_image_0000001818983374.png diff --git a/docs/vpc/umn/en-us_image_0000001818983398.png b/docs/vpc/umn/en-us_image_0000001818983398.png new file mode 100644 index 000000000..f3053c060 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001818983398.png differ diff --git a/docs/vpc/umn/en-us_image_0000001627056574.png b/docs/vpc/umn/en-us_image_0000001818983406.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627056574.png rename to docs/vpc/umn/en-us_image_0000001818983406.png diff --git a/docs/vpc/umn/en-us_image_0000001627056686.png b/docs/vpc/umn/en-us_image_0000001818983414.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627056686.png rename to docs/vpc/umn/en-us_image_0000001818983414.png diff --git a/docs/vpc/umn/en-us_image_0000001627744152.png b/docs/vpc/umn/en-us_image_0000001818983426.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001627744152.png rename to docs/vpc/umn/en-us_image_0000001818983426.png diff --git a/docs/vpc/umn/en-us_image_0000001209777270.png b/docs/vpc/umn/en-us_image_0000001818983474.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001209777270.png rename to docs/vpc/umn/en-us_image_0000001818983474.png diff --git a/docs/vpc/umn/en-us_image_0000001646961692.png b/docs/vpc/umn/en-us_image_0000001818983486.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001646961692.png rename to docs/vpc/umn/en-us_image_0000001818983486.png diff --git a/docs/vpc/umn/en-us_image_0000001675254013.png b/docs/vpc/umn/en-us_image_0000001818983494.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675254013.png rename to docs/vpc/umn/en-us_image_0000001818983494.png diff --git a/docs/vpc/umn/en-us_image_0000001675254017.png b/docs/vpc/umn/en-us_image_0000001818983506.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675254017.png rename to docs/vpc/umn/en-us_image_0000001818983506.png diff --git a/docs/vpc/umn/en-us_image_0000001675254021.png b/docs/vpc/umn/en-us_image_0000001818983610.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675254021.png rename to docs/vpc/umn/en-us_image_0000001818983610.png diff --git a/docs/vpc/umn/en-us_image_0000001832479012.png b/docs/vpc/umn/en-us_image_0000001832479012.png new file mode 100644 index 000000000..2fb3fb2dd Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001832479012.png differ diff --git a/docs/vpc/umn/en-us_image_0000001602035305.png b/docs/vpc/umn/en-us_image_0000001865582513.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001602035305.png rename to docs/vpc/umn/en-us_image_0000001865582513.png diff --git a/docs/vpc/umn/en-us_image_0000001163949251.png b/docs/vpc/umn/en-us_image_0000001865582577.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001163949251.png rename to docs/vpc/umn/en-us_image_0000001865582577.png diff --git a/docs/vpc/umn/en-us_image_0000001675254033.png b/docs/vpc/umn/en-us_image_0000001865582585.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675254033.png rename to docs/vpc/umn/en-us_image_0000001865582585.png diff --git a/docs/vpc/umn/en-us_image_0000001675255405.png b/docs/vpc/umn/en-us_image_0000001865582593.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675255405.png rename to docs/vpc/umn/en-us_image_0000001865582593.png diff --git a/docs/vpc/umn/en-us_image_0211560998.png b/docs/vpc/umn/en-us_image_0000001865582617.png similarity index 100% rename from docs/vpc/umn/en-us_image_0211560998.png rename to docs/vpc/umn/en-us_image_0000001865582617.png diff --git a/docs/vpc/umn/en-us_image_0284993717.png b/docs/vpc/umn/en-us_image_0000001865582629.png similarity index 100% rename from docs/vpc/umn/en-us_image_0284993717.png rename to docs/vpc/umn/en-us_image_0000001865582629.png diff --git a/docs/vpc/umn/en-us_image_0000001675256029.png b/docs/vpc/umn/en-us_image_0000001865582633.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675256029.png rename to docs/vpc/umn/en-us_image_0000001865582633.png diff --git a/docs/vpc/umn/en-us_image_0000001675256529.png b/docs/vpc/umn/en-us_image_0000001865582665.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675256529.png rename to docs/vpc/umn/en-us_image_0000001865582665.png diff --git a/docs/vpc/umn/en-us_image_0000001675256657.png b/docs/vpc/umn/en-us_image_0000001865582673.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675256657.png rename to docs/vpc/umn/en-us_image_0000001865582673.png diff --git a/docs/vpc/umn/en-us_image_0000001237328110.png b/docs/vpc/umn/en-us_image_0000001865582677.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001237328110.png rename to docs/vpc/umn/en-us_image_0000001865582677.png diff --git a/docs/vpc/umn/en-us_image_0000001675258381.png b/docs/vpc/umn/en-us_image_0000001865582681.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675258381.png rename to docs/vpc/umn/en-us_image_0000001865582681.png diff --git a/docs/vpc/umn/en-us_image_0000001675258889.png b/docs/vpc/umn/en-us_image_0000001865582701.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675258889.png rename to docs/vpc/umn/en-us_image_0000001865582701.png diff --git a/docs/vpc/umn/en-us_image_0000001675373901.png b/docs/vpc/umn/en-us_image_0000001865582721.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675373901.png rename to docs/vpc/umn/en-us_image_0000001865582721.png diff --git a/docs/vpc/umn/en-us_image_0000001675373905.png b/docs/vpc/umn/en-us_image_0000001865582729.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675373905.png rename to docs/vpc/umn/en-us_image_0000001865582729.png diff --git a/docs/vpc/umn/en-us_image_0000001675373909.png b/docs/vpc/umn/en-us_image_0000001865582809.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675373909.png rename to docs/vpc/umn/en-us_image_0000001865582809.png diff --git a/docs/vpc/umn/en-us_image_0000001675373913.png b/docs/vpc/umn/en-us_image_0000001865582817.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675373913.png rename to docs/vpc/umn/en-us_image_0000001865582817.png diff --git a/docs/vpc/umn/en-us_image_0000001675373917.png b/docs/vpc/umn/en-us_image_0000001865582825.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675373917.png rename to docs/vpc/umn/en-us_image_0000001865582825.png diff --git a/docs/vpc/umn/en-us_image_0000001675375297.png b/docs/vpc/umn/en-us_image_0000001865582893.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675375297.png rename to docs/vpc/umn/en-us_image_0000001865582893.png diff --git a/docs/vpc/umn/en-us_image_0191544038.png b/docs/vpc/umn/en-us_image_0000001865582905.png similarity index 100% rename from docs/vpc/umn/en-us_image_0191544038.png rename to docs/vpc/umn/en-us_image_0000001865582905.png diff --git a/docs/vpc/umn/en-us_image_0000001675375405.png b/docs/vpc/umn/en-us_image_0000001865582933.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675375405.png rename to docs/vpc/umn/en-us_image_0000001865582933.png diff --git a/docs/vpc/umn/en-us_image_0275513364.png b/docs/vpc/umn/en-us_image_0000001865582937.png similarity index 100% rename from docs/vpc/umn/en-us_image_0275513364.png rename to docs/vpc/umn/en-us_image_0000001865582937.png diff --git a/docs/vpc/umn/en-us_image_0285048674.png b/docs/vpc/umn/en-us_image_0000001865582941.png similarity index 100% rename from docs/vpc/umn/en-us_image_0285048674.png rename to docs/vpc/umn/en-us_image_0000001865582941.png diff --git a/docs/vpc/umn/en-us_image_0000001675378241.png b/docs/vpc/umn/en-us_image_0000001865582981.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675378241.png rename to docs/vpc/umn/en-us_image_0000001865582981.png diff --git a/docs/vpc/umn/en-us_image_0000001675413821.png b/docs/vpc/umn/en-us_image_0000001865582989.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675413821.png rename to docs/vpc/umn/en-us_image_0000001865582989.png diff --git a/docs/vpc/umn/en-us_image_0000001675413825.png b/docs/vpc/umn/en-us_image_0000001865583133.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675413825.png rename to docs/vpc/umn/en-us_image_0000001865583133.png diff --git a/docs/vpc/umn/en-us_image_0000001865583153.png b/docs/vpc/umn/en-us_image_0000001865583153.png new file mode 100644 index 000000000..53878c8d1 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865583153.png differ diff --git a/docs/vpc/umn/en-us_image_0000001675413829.png b/docs/vpc/umn/en-us_image_0000001865583165.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675413829.png rename to docs/vpc/umn/en-us_image_0000001865583165.png diff --git a/docs/vpc/umn/en-us_image_0000001675413833.png b/docs/vpc/umn/en-us_image_0000001865583185.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675413833.png rename to docs/vpc/umn/en-us_image_0000001865583185.png diff --git a/docs/vpc/umn/en-us_image_0000001462622484.png b/docs/vpc/umn/en-us_image_0000001865583217.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001462622484.png rename to docs/vpc/umn/en-us_image_0000001865583217.png diff --git a/docs/vpc/umn/en-us_image_0000001675413841.png b/docs/vpc/umn/en-us_image_0000001865583245.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675413841.png rename to docs/vpc/umn/en-us_image_0000001865583245.png diff --git a/docs/vpc/umn/en-us_image_0157880395.png b/docs/vpc/umn/en-us_image_0000001865583253.png similarity index 100% rename from docs/vpc/umn/en-us_image_0157880395.png rename to docs/vpc/umn/en-us_image_0000001865583253.png diff --git a/docs/vpc/umn/en-us_image_0000001865583269.png b/docs/vpc/umn/en-us_image_0000001865583269.png new file mode 100644 index 000000000..f1f960fee Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865583269.png differ diff --git a/docs/vpc/umn/en-us_image_0000001675413845.png b/docs/vpc/umn/en-us_image_0000001865583297.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675413845.png rename to docs/vpc/umn/en-us_image_0000001865583297.png diff --git a/docs/vpc/umn/en-us_image_0000001337710801.png b/docs/vpc/umn/en-us_image_0000001865583301.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001337710801.png rename to docs/vpc/umn/en-us_image_0000001865583301.png diff --git a/docs/vpc/umn/en-us_image_0000001675415213.png b/docs/vpc/umn/en-us_image_0000001865662721.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675415213.png rename to docs/vpc/umn/en-us_image_0000001865662721.png diff --git a/docs/vpc/umn/en-us_image_0000001865662737.png b/docs/vpc/umn/en-us_image_0000001865662737.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865662737.png differ diff --git a/docs/vpc/umn/en-us_image_0000001675415841.png b/docs/vpc/umn/en-us_image_0000001865662745.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675415841.png rename to docs/vpc/umn/en-us_image_0000001865662745.png diff --git a/docs/vpc/umn/en-us_image_0118499144.png b/docs/vpc/umn/en-us_image_0000001865662749.png similarity index 100% rename from docs/vpc/umn/en-us_image_0118499144.png rename to docs/vpc/umn/en-us_image_0000001865662749.png diff --git a/docs/vpc/umn/en-us_image_0162733894.png b/docs/vpc/umn/en-us_image_0000001865662753.png similarity index 100% rename from docs/vpc/umn/en-us_image_0162733894.png rename to docs/vpc/umn/en-us_image_0000001865662753.png diff --git a/docs/vpc/umn/en-us_image_0000001865662757.jpg b/docs/vpc/umn/en-us_image_0000001865662757.jpg new file mode 100644 index 000000000..ad5684271 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865662757.jpg differ diff --git a/docs/vpc/umn/en-us_image_0000001166028070.png b/docs/vpc/umn/en-us_image_0000001865662761.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001166028070.png rename to docs/vpc/umn/en-us_image_0000001865662761.png diff --git a/docs/vpc/umn/en-us_image_0000001675416345.png b/docs/vpc/umn/en-us_image_0000001865662765.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675416345.png rename to docs/vpc/umn/en-us_image_0000001865662765.png diff --git a/docs/vpc/umn/en-us_image_0000001675418673.png b/docs/vpc/umn/en-us_image_0000001865662773.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675418673.png rename to docs/vpc/umn/en-us_image_0000001865662773.png diff --git a/docs/vpc/umn/en-us_image_0284920908.png b/docs/vpc/umn/en-us_image_0000001865662817.png similarity index 100% rename from docs/vpc/umn/en-us_image_0284920908.png rename to docs/vpc/umn/en-us_image_0000001865662817.png diff --git a/docs/vpc/umn/en-us_image_0000001230120807.png b/docs/vpc/umn/en-us_image_0000001865662829.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001230120807.png rename to docs/vpc/umn/en-us_image_0000001865662829.png diff --git a/docs/vpc/umn/en-us_image_0000001521533677.png b/docs/vpc/umn/en-us_image_0000001865662833.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001521533677.png rename to docs/vpc/umn/en-us_image_0000001865662833.png diff --git a/docs/vpc/umn/en-us_image_0000001207827554.png b/docs/vpc/umn/en-us_image_0000001865662841.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001207827554.png rename to docs/vpc/umn/en-us_image_0000001865662841.png diff --git a/docs/vpc/umn/en-us_image_0000001197426329.png b/docs/vpc/umn/en-us_image_0000001865662885.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001197426329.png rename to docs/vpc/umn/en-us_image_0000001865662885.png diff --git a/docs/vpc/umn/en-us_image_0000001675613937.png b/docs/vpc/umn/en-us_image_0000001865662901.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675613937.png rename to docs/vpc/umn/en-us_image_0000001865662901.png diff --git a/docs/vpc/umn/en-us_image_0000001650535960.png b/docs/vpc/umn/en-us_image_0000001865662949.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001650535960.png rename to docs/vpc/umn/en-us_image_0000001865662949.png diff --git a/docs/vpc/umn/en-us_image_0000001540846821.png b/docs/vpc/umn/en-us_image_0000001865662969.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001540846821.png rename to docs/vpc/umn/en-us_image_0000001865662969.png diff --git a/docs/vpc/umn/en-us_image_0000001675613941.png b/docs/vpc/umn/en-us_image_0000001865662989.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675613941.png rename to docs/vpc/umn/en-us_image_0000001865662989.png diff --git a/docs/vpc/umn/en-us_image_0000001675613945.png b/docs/vpc/umn/en-us_image_0000001865663001.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675613945.png rename to docs/vpc/umn/en-us_image_0000001865663001.png diff --git a/docs/vpc/umn/en-us_image_0000001865663033.png b/docs/vpc/umn/en-us_image_0000001865663033.png new file mode 100644 index 000000000..ce84b5c56 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865663033.png differ diff --git a/docs/vpc/umn/en-us_image_0000001675613953.png b/docs/vpc/umn/en-us_image_0000001865663057.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675613953.png rename to docs/vpc/umn/en-us_image_0000001865663057.png diff --git a/docs/vpc/umn/en-us_image_0000001675613957.png b/docs/vpc/umn/en-us_image_0000001865663089.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675613957.png rename to docs/vpc/umn/en-us_image_0000001865663089.png diff --git a/docs/vpc/umn/en-us_image_0000001865663101.png b/docs/vpc/umn/en-us_image_0000001865663101.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865663101.png differ diff --git a/docs/vpc/umn/en-us_image_0000001675615337.png b/docs/vpc/umn/en-us_image_0000001865663109.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675615337.png rename to docs/vpc/umn/en-us_image_0000001865663109.png diff --git a/docs/vpc/umn/en-us_image_0152667656.png b/docs/vpc/umn/en-us_image_0000001865663121.png similarity index 100% rename from docs/vpc/umn/en-us_image_0152667656.png rename to docs/vpc/umn/en-us_image_0000001865663121.png diff --git a/docs/vpc/umn/en-us_image_0000001675616433.png b/docs/vpc/umn/en-us_image_0000001865663129.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675616433.png rename to docs/vpc/umn/en-us_image_0000001865663129.png diff --git a/docs/vpc/umn/en-us_image_0000001675813933.png b/docs/vpc/umn/en-us_image_0000001865663133.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675813933.png rename to docs/vpc/umn/en-us_image_0000001865663133.png diff --git a/docs/vpc/umn/en-us_image_0000001675616561.png b/docs/vpc/umn/en-us_image_0000001865663157.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675616561.png rename to docs/vpc/umn/en-us_image_0000001865663157.png diff --git a/docs/vpc/umn/en-us_image_0191577030.png b/docs/vpc/umn/en-us_image_0000001865663181.png similarity index 100% rename from docs/vpc/umn/en-us_image_0191577030.png rename to docs/vpc/umn/en-us_image_0000001865663181.png diff --git a/docs/vpc/umn/en-us_image_0209606948.png b/docs/vpc/umn/en-us_image_0000001865663209.png similarity index 100% rename from docs/vpc/umn/en-us_image_0209606948.png rename to docs/vpc/umn/en-us_image_0000001865663209.png diff --git a/docs/vpc/umn/en-us_image_0000001675618277.png b/docs/vpc/umn/en-us_image_0000001865663213.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675618277.png rename to docs/vpc/umn/en-us_image_0000001865663213.png diff --git a/docs/vpc/umn/en-us_image_0000001512876289.png b/docs/vpc/umn/en-us_image_0000001865663449.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001512876289.png rename to docs/vpc/umn/en-us_image_0000001865663449.png diff --git a/docs/vpc/umn/en-us_image_0167840073.png b/docs/vpc/umn/en-us_image_0000001865663453.png similarity index 100% rename from docs/vpc/umn/en-us_image_0167840073.png rename to docs/vpc/umn/en-us_image_0000001865663453.png diff --git a/docs/vpc/umn/en-us_image_0000001675619157.png b/docs/vpc/umn/en-us_image_0000001865663457.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001675619157.png rename to docs/vpc/umn/en-us_image_0000001865663457.png diff --git a/docs/vpc/umn/en-us_image_0000001676063997.png b/docs/vpc/umn/en-us_image_0000001865663461.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001676063997.png rename to docs/vpc/umn/en-us_image_0000001865663461.png diff --git a/docs/vpc/umn/en-us_image_0000001681512581.png b/docs/vpc/umn/en-us_image_0000001865663473.png similarity index 100% rename from docs/vpc/umn/en-us_image_0000001681512581.png rename to docs/vpc/umn/en-us_image_0000001865663473.png diff --git a/docs/vpc/umn/en-us_image_0000001865663509.png b/docs/vpc/umn/en-us_image_0000001865663509.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865663509.png differ diff --git a/docs/vpc/umn/en-us_image_0000001865663521.png b/docs/vpc/umn/en-us_image_0000001865663521.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001865663521.png differ diff --git a/docs/vpc/umn/en-us_image_0240332622.png b/docs/vpc/umn/en-us_image_0000001865663537.png similarity index 100% rename from docs/vpc/umn/en-us_image_0240332622.png rename to docs/vpc/umn/en-us_image_0000001865663537.png diff --git a/docs/vpc/umn/en-us_image_0000001879005797.png b/docs/vpc/umn/en-us_image_0000001879005797.png new file mode 100644 index 000000000..f6203273d Binary files /dev/null and b/docs/vpc/umn/en-us_image_0000001879005797.png differ diff --git a/docs/vpc/umn/en-us_image_0142360062.png b/docs/vpc/umn/en-us_image_0142360062.png deleted file mode 100644 index f5a39cdd6..000000000 Binary files a/docs/vpc/umn/en-us_image_0142360062.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0162391155.png b/docs/vpc/umn/en-us_image_0162391155.png deleted file mode 100644 index 8dc4f6feb..000000000 Binary files a/docs/vpc/umn/en-us_image_0162391155.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0214585306.png b/docs/vpc/umn/en-us_image_0214585306.png deleted file mode 100644 index e0684deaf..000000000 Binary files a/docs/vpc/umn/en-us_image_0214585306.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0214585307.png b/docs/vpc/umn/en-us_image_0214585307.png deleted file mode 100644 index f5a39cdd6..000000000 Binary files a/docs/vpc/umn/en-us_image_0214585307.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0233469196.png b/docs/vpc/umn/en-us_image_0233469196.png deleted file mode 100644 index a844ced30..000000000 Binary files a/docs/vpc/umn/en-us_image_0233469196.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_image_0233469654.png b/docs/vpc/umn/en-us_image_0233469654.png deleted file mode 100644 index f5a39cdd6..000000000 Binary files a/docs/vpc/umn/en-us_image_0233469654.png and /dev/null differ diff --git a/docs/vpc/umn/en-us_topic_0000001818822858.html b/docs/vpc/umn/en-us_topic_0000001818822858.html new file mode 100644 index 000000000..11173ef67 --- /dev/null +++ b/docs/vpc/umn/en-us_topic_0000001818822858.html @@ -0,0 +1,53 @@ + + +

        What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?

        +

        Table 1 lists the differences between 5_bgp, 5_mailbgp, and 5_gray EIPs.

        + +
        + + + + + + + + + + + + + + + + + + + + + +
        Table 1 Differences between 5_bgp, 5_mailbgp, and 5_gray EIPs

        Dimension

        +

        5_bgp EIP

        +

        5_gray EIP

        +

        5_mailbgp EIP

        +

        Application scenario

        +

        Dynamic BGP provides automatic failover and chooses the optimal path when a network connection fails.

        +

        5_bgp EIPs can be bound to cloud resources except dedicated load balancers.

        +

        5_gray EIPs are no longer supported.

        +

        5_mailbgp EIPs are used together with port 25, 465, or 587 for email services.

        +

        Differences

        +
        • Cannot be used for email services.
        • Can be bound to dedicated and shared load balancers.
        +
        • Not suggested to be bound to dedicated or shared load balancers by default.
        • Cannot be used for email services.
        +
        • Cannot be bound to dedicated load balancers.
        • Can be used for email services.
        +

        Constraints

        +

        The selected EIP type cannot be changed after the EIP is assigned.

        +
        • In eu-de, existing 5_gray EIPs cannot be bound to dedicated or shared load balancers. You can use 5_bgp EIPs instead.
        • In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
        +

        If you need an EIP of this type, contact the account administrator to grant the required permissions.

        +
        +
        +
        +
        +
        +
        Parent topic: EIPs
        +
        +
        + diff --git a/docs/vpc/umn/en-us_topic_0013748715.html b/docs/vpc/umn/en-us_topic_0013748715.html index 2b4bd5a6d..8b5fc2b96 100644 --- a/docs/vpc/umn/en-us_topic_0013748715.html +++ b/docs/vpc/umn/en-us_topic_0013748715.html @@ -8,10 +8,10 @@

        Notes and Constraints

        If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when you create it.

        The default security group name is default. For details, see Default Security Group and Its Rules.

        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select the desired region and project.
        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

          The Virtual Private Cloud page is displayed.

          +

          Procedure

          1. Log in to the management console.
          2. Click in the upper left corner and select the desired region and project.
          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

            The Virtual Private Cloud page is displayed.

          4. In the navigation pane on the left, choose Access Control > Security Groups.

            The security group list is displayed.

          5. In the upper right corner, click Create Security Group.

            The Create Security Group page is displayed.

            -
          6. Configure the parameters as prompted.
            Figure 1 Create Security Group
            +
          7. Configure the parameters as prompted.
            Figure 1 Create Security Group
            @@ -45,7 +45,7 @@ @@ -67,7 +67,7 @@
            -
            Parent topic: Security Group
            +
            Parent topic: Managing a Security Group
            diff --git a/docs/vpc/umn/en-us_topic_0013748726.html b/docs/vpc/umn/en-us_topic_0013748726.html index 57a95dc05..1644b73bd 100644 --- a/docs/vpc/umn/en-us_topic_0013748726.html +++ b/docs/vpc/umn/en-us_topic_0013748726.html @@ -4,123 +4,123 @@

            Scenarios

            A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.

            A subnet is configured with DHCP by default. When an ECS in this subnet starts, the ECS automatically obtains an IP address using DHCP.

            -

            Procedure

            1. Log in to the management console.
            1. Click in the upper left corner and select the desired region and project.
            2. Click in the upper left corner and choose Network > Virtual Private Cloud.

              The Virtual Private Cloud page is displayed.

              +

              Procedure

              1. Log in to the management console.
              1. Click in the upper left corner and select the desired region and project.
              2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                The Virtual Private Cloud page is displayed.

              3. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
              4. Click Create Subnet.

                The Create Subnet page is displayed.

                -
              5. Set the parameters as prompted.
                Figure 1 Create Subnet
                -

                +
              6. Set the parameters as prompted.
                Figure 1 Create Subnet
                -
            Table 1 Parameter description

            Parameter

            Mandatory

            A template comes with default security group rules, helping you quickly create security groups. The following templates are provided:

            -
            • Custom: This template allows you to create security groups with custom security group rules.
            • General-purpose web server (default value): The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389.
            • All ports open: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks.
            +
            • Custom: This template allows you to create security groups with custom security group rules.
            • General-purpose web server (default value): The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389.
            • All ports open: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks.

            General-purpose web server
            Table 1 Parameter descriptions

            Parameter

            +
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 1 Parameter descriptions

            Parameter

            Description

            +

            Description

            Example Value

            +

            Example Value

            VPC

            +

            VPC

            The VPC for which you want to create a subnet.

            +

            The VPC for which you want to create a subnet.

            -

            +

            -

            Name

            +

            Name

            The 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.

            Subnet

            +

            Subnet

            IPv4 CIDR Block

            +

            IPv4 CIDR Block

            The CIDR block for the subnet. This value must be within the VPC CIDR block.

            +

            The CIDR block for the subnet. This value must be within the VPC CIDR block.

            +

            If the VPC has a secondary CIDR block, you can select the primary or the secondary CIDR block that the subnet will belong to based on service requirements.

            192.168.0.0/24

            +

            192.168.0.0/24

            IPv6 CIDR Block

            +

            IPv6 CIDR Block

            Specifies whether to set IPv6 CIDR Block to Enable.

            +

            Specifies whether to set IPv6 CIDR Block to Enable.

            If you select this option, 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.

            -

            +

            -

            Associated Route Table

            +

            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

            +

            Default

            Advanced Settings/Gateway

            +

            Advanced Settings/Gateway

            The gateway address of the subnet.

            +

            The gateway address of the subnet.

            192.168.0.1

            +

            192.168.0.1

            Advanced Settings/DNS Server Address

            +

            Advanced Settings/DNS Server Address

            By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

            +

            By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

            100.125.x.x

            +

            100.125.x.x

            Advanced Settings/NTP Server Address

            +

            Advanced Settings/NTP Server Address

            The IP address of the NTP server. This parameter is optional.

            +

            The IP address of the NTP server. This parameter is optional.

            You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added.

            A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).

            192.168.2.1

            +

            192.168.2.1

            Advanced Settings/Tag

            +

            Advanced Settings/Tag

            The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

            -

            The tag key and value must meet the requirements listed in Table 2.

            +

            The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

            +

            The tag key and value must meet the requirements listed in Table 2.

            • Key: subnet_key1
            • Value: subnet-01
            +
            • Key: subnet_key1
            • Value: subnet-01

            Advanced Settings/Description

            +

            Advanced Settings/Description

            Supplementary information about the subnet. This parameter is optional.

            +

            Supplementary information about the subnet. This parameter is optional.

            The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

            -

            +

            -
            -
            Table 2 Subnet tag key and value requirements

            Parameter

            +
            - - - - - - - - diff --git a/docs/vpc/umn/en-us_topic_0013748729.html b/docs/vpc/umn/en-us_topic_0013748729.html index dbcaf4cde..b6f01e3cd 100644 --- a/docs/vpc/umn/en-us_topic_0013748729.html +++ b/docs/vpc/umn/en-us_topic_0013748729.html @@ -4,7 +4,7 @@

            Overview

            The Virtual Private Cloud (VPC) service enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security and simplifying network deployment. You can configure and manage the virtual networks as required.

            Within your own VPC, you can create security groups and VPNs, configure IP address ranges, specify bandwidth sizes, manage the networks in the VPC, and make changes to these networks as needed, quickly and securely. You can also define rules to control communications between ECSs in the same security group or in different security groups.

            -
            Figure 1 VPC components
            +
            Figure 1 VPC components

            Accessing the VPC Service

            You can access the VPC service through the management console or using HTTPS-based APIs.
            • Management console

              You can use the console to directly perform operations on VPC resources. To access the VPC service, log in to the management console and select Virtual Private Cloud from the console homepage.

            • API

              If you need to integrate a VPC into a third-party system for secondary development, you can use APIs to access the VPC service. For details, see the Virtual Private Cloud API Reference.

            diff --git a/docs/vpc/umn/en-us_topic_0013748738.html b/docs/vpc/umn/en-us_topic_0013748738.html index 84d213552..58db3f012 100644 --- a/docs/vpc/umn/en-us_topic_0013748738.html +++ b/docs/vpc/umn/en-us_topic_0013748738.html @@ -7,7 +7,7 @@
            -

            Assigning an EIP

            1. Log in to the management console.
            2. Click in the upper left corner and select the desired region and project.
            3. Click in the upper left corner and choose Network > Elastic IP.
            4. On the displayed page, click Assign EIP.
            5. Set the parameters as prompted.
              Figure 1 Assign EIP
              +

              Assigning an EIP

              1. Log in to the management console.
              2. Click in the upper left corner and select the desired region and project.
              3. Click in the upper left corner and choose Network > Elastic IP.
              4. On the displayed page, click Assign EIP.
              5. Set the parameters as prompted.
                Figure 1 Assign EIP
            Table 2 Subnet tag key and value requirements

            Parameter

            Requirements

            +

            Requirements

            Example Value

            +

            Example Value

            Key

            +

            Key

            • Cannot be left blank.
            • Must be unique for each subnet.
            • Can contain a maximum of 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Cannot be left blank.
            • Must be unique for each subnet.
            • Can contain a maximum of 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            subnet_key1

            +

            subnet_key1

            Value

            +

            Value

            • Can contain a maximum of 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Can contain a maximum of 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            subnet-01

            +

            subnet-01
            @@ -26,7 +26,7 @@ - @@ -57,7 +57,7 @@ @@ -88,28 +88,28 @@
            Table 1 Parameter descriptions

            Parameter

            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

            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.

            +

            An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.

            default

            -
            Table 2 EIP tag requirements

            Parameter

            +
            - - - - - - - - @@ -117,7 +117,7 @@
          8. Click Create Now.
          9. Click Submit.
            10. -

            Binding an EIP

            1. On the EIPs page, locate the row that contains the target EIP, and click Bind.
            2. Select the instance that you want to bind the EIP to.
              Figure 2 Bind EIP
              +

              Binding an EIP

              1. On the EIPs page, locate the row that contains the target EIP, and click Bind.
              2. Select the instance that you want to bind the EIP to.
                Figure 2 Bind EIP
              3. 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?

              diff --git a/docs/vpc/umn/en-us_topic_0013748743.html b/docs/vpc/umn/en-us_topic_0013748743.html index c31e7e264..cd3ea0f2b 100644 --- a/docs/vpc/umn/en-us_topic_0013748743.html +++ b/docs/vpc/umn/en-us_topic_0013748743.html @@ -5,7 +5,7 @@

              This section describes how to modify the dedicated bandwidth or shared bandwidth of an EIP. For details about how to modify a shared bandwidth, see Modifying a Shared Bandwidth.

              -

              Procedure

              1. Log in to the management console.
              2. Click in the upper left corner and select the desired region and project.
              3. Click in the upper left corner and choose Network > Elastic IP.
              4. Locate the row that contains the target EIP in the EIP list, click More in the Operation column, and select Modify Bandwidth.
              5. Modify the bandwidth parameters as prompted.

                +

                Procedure

                1. Log in to the management console.
                2. Click in the upper left corner and select the desired region and project.
                3. Click in the upper left corner, and choose Network > Elastic IP.
                4. Locate the row that contains the target EIP in the EIP list, click More in the Operation column, and select Modify Bandwidth.
                5. Modify the bandwidth parameters as prompted.

                6. Click Next.
                7. Click Submit.
              diff --git a/docs/vpc/umn/en-us_topic_0013935842.html b/docs/vpc/umn/en-us_topic_0013935842.html index 010bc423a..a79e633da 100644 --- a/docs/vpc/umn/en-us_topic_0013935842.html +++ b/docs/vpc/umn/en-us_topic_0013935842.html @@ -4,16 +4,16 @@

              Scenarios

              A VPC provides an isolated virtual network for ECSs. You can configure and manage the network as required.

              You can create a VPC by following the procedure provided in this section. Then, create subnets, security groups, and assign EIPs by following the procedure provided in subsequent sections based on your actual network requirements.

              -

              Procedure

              1. Log in to the management console.
              2. Click in the upper left corner and select the desired region and project.
              3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                The Virtual Private Cloud page is displayed.

                +

                Procedure

                1. Log in to the management console.
                2. Click in the upper left corner and select the desired region and project.
                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                  The Virtual Private Cloud page is displayed.

                4. Click Create VPC.
                5. 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.

            Table 2 EIP tag requirements

            Parameter

            Requirement

            +

            Requirement

            Example Value

            +

            Example Value

            Key

            +

            Key

            • Cannot be left blank.
            • Must be unique for each EIP.
            • Can contain a maximum of 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Cannot be left blank.
            • The key value must be unique for the same EIP.
            • Can contain up to 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            Ipv4_key1

            +

            Ipv4_key1

            Value

            +

            Value

            • Can contain a maximum of 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Can contain up to 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            3005eip

            +

            3005eip
            - - - @@ -102,7 +102,7 @@ - - diff --git a/docs/vpc/umn/en-us_topic_0017816228.html b/docs/vpc/umn/en-us_topic_0017816228.html index 6ebe1ea57..e80ce7027 100644 --- a/docs/vpc/umn/en-us_topic_0017816228.html +++ b/docs/vpc/umn/en-us_topic_0017816228.html @@ -1,228 +1,228 @@

            Configuring a VPC for ECSs That Access the Internet Using EIPs

            -
            1. Log in to the management console.
            2. Click in the upper left corner and select the desired region and project.
            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

              The Virtual Private Cloud page is displayed.

              -
            4. Click Create VPC.
            5. 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.

              +
              1. Log in to the management console.
              2. Click in the upper left corner and select the desired region and project.
              3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                The Virtual Private Cloud page is displayed.

                +
              4. Click Create VPC.
              5. 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.

                -
            Table 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.

            -

            @@ -112,7 +112,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
            Table 1 VPC parameter descriptions

            Category

            +
            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
            Table 1 VPC parameter descriptions

            Category

            Parameter

            +

            Parameter

            Description

            +

            Description

            Example Value

            +

            Example Value

            Basic Information

            +

            Basic Information

            Region

            +

            Region

            Select the region nearest to you to ensure the lowest latency possible.

            +

            Select the region nearest to you to ensure the lowest latency possible.

            eu-de

            +

            eu-de

            Basic Information

            +

            Basic Information

            Name

            +

            Name

            The VPC 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.

            +

            The VPC 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.

            VPC-001

            +

            VPC-001

            Basic Information

            +

            Basic Information

            IPv4 CIDR Block

            +

            IPv4 CIDR Block

            The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC).

            -

            The following CIDR blocks are supported:

            -

            10.0.0.0/8-24

            -

            172.16.0.0/12-24

            -

            192.168.0.0/16-24

            +

            The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC).

            +

            The following CIDR blocks are supported:

            +

            10.0.0.0/8-24

            +

            172.16.0.0/12-24

            +

            192.168.0.0/16-24

            192.168.0.0/16

            +

            192.168.0.0/16

            Basic Information

            +

            Basic Information

            Enterprise Project

            +

            Enterprise Project

            The enterprise project to which the VPC belongs.

            -

            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 to which the VPC belongs.

            +

            An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.

            default

            +

            default

            Basic Information/Advanced Settings

            +

            Basic Information/Advanced Settings

            Tag

            +

            Tag

            The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC.

            -

            The tag key and value must meet the requirements listed in Table 2.

            +

            The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC.

            +

            The tag key and value must meet the requirements listed in Table 2.

            • Key: vpc_key1
            • Value: vpc-01
            +
            • Key: vpc_key1
            • Value: vpc-01

            Basic Information/Advanced Settings

            +

            Basic Information/Advanced Settings

            Description

            +

            Description

            Supplementary information about the VPC. This parameter is optional.

            -

            The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

            +

            Supplementary information about the VPC. This parameter is optional.

            +

            The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

            N/A

            +

            N/A

            Default Subnet

            +

            Default Subnet

            Name

            +

            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.

            +

            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.

            Subnet

            +

            Subnet

            Default Subnet

            +

            Default Subnet

            IPv4 CIDR Block

            +

            IPv4 CIDR Block

            The CIDR block for the subnet. This value must be within the VPC CIDR block.

            +

            The CIDR block for the subnet. This value must be within the VPC CIDR block.

            192.168.0.0/24

            +

            192.168.0.0/24

            Default Subnet

            +

            Default Subnet

            IPv6 CIDR Block

            +

            IPv6 CIDR Block

            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.

            +

            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.

            -

            +

            -

            Default Subnet

            +

            Default Subnet

            Associated Route Table

            +

            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

            +

            Default

            Default Subnet/Advanced Settings

            +

            Default Subnet/Advanced Settings

            Gateway

            +

            Gateway

            The gateway address of the subnet.

            +

            The gateway address of the subnet.

            192.168.0.1

            +

            192.168.0.1

            Default Subnet/Advanced Settings

            +

            Default Subnet/Advanced Settings

            DNS Server Address

            +

            DNS Server Address

            By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

            +

            By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

            100.125.x.x

            +

            100.125.x.x

            Default Subnet/Advanced Settings

            +

            Default Subnet/Advanced Settings

            NTP Server Address

            +

            NTP Server Address

            The IP address of the NTP server. This parameter is optional.

            -

            You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added.

            -

            A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).

            +

            The IP address of the NTP server. This parameter is optional.

            +

            You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added.

            +

            A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).

            192.168.2.1

            +

            192.168.2.1

            Default Subnet/Advanced Settings

            +

            Default Subnet/Advanced Settings

            Tag

            +

            Tag

            The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

            -

            The tag key and value must meet the requirements listed in Table 3.

            +

            The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

            +

            The tag key and value must meet the requirements listed in Table 3.

            • Key: subnet_key1
            • Value: subnet-01
            +
            • Key: subnet_key1
            • Value: subnet-01

            Default Subnet/Advanced Settings

            +

            Default Subnet/Advanced Settings

            Description

            +

            Description

            Supplementary information about the subnet. This parameter is optional.

            -

            The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

            +

            Supplementary information about the subnet. This parameter is optional.

            +

            The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

            N/A

            +

            N/A
            -
            Table 2 VPC tag key and value requirements

            Parameter

            +
            - - - - - - - -
            Table 2 VPC tag key and value requirements

            Parameter

            Requirements

            +

            Requirements

            Example Value

            +

            Example Value

            Key

            +

            Key

            • Cannot be left blank.
            • Must be unique for each VPC and can be the same for different VPCs.
            • Can contain a maximum of 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Cannot be left blank.
            • Must be unique for each VPC and can be the same for different VPCs.
            • Can contain a maximum of 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            vpc_key1

            +

            vpc_key1

            Value

            +

            Value

            • Can contain a maximum of 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Can contain a maximum of 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            vpc-01

            +

            vpc-01
            -
            Table 3 Subnet tag key and value requirements

            Parameter

            +
            - - - - - - - -
            Table 3 Subnet tag key and value requirements

            Parameter

            Requirements

            +

            Requirements

            Example Value

            +

            Example Value

            Key

            +

            Key

            • Cannot be left blank.
            • Must be unique for each subnet.
            • Can contain a maximum of 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Cannot be left blank.
            • Must be unique for each subnet.
            • Can contain a maximum of 36 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            subnet_key1

            +

            subnet_key1

            Value

            +

            Value

            • Can contain a maximum of 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)
              +
            • Can contain a maximum of 43 characters.
            • Can contain only the following character types:
              • Uppercase letters
              • Lowercase letters
              • Digits
              • Special characters, including hyphens (-) and underscores (_)

            subnet-01

            +

            subnet-01
            -
          10. Click Create Now.
            11. +
          11. Click Create Now.
            12. diff --git a/docs/vpc/umn/en-us_topic_0030969424.html b/docs/vpc/umn/en-us_topic_0030969424.html index ac00764c2..826bf7833 100644 --- a/docs/vpc/umn/en-us_topic_0030969424.html +++ b/docs/vpc/umn/en-us_topic_0030969424.html @@ -2,7 +2,7 @@

            Subnet

            A subnet is a unique CIDR block with a range of IP addresses in a VPC. All resources in a VPC must be deployed on subnets.

            -
            • By default, all instances in different subnets of the same VPC can communicate with each other and the subnets can be located in different AZs. For example, VPC-A has subnet A01 in AZ A and subnet A02 in AZ B. Subnet A01 and subnet B01 can communicate with each other by default.
            • After a subnet is created, its CIDR block cannot be modified. Subnets in the same VPC cannot overlap.

              A subnet mask can be between the netmask of its VPC CIDR block and /29 netmask. If a VPC CIDR block is 10.0.0.0/16, its subnet mask can between 16 to 29.

              +
              • By default, all instances in different subnets of the same VPC can communicate with each other. If you have a VPC with two subnets in it, they can communicate with each other by default.
              • After a subnet is created, its CIDR block cannot be modified. Subnets in the same VPC cannot overlap.

                A subnet mask can be between the netmask of its VPC CIDR block and /29 netmask. If a VPC CIDR block is 10.0.0.0/16, its subnet mask can be between 16 and 29.

                For example, if the CIDR block of VPC-A is 10.0.0.0/16, you can specify 10.0.0.0/24 for subnet A01, 10.0.1.0/24 for subnet A02, and 10.0.3.0/24 for subnet A03.

                By default, you can create a maximum of 100 subnets in each region. If this cannot meet your service requirements, request a quota increase by referring to What Is a Quota?

                diff --git a/docs/vpc/umn/en-us_topic_0030969462.html b/docs/vpc/umn/en-us_topic_0030969462.html index 280ed778b..4e630b250 100644 --- a/docs/vpc/umn/en-us_topic_0030969462.html +++ b/docs/vpc/umn/en-us_topic_0030969462.html @@ -1,24 +1,21 @@

                Modifying a VPC

                -

                Scenarios

                You can modify the following information about a VPC: +

                Scenarios

                You can modify the following information about a VPC:
                -

                Modifying the Name and Description of a VPC

                1. Log in to the management console.
                2. Click in the upper left corner and select the desired region and project.
                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                  The Virtual Private Cloud page is displayed.

                  -
                4. Modify the name and description of a VPC using either of the following methods:
                  • Method 1:
                    1. In the VPC list, click on the right of the VPC name.
                    2. Enter the VPC name and click OK.
                    +

                    Modifying the Name and Description of a VPC

                    1. Log in to the management console.
                    2. Click in the upper left corner and select the desired region and project.
                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                      The Virtual Private Cloud page is displayed.

                      +
                    4. Modify the name and description of a VPC using either of the following methods:
                      • Method 1:
                        1. In the VPC list, click on the right of the VPC name.
                        2. Enter the VPC name and click OK.
                      • Method 2:
                        1. In the VPC list, click the VPC name with a hyperlink.

                          The Summary page is displayed.

                          -
                        2. Click on the right of the VPC name or description, enter the information, and click .
                        +
                      • Click on the right of the VPC name or description, enter the information, and click .
                -

                Modifying the CIDR Block of a VPC

                1. Log in to the management console.
                2. Click in the upper left corner and select the desired region and project.
                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                  The Virtual Private Cloud page is displayed.

                  +

                  Modifying the CIDR Block of a VPC

                  1. Log in to the management console.
                  2. Click in the upper left corner and select the desired region and project.
                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                    The Virtual Private Cloud page is displayed.

                  1. In the VPC list, locate the row that contains the VPC and click Edit CIDR Block in the Operation column.

                    The Edit CIDR Block dialog box is displayed.

                    -
                  2. Modify the VPC CIDR block as prompted.

                    A VPC CIDR block must be from 10.0.0.0/8-24, 172.16.0.0/12-24, or 192.168.0.0/16-24.

                    -
                    -
                    • If a VPC has no subnets, you can change both its network address and subnet mask.
                      Figure 1 Modifying network address and subnet mask
                      -
                    • If a VPC has subnets, you only can change its subnet mask.
                      Figure 2 Modifying subnet mask
                      -
                    -
                  3. Click OK.
                  +
                4. Click Add Secondary IPv4 CIDR Block.
                5. Enter the secondary CIDR block and click OK.
                diff --git a/docs/vpc/umn/en-us_topic_0030969470.html b/docs/vpc/umn/en-us_topic_0030969470.html index 154f1dcca..43caf0816 100644 --- a/docs/vpc/umn/en-us_topic_0030969470.html +++ b/docs/vpc/umn/en-us_topic_0030969470.html @@ -3,27 +3,27 @@

                Adding a Security Group Rule

                Scenarios

                A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                Each ECS must be associated with at least one security group. If you do not have a security group when creating an ECS, the system provides a default security group.

                -
                Like whitelists, security group rules work as follows:
                • Inbound rules control incoming traffic to instances in the security group.

                  If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                  -

                  By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                  -
                • Outbound rules control outgoing traffic from instances in the security group.

                  If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                  -

                  0.0.0.0/0 represents all IPv4 addresses.

                  -

                  ::/0 represents all IPv6 addresses.

                  +
                  Like whitelists, security group rules work as follows:
                  • Inbound rules control incoming traffic to instances in the security group.

                    If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                    +

                    By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                    +
                  • Outbound rules control outgoing traffic from instances in the security group.

                    If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                    +

                    0.0.0.0/0 represents all IPv4 addresses.

                    +

                    ::/0 represents all IPv6 addresses.

                  If the rules of the security group associated with your instance cannot meet your requirements, for example, you need to allow inbound traffic on a specific TCP port, you can add an inbound rule to allow traffic on the TCP port.

                Security Group Rule Configuration Examples

                • The system provides a default security group. For details about the default security group rules, see Default Security Group and Its Rules. If the default security group rules cannot meet your requirements, you can modify them.
                • Before configuring security group rules, you need to plan access policies for instances in the security group. For details about common security group rule configuration examples, see Security Group Configuration Examples.
                -

                Procedure

                1. Log in to the management console.
                2. Click in the upper left corner and select the desired region and project.
                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                  The Virtual Private Cloud page is displayed.

                  +

                  Procedure

                  1. Log in to the management console.
                  2. Click in the upper left corner and select the desired region and project.
                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                    The Virtual Private Cloud page is displayed.

                  4. In the navigation pane on the left, choose Access Control > Security Groups.

                    The security group list is displayed.

                  5. 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.

                  6. On the Inbound Rules tab, click Add Rule.

                    The Add Inbound Rule dialog box is displayed.

                  7. 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

                    +
                    - @@ -53,7 +53,7 @@ @@ -74,11 +74,11 @@
                  8. Click OK.

                    The inbound rule list is displayed.

                  9. On the Outbound Rules tab, click Add Rule.

                    The Add Outbound Rule dialog box is displayed.

                  10. Configure required parameters.

                    You can click + to add more outbound rules.

                    -
                    Figure 2 Add Outbound Rule
                    +
                    Figure 2 Add Outbound Rule
                    -
                    11. Table 1 Inbound rule parameter description

                    Parameter

                    Description

                    +

                    Description

                    Example Value

                    Source
                    Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example:
                    • IP address:
                      • Single IP address: 192.168.10.10/32
                      • All IP addresses: 0.0.0.0/0
                      • IP address range: 192.168.1.0/24
                      -
                    • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                    • IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                    +
                  11. Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.

                    12. If the source is a security group, this rule will apply to all instances associated with the selected security group.

                    Table 2 Outbound rule parameter description

                    Parameter

                    +
                    - @@ -109,8 +109,8 @@ @@ -132,7 +132,7 @@
                    -
                    Parent topic: Security Group
                    +
                    Parent topic: Managing Security Group Rules
                    diff --git a/docs/vpc/umn/en-us_topic_0038263963.html b/docs/vpc/umn/en-us_topic_0038263963.html index dde7ab9a9..074847284 100644 --- a/docs/vpc/umn/en-us_topic_0038263963.html +++ b/docs/vpc/umn/en-us_topic_0038263963.html @@ -2,40 +2,40 @@

                    Route Table

                    Route Tables

                    A route table contains a set of routes that are used to determine where network traffic from your subnets in a VPC is directed. Each subnet must be associated with a route table. A subnet can only be associated with one route table, but you can associate multiple subnets with the same route table.

                    -
                    Figure 1 Route tables
                    +
                    Figure 1 Route tables
                    • Default route table: When you create a VPC, the system automatically generates a default route table for the VPC. If you create a subnet in the VPC, the subnet automatically associates with the default route table. The default route table ensures that subnets in a VPC can communicate with each other.
                      • You can add routes to, delete routes from, and modify routes in the default route table, but cannot delete the table.
                      • When you create a VPC endpoint, VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or modified.
                    • Custom route table: If you do not want to use the default route table, you can create a custom route table and associate it with the subnet. Custom route tables can be deleted if they are no longer required.

                      The custom route table associated with a subnet affects only the outbound traffic. The default route table of a subnet controls the inbound traffic.

                    -

                    Route

                    You can add routes to default and custom route tables and configure the destination, next hop type, and next hop in the routes to determine where network traffic is directed. Routes are classified into system routes and custom routes.

                    -
                    • System routes: These routes are automatically added by the system and cannot be modified or deleted.
                      After a route table is created, the system automatically adds the following system routes to the route table, so that instances in a VPC can communicate with each other.
                      • Routes whose destination is 100.64.0.0/10 or 198.19.128.0/20.
                      • Routes whose destination is a subnet CIDR block.
                        If you enable IPv6 when creating a subnet, the system automatically assigns an IPv6 CIDR block to the subnet. Then, you can view IPv6 routes in its route table. Example destinations of subnet CIDR blocks are as follows:
                        • IPv4: 192.168.2.0/24
                        • IPv6: 2407:c080:802:be7::/64
                        +

                        Route

                        You can add routes to default and custom route tables and configure the destination type destination, next hop type, and next hop in the routes to determine where network traffic is directed. Routes are classified into system routes and custom routes.

                        +
                        • System routes: These routes are automatically added by the system and cannot be modified or deleted.
                          After a route table is created, the system automatically adds the following system routes to the route table, so that instances in a VPC can communicate with each other.
                          • Routes whose destination is 100.64.0.0/10 or 198.19.128.0/20.
                          • Routes whose destination is a subnet CIDR block.
                            If you enable IPv6 when creating a subnet, the system automatically assigns an IPv6 CIDR block to the subnet. Then, you can view IPv6 routes in its route table. Example destinations of subnet CIDR blocks are as follows:
                            • IPv4: 192.168.2.0/24
                            • IPv6: 2407:c080:802:be7::/64

                            In addition to the preceding system routes, the system automatically adds a route whose destination is 127.0.0.0/8. This is the local loopback address.

                          -
                        • Custom routes: These are routes that you can add, modify, and delete. The destination of a custom route cannot overlap with that of a system route.

                          You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. Table 1 lists the supported types of next hops.

                          +
                        • Custom routes: These are routes that you can add, modify, and delete. The destination of a custom route cannot overlap with that of a system route.

                          You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. Table 1 lists the supported types of next hops.

                          You cannot add two routes with the same destination to a VPC route table even if their next hop types are different. The route priority depends on the destination. According to the longest match routing rule, the destination with a higher matching degree is preferentially selected for packet forwarding.

                          -
                    Table 2 Outbound rule parameter description

                    Parameter

                    Description

                    +

                    Description

                    Example Value

                    Destination

                    Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:

                    -
                    • IP address:
                      • Single IP address: 192.168.10.10/32
                      • All IP addresses: 0.0.0.0/0
                      • IP address range: 192.168.1.0/24
                      -
                    • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                    • IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                    +
                    • IP address:
                      • Single IP address: 192.168.10.10/32
                      • All IP addresses: 0.0.0.0/0
                      • IP address range: 192.168.1.0/24
                      +
                    • Security group: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. For example, instance A is in security group A and instance B is in security group B. If security group A has an outbound rule with Action set to Allow and Destination set to security group B, access from instance A is allowed to instance B.

                    0.0.0.0/0
                    Table 1 Next hop type

                    Next Hop Type

                    +
                    - - - - - @@ -44,40 +44,40 @@ - - - - - - - - - - - @@ -85,8 +85,8 @@
                    Table 1 Next hop type

                    Next Hop Type

                    Description

                    +

                    Description

                    Supported Route Table

                    Server

                    +

                    Server

                    Traffic intended for the destination is forwarded to an ECS in the VPC.

                    +

                    Traffic intended for the destination is forwarded to an ECS in the VPC.
                    • Default route table
                    • Custom route table

                    Extension NIC

                    +

                    Extension NIC

                    Traffic intended for the destination is forwarded to the extension NIC of an ECS in the VPC.

                    +

                    Traffic intended for the destination is forwarded to the extension NIC of an ECS in the VPC.
                    • Default route table
                    • Custom route table

                    Traffic intended for the destination is forwarded to a BMS user-defined network. Currently, this parameter is available only in eu-de.

                    • Default route table
                    • Custom route table
                    +
                    • Custom route table

                    VPN connection

                    +

                    VPN connection

                    Traffic intended for the destination is forwarded to a VPN gateway.

                    +

                    Traffic intended for the destination is forwarded to a VPN gateway.

                    Custom route table

                    Direct Connect gateway

                    +

                    Direct Connect gateway

                    Traffic intended for the destination is forwarded to a Direct Connect gateway.

                    +

                    Traffic intended for the destination is forwarded to a Direct Connect gateway.

                    Custom route table

                    NAT gateway

                    +

                    NAT gateway

                    Traffic intended for the destination is forwarded to a NAT gateway.

                    +

                    Traffic intended for the destination is forwarded to a NAT gateway.
                    • Default route table
                    • Custom route table

                    VPC peering connection

                    +

                    VPC peering connection

                    Traffic intended for the destination is forwarded to a VPC peering connection.

                    +

                    Traffic intended for the destination is forwarded to a VPC peering connection.
                    • Default route table
                    • Custom route table

                    Virtual IP address

                    +

                    Virtual IP address

                    Traffic intended for the destination is forwarded to a virtual IP address and then sent to active and standby ECSs to which the virtual IP address is bound.

                    +

                    Traffic intended for the destination is forwarded to a virtual IP address and then sent to active and standby ECSs to which the virtual IP address is bound.
                    • Default route table
                    • Custom route table
                    -

                    If you specify the destination when creating a resource, a system route is delivered. If you do not specify a destination when creating a resource, a custom route that can be modified or deleted is delivered.

                    -

                    For example, when you create a NAT gateway, the system automatically delivers a custom route without a specific destination (0.0.0.0/0 is used by default). In this case, you can change the destination. However, when you create a VPN connection or Direct Connect gateway, you need to specify the remote subnet, that is, the destination of a route. In this case, the system delivers this system route. Do not modify the route destination on the Route Tables page. If you do, the destination will be inconsistent with the configured remote subnet. To modify the route destination, go to the specific resource page and modify the remote subnet, then the route destination will be changed accordingly.

                    +

                    If you specify the destination when creating a resource, a system route is delivered. If you do not specify a destination when creating a resource, a custom route that can be modified or deleted is delivered.

                    +

                    For example, when you create a NAT gateway, the system automatically delivers a custom route without a specific destination (0.0.0.0/0 is used by default). In this case, you can change the destination. However, when you create a VPN connection or Direct Connect gateway, you need to specify the remote subnet, that is, the destination of a route. In this case, the system delivers a system route. Do not modify the route destination on the Route Tables page. If you do, the destination will be inconsistent with the configured remote subnet. To modify the route destination, go to the specific resource page and modify the remote subnet, then the route destination will be changed accordingly.

                    diff --git a/docs/vpc/umn/en-us_topic_0046655036.html b/docs/vpc/umn/en-us_topic_0046655036.html index d1775cfc0..b4b4290ae 100644 --- a/docs/vpc/umn/en-us_topic_0046655036.html +++ b/docs/vpc/umn/en-us_topic_0046655036.html @@ -5,14 +5,14 @@
                    Figure 1 shows an application scenario of VPC peering connections.
                    • There are two VPCs (VPC-A and VPC-B) in region A that are not connected.
                    • Service servers (ECS-A01 and ECS-A02) are in VPC-A, and database servers (RDS-B01 and RDS-B02) are in VPC-B. The service servers and database servers cannot communicate with each other.
                    • You need to create a VPC peering connection (peering-AB) between VPC-A and VPC-B so the service servers and database servers can communicate with each other.
                    -
                    Figure 1 VPC peering connection network diagram
                    +
                    Figure 1 VPC peering connection network diagram

                    VPC Peering Connection Creation Process

                    A VPC peering connection can only connect VPCs in the same region.

                    -
                    • If two VPCs are in the same account, the process of creating a VPC peering connection is shown in Figure 2.
                      For details about how to create a VPC peering connection, see Creating a VPC Peering Connection with Another VPC in Your Account.
                      Figure 2 Process of creating a VPC peering connection between VPCs in the same account
                      +
                      • If two VPCs are in the same account, the process of creating a VPC peering connection is shown in Figure 2.
                        For details about how to create a VPC peering connection, see Creating a VPC Peering Connection with Another VPC in Your Account.
                        Figure 2 Process of creating a VPC peering connection between VPCs in the same account
                      • If two VPCs are in different accounts, the process of creating a VPC peering connection is shown in Figure 3.

                        For details about how to create a VPC peering connection, see Creating a VPC Peering Connection with a VPC in Another Account.

                        -
                        If account A initiates a request to create a VPC peering connection with a VPC in account B, the VPC peering connection takes effect only after account B accepts the request.
                        Figure 3 Process of creating a VPC peering connection between VPCs in different accounts
                        +
                        If account A initiates a request to create a VPC peering connection with a VPC in account B, the VPC peering connection takes effect only after account B accepts the request.
                        Figure 3 Process of creating a VPC peering connection between VPCs in different accounts
                      diff --git a/docs/vpc/umn/en-us_topic_0046655037.html b/docs/vpc/umn/en-us_topic_0046655037.html index a4e6c52dd..bfb26de01 100644 --- a/docs/vpc/umn/en-us_topic_0046655037.html +++ b/docs/vpc/umn/en-us_topic_0046655037.html @@ -5,92 +5,91 @@

                      This following describes how to create a VPC peering connection between VPC-A and VPC-B in account A to enable communications between ECS-A01 and RDS-B01.

                      Procedure:

                      Step 1: Create a VPC Peering Connection

                      -

                      Step 2: Add Routes for the VPC Peering Connection

                      +

                      Step 2: Add Routes for the VPC Peering Connection

                      Step 3: Verify Network Connectivity

                      -
                      Figure 1 Networking diagram of a VPC peering connection between VPCs in the same account
                      +
                      Figure 1 Networking diagram of a VPC peering connection between VPCs in the same account

                    Notes and Constraints

                    • Only one VPC peering connection can be created between two VPCs at the same time.
                    • A VPC peering connection can only connect VPCs in the same region.
                    • If the local and peer VPCs have overlapping CIDR blocks, the VPC peering connection may not take effect.
                    • After a VPC peering connection is created, you must add routes to the route tables of the local and peer VPCs. Otherwise, the VPC peering connection does not take effect.

                    Prerequisites

                    You have two VPCs from the same account in the same region. If you want to create one, see Creating a VPC.

                    -

                    Step 1: Create a VPC Peering Connection

                    1. Log in to the management console.
                    1. Click in the upper left corner and select the desired region and project.
                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                      The Virtual Private Cloud page is displayed.

                      +

                      Step 1: Create a VPC Peering Connection

                      1. Log in to the management console.
                      1. Click in the upper left corner and select the desired region and project.
                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                        The Virtual Private Cloud page is displayed.

                      3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                        The VPC peering connection list is displayed.

                      4. In the upper right corner of the page, click Create VPC Peering Connection.

                        The Create VPC Peering Connection dialog box is displayed.

                        -
                      5. Configure the parameters as prompted.

                        For details, see Table 1.

                        -
                        Figure 2 Create VPC Peering Connection
                        +
                      6. 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

                        +
                        - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -98,100 +97,108 @@
                      7. Click OK.

                        A dialog box for adding routes is displayed.

                        -
                      8. Click Add Route or Add Later.
                        1. If you click Add Route, the Local Routes page is displayed. Then, go to Step 2: Add Routes for the VPC Peering Connection.
                        2. If you click Add Later, the VPC peering connection list is displayed.
                        -
                        9. +
                      9. 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.
                        10. -

                        Step 2: Add Routes for the VPC Peering Connection

                        To enable communications between VPCs connected by a VPC peering connection, you need to add forward and return routes to the route tables of the VPCs. For details, see VPC Peering Connection Usage Examples.

                        -
                        1. Add routes to the route table of the local VPC:
                          1. On the Local Routes tab of the VPC peering connection, click the Route Tables hyperlink.

                            The Summary tab of the default route table for the local VPC is displayed.

                            -
                          2. Click Add Route.

                            Table 2 describes the route parameters.

                            +

                            Step 2: Add Routes for the VPC Peering Connection

                            1. 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
                              +
                            2. Add routes to the route tables as prompted.

                              Table 2 describes the parameters.

                              -
                        Table 1 Parameters for creating a VPC peering connection

                        Parameter

                        Description

                        +

                        Description

                        Example Value

                        +

                        Example Value

                        VPC Peering Connection Name

                        +

                        VPC Peering Connection Name

                        Mandatory

                        +

                        Mandatory

                        Enter a name for the VPC peering connection.

                        The name can contain a maximum of 64 characters, including letters, digits, hyphens (-), and underscores (_).

                        peering-AB

                        +

                        peering-AB

                        Local VPC

                        +

                        Local VPC

                        Mandatory

                        +

                        Mandatory

                        VPC at one end of the VPC peering connection. You can select one from the drop-down list.

                        VPC-A

                        +

                        VPC-A

                        Local VPC CIDR Block

                        +

                        Local VPC CIDR Block

                        CIDR block of the selected local VPC

                        +

                        CIDR block of the selected local VPC

                        172.16.0.0/16

                        +

                        172.16.0.0/16

                        Account

                        +

                        Account

                        Mandatory

                        +

                        Mandatory

                        • Options: My account and Another account
                        • Select My account.

                        My account

                        +

                        My account

                        Peer Project

                        +

                        Peer Project

                        The system fills in the corresponding project by default because My account is set to Account.

                        +

                        The system fills in the corresponding project by default because My account is set to Account.

                        For example, if VPC-A and VPC-B are in account A and region A, the system fills in the correspond project of account A in region A by default.

                        ab-cdef-1

                        +

                        ab-cdef-1

                        Peer VPC

                        +

                        Peer VPC

                        This parameter is mandatory if Account is set to My account.

                        +

                        This parameter is mandatory if Account is set to My account.

                        VPC at the other end of the VPC peering connection. You can select one from the drop-down list.

                        VPC-B

                        +

                        VPC-B

                        Peer VPC CIDR Block

                        +

                        Peer VPC CIDR Block

                        CIDR block of the selected peer VPC

                        +

                        CIDR block of the selected peer VPC

                        If the local and peer VPCs have overlapping CIDR blocks, the VPC peering connection may not take effect. For details, see VPC Peering Connection Usage Examples.

                        172.17.0.0/16

                        +

                        172.17.0.0/16

                        Description

                        +

                        Description

                        Optional

                        +

                        Optional

                        Enter the description of the VPC peering connection in the text box as required.

                        peering-AB connects VPC-A and VPC-B.

                        +

                        peering-AB connects VPC-A and VPC-B.
                        Table 2 Parameter description

                        Parameter

                        +
                        - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                        Table 2 Parameter description

                        Parameter

                        Description

                        +

                        Description

                        Example Value

                        +

                        Example Value

                        Destination

                        +

                        VPC

                        The peer VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see VPC Peering Connection Usage Examples.

                        +

                        Select a VPC that is connected by the VPC peering connection.

                        VPC-B CIDR block: 172.17.0.0/16

                        +

                        VPC-A

                        Next Hop Type

                        +

                        Route Table

                        The next hop type. Select VPC peering connection.

                        +

                        Select the route table of the VPC. The route will be added to this route table.

                        +
                        Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets.
                        • If there is only the default route table in the drop-down list, select the default route table.
                        • If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.
                        +

                        VPC peering connection

                        +

                        rtb-VPC-A (Default route table)

                        Next Hop

                        +

                        Destination

                        The next hop address. Select the name of the current VPC peering connection.

                        +

                        An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see VPC Peering Connection Usage Examples.

                        peering-AB

                        +

                        VPC-B CIDR block: 172.17.0.0/16

                        Description

                        +

                        Next Hop

                        Supplementary information about the route. This parameter is optional.

                        -

                        The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                        +

                        The default value is the current VPC peering connection. You do not need to specify this parameter.

                        -

                        +

                        peering-AB

                        +

                        Description

                        +

                        Supplementary information about the route. This parameter is optional.

                        +

                        The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                        +

                        Route from VPC-A to VPC-B

                        +

                        Add a route for the other VPC

                        +

                        If you select this option, you can also add a route for the other VPC connected by the VPC peering connection.

                        +

                        To enable communications between VPCs connected by a VPC peering connection, you need to add both forward and return routes to the route tables of the VPCs. For details, see VPC Peering Connection Usage Examples.

                        +

                        Selected

                        +

                        VPC

                        +

                        By default, the system selects the other VPC connected by the VPC peering connection. You do not need to specify this parameter.

                        +

                        VPC-B

                        +

                        Route Table

                        +

                        Select the route table of the VPC. The route will be added to this route table.

                        +
                        Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets.
                        • If there is only the default route table in the drop-down list, select the default route table.
                        • If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.
                        +
                        +

                        rtb-VPC-B (Default route table)

                        +

                        Destination

                        +

                        An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see VPC Peering Connection Usage Examples.

                        +

                        VPC-A CIDR block: 172.16.0.0/16

                        +

                        Next Hop

                        +

                        The default value is the current VPC peering connection. You do not need to specify this parameter.

                        +

                        peering-AB

                        +

                        Description

                        +

                        Supplementary information about the route. This parameter is optional.

                        +

                        The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                        +

                        Route from VPC-B to VPC-A.
                        -
                      10. Click OK.

                        You can view the route in the route list.

                        -
                        11. -
                        1. Add routes to the route table of the peer VPC:
                          1. On the Peer Routes tab of the VPC peering connection, click the Route Tables hyperlink.

                            The Summary tab of the default route table for the peer VPC is displayed.

                            -
                          2. Click Add Route.

                            Table 3 describes the route parameters.

                            - -
                            - - - - - - - - - - - - - - - - - - - - - -
                            Table 3 Parameter description

                            Parameter

                            -

                            Description

                            -

                            Example Value

                            -

                            Destination

                            -

                            The local VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see VPC Peering Connection Usage Examples.

                            -

                            VPC-A CIDR block: 172.16.0.0/16

                            -

                            Next Hop Type

                            -

                            The next hop type. Select VPC peering connection.

                            -

                            VPC peering connection

                            -

                            Next Hop

                            -

                            The next hop address. Select the name of the current VPC peering connection.

                            -

                            peering-AB

                            -

                            Description

                            -

                            Supplementary information about the route. This parameter is optional.

                            -

                            The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                            -

                            -

                            -
                            -
                            -
                          3. Click OK.

                            You can view the route in the route list.

                            -
                          +
                        2. Click OK.

                          You can view the routes in the route list.

                        Step 3: Verify Network Connectivity

                        After you add routes for the VPC peering connection, verify the communication between the local and peer VPCs.
                        1. Log in to ECS-A01 in the local VPC.
                        2. Check whether ECS-A01 can communicate with RDS-B01.

                          ping IP address of RDS-B01

                          diff --git a/docs/vpc/umn/en-us_topic_0046655038.html b/docs/vpc/umn/en-us_topic_0046655038.html index 722b851e5..9f9d1eb17 100644 --- a/docs/vpc/umn/en-us_topic_0046655038.html +++ b/docs/vpc/umn/en-us_topic_0046655038.html @@ -6,89 +6,89 @@

                          Procedure:

                          Step 1: Create a VPC Peering Connection

                          Step 2: Peer Account Accepts the VPC Peering Connection Request

                          -

                          Step 3: Add Routes for the VPC Peering Connection

                          +

                          Step 3: Add Routes for the VPC Peering Connection

                          Step 4: Verify Network Connectivity

                          -
                          Figure 1 Networking diagram of a VPC peering connection between VPCs in different accounts
                          +
                          Figure 1 Networking diagram of a VPC peering connection between VPCs in different accounts
                        -

                        Notes and Constraints

                        • Only one VPC peering connection can be created between two VPCs at the same time.
                        • A VPC peering connection can only connect VPCs in the same region. +

                          Notes and Constraints

                          • Only one VPC peering connection can be created between two VPCs at the same time.
                          • A VPC peering connection can only connect VPCs in the same region.
                          • If the local and peer VPCs have overlapping CIDR blocks, the VPC peering connection may not take effect.
                          • For a VPC peering connection between VPCs in different accounts:
                            • If account A initiates a request to create a VPC peering connection with a VPC in account B, the VPC peering connection takes effect only after account B accepts the request.
                            • To ensure network security, do not accept VPC peering connections from unknown accounts.
                          -

                          Prerequisites

                          You have two VPCs in the same region, but they are from different accounts. If you want to create one, see Creating a VPC.

                          +

                          Prerequisites

                          You have two VPCs in the same region, but they are from different accounts. If you want to create one, see Creating a VPC.

                          -

                          Step 1: Create a VPC Peering Connection

                          1. Log in to the management console.
                          1. Click in the upper left corner and select the desired region and project.
                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                            The Virtual Private Cloud page is displayed.

                            +

                            Step 1: Create a VPC Peering Connection

                            1. Log in to the management console.
                            1. Click in the upper left corner and select the desired region and project.
                            2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                              The Virtual Private Cloud page is displayed.

                            3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                              The VPC peering connection list is displayed.

                            4. In the upper right corner of the page, click Create VPC Peering Connection.

                              The Create VPC Peering Connection dialog box is displayed.

                            5. 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

                              +
                              - - - - - - - - - - - - - - - - - - - - - - - @@ -99,112 +99,132 @@

                              Step 2: Peer Account Accepts the VPC Peering Connection Request

                              After you create a VPC peering connection with a VPC in another account, you need to contact the peer account to accept the VPC peering connection request. In this example, account A notifies account B to accept the request. Account B needs to:

                              -
                              1. Log in to the management console.
                              2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                The Virtual Private Cloud page is displayed.

                                +
                                1. Log in to the management console.
                                2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                  The Virtual Private Cloud page is displayed.

                                3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                  The VPC peering connection list is displayed.

                                  -
                                4. In the VPC peering connection list, locate the VPC peering connection request to be accepted.
                                  Figure 3 VPC peering connection list
                                  +
                                5. In the upper part of the VPC peering connection list, locate the VPC peering connection request to be accepted.
                                  Figure 3 Accept Request
                                6. Locate the row that contains the target VPC peering connection and click Accept Request in the Operation column.

                                  After the status of the VPC peering connection changes to Accepted, the VPC peering connection is created.

                                  -
                                7. Go to Step 3: Add Routes for the VPC Peering Connection.
                                +
                              3. Go to Step 3: Add Routes for the VPC Peering Connection.
                              -

                              Step 3: Add Routes for the VPC Peering Connection

                              To enable communications between VPCs connected by a VPC peering connection, you need to add forward and return routes to the route tables of the VPCs. For details, see VPC Peering Connection Usage Examples.

                              -

                              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.

                              -
                              1. Add routes to the route table of the local VPC:
                                1. In the VPC peering connection list of the local account, click the name of the target VPC peering connection.

                                  The Basic Information tab of the VPC peering connection is displayed.

                                  -
                                2. On the Local Routes tab of the VPC peering connection, click the Route Tables hyperlink.

                                  The Summary tab of the default route table for the local VPC is displayed.

                                  -
                                3. Click Add Route.

                                  Table 2 describes the route parameters.

                                  +

                                  Step 3: Add Routes for the VPC Peering Connection

                                  To enable communications between VPCs connected by a VPC peering connection, you need to add forward and return routes to the route tables of the VPCs. For details, see VPC Peering Connection Usage Examples.

                                  +

                                  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.

                                  +
                                  1. Add routes to the route table of the local VPC:
                                    1. 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.

                                      +
                                    2. 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
                                      +
                                    3. Add routes to the route tables as prompted.

                                      Table 2 describes the parameters.

                                      -
                              Table 1 Parameters for creating a VPC peering connection

                              Parameter

                              Description

                              +

                              Description

                              Example Value

                              +

                              Example Value

                              VPC Peering Connection Name

                              +

                              VPC Peering Connection Name

                              Mandatory

                              +

                              Mandatory

                              Enter a name for the VPC peering connection.

                              The name can contain a maximum of 64 characters, including letters, digits, hyphens (-), and underscores (_).

                              peering-AB

                              +

                              peering-AB

                              Local VPC

                              +

                              Local VPC

                              Mandatory

                              +

                              Mandatory

                              VPC at one end of the VPC peering connection. You can select one from the drop-down list.

                              VPC-A

                              +

                              VPC-A

                              Local VPC CIDR Block

                              +

                              Local VPC CIDR Block

                              CIDR block of the selected local VPC

                              +

                              CIDR block of the selected local VPC

                              172.16.0.0/16

                              +

                              172.16.0.0/16

                              Account

                              +

                              Account

                              Mandatory

                              +

                              Mandatory

                              • Options: My account and Another account
                              • Select Another account.

                              Another account

                              +

                              Another account

                              Peer Project ID

                              +

                              Peer Project ID

                              This parameter is mandatory because Account is set to Another account.

                              +

                              This parameter is mandatory because Account is set to Another account.

                              The project ID of the region that the peer VPC resides. For details about how to obtain the project ID, see Obtaining the Peer Project ID of a VPC Peering Connection.

                              Project ID of VPC-B in region A:

                              +

                              Project ID of VPC-B in region A:

                              067cf8aecf3XXX08322f13b

                              Peer VPC ID

                              +

                              Peer VPC ID

                              This parameter is mandatory because Account is set to Another account.

                              +

                              This parameter is mandatory because Account is set to Another account.

                              ID of the VPC at the other end of the VPC peering connection. For details about how to obtain the ID, see Obtaining a VPC ID.

                              VPC-B ID:

                              +

                              VPC-B ID:

                              17cd7278-XXX-530c952dcf35

                              Description

                              +

                              Description

                              Optional

                              +

                              Optional

                              Enter the description of the VPC peering connection in the text box as required. The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                              peering-AB connects VPC-A and VPC-B.

                              +

                              peering-AB connects VPC-A and VPC-B.
                              Table 2 Parameter description

                              Parameter

                              +
                              - - - - - - - - - - - - - - + + + +
                              Table 2 Parameter description

                              Parameter

                              Description

                              +

                              Description

                              Example Value

                              +

                              Example Value

                              Destination

                              +

                              VPC

                              The peer VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see VPC Peering Connection Usage Examples.

                              +

                              The default value is the VPC connected by the VPC peering connection in the current account. You do not need to select a VPC.

                              VPC-B CIDR block: 172.17.0.0/16

                              +

                              VPC-A

                              Next Hop Type

                              +

                              Route Table

                              The next hop type. Select VPC peering connection.

                              +

                              Select the route table of the VPC. The route will be added to this route table.

                              +
                              Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets.
                              • If there is only the default route table in the drop-down list, select the default route table.
                              • If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.
                              +

                              VPC peering connection

                              +

                              rtb-VPC-A (Default route table)

                              Next Hop

                              +

                              Destination

                              The next hop address. Select the name of the current VPC peering connection.

                              +

                              An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see VPC Peering Connection Usage Examples.

                              peering-AB

                              +

                              VPC-B CIDR block: 172.17.0.0/16

                              Description

                              +

                              Next Hop

                              Supplementary information about the route. This parameter is optional.

                              -

                              The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                              +

                              The default value is the current VPC peering connection. You do not need to specify this parameter.

                              -

                              +

                              peering-AB

                              +

                              Description

                              +

                              Supplementary information about the route. This parameter is optional.

                              +

                              The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                              +

                              Route from VPC-A to VPC-B
                              -
                            6. Click OK.

                              You can view the route in the route list.

                              +
                            7. Click OK.

                              You can view the routes in the route list.

                              8. -
                            8. Add routes to the route table of the peer VPC:
                              1. In the VPC peering connection list of the peer account, click the name of the target VPC peering connection.

                                The Basic Information tab of the VPC peering connection is displayed.

                                -
                              2. On the Local Routes tab of the VPC peering connection, click the Route Tables hyperlink.

                                The Summary tab of the default route table for the peer VPC is displayed.

                                -
                              3. Click Add Route.

                                Table 3 describes the route parameters.

                                +
                              4. Add routes to the route table of the peer VPC:
                                1. 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.

                                  +
                                2. 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
                                  +
                                3. Add routes to the route table as prompted.

                                  Table 3 describes the parameters.

                                  -
                                  Table 3 Parameter description

                                  Parameter

                                  +
                                  - - - - - - - - - - - - - - + + + +
                                  Table 3 Parameter description

                                  Parameter

                                  Description

                                  +

                                  Description

                                  Example Value

                                  +

                                  Example Value

                                  Destination

                                  +

                                  VPC

                                  The local VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see VPC Peering Connection Usage Examples.

                                  +

                                  The default value is the VPC connected by the VPC peering connection in the current account. You do not need to select a VPC.

                                  VPC-A CIDR block: 172.16.0.0/16

                                  +

                                  VPC-B

                                  Next Hop Type

                                  +

                                  Route Table

                                  The next hop type. Select VPC peering connection.

                                  +

                                  Select the route table of the VPC. The route will be added to this route table.

                                  +
                                  Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets.
                                  • If there is only the default route table in the drop-down list, select the default route table.
                                  • If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.
                                  +

                                  VPC peering connection

                                  +

                                  rtb-VPC-B (Default route table)

                                  Next Hop

                                  +

                                  Destination

                                  The next hop address. Select the name of the current VPC peering connection.

                                  +

                                  An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see VPC Peering Connection Usage Examples.

                                  peering-AB

                                  +

                                  VPC-A CIDR block: 172.16.0.0/16

                                  Description

                                  +

                                  Next Hop

                                  Supplementary information about the route. This parameter is optional.

                                  -

                                  The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                  +

                                  The default value is the current VPC peering connection. You do not need to specify this parameter.

                                  -

                                  +

                                  peering-AB

                                  +

                                  Description

                                  +

                                  Supplementary information about the route. This parameter is optional.

                                  +

                                  The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                  +

                                  Route from VPC-B to VPC-A.
                                  -
                                4. Click OK.

                                  You can view the route in the route list.

                                  +
                                5. Click OK.

                                  You can view the route in the route list.

                                  6. -

                                  Step 4: Verify Network Connectivity

                                  After you add routes for the VPC peering connection, verify the communication between the local and peer VPCs.
                                  1. Log in to ECS-A01 in the local VPC.
                                  2. Check whether ECS-A01 can communicate with RDS-B01.

                                    ping IP address of RDS-B01

                                    -

                                    Example command:

                                    -

                                    ping 172.17.0.21

                                    -
                                    If information similar to the following is displayed, ECS-A01 and RDS-B01 can communicate with each other, and the VPC peering connection between VPC-A and VPC-B is successfully created.
                                    [root@ecs-A02 ~]# ping 172.17.0.21
+
                                    Step 4: Verify Network Connectivity
                                    After you add routes for the VPC peering connection, verify the communication between the local and peer VPCs.
                                    1. Log in to ECS-A01 in the local VPC.
                                    2. Check whether ECS-A01 can communicate with RDS-B01.
                                      ping IP address of RDS-B01
                                      
+
                                      Run the following commands:
                                      
+
                                      ping 172.17.0.21
                                      
+
                                      If information similar to the following is displayed, ECS-A01 and RDS-B01 can communicate with each other, and the VPC peering connection between VPC-A and VPC-B is successfully created.
                                      [root@ecs-A02 ~]# ping 172.17.0.21
 PING 172.17.0.21 (172.17.0.21) 56(84) bytes of data.
 64 bytes from 172.17.0.21: icmp_seq=1 ttl=64 time=0.849 ms
 64 bytes from 172.17.0.21: icmp_seq=2 ttl=64 time=0.455 ms
@@ -213,7 +233,7 @@ PING 172.17.0.21 (172.17.0.21) 56(84) bytes of data.
 ...
 --- 172.17.0.21 ping statistics ---
                                      
 
                                      
-
                                       
                                      
+
                                       
                                      
 
                                      
 
                                    
 
                                    
diff --git a/docs/vpc/umn/en-us_topic_0046809840.html b/docs/vpc/umn/en-us_topic_0046809840.html
index 9a9759493..6a9c40f9d 100644
--- a/docs/vpc/umn/en-us_topic_0046809840.html
+++ b/docs/vpc/umn/en-us_topic_0046809840.html
@@ -48,7 +48,7 @@

                                  -

                                  Peering Two or More VPCs

                                  • Two VPCs peered together: Figure 1 shows the networking diagram of a VPC peering connection that connects VPC-A and VPC-B.
                                    Figure 1 Networking diagram (IPv4)
                                    +

                                    Peering Two or More VPCs

                                    • Two VPCs peered together: Figure 1 shows the networking diagram of a VPC peering connection that connects VPC-A and VPC-B.
                                      Figure 1 Networking diagram (IPv4)
                                      @@ -110,7 +110,7 @@
                                      Table 2 Peering relationships (IPv4)

                                      Peering Relationship
                                      -
                                    • Multiple VPCs peered together: Figure 2 shows the networking diagram of VPC peering connections that connect VPC-A, VPC-B, and VPC-C.
                                      Figure 2 Networking diagram (IPv4)
                                      +
                                    • Multiple VPCs peered together: Figure 2 shows the networking diagram of VPC peering connections that connect VPC-A, VPC-B, and VPC-C.
                                      Figure 2 Networking diagram (IPv4)
                                      @@ -231,7 +231,7 @@

                                      Peering One Central VPC with Multiple VPCs

                                      Figure 3 shows the networking diagram of VPC peering connections that connect VPC-B, VPC-C, VPC-D, VPC-E, VPC-F, VPC-G, and central VPC-A.

                                      -
                                      Figure 3 Networking diagram (IPv4)
                                      +
                                      Figure 3 Networking diagram (IPv4)
                                      Table 4 Peering relationships (IPv4)

                                      Peering Relationship
                                      @@ -439,7 +439,7 @@
                                      Table 6 Peering relationships (IPv4)

                                      Peering Relationship

                                    -

                                    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.
                                    Figure 4 Networking diagram (IPv4)
                                    +

                                    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.
                                    Figure 4 Networking diagram (IPv4)
                                    @@ -505,7 +505,7 @@

                                    Peering ECSs in a Central VPC with ECSs in Two Other VPCs

                                    As shown in Figure 5, VPC-B and VPC-C have overlapping CIDR blocks, and their Subnet-B01 and Subnet-C01 have overlapping CIDR blocks. You can only create a VPC peering connection between ECSs.
                                    • Use VPC peering connection Peering-AB to connect ECSs in Subnet-B01 and Subnet-A01.
                                    • Use VPC peering connection Peering-AC to connect ECSs in Subnet-C01 and Subnet-A01.
                                    -
                                    Figure 5 Networking diagram (IPv4)
                                    +
                                    Figure 5 Networking diagram (IPv4)
                                    Table 8 Peering relationships (IPv4)

                                    Peering Relationship
                                    @@ -598,7 +598,7 @@

                                    Invalid VPC Peering Connections

                                    If VPCs with the same CIDR block also include subnets that overlap, VPC peering connections are not usable. VPC-A and VPC-B have the same CIDR block and their subnets have the same CIDR block. If a VPC peering connection is created between VPC-A and VPC-B, traffic cannot be routed between them because there are routes with the same destination.

                                    -
                                    In the rtb-VPC-A route table, the custom route for routing traffic from VPC-A to VPC-B and the local route have overlapping destinations. The local route has a higher priority and traffic will be forwarded within VPC-A and cannot reach VPC-B.
                                    Figure 6 Networking diagram (IPv4)
                                    +
                                    In the rtb-VPC-A route table, the custom route for routing traffic from VPC-A to VPC-B and the local route have overlapping destinations. The local route has a higher priority and traffic will be forwarded within VPC-A and cannot reach VPC-B.
                                    Figure 6 Networking diagram (IPv4)
                                    Table 10 Peering relationships (IPv4)

                                    Peering Relationship
                                    diff --git a/docs/vpc/umn/en-us_topic_0051746676.html b/docs/vpc/umn/en-us_topic_0051746676.html index a50d792c8..e96acf141 100644 --- a/docs/vpc/umn/en-us_topic_0051746676.html +++ b/docs/vpc/umn/en-us_topic_0051746676.html @@ -2,6 +2,8 @@

                                    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.

                                    +
                                    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.

                                    diff --git a/docs/vpc/umn/en-us_topic_0051746698.html b/docs/vpc/umn/en-us_topic_0051746698.html index 9600f29bf..a39ce748b 100644 --- a/docs/vpc/umn/en-us_topic_0051746698.html +++ b/docs/vpc/umn/en-us_topic_0051746698.html @@ -4,8 +4,8 @@

                                    Scenarios

                                    You can create a custom firewall. By default, a newly created firewall is disabled and has no inbound or outbound rules, or any subnets associated.

                                    By default, you can create a maximum of 200 firewalls in a region.

                                    -

                                    Procedure

                                    1. Log in to the management console.
                                    1. Click in the upper left corner and select the desired region and project.
                                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                      The Virtual Private Cloud page is displayed.

                                      -
                                    3. In the navigation pane on the left, choose Access Control > Firewalls.
                                    4. In the right pane displayed, click Create Firewall.
                                    5. On the Create Firewall page, configure parameters as prompted.
                                      Figure 1 Create Firewall
                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      1. Click in the upper left corner and select the desired region and project.
                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                        The Virtual Private Cloud page is displayed.

                                        +
                                      3. In the navigation pane on the left, choose Access Control > Firewalls.
                                      4. In the right pane displayed, click Create Firewall.
                                      5. On the Create Firewall page, configure parameters as prompted.
                                        Figure 1 Create Firewall
                                    Table 12 VPC route table details

                                    Route Table
                                    @@ -39,7 +39,7 @@
                                    -
                                    Parent topic: Firewall
                                    +
                                    Parent topic: Managing Firewalls
                                    diff --git a/docs/vpc/umn/en-us_topic_0051746700.html b/docs/vpc/umn/en-us_topic_0051746700.html index df974633f..7cd7e6fe3 100644 --- a/docs/vpc/umn/en-us_topic_0051746700.html +++ b/docs/vpc/umn/en-us_topic_0051746700.html @@ -5,7 +5,7 @@

                                    Notes and Constraints

                                    • You can associate a firewall with multiple subnets. However, a subnet can only be associated with one firewall at a time.
                                    • After a firewall is associated with a subnet, the default firewall rules deny all traffic to and from the subnet until you add custom rules to allow traffic. For details, see Adding a Firewall Rule.
                                    -

                                    Procedure

                                    1. Log in to the management console.
                                    1. Click in the upper left corner and select the desired region and project.
                                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                      The Virtual Private Cloud page is displayed.

                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      1. Click in the upper left corner and select the desired region and project.
                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                        The Virtual Private Cloud page is displayed.

                                      3. In the navigation pane on the left, choose Access Control > Firewalls.
                                      4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                      5. On the displayed page, click the Associated Subnets tab.
                                      6. On the Associated Subnets tab, click Associate.
                                      7. On the displayed page, select the subnets to be associated with the firewall, and click OK.

                                      A subnet with a firewall associated will not be displayed on the page for you to select. If you want to associate such a subnet with another firewall, you must first disassociate the subnet from the original firewall. One-click subnet association and disassociation are not supported currently. A subnet can only be associated with one firewall.

                                      @@ -13,7 +13,7 @@
                                      diff --git a/docs/vpc/umn/en-us_topic_0051746702.html b/docs/vpc/umn/en-us_topic_0051746702.html index fb96094bd..6732c3fe7 100644 --- a/docs/vpc/umn/en-us_topic_0051746702.html +++ b/docs/vpc/umn/en-us_topic_0051746702.html @@ -5,9 +5,9 @@

                                    Notes and Constraints

                                    A firewall can contain no more than 20 rules in one direction, or performance will deteriorate.

                                    -

                                    Procedure

                                    1. Log in to the management console.
                                    1. Click in the upper left corner and select the desired region and project.
                                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                      The Virtual Private Cloud page is displayed.

                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      1. Click in the upper left corner and select the desired region and project.
                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                        The Virtual Private Cloud page is displayed.

                                      3. In the navigation pane on the left, choose Access Control > Firewalls.
                                      4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                      5. 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
                                    @@ -42,8 +42,8 @@ @@ -60,7 +60,7 @@ @@ -90,7 +90,7 @@
                                    -
                                    Parent topic: Firewall
                                    +
                                    Parent topic: Management Firewall Rules
                                    diff --git a/docs/vpc/umn/en-us_topic_0052003963.html b/docs/vpc/umn/en-us_topic_0052003963.html index ea47ae695..2ad5758f1 100644 --- a/docs/vpc/umn/en-us_topic_0052003963.html +++ b/docs/vpc/umn/en-us_topic_0052003963.html @@ -1,59 +1,60 @@

                                    Differences Between Security Groups and Firewalls

                                    -

                                    You can configure security groups and firewalls to increase the security of ECSs in your VPC.

                                    -
                                    • Security groups operate at the ECS level.
                                    • Firewalls protect associated subnets and all the resources in the subnets.
                                    +

                                    You can configure firewall and security group rules to protect the instances in your VPC, such as ECSs and databases.

                                    +
                                    • A security group protects the instances in it.
                                    • A firewall protects associated subnets and all the resources in the subnets.

                                    For details, see Figure 1.

                                    -
                                    Figure 1 Security groups and firewalls
                                    -

                                    Table 1 describes the differences between security groups and firewalls.

                                    - -
                                    Table 1 Parameter descriptions

                                    Parameter

                                    Source

                                    The source from which the traffic is allowed. The source can be an IP address or IP address range.

                                    -
                                    • IP address:
                                      • Single IP address: 192.168.10.10/32
                                      • All IP addresses: 0.0.0.0/0
                                      • IP address range: 192.168.1.0/24
                                      -
                                    • IP address group: The source is an IP address group. An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                    +
                                    • IP address:
                                      • Single IP address: 192.168.10.10/32
                                      • All IP addresses: 0.0.0.0/0
                                      • IP address range: 192.168.1.0/24
                                      +

                                    0.0.0.0/0

                                    The destination to which the traffic is allowed. The destination can be an IP address or IP address range.

                                    • IP address:
                                      • Single IP address: 192.168.10.10/32
                                      • All IP addresses: 0.0.0.0/0
                                      • IP address range: 192.168.1.0/24
                                      -
                                    • IP address group: The source is an IP address group. An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                    +

                                    0.0.0.0/0
                                    Table 1 Differences between security groups and firewalls

                                    Category

                                    +
                                    Figure 1 Security groups and firewalls
                                    +
                                    Table 1 describes the differences between security groups and firewalls. +
                                    - - - - - - - - - - - - - - - - -
                                    Table 1 Differences between security groups and firewalls

                                    Category

                                    Security Group

                                    +

                                    Security Group

                                    Firewall

                                    +

                                    Firewall

                                    Scope

                                    +

                                    Protection Scope

                                    Operates at the ECS level.

                                    +

                                    Protects instances in a security group, such as ECSs and databases.

                                    Operates at the subnet level.

                                    +

                                    Protects subnets and all the instances in the subnets.

                                    Rules

                                    +

                                    Rules

                                    Does not support Allow or Deny rules.

                                    +

                                    Does not support Allow or Deny rules.

                                    Supports both Allow and Deny rules.

                                    +

                                    Supports both Allow and Deny rules.

                                    Priority

                                    +

                                    Matching Order

                                    If there are conflicting rules, they are combined and applied together.

                                    +

                                    If there are conflicting rules, they are combined and applied together.

                                    If rules conflict, the rule with the highest priority takes effect.

                                    +

                                    If rules conflict, the rule with the highest priority takes effect.

                                    Usage

                                    +

                                    Usage

                                    Automatically applies to ECSs in the security group that is selected during ECS creation. You must select a security group when creating ECSs.

                                    +
                                    • When creating an instance, such as an ECS, you must select a security group. If you do not have a security group, a default security group will be created for you.
                                    • After creating an instance, you can:
                                      • Add or remove the instance to or from the security group on the security group console.
                                      • Associate or disassociate a security group with or from the instance on the instance console.
                                      +

                                    Applies to all ECSs in the subnets associated with the firewall. Selecting a firewall is not allowed during subnet creation. You must create a firewall, associate subnets with it, add inbound and outbound rules, and enable firewall. The firewall then takes effect for the associated subnets and ECSs in the subnets.

                                    +

                                    Selecting a firewall is not allowed when you create a subnet. You must create a firewall, add inbound and outbound rules, associate subnets with it, and enable firewall. The firewall then protects the associated subnets and instances in the subnets.

                                    Packets

                                    +

                                    Packets

                                    Only packet filtering based on the 3-tuple (protocol, port, and peer IP address) is supported.

                                    +

                                    Packet filtering based on the 3-tuple (protocol, port, and source/destination) is supported.

                                    Only packet filtering based on the 5-tuple (protocol, source port, destination port, source IP address, and destination IP address) is supported.

                                    +

                                    Packet filtering based on the 5-tuple (protocol, source port, destination port, and source/destination) is supported.
                                    +
                                    Parent topic: Access Control
                                    diff --git a/docs/vpc/umn/en-us_topic_0067802474.html b/docs/vpc/umn/en-us_topic_0067802474.html index 73007a4e2..25b072c41 100644 --- a/docs/vpc/umn/en-us_topic_0067802474.html +++ b/docs/vpc/umn/en-us_topic_0067802474.html @@ -4,9 +4,9 @@

                                    Scenarios

                                    You can use a virtual IP address and an EIP together.

                                    If you bind a virtual IP address to ECSs that work in active/standby pairs and bind an EIP to the virtual IP address, you can access the ECSs over the Internet.

                                    -

                                    Notes and Constraints

                                    • Each virtual IP address can be bound to only one EIP.
                                    +

                                    Notes and Constraints

                                    • A virtual IP address can only be bound to one EIP.
                                    -

                                    Binding a Virtual IP Address to an EIP or ECS on the Console

                                    1. Log in to the management console.
                                    2. Click in the upper left corner and select the desired region and project.
                                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                      The Virtual Private Cloud page is displayed.

                                      +

                                      Binding a Virtual IP Address to an EIP or ECS on the Console

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select the desired region and project.
                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                        The Virtual Private Cloud page is displayed.

                                      4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                        The Subnets page is displayed.

                                      5. Click the name with a hyperlink of the subnet that the virtual IP address belongs to.

                                        The subnet details page is displayed.

                                      6. Click the IP Addresses tab.
                                        • To bind a virtual IP address to an EIP, locate the row that contains the virtual IP address and click Bind to EIP in the Operation column.
                                        • To bind a virtual IP address to an ECS, locate the row that contains the virtual IP address and click Bind to Server in the Operation column.
                                        @@ -17,11 +17,11 @@

                                      Configuring a Virtual IP Address for an ECS

                                      Manually configure the virtual IP address bound to an ECS.

                                      -
                                      This following OSs are used as examples here. For other OSs, see the help documents on their official websites.
                                      • Linux: CentOS 7.2 64bit and Ubuntu 22.04 server 64bit
                                      • Windows: Windows Server
                                      +
                                      The following OSs are used as examples here. For other OSs, see the help documents on their official websites.
                                      • Linux: CentOS 7.2 64bit and Ubuntu 22.04 server 64bit
                                      • Windows: Windows Server
                                      Linux (CentOS 7.2 64bit is used as an example.)
                                      1. Obtain the NIC that the virtual IP address is to be bound and the connection of the NIC:

                                        nmcli connection

                                        Information similar to the following is displayed:

                                        -

                                        +

                                        The command output in this example is described as follows:

                                        • eth0 in the DEVICE column indicates the NIC that the virtual IP address is to be bound.
                                        • Wired connection 1 in the NAME column indicates the connection of the NIC.
                                      2. Add the virtual IP address for the connection:

                                        nmcli connection modify "Connection name of the NIC" +ipv4.addresses Virtual IP address

                                        @@ -33,20 +33,20 @@

                                        In this example, run the following command:

                                        nmcli connection up "Wired connection 1"

                                        Information similar to the following is displayed:

                                        -

                                        +

                                      3. Check whether the virtual IP address has been bound:

                                        ip a

                                        Information similar to the following is displayed. In the command output, the virtual IP address 172.16.0.125 is bound to NIC eth0.

                                        -

                                        +

                                        To delete an added virtual IP address, perform the following steps:

                                        1. Delete the virtual IP address from the connection of the NIC:

                                          nmcli connection modify "Connection name of the NIC" -ipv4.addresses Virtual IP address

                                          -
                                          To delete multiple virtual IP addresses at a time, separate every two with a comma (,). Example commands are as follows:
                                          • Deleting a single virtual IP address: nmcli connection modify "Wired connection 1" -ipv4.addresses 172.16.0.125
                                          • Deleting multiple virtual IP addresses: nmcli connection modify "Wired connection 1" -ipv4.addresses 172.16.0.125,172.16.0.126
                                          +
                                          To delete multiple virtual IP addresses at a time, separate every two with a comma (,). Example commands are as follows:
                                          • Deleting a single virtual IP address: nmcli connection modify "Wired connection 1" -ipv4.addresses 172.16.0.125
                                          • Deleting multiple virtual IP addresses: nmcli connection modify "Wired connection 1" -ipv4.addresses 172.16.0.125,172.16.0.126
                                        2. Make the deletion take effect by referring to 3.

                                      Linux (Ubuntu 22.04 server 64bit is used as an example.)

                                      -
                                      If an ECS runs Ubuntu 22 or Ubuntu 20, perform the following operations:
                                      1. Obtain the NIC that the virtual IP address is to be bound:

                                        ifconfig

                                        +
                                        For Ubuntu 22 or Ubuntu 20 ECSs, perform the following operations:
                                        1. Obtain the NIC that the virtual IP address is to be bound:

                                          ifconfig

                                          Information similar to the following is displayed. In this example, the NIC bound to the virtual IP address is eth0.
                                          root@ecs-X-ubantu:~# ifconfig
 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 172.16.0.210  netmask 255.255.255.0  broadcast 172.16.0.255
@@ -102,9 +102,9 @@ eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

                                        Windows OS (Windows Server is used as an example here.)

                                        -
                                        1. In Control Panel, click Network and Sharing Center, and click the corresponding local connection.
                                        2. On the displayed page, click Properties.
                                        3. On the Network tab page, select Internet Protocol Version 4 (TCP/IPv4).
                                        4. Click Properties.
                                        5. Select Use the following IP address and set IP address to the private IP address of the ECS, for example, 10.0.0.101.
                                          Figure 1 Configuring private IP address
                                          +
                                          1. In Control Panel, click Network and Sharing Center, and click the corresponding local connection.
                                          2. On the displayed page, click Properties.
                                          3. On the Network tab page, select Internet Protocol Version 4 (TCP/IPv4).
                                          4. Click Properties.
                                          5. Select Use the following IP address and set IP address to the private IP address of the ECS, for example, 10.0.0.101.
                                            Figure 1 Configuring private IP address
                                          6. Click Advanced.
                                          7. On the IP Settings tab, click Add in the IP addresses area.

                                            Add the virtual IP address, for example, 10.0.0.154.

                                            -
                                            Figure 2 Configuring virtual IP address
                                            +
                                            Figure 2 Configuring virtual IP address
                                          8. Click OK.
                                          9. In the Start menu, open the Windows command line window and run the following command to check whether the virtual IP address has been configured:

                                            ipconfig /all

                                            In the command output, IPv4 Address is the virtual IP address 10.0.0.154, indicating that the virtual IP address of the ECS NIC has been correctly configured.

                                            diff --git a/docs/vpc/umn/en-us_topic_0068145818.html b/docs/vpc/umn/en-us_topic_0068145818.html index 133e699f0..4cfd7af28 100644 --- a/docs/vpc/umn/en-us_topic_0068145818.html +++ b/docs/vpc/umn/en-us_topic_0068145818.html @@ -32,11 +32,12 @@
                                    -

                                    Procedure

                                    Searching for EIPs by tag key and value on the page showing the EIP list
                                    1. Log in to the management console.
                                    2. Click in the upper left corner and select the desired region and project.
                                    3. Click in the upper left corner and choose Network > Elastic IP.
                                    4. Click the search box above the EIP list.
                                    5. Select the tag key and value of the EIP.

                                      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 contain all of the tags you specified.

                                      -
                                    6. Click OK.

                                      The system displays the EIPs you are looking for based on the entered tag keys and values.

                                      +

                                      Procedure

                                      Searching for EIPs by tag key and value on the page showing the EIP list
                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select the desired region and project.
                                      3. Click in the upper left corner, and choose Network > Elastic IP.
                                      4. 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
                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select the desired region and project.
                                      3. Click in the upper left corner and choose Network > Elastic IP.
                                      4. On the displayed page, locate the EIP whose tags you want to manage, and click the EIP name.
                                      5. 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 EIP
                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select the desired region and project.
                                          3. Click in the upper left corner, and choose Network > Elastic IP.
                                          4. On the displayed page, locate the EIP whose tags you want to manage, and click the EIP name.
                                          5. 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.

                                              diff --git a/docs/vpc/umn/en-us_topic_0073379079.html b/docs/vpc/umn/en-us_topic_0073379079.html index 3e8e69582..a500fff80 100644 --- a/docs/vpc/umn/en-us_topic_0073379079.html +++ b/docs/vpc/umn/en-us_topic_0073379079.html @@ -1,42 +1,45 @@

                                              Security Groups and Security Group Rules

                                              -

                                              Security Groups

                                              A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection requirements and that are mutually trusted. After a security group is created, you can create various access rules for the security group and these rules will apply to all cloud resources added to this security group.

                                              +

                                              Security Groups

                                              A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection requirements and that are mutually trusted. After a security group is created, you can configure access rules that will apply to all cloud resources added to this security group.

                                              If you have not created any security groups yet, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when you create it. For details about the default security group, see Default Security Group and Its Rules.

                                              -

                                              Security groups are stateful. If you send a request from your instance and the outbound traffic is allowed, the response traffic for that request is allowed to flow in regardless of inbound security group rules. Similarly, if inbound traffic is allowed, responses to allowed inbound traffic are allowed to flow out, regardless of outbound rules.

                                              -

                                              Security groups use connection tracking to track traffic to and from instances that they contain and security group rules are applied based on the connection status of the traffic to determine whether to allow or deny traffic.

                                              -
                                              • If you add, modify, or delete a security group rule, or add or remove an instance to or from a security group, the inbound connection tracking of all instances in the security group will be automatically cleared. The inbound or outbound traffic of the instance will be considered as new connections, which need to match the inbound or outbound security group rules to ensure that the rules take effect immediately and the security of incoming traffic.
                                              -
                                              • If there is no inbound or outbound traffic of an instance for a long time, the traffic will be considered as new connections after the connection tracking times out, and the connections need to match the outbound and inbound rules. The timeout period of connection tracking varies according to the protocol. The timeout period of a TCP connection in the established state is 600s, and the timeout period 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. For protocols other than TCP, UDP, and ICMP, only the IP address and protocol number are tracked.
                                              +
                                              +

                                              Security Group Basics

                                              • Security groups are stateful. If you send a request from your instance and the outbound traffic is allowed, the response traffic for that request is allowed to flow in regardless of inbound security group rules. Similarly, if inbound traffic is allowed, responses to allowed inbound traffic are allowed to flow out, regardless of outbound rules.
                                              • Security groups use connection tracking to track traffic to and from instances. If an inbound rule is modified, the modified rule immediately takes effect for the existing traffic. Changes to outbound security group rules do not affect existing persistent connections and take effect only for new connections.

                                                If you add, modify, or delete a security group rule, or add or remove an instance to or from a security group, the inbound connections of all instances in the security group will be automatically cleared.

                                                +
                                                • The existing inbound persistent connections will be disconnected. All the new connections will match the new rules.
                                                • The existing outbound persistent connections will not be disconnected, and the original rule will still be applied. All the new connections will match the new rules.
                                                +
                                              +

                                              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.

                                              +
                                              • 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.
                                              +

                                              Security Group Rules

                                              A security group has inbound and outbound rules to control traffic that's allowed to reach or leave the instances associated with the security group. You can specify protocol, port, source/destination for a security group rule. Table 1 describes key information about a security group rule. -
                                              Table 1 Security group rule information

                                              Parameter

                                              +
                                              - - - - - - - - -
                                              Table 1 Security group rule information

                                              Parameter

                                              Description

                                              +

                                              Description

                                              Protocol

                                              +

                                              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.

                                              +

                                              The network protocol used to match traffic in a security group rule. Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.

                                              Port

                                              +

                                              Port

                                              Destination port used to match traffic in a security group rule. The value can be from 1 to 65535.

                                              +

                                              Destination port used to match traffic in a security group rule. The value can be from 1 to 65535.

                                              • Inbound rules control incoming traffic over specific ports to instances in the security group.
                                              • Outbound rules control outgoing traffic over specific ports from instances in the security group.

                                              Source (Inbound)

                                              +

                                              Source (Inbound)

                                              The source in an inbound rule is used to match the IP address or address range of an external request. The source can be:
                                              • IP address:
                                                • Example IPv4 address: 192.168.10.10/32
                                                • Example IPv6 address: 2002:50::44/128
                                                • Example IPv4 address range: 192.168.52.0/24 All IPv4 addresses: 0.0.0.0/0
                                                • Example IPv6 address range: 2407:c080:802:469::/64 All IPv6 addresses: ::/0
                                                +
                                              The source in an inbound rule is used to match the IP address or address range of an external request. The source can be:
                                              • IP address:
                                                • Example IPv4 address: 192.168.10.10/32
                                                • Example IPv6 address: 2002:50::44/128
                                                • Example IPv4 address range: 192.168.52.0/24 All IPv4 addresses: 0.0.0.0/0
                                                • Example IPv6 address range: 2407:c080:802:469::/64 All IPv6 addresses: ::/0
                                              • Security group: You can select another security group in the same region under the current account as the source.

                                                For example, instance A is in security group A and instance B is in security group B. If security group A has a rule with Source set to security group B, access from instance B is allowed to instance A.

                                              • IP address group: If you have multiple IP address ranges and IP addresses with same security requirements, add them to an IP address group and select the group as the source to help you manage them in a more simple way.

                                              Destination (Outbound)

                                              +

                                              Destination (Outbound)

                                              The destination in an outbound rule is used to match the IP address or address range of an internal request. The destination can be:

                                              +

                                              The destination in an outbound rule is used to match the IP address or address range of an internal request. The destination can be:

                                              • IP address:
                                                • Example IPv4 address: 192.168.10.10/32
                                                • Example IPv6 address: 2002:50::44/128
                                                • Example IPv4 address range: 192.168.52.0/24 All IPv4 addresses: 0.0.0.0/0
                                                • Example IPv6 address range: 2407:c080:802:469::/64 All IPv6 addresses: ::/0
                                              • Security group: You can select another security group in the same region under the current account as the destination.

                                                For example, instance A is in security group A and instance B is in security group B. If security group A has a rule with Destination set to security group B, access from instance A is allowed to instance B.

                                                @@ -55,82 +58,82 @@
                                              Table 2 uses custom security group sg-AB as an example to describe its inbound and outbound rules in detail. -
                                              Table 2 Rules in security group sg-AB

                                              Direction

                                              +
                                              - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/vpc/umn/faq_bandwidth.html b/docs/vpc/umn/faq_bandwidth.html index b220a0764..422c6ed12 100644 --- a/docs/vpc/umn/faq_bandwidth.html +++ b/docs/vpc/umn/faq_bandwidth.html @@ -8,7 +8,7 @@
                                            • What Bandwidth Types Are Available?
                                              • -
                                            • What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth or the Other Way Around?
                                              +
                                            • What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth?
                                              • diff --git a/docs/vpc/umn/faq_bandwidth_0003.html b/docs/vpc/umn/faq_bandwidth_0003.html index 974c6f178..f5f21d59b 100644 --- a/docs/vpc/umn/faq_bandwidth_0003.html +++ b/docs/vpc/umn/faq_bandwidth_0003.html @@ -1,8 +1,8 @@ -

                                              What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? Can a Dedicated Bandwidth Be Changed to a Shared Bandwidth or the Other Way Around?

                                              -

                                              A dedicated bandwidth can only be used by one EIP. An EIP can only be used by 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 workloads.

                                              +

                                              What Are the Differences Between a Dedicated Bandwidth and 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.

                                              • After you add an EIP to a shared bandwidth, the EIP will use the shared bandwidth.
                                              • After you remove an EIP from a shared bandwidth, the EIP will use the dedicated bandwidth.
                                              diff --git a/docs/vpc/umn/faq_connection_0001.html b/docs/vpc/umn/faq_connection_0001.html index cad7b4977..2d81853b5 100644 --- a/docs/vpc/umn/faq_connection_0001.html +++ b/docs/vpc/umn/faq_connection_0001.html @@ -2,9 +2,9 @@

                                              Can a VPC Peering Connection Connect VPCs in Different Regions?

                                              A VPC peering connection only can connect VPCs in the same region.

                                              -
                                              Figure 1 shows an application scenario of VPC peering connections.
                                              • There are two VPCs (VPC-A and VPC-B) in region A that are not connected.
                                              • Service servers (ECS-A01 and ECS-A02) are in VPC-A, and database servers (RDS-B01 and RDS-B02) are in VPC-B. The service servers and database servers cannot communicate with each other.
                                              -
                                              • You need to create a VPC peering connection (peering-AB) between VPC-A and VPC-B so the service servers and database servers can communicate with each other.
                                              -
                                              Figure 1 VPC peering connection network diagram
                                              +
                                              Figure 1 shows an application scenario of VPC peering connections.
                                              • There are two VPCs (VPC-A and VPC-B) in region A that are not connected.
                                              • Service servers (ECS-A01 and ECS-A02) are in VPC-A, and database servers (RDS-B01 and RDS-B02) are in VPC-B. The service servers and database servers cannot communicate with each other.
                                              +
                                              • You need to create a VPC peering connection (peering-AB) between VPC-A and VPC-B so the service servers and database servers can communicate with each other.
                                              +
                                              Figure 1 VPC peering connection network diagram
                                              diff --git a/docs/vpc/umn/faq_eip.html b/docs/vpc/umn/faq_eip.html index 93c018fac..c4ae7d5ab 100644 --- a/docs/vpc/umn/faq_eip.html +++ b/docs/vpc/umn/faq_eip.html @@ -14,6 +14,8 @@
                                            • Can I Change the Region of My EIP?
                                              • +
                                            • What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?
                                              +
                                              • diff --git a/docs/vpc/umn/faq_security.html b/docs/vpc/umn/faq_security.html index 36a9b5e56..6d3c9bc00 100644 --- a/docs/vpc/umn/faq_security.html +++ b/docs/vpc/umn/faq_security.html @@ -14,9 +14,9 @@
                                            • How Do I Configure a Security Group for Multi-Channel Protocols?
                                              • -
                                            • Does a Security Group Rule or a Firewall Rule Immediately Take Effect for Existing Connections After It Is Modified?
                                              +
                                            • Does a Modified Security Group Rule or a Firewall Rule Take Effect Immediately for Existing Connections?
                                              • -
                                            • Which Security Group Rule Has Priority When Multiple Security Group Rules Conflict?
                                              +
                                            • Which Security Group Rule Has a High Priority When Multiple Security Group Rules Conflict?
                                              • diff --git a/docs/vpc/umn/faq_security_0003.html b/docs/vpc/umn/faq_security_0003.html index 300db166e..d88812f4d 100644 --- a/docs/vpc/umn/faq_security_0003.html +++ b/docs/vpc/umn/faq_security_0003.html @@ -1,7 +1,7 @@

                                              Why Can't I Delete a Security Group?

                                              -
                                              • The default security group is named default and cannot be deleted.
                                              • If you want to delete a security group that is associated with instances, such as cloud servers, containers, and databases, you need to remove the instances from the security group first.
                                              • A security group cannot be deleted if it is used as the source or destination of a rule in another security group.

                                                You need to delete or modify the rule first and delete the security group.

                                                +
                                                • The default security group is named default and cannot be deleted.
                                                • If you want to delete a security group that is associated with instances, such as cloud servers, containers, and databases, you need to remove the instances from the security group first.
                                                • A security group cannot be deleted if it is used as the source or destination of a rule in another security group.

                                                  You need to delete or modify the rule first and delete the security group.

                                                  For example, if the source of a rule in security group sg-B is set to sg-A, you need to delete or modify the rule in sg-B before deleting sg-A.

                                                diff --git a/docs/vpc/umn/overview_0004.html b/docs/vpc/umn/overview_0004.html index 2f213cf7b..be12d03c3 100644 --- a/docs/vpc/umn/overview_0004.html +++ b/docs/vpc/umn/overview_0004.html @@ -3,8 +3,8 @@

                                                Product Advantages

                                                Flexible Configuration

                                                You can create VPCs, add subnets, specify IP address ranges, and configure DHCP and route tables. You can configure the same VPC for ECSs that are in different availability zones (AZs).

                                                -

                                                Secure and Reliable

                                                VPCs are logically isolated through tunneling technologies. By default, different VPCs cannot communicate with each other. You can use firewalls to protect subnets and use security groups to protect ECSs. They add additional layers of security to your VPCs, so your network is secure.

                                                -
                                                Figure 1 Secure and Reliable
                                                +

                                                Secure and Reliable

                                                VPCs are logically isolated through tunneling technologies. By default, different VPCs cannot communicate with each other. You can use firewalls to protect subnets and use security groups to protect ECSs. They add additional layers of security to your VPCs, so your network is secure.

                                                +
                                                Figure 1 Secure and Reliable

                                                Seamless Interconnectivity

                                                By default, instances in a VPC cannot access the Internet. You can use EIPs, load balancers, NAT gateways, VPN connections, and Direct Connect connections to enable access to or from the Internet.

                                                By default, instances in different VPCs cannot communicate with each other. You can create a VPC peering connection to enable the instances in the two VPCs in the same region to communicate with each other using private IP addresses.

                                                @@ -24,28 +24,28 @@
                                              - - - - diff --git a/docs/vpc/umn/overview_permission.html b/docs/vpc/umn/overview_permission.html index 2ee3a2c3b..0b01028c2 100644 --- a/docs/vpc/umn/overview_permission.html +++ b/docs/vpc/umn/overview_permission.html @@ -6,7 +6,7 @@

                                              If your cloud account does not require IAM for permissions management, you can skip this section.

                                              IAM is a free service. You only pay for the resources in your account. For more information, see IAM Service Overview.

                                              VPC Permissions

                                              New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.

                                              -

                                              VPC is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions , the users only have permissions for VPCs in the selected projects. If you set Scope to All resources, users have permissions for VPCs in all region-specific projects. When accessing VPCs, the users need to switch to the authorized region.

                                              +

                                              VPC is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for VPCs in the selected projects. If you set Scope to All resources, users have permissions for VPCs in all region-specific projects. When accessing VPCs, the users need to switch to the authorized region.

                                              You can grant permissions by using roles and policies.

                                              • Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. When you grant permissions using roles, you also need to attach dependent roles. Roles are not ideal for fine-grained authorization and least privilege access.
                                              • Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant VPC users only the permissions for managing a certain type of resources. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by VPC, see Permissions Policies and Supported Actions.

                                              Table 1 lists all the system-defined permissions for VPC.

                                              diff --git a/docs/vpc/umn/overview_region.html b/docs/vpc/umn/overview_region.html index 904b0f073..69e64fd93 100644 --- a/docs/vpc/umn/overview_region.html +++ b/docs/vpc/umn/overview_region.html @@ -1,7 +1,7 @@

                                              Region and AZ

                                              -

                                              Concept

                                              A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

                                              +

                                              Concept

                                              A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

                                              • A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
                                              • An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.

                                              Figure 1 shows the relationship between regions and AZs.

                                              Figure 1 Regions and AZs
                                              @@ -16,7 +16,7 @@
                                              -
                                              Parent topic: Basic Concepts
                                              +
                                              Parent topic: Service Overview
                                              diff --git a/docs/vpc/umn/permission_0003.html b/docs/vpc/umn/permission_0003.html index 93316d968..275a4c72d 100644 --- a/docs/vpc/umn/permission_0003.html +++ b/docs/vpc/umn/permission_0003.html @@ -5,15 +5,15 @@

                                              If your cloud account meets your permissions requirements, you can skip this section.

                                              Figure 1 shows the process flow for granting permissions.

                                              -

                                              Prerequisites

                                              Learn about the permissions (see Permissions) supported by VPC and choose policies or roles according to your requirements.

                                              +

                                              Prerequisites

                                              Before granting permissions to user groups, learn about permissions (Permissions) for VPC.

                                              To grant permissions for other services, learn about all permissions supported by IAM.

                                              -

                                              Process Flow

                                              Figure 1 Process for granting VPC permissions
                                              +

                                              Process Flow

                                              Figure 1 Process for granting VPC permissions

                                              1. On the IAM console, create a user group and assign permissions to it (VPC ReadOnlyAccess as an example).

                                              2. Create an IAM user and add it to the created user group.

                                              3. Log in as the IAM user and verify permissions.

                                                In the authorized region, perform the following operations:

                                                -
                                                • Choose Service List > Virtual Private Cloud. Then click Create VPC on the VPC console. If a message appears indicating that you have insufficient permissions to perform the operation, the VPCReadOnlyAccess policy is in effect.
                                                • Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the VPCReadOnlyAccess policy is in effect.
                                                +
                                                • Choose Service List > Virtual Private Cloud. Then click Create VPC on the VPC console. If a message appears indicating that you have insufficient permissions to perform the operation, the VPC ReadOnlyAccess policy is in effect.
                                                • Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the VPC ReadOnlyAccess policy is in effect.
                                              diff --git a/docs/vpc/umn/vpc010003.html b/docs/vpc/umn/vpc010003.html index eff6eed82..8a887ae80 100644 --- a/docs/vpc/umn/vpc010003.html +++ b/docs/vpc/umn/vpc010003.html @@ -16,6 +16,8 @@
                                            • Deleting a Shared Bandwidth
                                              • +
                                            • Exporting Shared Bandwidths
                                              +
                                              • diff --git a/docs/vpc/umn/vpc010004.html b/docs/vpc/umn/vpc010004.html index 5e0862ae0..4c636a809 100644 --- a/docs/vpc/umn/vpc010004.html +++ b/docs/vpc/umn/vpc010004.html @@ -7,7 +7,7 @@

                                              When you host a large number of applications on the cloud, if each EIP uses a bandwidth, a lot of bandwidths are required, increasing O&M workload. If all EIPs share the same bandwidth, VPCs and the region-level bandwidth can be managed in a unified manner, simplifying O&M statistics and network operations cost settlement.

                                              • Easy to Manage

                                                Region-level bandwidth sharing and multiplexing simplify O&M statistics, management, and operations cost settlement.

                                              • Flexible Operations

                                                You can add EIPs (except for 5_gray EIPs of dedicated load balancers) to or remove them from a shared bandwidth regardless of the type of instances that they are bound 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.
                                                +
                                                • 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/vpc010005.html b/docs/vpc/umn/vpc010005.html index 53c6d4725..f84e49486 100644 --- a/docs/vpc/umn/vpc010005.html +++ b/docs/vpc/umn/vpc010005.html @@ -3,8 +3,8 @@

                                              Assigning a Shared Bandwidth

                                              Scenarios

                                              Assign a shared bandwidth for use with EIPs.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select the desired region and project.
                                              3. Click in the upper left corner and choose Network > Elastic IP.
                                              4. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              5. In the upper right corner, click Assign Shared Bandwidth. On the displayed page, configure parameters as prompted.

                                                -
                                                Figure 1 Assigning Shared Bandwidth
                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select the desired region and project.
                                                3. Click in the upper left corner, and choose Network > Elastic IP.
                                                4. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                                5. In the upper right corner, click Assign Shared Bandwidth. On the displayed page, configure parameters as prompted.

                                                  +
                                                  Figure 1 Assigning Shared Bandwidth
                                              Table 2 Rules in security group sg-AB

                                              Direction

                                              Type

                                              +

                                              Type

                                              Protocol & Port

                                              +

                                              Protocol & Port

                                              Source/Destination

                                              +

                                              Source/Destination

                                              Description

                                              +

                                              Description

                                              Inbound

                                              +

                                              Inbound

                                              IPv4

                                              +

                                              IPv4

                                              All

                                              +

                                              All

                                              Source: sg-AB

                                              +

                                              Source: sg-AB

                                              Allows ECSs in the security group to communicate with each other.

                                              +

                                              Allows ECSs in the security group to communicate with each other.

                                              Inbound

                                              +

                                              Inbound

                                              IPv4

                                              +

                                              IPv4

                                              TCP: 22

                                              +

                                              TCP: 22

                                              Source: 0.0.0.0/0

                                              +

                                              Source: 0.0.0.0/0

                                              Allows all IPv4 addresses to access ECSs in the security group over port 22 (SSH) for remotely logging in to Linux ECSs.

                                              +

                                              Allows all IPv4 addresses to access ECSs in the security group over port 22 (SSH) for remotely logging in to Linux ECSs.

                                              Inbound

                                              +

                                              Inbound

                                              IPv4

                                              +

                                              IPv4

                                              TCP: 3389

                                              +

                                              TCP: 3389

                                              Source: 0.0.0.0/0

                                              +

                                              Source: 0.0.0.0/0

                                              Allows all IPv4 addresses to access ECSs in the security group over port 3389 (RDP) for remotely logging in to Windows ECSs.

                                              +

                                              Allows all IPv4 addresses to access ECSs in the security group over port 3389 (RDP) for remotely logging in to Windows ECSs.

                                              Inbound

                                              +

                                              Inbound

                                              IPv4

                                              +

                                              IPv4

                                              TCP: 80

                                              +

                                              TCP: 80

                                              Source: 10.5.6.30/32

                                              +

                                              Source: 10.5.6.30/32

                                              Allows IP address 10.5.6.30 to access ECSs in the security group over port 80.

                                              +

                                              Allows IP address 10.5.6.30 to access ECSs in the security group over port 80.

                                              Outbound

                                              +

                                              Outbound

                                              IPv4

                                              +

                                              IPv4

                                              All

                                              +

                                              All

                                              Destination: 0.0.0.0/0

                                              +

                                              Destination: 0.0.0.0/0

                                              Allows access from ECSs in the security group to any IPv4 address over any port.

                                              +

                                              Allows access from ECSs in the security group to any IPv4 address over any port.

                                              Outbound

                                              +

                                              Outbound

                                              IPv6

                                              +

                                              IPv6

                                              All

                                              +

                                              All

                                              Destination: ::/0

                                              +

                                              Destination: ::/0

                                              Allows access from ECSs in the security group to any IPv6 address over any port.

                                              +

                                              Allows access from ECSs in the security group to any IPv6 address over any port.

                                              Deployment cycle

                                              • You do not need to perform complex engineering deployment, including engineering planning and cabling.
                                              • You can determine your networks, subnets, and routes on based on service requirements.
                                              +
                                              • You do not need to perform complex engineering deployment, including engineering planning and cabling.
                                              • You can determine your networks, subnets, and routes on the cloud based on service requirements.

                                              You need to set up networks and perform tests. The entire process takes a long time and requires professional technical support.

                                              Total cost

                                              provides flexible billing modes for network services. You can select whichever one best fits your business needs. There are no upfront costs and network O&M costs, reducing the total cost of ownership (TCO).

                                              +

                                              The cloud provides flexible billing modes for network services. You can select whichever one best fits your business needs. There are no upfront costs and network O&M costs, reducing the total cost of ownership (TCO).

                                              You need to invest heavily in equipment rooms, power supply, construction, and hardware materials. You also need professional O&M teams to ensure network security. Asset management costs increase with any change in business requirements.

                                              Flexibility

                                              provides a variety of network services for you to choose from. If you need more network resources (for instance, if you need more bandwidth), you can expand resources on the fly.

                                              +

                                              The cloud provides a variety of network services for you to choose from. If you need more network resources (for instance, if you need more bandwidth), you can expand resources on the fly.

                                              You have to strictly comply with the network plan to complete the service deployment. If there are changes in your service requirements, it is difficult to dynamically adjust the network.

                                              Security

                                              VPCs are logically isolated from each other. You can use security features such as network ACLs and security groups, and even security services like Advanced Anti-DDoS (AAD) to protect your cloud resources.

                                              +

                                              VPCs are logically isolated from each other. You can use security features such as firewalls and security groups, and even security services like Advanced Anti-DDoS (AAD) to protect your cloud resources.

                                              The network is insecure and difficult to maintain. You need professional technical personnel to ensure network security.
                                              @@ -38,7 +38,7 @@ diff --git a/docs/vpc/umn/vpc010006.html b/docs/vpc/umn/vpc010006.html index b2cfbda59..c92458519 100644 --- a/docs/vpc/umn/vpc010006.html +++ b/docs/vpc/umn/vpc010006.html @@ -3,11 +3,9 @@

                                              Adding EIPs to a Shared Bandwidth

                                              Scenarios

                                              Add EIPs to a shared bandwidth and the EIPs can then share that bandwidth. You can add multiple EIPs to a shared bandwidth at the same time.

                                              -

                                              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.
                                              +

                                              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.
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              2. Click in the upper left corner and choose Network > Elastic IP.
                                              3. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              4. In the shared bandwidth list, locate the row that contains the shared bandwidth that you want to add EIPs to. In the Operation column, choose Add EIP, and select the EIPs to be added.
                                                • 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's dedicated bandwidth will be deleted and will no longer be billed.
                                                -
                                                -
                                                Figure 1 Add EIP
                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                1. Click in the upper left corner and select the desired region and project.
                                                2. Click in the upper left corner, and choose Network > Elastic IP.
                                                3. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                                4. 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
                                                5. Click OK.
                                              diff --git a/docs/vpc/umn/vpc010007.html b/docs/vpc/umn/vpc010007.html index ce59ad6a3..423141105 100644 --- a/docs/vpc/umn/vpc010007.html +++ b/docs/vpc/umn/vpc010007.html @@ -3,7 +3,7 @@

                                              Removing EIPs from a Shared Bandwidth

                                              Scenarios

                                              Remove EIPs that are no longer required from a shared bandwidth if needed.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              2. Click in the upper left corner and choose Network > Elastic IP.
                                              3. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              4. In the shared bandwidth list, locate the row that contains the bandwidth from which EIPs are to be removed, choose More > Remove EIP in the Operation column, and select the EIPs to be removed in the displayed dialog box.
                                                Figure 1 Remove EIP
                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                1. Click in the upper left corner and select the desired region and project.
                                                2. Click in the upper left corner, and choose Network > Elastic IP.
                                                3. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                                4. 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
                                                5. Click OK.
                                              diff --git a/docs/vpc/umn/vpc010008.html b/docs/vpc/umn/vpc010008.html index c44fbaf33..62f735f81 100644 --- a/docs/vpc/umn/vpc010008.html +++ b/docs/vpc/umn/vpc010008.html @@ -3,8 +3,8 @@

                                              Modifying a Shared Bandwidth

                                              Scenarios

                                              You can modify the name and size of a shared bandwidth as required.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              2. Click in the upper left corner and choose Network > Elastic IP.
                                              3. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              4. In the shared bandwidth list, locate the row that contains the shared bandwidth you want to modify, click Modify Bandwidth in the Operation column, and modify the bandwidth settings.
                                                Figure 1 Modify Bandwidth
                                                -
                                              5. Click Next.
                                              6. Click Submit.
                                              +

                                              Procedure

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              2. Click in the upper left corner, and choose Network > Elastic IP.
                                              3. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              4. In the shared bandwidth list, locate the row that contains the shared bandwidth you want to modify, click Modify Bandwidth in the Operation column, and modify the bandwidth settings.
                                                Figure 1 Modify Bandwidth
                                                +
                                              5. Click Next.
                                              6. Click Submit.
                                              diff --git a/docs/vpc/umn/vpc010009.html b/docs/vpc/umn/vpc010009.html index 06abaa8f1..ec96212aa 100644 --- a/docs/vpc/umn/vpc010009.html +++ b/docs/vpc/umn/vpc010009.html @@ -5,7 +5,7 @@

                                              Prerequisites

                                              Before deleting a shared bandwidth, remove all the EIPs associated with it. For details, see Removing EIPs from a Shared Bandwidth.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              1. Click in the upper left corner and choose Network > Elastic IP.
                                              1. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              2. 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.
                                              3. In the displayed dialog box, click OK.
                                              +

                                              Procedure

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              1. Click in the upper left corner, and choose Network > Elastic IP.
                                              1. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              2. 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.
                                              3. In the displayed dialog box, click OK.
                                              diff --git a/docs/vpc/umn/vpc010010.html b/docs/vpc/umn/vpc010010.html new file mode 100644 index 000000000..f4c78a2fa --- /dev/null +++ b/docs/vpc/umn/vpc010010.html @@ -0,0 +1,12 @@ + + +

                                              Exporting Shared Bandwidths

                                              +
                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              1. Click in the upper left corner, and choose Network > Elastic IP.
                                              1. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              2. 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.

                                                +
                                              +
                                              +
                                              +
                                              +
                                              Parent topic: Shared Bandwidth
                                              +
                                              +
                                              + diff --git a/docs/vpc/umn/vpc010012.html b/docs/vpc/umn/vpc010012.html index 9aaeb46ee..3ec11c64b 100644 --- a/docs/vpc/umn/vpc010012.html +++ b/docs/vpc/umn/vpc010012.html @@ -114,7 +114,6 @@
                                              -

                                              diff --git a/docs/vpc/umn/vpc010013.html b/docs/vpc/umn/vpc010013.html index 9d9c1efc1..7ba727384 100644 --- a/docs/vpc/umn/vpc010013.html +++ b/docs/vpc/umn/vpc010013.html @@ -4,9 +4,9 @@

                                              Scenarios

                                              You can view the bandwidth and EIP usage on the Elastic IP and Bandwidth or Cloud Eye console.

                                              You can view the inbound bandwidth, outbound bandwidth, inbound bandwidth usage, outbound bandwidth usage, inbound traffic, and outbound traffic in a specified period.

                                              -

                                              Procedure (Elastic IP and Bandwidth Console)

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select the desired region and project.
                                              3. Click in the upper left corner and choose Network > Elastic IP.
                                              4. On the EIPs page, search for the EIP, click More in the Operation column, and click View Metric to view the monitoring metric details.
                                              5. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              6. On the Shared Bandwidths page, locate the shared bandwidth, click More in the Operation column, and click View Metric to view the monitoring metric details.
                                              +

                                              Procedure (Elastic IP and Bandwidth Console)

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select the desired region and project.
                                              3. Click in the upper left corner and choose Network > Elastic IP.
                                              4. On the EIPs page, locate the target EIP and click View Metric in the Monitoring column to view the monitoring metrics.
                                              5. In the navigation pane on the left, choose Elastic IP and Bandwidth > Shared Bandwidths.
                                              6. On the Shared Bandwidths page, locate the shared bandwidth, click More in the Operation column, and click View Metric to view the monitoring metric details.
                                              -

                                              Procedure (Cloud Eye Console)

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              2. In the upper left corner of the page, click to open the service list and choose Management & Deployment > Cloud Eye.
                                              3. Click Cloud Service Monitoring on the left of the page, and choose Elastic IP and Bandwidth.
                                              4. Locate the row that contains the target bandwidth or EIP and click View Metric in the Operation column to check the bandwidth or EIP monitoring information.
                                              +

                                              Procedure (Cloud Eye Console)

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              2. In the upper left corner of the page, click to open the service list and choose Management & Deployment > Cloud Eye.
                                              3. Click Cloud Service Monitoring on the left of the page, and choose Elastic IP and Bandwidth.
                                              4. Locate the row that contains the target bandwidth or EIP and click View Metric in the Operation column to check the bandwidth or EIP monitoring information.
                                              diff --git a/docs/vpc/umn/vpc010014.html b/docs/vpc/umn/vpc010014.html index 0711f306b..b161026f4 100644 --- a/docs/vpc/umn/vpc010014.html +++ b/docs/vpc/umn/vpc010014.html @@ -3,8 +3,8 @@

                                              Creating an Alarm Rule

                                              Scenarios

                                              You can configure alarm rules to customize the monitored objects and notification policies. You can learn your resource statuses at any time.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              1. Click in the upper left corner and select the desired region and project.
                                              2. In the upper left corner of the page, click to open the service list and choose Management & Deployment > Cloud Eye.
                                              3. In the left navigation pane on the left, choose Alarm Management > Alarm Rules.
                                              4. On the Alarm Rules page, click Create Alarm Rule and set required parameters, or modify an existing alarm rule.
                                              5. After the parameters are set, click Create.

                                                After the alarm rule is created, the system automatically notifies you if an alarm is triggered for the VPC service.

                                                -

                                                For more information about alarm rules, see the Cloud Eye User Guide.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                1. Click in the upper left corner and select the desired region and project.
                                                2. In the upper left corner of the page, click to open the service list and choose Management & Deployment > Cloud Eye.
                                                3. In the left navigation pane on the left, choose Alarm Management > Alarm Rules.
                                                4. On the Alarm Rules page, click Create Alarm Rule and set required parameters, or modify an existing alarm rule.
                                                5. After the parameters are set, click Create.

                                                  After the alarm rule is created, the system automatically notifies you if an alarm is triggered for the VPC service.

                                                  +

                                                  For more information about alarm rules, see Cloud Eye User Guide.

                                                diff --git a/docs/vpc/umn/vpc_0002.html b/docs/vpc/umn/vpc_0002.html index f18478563..3df30e7df 100644 --- a/docs/vpc/umn/vpc_0002.html +++ b/docs/vpc/umn/vpc_0002.html @@ -7,57 +7,109 @@
                                              -

                                              Notes and Constraints

                                              • Only certain ECS specifications support IPv6 networks and can use IPv4/IPv6 dual-stack networks. You need to select such ECSs in supported regions.
                                                To check which ECSs support IPv6:
                                                • On the ECS console, click Buy ECS. On the displayed page, view the ECS specifications.

                                                  If there is the IPv6 parameter with the value of Yes, the ECS specifications support IPv6.

                                                  +

                                                  Notes and Constraints

                                                  • Only certain ECS specifications support IPv6 networks and can use IPv4/IPv6 dual-stack networks. You need to select such ECSs in supported regions.
                                                    To check which ECSs support IPv6:
                                                    • On the ECS console: Click Create ECS. On the displayed page, view the ECS specifications.

                                                      If there is the IPv6 parameter with the value of Yes, the ECS specifications support IPv6.

                                                  IPv6 Application Scenarios

                                                  If your ECS supports IPv6, you can use the IPv4/IPv6 dual-stack network. Table 1 shows the example application scenarios. -
                                              Table 1 Parameter descriptions

                                              Parameter

                                              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.

                                              +

                                              An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.

                                              default
                                              Table 1 Application scenarios of IPv4/IPv6 dual stack

                                              Application Scenario

                                              +
                                              - - - + - - - - + - - - - + - + + + + + + + + + + + + +
                                              Table 1 Application scenarios of IPv4/IPv6 dual stack

                                              Application Scenario

                                              Description

                                              +

                                              Description

                                              Subnet

                                              +

                                              Requirement

                                              ECS

                                              +

                                              IPv4 or IPv6 Subnet

                                              +

                                              ECS

                                              Private communication using IPv6 addresses

                                              +

                                              Private IPv4 communication

                                              Your applications deployed on ECSs need to communicate with other systems (such as databases) through private networks using IPv6 addresses.

                                              +

                                              Your applications on ECSs need to communicate with other systems (such as databases) through private networks using IPv4 addresses.

                                              • IPv4 CIDR block
                                              • IPv6 CIDR block
                                              +
                                              • IPv6 is not enabled for the VPC subnet.
                                              • No EIPs have been bound to the ECSs.
                                              • Private IPv4 address: used for private communication
                                              • IPv6 address: used for private communication.
                                              +

                                              IPv4 CIDR Block

                                              +

                                              Private IPv4 address: used for private IPv4 communication.

                                              Public communication using IPv6 addresses

                                              +

                                              Public IPv4 communication

                                              Your applications deployed on ECSs need to provide services accessible from the Internet using IPv6 addresses.

                                              +

                                              Your applications on ECSs need to communicate with other systems (such as databases) through public IPv4 addresses.

                                              • IPv4 CIDR block
                                              • IPv6 CIDR block
                                              +
                                              • IPv6 is not enabled for the VPC subnet.
                                              • EIPs have been bound to the ECSs.
                                              • Private IPv4 address + IPv4 EIP: used for public network communication
                                              • IPv6 address + shared bandwidth: used for public network communication
                                              +

                                              IPv4 CIDR Block

                                              +
                                              • Private IPv4 address: used for private IPv4 communication.
                                              • Public IPv4 address: used for public IPv4 communication.

                                              Your applications deployed on ECSs need to both provide services accessible from the Internet and analyze the access request data using IPv6 addresses.

                                              +

                                              Private IPv6 communication

                                              +

                                              Your applications on ECSs need to communicate with other systems (such as databases) through private IPv6 addresses.

                                              +
                                              • IPv6 has been enabled for the VPC subnet.
                                              • The network has been configured for the ECSs as follows:
                                                • VPC and Subnet: IPv6-enabled subnet and VPC.
                                                • Shared Bandwidth: Selected Do not configure.
                                                +
                                              +
                                              • IPv4 CIDR Block
                                              • IPv6 CIDR block
                                              +
                                              • Private IPv4 address + IPv4 EIP: Bind an IPv4 EIP to the instance to allow public IPv4 communication.
                                              • Private IPv4 address: Do not bind any IPv4 EIP to the instance and use only the private IPv4 address to allow private IPv4 communication.
                                              • IPv6 address: Do not configure shared bandwidth for the IPv6 address to allow private IPv6 communication.
                                              +

                                              Public IPv6 communication

                                              +

                                              An IPv6 network is required for the ECS to access the IPv6 service on the Internet.

                                              +
                                              • IPv6 has been enabled for the VPC subnet.
                                              • The network has been configured for the ECSs as follows:
                                                • VPC and Subnet: IPv6-enabled subnet and VPC.
                                                • Shared Bandwidth: Selected a shared bandwidth.
                                                +
                                              +
                                              • IPv4 CIDR Block
                                              • IPv6 CIDR block
                                              +
                                              • Private IPv4 address + IPv4 EIP: Bind an IPv4 EIP to the instance to allow public IPv4 communication.
                                              • Private IPv4 address: Do not bind any IPv4 EIP to the instance and use only the private IPv4 address to allow private IPv4 communication.
                                              +
                                              • IPv6 address + shared bandwidth: Allow both private IPv6 communication and public IPv6 communication.
                                              +
                                              +
                                              + +
                                              +
                                              + + + + + + + + +
                                              Table 2 Application scenarios of IPv6 EIPs

                                              Application Scenario

                                              +

                                              Description

                                              +

                                              Subnet

                                              +

                                              ECS

                                              +

                                              Public communication using IPv6 addresses

                                              +

                                              Your applications deployed on ECSs need to provide services accessible from the Internet using IPv6 addresses.

                                              +

                                              IPv4 CIDR block

                                              +
                                              • Private IPv4 address
                                              • IPv4 EIP (with IPv6 function enabled): used for public communication using IPv4 and IPv6 EIPs
                                              -

                                              Basic Operations

                                              Creating an IPv6 Subnet

                                              -

                                              Create an IPv6 subnet by following the instructions in Creating a Subnet for the VPC. Select Enable for IPv6 CIDR Block. An IPv6 CIDR block will be automatically assigned to the subnet. IPv6 cannot be disabled after the subnet is created. Currently, customizing IPv6 CIDR block is not supported.

                                              +

                                              Create an IPv6 subnet by following the instructions in Creating a Subnet for the VPC. Select Enable for IPv6 CIDR Block. An IPv6 CIDR block will be automatically assigned to the subnet. IPv6 cannot be disabled after the subnet is created.

                                              +

                                              To disable this function, call the API by referring to Updating Subnet Information.

                                              Viewing In-Use IPv6 Addresses

                                              In the subnet list, click the subnet name. On the displayed page, view in-use IPv4 and IPv6 addresses on the IP Addresses tab.

                                              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 a Network ACL Rule (IPv6)

                                              -

                                              Add a network ACL 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.

                                              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 7c5db6a7f..1d73290f5 100644 --- a/docs/vpc/umn/vpc_0003.html +++ b/docs/vpc/umn/vpc_0003.html @@ -8,6 +8,10 @@
                                            • Modifying a VPC
                                              • +
                                            • Adding a Secondary IPv4 CIDR Block to a VPC
                                              +
                                              • +
                                            • Deleting a Secondary IPv4 CIDR Block from a VPC
                                              +
                                            • Deleting a VPC
                                            • Managing VPC Tags
                                              diff --git a/docs/vpc/umn/vpc_Concepts_0001.html b/docs/vpc/umn/vpc_Concepts_0001.html index 771731dc9..b912dd95b 100644 --- a/docs/vpc/umn/vpc_Concepts_0001.html +++ b/docs/vpc/umn/vpc_Concepts_0001.html @@ -22,8 +22,6 @@
                                            • Virtual IP Address
                                              • -
                                            • Region and AZ
                                              -
                                              • diff --git a/docs/vpc/umn/vpc_Concepts_0003.html b/docs/vpc/umn/vpc_Concepts_0003.html index 51774d27c..9c435e0b5 100644 --- a/docs/vpc/umn/vpc_Concepts_0003.html +++ b/docs/vpc/umn/vpc_Concepts_0003.html @@ -2,7 +2,7 @@

                                              Elastic IP

                                              The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.

                                              -
                                              Each EIP can be used by only one cloud resource at a time.
                                              Figure 1 Accessing the Internet using an EIP
                                              +
                                              Each EIP can be used by only one cloud resource at a time.
                                              Figure 1 Accessing the Internet using an EIP
                                              diff --git a/docs/vpc/umn/vpc_Concepts_0005.html b/docs/vpc/umn/vpc_Concepts_0005.html index 15aa8c187..494aac802 100644 --- a/docs/vpc/umn/vpc_Concepts_0005.html +++ b/docs/vpc/umn/vpc_Concepts_0005.html @@ -1,91 +1,91 @@

                                              Security Group

                                              -

                                              A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection requirements and that are mutually trusted. After a security group is created, you can create various access rules for the security group and these rules will apply to all cloud resources added to this security group.

                                              -
                                              Like whitelists, security group rules work as follows:
                                              • Inbound rules control incoming traffic to instances in the security group.

                                                If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                                                -

                                                By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                                                -
                                              • Outbound rules control outgoing traffic from instances in the security group.

                                                If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                                                -

                                                0.0.0.0/0 represents all IPv4 addresses.

                                                -

                                                ::/0 represents all IPv6 addresses.

                                                +

                                                A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection requirements and that are mutually trusted. After a security group is created, you can configure access rules that will apply to all cloud resources added to this security group.

                                                +
                                                Like whitelists, security group rules work as follows:
                                                • Inbound rules control incoming traffic to instances in the security group.

                                                  If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                                                  +

                                                  By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                                                  +
                                                • Outbound rules control outgoing traffic from instances in the security group.

                                                  If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                                                  +

                                                  0.0.0.0/0 represents all IPv4 addresses.

                                                  +

                                                  ::/0 represents all IPv6 addresses.

                                                -
                                                Table 1 uses custom security group sg-AB as an example to describe its inbound and outbound rules in detail. -
                                                Table 1 Rules in security group sg-AB

                                                Direction

                                                +
                                                Table 1 uses custom security group sg-AB as an example to describe its inbound and outbound rules in detail. +
                                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/vpc/umn/vpc_Concepts_0010.html b/docs/vpc/umn/vpc_Concepts_0010.html index c2ad8f48d..df668566e 100644 --- a/docs/vpc/umn/vpc_Concepts_0010.html +++ b/docs/vpc/umn/vpc_Concepts_0010.html @@ -3,16 +3,14 @@

                                                Shared SNAT

                                                The VPC service provides free SNAT function, which allows ECSs to use a limited number of public IP addresses to gain one-way access to the Internet for operations, such as updating software. However, Internet users cannot directly access the ECSs.

                                                Figure 1 shows how shared SNAT works. The SNAT device forwards traffic from ECSs to the Internet and the response traffic from the Internet to the ECSs. When forwarding ECS traffic to the Internet, the SNAT device converts the source IP addresses (ECS private IP addresses) in the data packets into the public IP addresses set on the SNAT device. When processing the response packets from the Internet to the ECSs, the SNAT device changes the public IP addresses in the response data packets to the private IP addresses of the ECSs.

                                                -
                                                Figure 1 SNAT function
                                                -
                                                • To enable shared SNAT using the API, refer to Updating a Router and set enable_snat to true.
                                                • To enable shared SNAT on the management console:
                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    -
                                                  3. On the Virtual Private Cloud page, locate the VPC for which shared SNAT is to be enabled, and click Modify.
                                                  4. In the displayed dialog box, enable Shared SNAT.
                                                  5. Click OK.
                                                  -
                                                -

                                                After being configured for a VPC, shared SNAT takes effect for the whole VPC. If EIPs are bound to ECSs in a VPC for which shared SNAT is configured, Internet traffic is preferentially forwarded using the EIPs. If you want to prevent an ECS from connecting to the Internet, you can configure an outbound rule for the security group associated with the ECS.

                                                +
                                                Figure 1 SNAT function
                                                +
                                                • To enable shared SNAT using the API, refer to Updating a Router and set enable_snat to true.
                                                +

                                                After being configured for a VPC, shared SNAT takes effect for the whole VPC. If EIPs are bound to ECSs in a VPC for which shared SNAT is configured, Internet traffic is preferentially forwarded using the EIPs. If you want to prevent an ECS from connecting to the Internet, you can configure an outbound rule for the security group associated with the ECS.

                                                For example:

                                                To prevent an ECS from connecting to the Internet but allow the ECS to access 192.168.10.0/24, configure the following rule for the security group associated with the ECS:

                                                1. Delete the default outbound rule that allows all outgoing data packets from the security group.

                                                  After this rule is deleted, ECSs associated with this security group are not allowed to access any network, including the internal networks in the VPC of the ECSs.

                                                  -
                                                  Figure 2 Deleting the default outbound rule from the security group
                                                  -
                                                2. Add the required outbound rule.
                                                  The following shows the added outbound rule that allows the ECS to access the 192.168.10.0/24 CIDR block.
                                                  Figure 3 Adding an outbound rule for the security group
                                                  +
                                                  Figure 2 Deleting the default outbound rule from the security group
                                                  +
                                                3. Add the required outbound rule.
                                                  The following shows the added outbound rule that allows the ECS to access the 192.168.10.0/24 CIDR block.
                                                  Figure 3 Adding an outbound rule for the security group

                                                  The differences between shared SNAT and custom routes are as follows:

                                                  • Shared SNAT provides the SNAT function for a specified VPC through an API or the management console and enables all ECSs in the VPC to gain one-way access to the Internet.
                                                  • A custom route enables ECSs to access the Internet through an SNAT server that has an EIP bound. The ECSs' access requests are routed to the SNAT server based on the route table.
                                                  • Shared SNAT takes effect for the whole VPC by default, while a custom route takes effect for the VPC or subnet for which routes have been configured.
                                                  • A custom route has a higher priority than a shared SNAT.
                                                  diff --git a/docs/vpc/umn/vpc_Concepts_0011.html b/docs/vpc/umn/vpc_Concepts_0011.html index 28c073bb3..211af3268 100644 --- a/docs/vpc/umn/vpc_Concepts_0011.html +++ b/docs/vpc/umn/vpc_Concepts_0011.html @@ -5,7 +5,7 @@
                                                Figure 1 shows an application scenario of VPC peering connections.
                                                • There are two VPCs (VPC-A and VPC-B) in region A that are not connected.
                                                • Service servers (ECS-A01 and ECS-A02) are in VPC-A, and database servers (RDS-B01 and RDS-B02) are in VPC-B. The service servers and database servers cannot communicate with each other.
                                                • You need to create a VPC peering connection (peering-AB) between VPC-A and VPC-B so the service servers and database servers can communicate with each other.
                                                -
                                                Figure 1 VPC peering connection network diagram
                                                +
                                                Figure 1 VPC peering connection network diagram

                                                For details about VPC peering connections, see VPC Peering Connection.

                                                diff --git a/docs/vpc/umn/vpc_Concepts_0012.html b/docs/vpc/umn/vpc_Concepts_0012.html index 48890afb8..b795bece6 100644 --- a/docs/vpc/umn/vpc_Concepts_0012.html +++ b/docs/vpc/umn/vpc_Concepts_0012.html @@ -1,21 +1,21 @@

                                                Virtual IP Address

                                                -

                                                A virtual IP address can be shared among multiple ECSs. An ECS can have both private and virtual IP addresses, and you can access the ECS through either IP address. A virtual IP address has the same network access capabilities as a private IP address, including layer 2 and layer 3 communication in VPCs, access between VPCs using VPC peering connections, as well as access through EIPs, VPN connections, and Direct Connect connections.

                                                -

                                                You can bind ECSs deployed in active/standby mode with the same virtual IP address, and then bind an EIP to the virtual IP address. Virtual IP addresses can work together with Keepalived to ensure high availability and disaster recovery. If the active ECS is faulty, the standby ECS automatically takes over services from the active one.

                                                +

                                                You can use either IP address to enable layer 2 and layer 3 communications in a VPC, access a different VPC using peering connections, and access cloud servers through EIPs, Direct Connect connections, and VPN connections.

                                                +

                                                You can bind a virtual IP address to ECSs deployed in the active/standby pair, and then bind an EIP to the virtual IP address. Virtual IP addresses can work together with Keepalived to ensure high availability and disaster recovery. If the active ECS is faulty, the standby ECS automatically takes over services from the active one.

                                                Networking

                                                Virtual IP addresses are used for high availability and can work together with Keepalived to make active/standby ECS switchover possible. This way if one ECS goes down for some reason, the other one can take over and services continue uninterrupted. ECSs can be configured for HA or as load balancing clusters.

                                                -
                                                • Networking mode 1: HA

                                                  If you want to improve service availability and avoid single points of failure, you can deploy ECSs in the active/standby mode or deploy one active ECS and multiple standby ECSs. In this arrangement, the ECSs all use the same virtual IP address. If the active ECS becomes faulty, a standby ECS takes over services from the active ECS and services continue uninterrupted.

                                                  +
                                                  • Networking mode 1: HA

                                                    To improve service availability and eliminate single points of failure, you can deploy ECSs in the active/standby pair or deploy one active ECS and multiple standby ECSs. And then, you can bind the same virtual IP address to these ECSs. If the active ECS becomes faulty, a standby ECS takes over services from the active ECS and services continue uninterrupted.

                                                    Figure 1 Networking diagram of the HA mode
                                                    -
                                                    • In this configuration, a single virtual IP address is bound to two ECSs in the same subnet.
                                                    • Keepalived is then used to configure the two ECSs to work in the active/standby mode. Follow industry standards for configuring Keepalived. The details are not included here.
                                                    +
                                                    • As shown in the above figure, bind a virtual IP address to two ECSs in the same subnet.
                                                    • Configure Keepalived for the two ECSs to work in the active/standby pair. Follow industry standards for configuring Keepalived. The details are not included here.
                                                  • Networking mode 2: HA load balancing cluster

                                                    If you want to build a high-availability load balancing cluster, use Keepalived and configure LVS nodes as direct routers.

                                                    Figure 2 HA load balancing cluster
                                                    -
                                                    • Bind a single virtual IP address to two ECSs.
                                                    • Configure the two ECSs as LVS nodes working as direct routers and use Keepalived to configure the nodes in the active/standby mode. The two ECSs will evenly forward requests to different backend servers.
                                                    • Configure two more ECSs as backend servers.
                                                    • Disable the source/destination check for the two backend servers.
                                                    +
                                                    • Bind a single virtual IP address to two ECSs.
                                                    • Configure the two ECSs as LVS nodes working as direct routers and use Keepalived to configure the nodes in the active/standby pair. The two ECSs will evenly forward requests to different backend servers.
                                                    • Configure two more ECSs as backend servers.
                                                    • Disable the source/destination check for the two backend servers.

                                                    Follow industry standards for configuring Keepalived. The details are not included here.

                                                Application Scenarios

                                                • Accessing the virtual IP address through an EIP

                                                  If your application has high availability requirements and needs to provide services through the Internet, it is recommended that you bind an EIP to a virtual IP address.

                                                  -
                                                • Using a VPN, Direct Connect, or VPC peering connection to access a virtual IP address

                                                  To ensure high availability and access to the Internet, use a VPN for security and Direct Connect for a stable connection. The VPC peering connection is needed so that the VPCs in the same region can communicate with each other.

                                                  +
                                                • Using a VPN, Direct Connect, or VPC peering connection to access a virtual IP address

                                                  To ensure high availability and access to the Internet, use a VPN for security and Direct Connect for a stable connection. A VPC peering connection is needed so that two VPCs in the same region can communicate with each other.

                                                diff --git a/docs/vpc/umn/vpc_SecurityGroup_0001.html b/docs/vpc/umn/vpc_SecurityGroup_0001.html index 8ec25020f..9995f193c 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0001.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0001.html @@ -10,33 +10,11 @@
                                              • Security Group Configuration Examples
                                                • -
                                              • Creating a Security Group
                                                +
                                              • Managing a Security Group
                                                • -
                                              • Cloning a Security Group
                                                +
                                              • Managing Security Group Rules
                                                • -
                                              • Modifying a Security Group
                                                -
                                                • -
                                              • Deleting a Security Group
                                                -
                                                • -
                                              • Adding a Security Group Rule
                                                -
                                                • -
                                              • Fast-Adding Security Group Rules
                                                -
                                                • -
                                              • Allowing Common Ports with A Few Clicks
                                                -
                                                • -
                                              • Modifying a Security Group Rule
                                                -
                                                • -
                                              • Replicating a Security Group Rule
                                                -
                                                • -
                                              • Importing and Exporting Security Group Rules
                                                -
                                                • -
                                              • Deleting a Security Group Rule
                                                -
                                                • -
                                              • Adding an Instance to or Removing an Instance from a Security Group
                                                -
                                                • -
                                              • Viewing the Security Group of an ECS
                                                -
                                                • -
                                              • Changing the Security Group of an ECS
                                                +
                                              • Managing Instances Associated with a Security Group
                                                • diff --git a/docs/vpc/umn/vpc_SecurityGroup_0004.html b/docs/vpc/umn/vpc_SecurityGroup_0004.html index 274cc237d..58a713e99 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0004.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0004.html @@ -3,7 +3,7 @@

                                                Replicating a Security Group Rule

                                                Scenarios

                                                You can replicate an existing security group rule and modify it to quickly generate a new rule.

                                                -

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select the desired region and project.
                                                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                  The Virtual Private Cloud page is displayed.

                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select the desired region and project.
                                                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                  4. In the security group list, click the name of the security group.

                                                    The security group details page is displayed.

                                                  5. Click the Inbound Rules or Outbound Rules tab as required.

                                                    The security group rule list is displayed.

                                                  6. Locate the row that contains the rule and click Replicate in the Operation column.

                                                    The Replicate Inbound Rule dialog box is displayed.

                                                    @@ -12,7 +12,7 @@
                                                  -
                                                  Parent topic: Security Group
                                                  +
                                                  Parent topic: Managing Security Group Rules
                                                  diff --git a/docs/vpc/umn/vpc_SecurityGroup_0005.html b/docs/vpc/umn/vpc_SecurityGroup_0005.html index f8b0904e4..77c0a10c0 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0005.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0005.html @@ -3,7 +3,7 @@

                                                  Modifying a Security Group Rule

                                                  Scenarios

                                                  You can modify the port, protocol, and IP address of your security group rules as required to ensure the security of your instances.

                                                  -

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select the desired region and project.
                                                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select the desired region and project.
                                                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                      The Virtual Private Cloud page is displayed.

                                                    4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                      The security group list is displayed.

                                                    5. In the security group list, click the name of the security group.

                                                      The security group details page is displayed.

                                                    6. Click the Inbound Rules or Outbound Rules tab as required.

                                                      The security group rule list is displayed.

                                                      @@ -12,7 +12,7 @@
                                                    -
                                                    Parent topic: Security Group
                                                    +
                                                    Parent topic: Managing Security Group Rules
                                                    diff --git a/docs/vpc/umn/vpc_SecurityGroup_0006.html b/docs/vpc/umn/vpc_SecurityGroup_0006.html index 1a0c437e8..279fbc032 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0006.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0006.html @@ -6,7 +6,7 @@

                                                    Notes and Constraints

                                                    Security group rules use whitelists. Deleting a security group rule may result in ECS access failures. Security group rules work as follows:
                                                    • Inbound rule: If an inbound request matches the source in an inbound security group rule with Action set to Allow, the request is allowed.
                                                    • Outbound rule: If the destination of an outbound security group rule with Action set to Allow is 0.0.0.0/0, all outbound requests are allowed.
                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    1. Click in the upper left corner and select the desired region and project.
                                                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                      The Virtual Private Cloud page is displayed.

                                                      +

                                                      Procedure

                                                      1. Log in to the management console.
                                                      1. Click in the upper left corner and select the desired region and project.
                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                        The Virtual Private Cloud page is displayed.

                                                      3. In the navigation pane on the left, choose Access Control > Security Groups.

                                                        The security group list is displayed.

                                                      4. In the security group list, click the name of the security group.

                                                        The security group details page is displayed.

                                                      5. Click the Inbound Rules or Outbound Rules tab as required.

                                                        The security group rule list is displayed.

                                                        @@ -16,7 +16,7 @@
                                                      -
                                                      Parent topic: Security Group
                                                      +
                                                      Parent topic: Managing Security Group Rules
                                                      diff --git a/docs/vpc/umn/vpc_SecurityGroup_0007.html b/docs/vpc/umn/vpc_SecurityGroup_0007.html index 1260bb929..ce44489b5 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0007.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0007.html @@ -6,10 +6,10 @@

                                                    Notes and Constraints

                                                    • The security group rules to be imported must be configured based on the template. Do not add parameters or change existing parameters. Otherwise, the import will fail.
                                                    • Duplicate rules are not allowed, you can delete the rule and try again.
                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select the desired region and project.
                                                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                      The Virtual Private Cloud page is displayed.

                                                      +

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                        The Virtual Private Cloud page is displayed.

                                                      4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                        The security group list is displayed.

                                                      5. On the security group list, click the name of the target security group.

                                                        The security group details page is displayed.

                                                        -
                                                      6. 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 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.
                                                Table 1 Rules in security group sg-AB

                                                Direction

                                                Type

                                                +

                                                Type

                                                Protocol & Port

                                                +

                                                Protocol & Port

                                                Source/Destination

                                                +

                                                Source/Destination

                                                Description

                                                +

                                                Description

                                                Inbound

                                                +

                                                Inbound

                                                IPv4

                                                +

                                                IPv4

                                                All

                                                +

                                                All

                                                Source: sg-AB

                                                +

                                                Source: sg-AB

                                                Allows ECSs in the security group to communicate with each other.

                                                +

                                                Allows ECSs in the security group to communicate with each other.

                                                Inbound

                                                +

                                                Inbound

                                                IPv4

                                                +

                                                IPv4

                                                TCP: 22

                                                +

                                                TCP: 22

                                                Source: 0.0.0.0/0

                                                +

                                                Source: 0.0.0.0/0

                                                Allows all IPv4 addresses to access ECSs in the security group over port 22 (SSH) for remotely logging in to Linux ECSs.

                                                +

                                                Allows all IPv4 addresses to access ECSs in the security group over port 22 (SSH) for remotely logging in to Linux ECSs.

                                                Inbound

                                                +

                                                Inbound

                                                IPv4

                                                +

                                                IPv4

                                                TCP: 3389

                                                +

                                                TCP: 3389

                                                Source: 0.0.0.0/0

                                                +

                                                Source: 0.0.0.0/0

                                                Allows all IPv4 addresses to access ECSs in the security group over port 3389 (RDP) for remotely logging in to Windows ECSs.

                                                +

                                                Allows all IPv4 addresses to access ECSs in the security group over port 3389 (RDP) for remotely logging in to Windows ECSs.

                                                Inbound

                                                +

                                                Inbound

                                                IPv4

                                                +

                                                IPv4

                                                TCP: 80

                                                +

                                                TCP: 80

                                                Source: 10.5.6.30/32

                                                +

                                                Source: 10.5.6.30/32

                                                Allows IP address 10.5.6.30 to access ECSs in the security group over port 80.

                                                +

                                                Allows IP address 10.5.6.30 to access ECSs in the security group over port 80.

                                                Outbound

                                                +

                                                Outbound

                                                IPv4

                                                +

                                                IPv4

                                                All

                                                +

                                                All

                                                Destination: 0.0.0.0/0

                                                +

                                                Destination: 0.0.0.0/0

                                                Allows access from ECSs in the security group to any IPv4 address over any port.

                                                +

                                                Allows access from ECSs in the security group to any IPv4 address over any port.

                                                Outbound

                                                +

                                                Outbound

                                                IPv6

                                                +

                                                IPv6

                                                All

                                                +

                                                All

                                                Destination: ::/0

                                                +

                                                Destination: ::/0

                                                Allows access from ECSs in the security group to any IPv6 address over any port.

                                                +

                                                Allows access from ECSs in the security group to any IPv6 address over any port.
                                                @@ -41,7 +41,7 @@ - - - @@ -81,7 +81,7 @@
                                                -
                                                Parent topic: Security Group
                                                +
                                                Parent topic: Managing Security Group Rules
                                                diff --git a/docs/vpc/umn/vpc_SecurityGroup_0008.html b/docs/vpc/umn/vpc_SecurityGroup_0008.html index 040b80f17..e819d5fa6 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0008.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0008.html @@ -7,7 +7,7 @@

                                                For example, if the source of a rule in security group sg-B is set to sg-A, you need to delete or modify the rule in sg-B before deleting sg-A.

                                                -

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select the desired region and project.
                                                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                  The Virtual Private Cloud page is displayed.

                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select the desired region and project.
                                                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                  4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                    The security group list is displayed.

                                                  5. Locate the row that contains the target security group, click More in the Operation column, and click Delete.

                                                    A confirmation dialog box is displayed.

                                                  6. Confirm the information and click Yes.
                                                  @@ -15,7 +15,7 @@
                                                  -
                                                  Parent topic: Security Group
                                                  +
                                                  Parent topic: Managing a Security Group
                                                  diff --git a/docs/vpc/umn/vpc_SecurityGroup_0009.html b/docs/vpc/umn/vpc_SecurityGroup_0009.html index cae99bc6b..1f7ef4f83 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0009.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0009.html @@ -8,16 +8,16 @@

                                                  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

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select the desired region and project.
                                                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select the desired region and project.
                                                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                      The Virtual Private Cloud page is displayed.

                                                    4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                      The security group list is displayed.

                                                      -
                                                    5. Locate the row that contains the security group, click More in the Operation column, and click Clone.
                                                    6. Select the region and name of the new security group as prompted.
                                                      Figure 1 Clone Security Group
                                                      +
                                                    7. Locate the row that contains the security group, click More in the Operation column, and click Clone.
                                                    8. Select the region and name of the new security group as prompted.
                                                      Figure 1 Clone Security Group
                                                    9. Click OK.

                                                      You can then switch to the required region to view the cloned security group in the security group list.

                                                  -
                                                  Parent topic: Security Group
                                                  +
                                                  Parent topic: Managing a Security Group
                                                  diff --git a/docs/vpc/umn/vpc_SecurityGroup_0010.html b/docs/vpc/umn/vpc_SecurityGroup_0010.html index a20717b2e..40cda7549 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0010.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0010.html @@ -4,7 +4,7 @@

                                                  Scenarios

                                                  After a security group is created, you can change its name and description.

                                                  -

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select the desired region and project.
                                                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select the desired region and project.
                                                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                      The Virtual Private Cloud page is displayed.

                                                    4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                      The security group list is displayed.

                                                    5. Locate the row that contains the security group, click More in the Operation column, and click Modify.

                                                      The Modify Security Group dialog box is displayed.

                                                    6. Modify the name and description of the security group as required.
                                                    7. Click OK to save the modification.
                                                    @@ -12,7 +12,7 @@
                                                    -
                                                    Parent topic: Security Group
                                                    +
                                                    Parent topic: Managing a Security Group
                                                    diff --git a/docs/vpc/umn/vpc_SecurityGroup_0011.html b/docs/vpc/umn/vpc_SecurityGroup_0011.html index 842eb1f48..b461908af 100644 --- a/docs/vpc/umn/vpc_SecurityGroup_0011.html +++ b/docs/vpc/umn/vpc_SecurityGroup_0011.html @@ -3,7 +3,7 @@

                                                    Viewing the Security Group of an ECS

                                                    Scenarios

                                                    View inbound and outbound rules of a security group used by an ECS.

                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select the desired region and project.
                                                    3. In the upper left corner of the page, click . In the service list, choose Computing > Elastic Cloud Server.

                                                      The ECS list is displayed.

                                                      +

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. In the upper left corner of the page, click . In the service list, choose Computing > Elastic Cloud Server.

                                                        The ECS list is displayed.

                                                      4. On the Elastic Cloud Server page, click the name of the target ECS.

                                                        The page providing details about the ECS is displayed.

                                                      5. Click the Security Groups tab and view information about the security group used by the ECS.

                                                        You can view the security groups associated with the ECS and the inbound and outbound rules.

                                                      @@ -11,7 +11,7 @@
                                                      diff --git a/docs/vpc/umn/vpc_SecurityGroup_0012.html b/docs/vpc/umn/vpc_SecurityGroup_0012.html new file mode 100644 index 000000000..702af8581 --- /dev/null +++ b/docs/vpc/umn/vpc_SecurityGroup_0012.html @@ -0,0 +1,25 @@ + + + +

                                                      Managing a Security Group

                                                      + +

                                                      +
                                                      + + + diff --git a/docs/vpc/umn/vpc_SecurityGroup_0013.html b/docs/vpc/umn/vpc_SecurityGroup_0013.html new file mode 100644 index 000000000..d0a538ee7 --- /dev/null +++ b/docs/vpc/umn/vpc_SecurityGroup_0013.html @@ -0,0 +1,31 @@ + + + +

                                                      Managing Security Group Rules

                                                      + +

                                                      +
                                                      + + + diff --git a/docs/vpc/umn/vpc_SecurityGroup_0014.html b/docs/vpc/umn/vpc_SecurityGroup_0014.html new file mode 100644 index 000000000..85c527a55 --- /dev/null +++ b/docs/vpc/umn/vpc_SecurityGroup_0014.html @@ -0,0 +1,19 @@ + + +

                                                      Managing Instances Associated with a Security Group

                                                      +
                                                      + + diff --git a/docs/vpc/umn/vpc_acl_0000.html b/docs/vpc/umn/vpc_acl_0000.html index 268adb203..a14ca00e2 100644 --- a/docs/vpc/umn/vpc_acl_0000.html +++ b/docs/vpc/umn/vpc_acl_0000.html @@ -8,29 +8,11 @@
                                                    4. Firewall Configuration Examples
                                                      5. -
                                                    5. Creating a Firewall
                                                      +
                                                    6. Managing Firewalls
                                                      7. -
                                                    7. Adding a Firewall Rule
                                                      +
                                                    8. Management Firewall Rules
                                                      9. -
                                                    9. Associating Subnets with a Firewall
                                                      -
                                                      10. -
                                                    10. Disassociating Subnets from a Firewall
                                                      -
                                                      11. -
                                                    11. Changing the Sequence of a Firewall Rule
                                                      -
                                                      12. -
                                                    12. Modifying a Firewall Rule
                                                      -
                                                      13. -
                                                    13. Enabling or Disabling a Firewall Rule
                                                      -
                                                      14. -
                                                    14. Deleting a Firewall Rule
                                                      -
                                                      15. -
                                                    15. Viewing a Firewall
                                                      -
                                                      16. -
                                                    16. Modifying a Firewall
                                                      -
                                                      17. -
                                                    17. Enabling or Disabling a Firewall
                                                      -
                                                      18. -
                                                    18. Deleting a Firewall
                                                      +
                                                    19. Managing Subnets Associated with a Firewall
                                                      20. diff --git a/docs/vpc/umn/vpc_acl_0003.html b/docs/vpc/umn/vpc_acl_0003.html index a62dd1247..867067e3a 100644 --- a/docs/vpc/umn/vpc_acl_0003.html +++ b/docs/vpc/umn/vpc_acl_0003.html @@ -3,7 +3,7 @@

                                                      Disassociating Subnets from a Firewall

                                                      Scenarios

                                                      You can disassociate a subnet from its firewall based on your network requirements.

                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      1. Click in the upper left corner and select the desired region and project.
                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                        The Virtual Private Cloud page is displayed.

                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        1. Click in the upper left corner and select the desired region and project.
                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                          The Virtual Private Cloud page is displayed.

                                                        3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                        4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                        5. On the displayed page, click the Associated Subnets tab.
                                                        6. On the Associated Subnets page, locate the row that contains the target subnet and click Disassociate in the Operation column.
                                                        7. Click Yes in the displayed dialog box.

                                                        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.

                                                        @@ -11,7 +11,7 @@
                                                        diff --git a/docs/vpc/umn/vpc_acl_0004.html b/docs/vpc/umn/vpc_acl_0004.html index 625245a06..5c8032ba5 100644 --- a/docs/vpc/umn/vpc_acl_0004.html +++ b/docs/vpc/umn/vpc_acl_0004.html @@ -4,14 +4,14 @@

                                                        Scenarios

                                                        If you need a rule to take effect before or after a specific rule, you can insert that rule before or after the specific rule.

                                                        If multiple firewall rules conflict, only the rule with the highest priority takes effect.

                                                        -

                                                        Procedure

                                                        1. Log in to the management console.
                                                        1. Click in the upper left corner and select the desired region and project.
                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                          The Virtual Private Cloud page is displayed.

                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          1. Click in the upper left corner and select the desired region and project.
                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                            The Virtual Private Cloud page is displayed.

                                                          3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                          4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                          5. On the Inbound Rules or Outbound Rules tab, locate the target rule, click More in the Operation column, and select Insert Rule Above or Insert Rule Below.
                                                          6. In the displayed dialog box, configure required parameters and click OK.

                                                            The rule is inserted. The procedure for inserting an outbound rule is the same as that for inserting an inbound rule.

                                                        -
                                                        Parent topic: Firewall
                                                        +
                                                        Parent topic: Management Firewall Rules
                                                        diff --git a/docs/vpc/umn/vpc_acl_0005.html b/docs/vpc/umn/vpc_acl_0005.html index e047df870..a3ceb4e3c 100644 --- a/docs/vpc/umn/vpc_acl_0005.html +++ b/docs/vpc/umn/vpc_acl_0005.html @@ -3,79 +3,79 @@

                                                        Modifying a Firewall Rule

                                                        Scenarios

                                                        Modify an inbound or outbound firewall rule based on your network security requirements.

                                                        -

                                                        Procedure

                                                        1. Log in to the management console.
                                                        1. Click in the upper left corner and select the desired region and project.
                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                          The Virtual Private Cloud page is displayed.

                                                          -
                                                        3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                        4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                        5. On the Inbound Rules or Outbound Rules tab, locate the row that contains the target rule and click Modify in the Operation column. In the displayed dialog box, configure parameters as prompted. Table 1 lists the parameters to be configured.
                                                          Figure 1 Modify Rule
                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          1. Click in the upper left corner and select the desired region and project.
                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                            The Virtual Private Cloud page is displayed.

                                                            +
                                                          3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                          4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                          5. On the Inbound Rules or Outbound Rules tab, locate the row that contains the target rule and click Modify in the Operation column. In the displayed dialog box, configure parameters as prompted. Table 1 lists the parameters to be configured.
                                                            Figure 1 Modify Rule
                                                            -
                                                Table 1 Template parameters

                                                Parameter

                                                Description

                                                @@ -29,7 +29,7 @@

                                                Protocol & Port

                                                The network protocol used to match traffic in a security group rule.

                                                -

                                                Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.

                                                +

                                                Currently, the value can be All, TCP, UDP, GRE, ICMP, or more.

                                                TCP

                                                Type

                                                Source IP address version. You can select:
                                                • IPv4
                                                • IPv6
                                                +
                                                Source IP address version. You can select:
                                                • IPv4
                                                • IPv6

                                                IPv4

                                                @@ -49,8 +49,8 @@

                                                Source

                                                Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example:
                                                • IP address:
                                                  • Single IP address: 192.168.10.10/32
                                                  • All IP addresses: 0.0.0.0/0
                                                  • IP address range: 192.168.1.0/24
                                                  -
                                                • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                                                • IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                                +
                                                Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example:
                                                • IP address:
                                                  • Single IP address: 192.168.10.10/32
                                                  • All IP addresses: 0.0.0.0/0
                                                  • IP address range: 192.168.1.0/24
                                                  +
                                                • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                                                • IP address group: The source is an IP address group. An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.

                                                sg-test[96a8a93f-XXX-d7872990c314]

                                                @@ -65,8 +65,8 @@

                                                Description

                                                Supplementary information about the security group rule. This parameter is optional.

                                                -

                                                The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                                +

                                                (Optional) Supplementary information about the security group rule.

                                                +

                                                The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                                -
                                                Table 1 Parameter descriptions

                                                Parameter

                                                +
                                                - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -86,7 +86,7 @@
                                                -
                                                Parent topic: Firewall
                                                +
                                                Parent topic: Management Firewall Rules
                                                diff --git a/docs/vpc/umn/vpc_acl_0006.html b/docs/vpc/umn/vpc_acl_0006.html index 747d945e5..734af51d3 100644 --- a/docs/vpc/umn/vpc_acl_0006.html +++ b/docs/vpc/umn/vpc_acl_0006.html @@ -3,14 +3,14 @@

                                                Enabling or Disabling a Firewall Rule

                                                Scenarios

                                                Enable or disable an inbound or outbound rule based on your network security requirements.

                                                -

                                                Procedure

                                                1. Log in to the management console.
                                                1. Click in the upper left corner and select the desired region and project.
                                                2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                  The Virtual Private Cloud page is displayed.

                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                  3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                  4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                  5. 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.
                                                  6. 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.

                                                -
                                                Parent topic: Firewall
                                                +
                                                Parent topic: Management Firewall Rules
                                                diff --git a/docs/vpc/umn/vpc_acl_0007.html b/docs/vpc/umn/vpc_acl_0007.html index 6769a499d..dbbd20ef6 100644 --- a/docs/vpc/umn/vpc_acl_0007.html +++ b/docs/vpc/umn/vpc_acl_0007.html @@ -3,7 +3,7 @@

                                                Deleting a Firewall Rule

                                                Scenarios

                                                Delete an inbound or outbound rule based on your network security requirements.

                                                -

                                                Procedure

                                                1. Log in to the management console.
                                                1. Click in the upper left corner and select the desired region and project.
                                                2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                  The Virtual Private Cloud page is displayed.

                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                  3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                  4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                  5. On the Inbound Rules or Outbound Rules tab, locate the row that contains the target rule and click Delete in the Operation column.
                                                  6. Click Yes in the displayed dialog box.

                                                  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.

                                                  @@ -11,7 +11,7 @@
                                                  -
                                                  Parent topic: Firewall
                                                  +
                                                  Parent topic: Management Firewall Rules
                                                  diff --git a/docs/vpc/umn/vpc_acl_0009.html b/docs/vpc/umn/vpc_acl_0009.html index ad34f5218..a54d72616 100644 --- a/docs/vpc/umn/vpc_acl_0009.html +++ b/docs/vpc/umn/vpc_acl_0009.html @@ -3,13 +3,13 @@

                                                  Viewing a Firewall

                                                  Scenarios

                                                  View details about a firewall.

                                                  -

                                                  Procedure

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    1. Click in the upper left corner and select the desired region and project.
                                                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                      The Virtual Private Cloud page is displayed.

                                                    3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                    4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                    5. On the displayed page, click the Inbound Rules, Outbound Rules, and Associated Subnets tabs one by one to view details about inbound rules, outbound rules, and subnet associations.
                                                  -
                                                  Parent topic: Firewall
                                                  +
                                                  Parent topic: Managing Firewalls
                                                  diff --git a/docs/vpc/umn/vpc_acl_0010.html b/docs/vpc/umn/vpc_acl_0010.html index 55e5f7eb2..35bb603d6 100644 --- a/docs/vpc/umn/vpc_acl_0010.html +++ b/docs/vpc/umn/vpc_acl_0010.html @@ -3,13 +3,13 @@

                                                  Modifying a Firewall

                                                  Scenarios

                                                  Modify the name and description of a firewall.

                                                  -

                                                  Procedure

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    -
                                                  3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                  4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                  5. On the displayed page, click on the right of Name and edit the firewall name.
                                                  6. Click √ to save the new firewall name.
                                                  7. Click on the right of Description and edit the firewall description.
                                                  8. Click √ to save the new firewall description.
                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    +
                                                  3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                  4. Locate the target firewall and click its name to switch to the page showing details of that particular firewall.
                                                  5. On the displayed page, click on the right of Name and edit the firewall name.
                                                  6. Click √ to save the new firewall name.
                                                  7. Click on the right of Description and edit the firewall description.
                                                  8. Click √ to save the new firewall description.
                                                  -
                                                  Parent topic: Firewall
                                                  +
                                                  Parent topic: Managing Firewalls
                                                  diff --git a/docs/vpc/umn/vpc_acl_0011.html b/docs/vpc/umn/vpc_acl_0011.html index af56c4f3d..62f2f57dd 100644 --- a/docs/vpc/umn/vpc_acl_0011.html +++ b/docs/vpc/umn/vpc_acl_0011.html @@ -4,13 +4,13 @@

                                                  Scenarios

                                                  After a firewall is created, you may need to enable it based on network security requirements. You can also disable an enabled firewall if needed. Before enabling a firewall, ensure that subnets have been associated with the firewall and that inbound and outbound rules have been added to the firewall.

                                                  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

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    -
                                                  3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                  4. Locate the row that contains the firewall, click More in the Operation column, and click Enable or Disable.
                                                  5. Click Yes in the displayed dialog box.
                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    +
                                                  3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                  4. Locate the row that contains the firewall, click More in the Operation column, and click Enable or Disable.
                                                  5. Click Yes in the displayed dialog box.
                                                  -
                                                  Parent topic: Firewall
                                                  +
                                                  Parent topic: Managing Firewalls
                                                  diff --git a/docs/vpc/umn/vpc_acl_0012.html b/docs/vpc/umn/vpc_acl_0012.html index 81dd6076d..251cfa268 100644 --- a/docs/vpc/umn/vpc_acl_0012.html +++ b/docs/vpc/umn/vpc_acl_0012.html @@ -3,7 +3,7 @@

                                                  Deleting a Firewall

                                                  Scenarios

                                                  Delete a firewall when it is no longer required.

                                                  -

                                                  Procedure

                                                  1. Log in to the management console.
                                                  1. Click in the upper left corner and select the desired region and project.
                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                    The Virtual Private Cloud page is displayed.

                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    1. Click in the upper left corner and select the desired region and project.
                                                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                      The Virtual Private Cloud page is displayed.

                                                    3. In the navigation pane on the left, choose Access Control > Firewalls.
                                                    4. Locate the firewall, click More in the Operation column, and click Delete.
                                                    5. Click Yes.

                                                      Deleting a firewall will also disassociate its associated subnets and delete the firewall rules.

                                                    @@ -11,7 +11,7 @@
                                                    -
                                                    Parent topic: Firewall
                                                    +
                                                    Parent topic: Managing Firewalls
                                                    diff --git a/docs/vpc/umn/vpc_acl_0014.html b/docs/vpc/umn/vpc_acl_0014.html new file mode 100644 index 000000000..234f74c24 --- /dev/null +++ b/docs/vpc/umn/vpc_acl_0014.html @@ -0,0 +1,24 @@ + + +

                                                    Managing Firewalls

                                                    +

                                                    +
                                                    + + diff --git a/docs/vpc/umn/vpc_acl_0015.html b/docs/vpc/umn/vpc_acl_0015.html new file mode 100644 index 000000000..7583147f2 --- /dev/null +++ b/docs/vpc/umn/vpc_acl_0015.html @@ -0,0 +1,24 @@ + + +

                                                    Management Firewall Rules

                                                    +

                                                    +
                                                    + + diff --git a/docs/vpc/umn/vpc_acl_0016.html b/docs/vpc/umn/vpc_acl_0016.html new file mode 100644 index 000000000..24bb8b821 --- /dev/null +++ b/docs/vpc/umn/vpc_acl_0016.html @@ -0,0 +1,18 @@ + + +

                                                    Managing Subnets Associated with a Firewall

                                                    +

                                                    +
                                                    + + diff --git a/docs/vpc/umn/vpc_eip_0001.html b/docs/vpc/umn/vpc_eip_0001.html index 19b50d366..453a00b17 100644 --- a/docs/vpc/umn/vpc_eip_0001.html +++ b/docs/vpc/umn/vpc_eip_0001.html @@ -3,17 +3,17 @@

                                                    Unbinding an EIP from an ECS and Releasing the EIP

                                                    Scenarios

                                                    If you no longer need an EIP, unbind it from the ECS and release the EIP to avoid wasting network resources.

                                                    -

                                                    Notes and Constraints

                                                    • In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
                                                    • Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
                                                      • The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
                                                      • You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
                                                      • EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
                                                      • You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
                                                      +

                                                      Notes and Constraints

                                                      • In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
                                                      • Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
                                                        • The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
                                                        • You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
                                                        • EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
                                                        • You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
                                                      • 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

                                                      -
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner and choose Network > Elastic IP.
                                                      4. On the displayed page, locate the row that contains the EIP, and click Unbind.
                                                      5. Click Yes in the displayed dialog box.
                                                      -
                                                      Releasing a single EIP
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner and choose Network > Elastic IP.
                                                      4. On the displayed page, locate the row that contains the target EIP, click More and then Release in the Operation column.
                                                      5. Click Yes in the displayed dialog box.
                                                      +
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner, and choose Network > Elastic IP.
                                                      4. On the displayed page, locate the row that contains the EIP, and click Unbind.
                                                      5. Click Yes in the displayed dialog box.
                                                      +
                                                      Releasing a single EIP
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner, and choose Network > Elastic IP.
                                                      4. On the displayed page, locate the row that contains the target EIP, click More and then Release in the Operation column.
                                                      5. Click Yes in the displayed dialog box.

                                                      Unbinding multiple EIPs at once

                                                      -
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner and choose Network > Elastic IP.
                                                      4. On the displayed page, select the EIPs to be unbound.
                                                      5. Click the Unbind button located above the EIP list.
                                                      6. Click Yes in the displayed dialog box.
                                                      +
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner, and choose Network > Elastic IP.
                                                      4. On the displayed page, select the EIPs to be unbound.
                                                      5. Click the Unbind button located above the EIP list.
                                                      6. Click Yes in the displayed dialog box.

                                                      Releasing multiple EIPs at once

                                                      -
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner and choose Network > Elastic IP.
                                                      4. On the displayed page, select the EIPs to be released.
                                                      5. Click the Release button located above the EIP list.
                                                      6. Click Yes in the displayed dialog box.
                                                      +
                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. Click in the upper left corner, and choose Network > Elastic IP.
                                                      4. On the displayed page, select the EIPs to be released.
                                                      5. Click the Release button located above the EIP list.
                                                      6. Click Yes in the displayed dialog box.
                                                      diff --git a/docs/vpc/umn/vpc_faq_0001.html b/docs/vpc/umn/vpc_faq_0001.html index af526e17a..20111dbd4 100644 --- a/docs/vpc/umn/vpc_faq_0001.html +++ b/docs/vpc/umn/vpc_faq_0001.html @@ -1,9 +1,9 @@

                                                      What Is Virtual Private Cloud?

                                                      -

                                                      The Virtual Private Cloud (VPC) service enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security and simplifying network deployment. You can configure and manage the virtual networks as required.

                                                      -

                                                      Within your own VPC, you can create security groups and VPNs, configure IP address ranges, specify bandwidth sizes, manage the networks in the VPC, and make changes to these networks as needed, quickly and securely. You can also define rules to control communications between ECSs in the same security group or in different security groups.

                                                      -
                                                      Figure 1 VPC components
                                                      +

                                                      Virtual Private Cloud (VPC) enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security and simplifying network deployment. You can configure and manage the virtual networks as required.

                                                      +

                                                      Within your own VPC, you can create security groups and VPNs, configure IP address ranges, specify bandwidth sizes, manage the networks in the VPC, and make changes to these networks as needed, quickly and securely. You can also customize the ECS access rules within a security group and between security groups to enhance ECS security.

                                                      +
                                                      Figure 1 VPC components
                                                      diff --git a/docs/vpc/umn/vpc_faq_0011.html b/docs/vpc/umn/vpc_faq_0011.html index 47d1b7de8..209934841 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 5 Mbit/s to 1000 Mbit/s.

                                                      +

                                                      The bandwidth range is from 5Mbit/s to 1000Mbit/s.

                                                      diff --git a/docs/vpc/umn/vpc_faq_0013.html b/docs/vpc/umn/vpc_faq_0013.html index edd36c965..208763c48 100644 --- a/docs/vpc/umn/vpc_faq_0013.html +++ b/docs/vpc/umn/vpc_faq_0013.html @@ -2,7 +2,7 @@

                                                      What Is an EIP?

                                                      The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.

                                                      -
                                                      Each EIP can be used by only one cloud resource at a time.
                                                      Figure 1 Accessing the Internet using an EIP
                                                      +
                                                      Each EIP can be used by only one cloud resource at a time.
                                                      Figure 1 Accessing the Internet using an EIP
                                                      diff --git a/docs/vpc/umn/vpc_faq_0019.html b/docs/vpc/umn/vpc_faq_0019.html index 27c1e5261..be59e418c 100644 --- a/docs/vpc/umn/vpc_faq_0019.html +++ b/docs/vpc/umn/vpc_faq_0019.html @@ -2,7 +2,7 @@

                                                      Can I Bind an EIP to Multiple ECSs?

                                                      Each EIP can be bound to only one ECS at a time.

                                                      -

                                                      Multiple ECSs cannot share the same EIP. An ECS and its bound EIP must be in the same region. If you want multiple ECSs in the same VPC to share an EIP, you have to use a NAT gateway. For more information, see NAT Gateway User Guide.

                                                      +

                                                      Multiple ECSs cannot share the same EIP. An ECS and its EIP must be in the same region. To enable ECSs across AZs in a VPC to share an EIP, you can use a NAT gateway by referring to NAT Gateway User Guide.

                                                      diff --git a/docs/vpc/umn/vpc_faq_0051.html b/docs/vpc/umn/vpc_faq_0051.html index 5e8a07e88..9997b543d 100644 --- a/docs/vpc/umn/vpc_faq_0051.html +++ b/docs/vpc/umn/vpc_faq_0051.html @@ -4,14 +4,14 @@

                                                      What Is a Quota?

                                                      A quota limits the quantity of a resource available to users, thereby preventing spikes in the usage of the resource. For example, a VPC quota limits the number of VPCs that can be created.

                                                      You can also request for an increased quota if your existing quota cannot meet your service requirements.

                                                      -

                                                      How Do I View My Quotas?

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select the desired region and project.
                                                      3. In the upper right corner of the page, click .

                                                        The Service Quota page is displayed.

                                                        -
                                                      4. View the used and total quota of each type of resources on the displayed page.

                                                        If a quota cannot meet service requirements, apply for a higher quota.

                                                        +

                                                        How Do I View My Quotas?

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select the desired region and project.
                                                        3. In the upper right corner of the page, click .

                                                          The Quotas page is displayed.

                                                          +
                                                        4. On the Quotas page, view the used and total quotas of each type of resources.

                                                          If a quota cannot meet your needs, apply for a higher quota by performing the following operations.

                                                        -

                                                        How Do I Apply for a Higher Quota?

                                                        The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.

                                                        +

                                                        How Do I Increase My Quota?

                                                        The system does not support online quota adjustment. To adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.

                                                        Before dialing the hotline number or sending an email, make sure that the following information has been obtained:

                                                        -
                                                        • Domain name, project name, and project ID, which can be obtained by performing the following operations:

                                                          Log in to the management console using the cloud account, click the username in the upper right corner, select My Credentials from the drop-down list, and obtain the domain name, project name, and project ID on the My Credentials page.

                                                          -
                                                        • Quota information, which includes:
                                                          • Service name
                                                          • Quota type
                                                          • Required quota
                                                          +
                                                          • Domain name, project name, and project ID

                                                            To obtain the preceding information, log in to the management console, click the username in the upper-right corner, and choose My Credentials from the drop-down list.

                                                            +
                                                          • Quota information, which includes:
                                                            • Service Name
                                                            • Quota type
                                                            • Required quota

                                                          Learn how to obtain the service hotline and email address.

                                                        diff --git a/docs/vpc/umn/vpc_faq_0059.html b/docs/vpc/umn/vpc_faq_0059.html index 12d90d34e..a2b529b8b 100644 --- a/docs/vpc/umn/vpc_faq_0059.html +++ b/docs/vpc/umn/vpc_faq_0059.html @@ -5,7 +5,7 @@

                                                        Security Group Configuration

                                                        You can configure port 69 and configure data channel ports used by TFTP for the security group. In RFC1350, the TFTP protocol specifies that ports available to data channels range from 0 to 65535. However, not all these ports are used by the TFTP daemon processes of different applications. You can configure a smaller range of ports for the TFTP daemon.

                                                        The following figure provides an example of the security group rule configuration if the ports used by data channels range from 60001 to 60100.

                                                        -
                                                        Figure 1 Security group rules
                                                        +
                                                        Figure 1 Security group rules
                                                      diff --git a/docs/vpc/umn/vpc_faq_0060.html b/docs/vpc/umn/vpc_faq_0060.html index 0b5d37497..b098cbf26 100644 --- a/docs/vpc/umn/vpc_faq_0060.html +++ b/docs/vpc/umn/vpc_faq_0060.html @@ -2,7 +2,7 @@

                                                      Why Are Internet or Internal Domain Names in the Cloud Inaccessible Through Domain Names When My ECS Has Multiple NICs?

                                                      -

                                                      When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access the Internet or domain names in the cloud.

                                                      +

                                                      When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access public websites or internal domain names in the cloud.

                                                      You can resolve this issue by configuring the same DNS server address for the subnets used by the same ECS. You can perform the following steps to modify DNS server addresses of subnets in a VPC:

                                                      1. Log in to the management console.
                                                      1. On the console homepage, under Network, click Virtual Private Cloud.
                                                      2. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
                                                      3. In the subnet list, locate the target subnet and click its name.
                                                      4. On the subnet details page, change the DNS server address of the subnet.
                                                      5. Click OK.
                                                      diff --git a/docs/vpc/umn/vpc_faq_0069.html b/docs/vpc/umn/vpc_faq_0069.html index 3b71976e0..7c28f1386 100644 --- a/docs/vpc/umn/vpc_faq_0069.html +++ b/docs/vpc/umn/vpc_faq_0069.html @@ -31,7 +31,7 @@
                                                -
                                                Table 1 Parameter descriptions

                                                Item

                                                Description

                                                +

                                                Description

                                                Example Value

                                                +

                                                Example Value

                                                Type

                                                +

                                                Type

                                                The firewall type. This parameter is mandatory. You can select a value from the drop-down list. Currently, only IPv4 and IPv6 are supported.

                                                +

                                                Specifies the firewall type. This parameter is mandatory. You can select a value from the drop-down list. Currently, only IPv4 and IPv6 are supported.

                                                IPv4

                                                +

                                                IPv4

                                                Action

                                                +

                                                Action

                                                The action in the firewall. This parameter is mandatory. You can select a value from the drop-down list. Currently, the value can be Allow or Deny.

                                                +

                                                Specifies the firewall policy. This parameter is mandatory. You can select a value from the drop-down list. Currently, the value can be Allow or Deny.

                                                Allow

                                                +

                                                Allow

                                                Protocol

                                                +

                                                Protocol

                                                The protocol supported by the firewall. This parameter is mandatory. You can select a protocol from the drop-down list.

                                                -

                                                You can select TCP, UDP, ICMP, or All.

                                                +

                                                Specifies the protocol supported by the firewall. This parameter is mandatory. You can select a value from the drop-down list.

                                                +

                                                You can select TCP, UDP, ICMP, or All.

                                                TCP

                                                +

                                                TCP

                                                Source

                                                +

                                                Source

                                                The source from which the traffic is allowed. The source can be an IP address or IP address range.

                                                -
                                                • IP address:
                                                  • Single IP address: 192.168.10.10/32
                                                  • All IP addresses: 0.0.0.0/0
                                                  • IP address range: 192.168.1.0/24
                                                  -
                                                • IP address group: The source is an IP address group. An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                                +

                                                The source from which the traffic is allowed. The source can be an IP address or IP address range.

                                                +
                                                • IP address:
                                                  • Single IP address: 192.168.10.10/32
                                                  • All IP addresses: 0.0.0.0/0
                                                  • IP address range: 192.168.1.0/24
                                                  +

                                                0.0.0.0/0

                                                +

                                                0.0.0.0/0

                                                Source Port Range

                                                +

                                                Source Port Range

                                                The source port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, 1-100.

                                                -

                                                You must specify this parameter if TCP or UDP is selected for Protocol.

                                                +

                                                The source port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, 1-100.

                                                +

                                                You must specify this parameter if TCP or UDP is selected for Protocol.

                                                22, or 22-30

                                                +

                                                22, or 22-30

                                                Destination

                                                +

                                                Destination

                                                The destination to which the traffic is allowed. The destination can be an IP address or IP address range.

                                                -
                                                • IP address:
                                                  • Single IP address: 192.168.10.10/32
                                                  • All IP addresses: 0.0.0.0/0
                                                  • IP address range: 192.168.1.0/24
                                                  -
                                                • IP address group: The source is an IP address group. An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                                +

                                                The destination to which the traffic is allowed. The destination can be an IP address or IP address range.

                                                +
                                                • IP address:
                                                  • Single IP address: 192.168.10.10/32
                                                  • All IP addresses: 0.0.0.0/0
                                                  • IP address range: 192.168.1.0/24
                                                  +

                                                0.0.0.0/0

                                                +

                                                0.0.0.0/0

                                                Destination Port Range

                                                +

                                                Destination Port Range

                                                The destination port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, 1-100.

                                                -

                                                You must specify this parameter if TCP or UDP is selected for Protocol.

                                                +

                                                The destination port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, 1-100.

                                                +

                                                You must specify this parameter if TCP or UDP is selected for Protocol.

                                                22, or 22-30

                                                +

                                                22, or 22-30

                                                Description

                                                +

                                                Description

                                                Supplementary information about the firewall rule. This parameter is optional.

                                                -

                                                The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                                +

                                                Provides supplementary information about the firewall network ACL rule. This parameter is optional.

                                                +

                                                The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                                N/A

                                                +

                                                -

                                                3

                                                Incorrect network configuration
                                                • The security group rules of the ECSs that need to communicate deny inbound traffic from each other.
                                                • The firewall of the ECS NIC blocks traffic.
                                                • The network ACL rules of the subnets connected by the VPC peering connection deny inbound traffic.
                                                • Check the policy-based routing configuration of an ECS with multiple NICs.
                                                +
                                                Incorrect network configuration
                                                • The security group rules of the ECSs that need to communicate deny inbound traffic from each other.
                                                • The firewall of the ECS NIC blocks traffic.
                                                • The firewall rules of the subnets connected by the VPC peering connection deny inbound traffic.
                                                • Check the policy-based routing configuration of an ECS with multiple NICs.

                                                Refer to Incorrect Network Configuration.

                                                @@ -79,10 +79,10 @@
                                                -
                                                Figure 1 Networking diagram (IPv4)
                                                -
                                                Figure 2 Networking diagram (IPv4)
                                                +
                                                Figure 1 Networking diagram (IPv4)
                                                +
                                                Figure 2 Networking diagram (IPv4)

                                                If CIDR blocks of VPCs overlap and some of their subnets overlap, you can create a VPC peering connection between their subnets with non-overlapping CIDR blocks. Figure 3 shows the networking diagram of connecting Subnet-A02 and Subnet-B02. Table 3 describes the routes required.

                                                -
                                                Figure 3 Networking diagram (IPv4)
                                                +
                                                Figure 3 Networking diagram (IPv4)
                                                @@ -116,7 +116,7 @@
                                                Table 3 Routes required for the VPC peering connection between Subnet-A02 and Subnet-B02

                                                Route Table

                                                -

                                                Incorrect Route Configuration for Local and Peer VPCs

                                                Check the routes in the route tables of the local and peer VPCs by referring to Viewing Routes Configured for a VPC Peering Connection. Table 4 lists the items that you need to check.

                                                +

                                                Incorrect Route Configuration for Local and Peer VPCs

                                                Viewing Routes Configured for a VPC Peering Connection. Table 4 lists the items that you need to check.

                                                @@ -133,7 +133,7 @@ -
                                                Table 4 Route check items

                                                Item

                                                Check the destinations of routes added to the route tables of the local and peer VPCs.
                                                • In the route table of the local VPC, check whether the route destination is the CIDR block, subnet CIDR block, or related private IP address of the peer VPC.
                                                • In the route table of the peer VPC, check whether the route destination is the CIDR block, subnet CIDR block, or related private IP address of the local VPC.

                                                If the route destination is incorrect, change it by referring to Modifying Routes Configured for a VPC Peering Connection.

                                                +

                                                If the route destination is incorrect, modify it by referring to Modifying Routes Configured for a VPC Peering Connection.

                                                Destinations of the routes overlap with that configured for Direct Connect or VPN connections.

                                                @@ -146,9 +146,9 @@
                                                -

                                                Incorrect Network Configuration

                                                1. Check whether security group rules of the ECSs that need to communicate allow inbound traffic from each other by referring to Viewing the Security Group of an ECS.
                                                  • If the ECSs are associated with the same security group, you do not need to check their rules.
                                                  • If the ECSs are associated with different security groups, add an inbound rule to allow access from each other by referring to Security Group Configuration Examples.
                                                  +

                                                  Incorrect Network Configuration

                                                  1. Check whether the security group rules of the ECSs that need to communicate with each other are correctly configured. For details, see Viewing the Security Group of an ECS.
                                                    • If the ECSs are associated with the same security group, you do not need to check their rules.
                                                    • If the ECSs are in different security groups, you need to add inbound rules to allow access from the peer security group. For details, see Security Group Configuration Examples.
                                                  2. Check whether the firewall of the ECS NIC blocks traffic.

                                                    If the firewall blocks traffic, configure the firewall to allow inbound traffic.

                                                    -
                                                  3. Check whether network ACL rules of the subnets connected by the VPC peering connection deny inbound traffic.

                                                    If the network ACL rules deny inbound traffic, configure the rules to allow the traffic.

                                                    +
                                                  4. Check whether firewall rules of the subnets connected by the VPC peering connection deny inbound traffic.

                                                    If the firewall rules deny inbound traffic, configure the rules to allow the traffic.

                                                  5. If an ECS has more than one NIC, check whether correct policy-based routing has been configured for the ECS and packets with different source IP addresses match their own routes from each NIC.
                                                    If an ECS has two NICs (eth0 and eth1):
                                                    • IP address of eth0: 192.168.1.10; Subnet gateway: 192.168.1.1
                                                    • IP address of eth1: 192.168.2.10; Subnet gateway: 192.168.2.1
                                                    Command format:
                                                    • ping -l IP address of eth0 Subnet gateway address of eth0
                                                    • ping -l IP address of eth1 Subnet gateway address of eth1
                                                    @@ -159,7 +159,6 @@

                                                  ECS Network Failure

                                                  1. Log in to the ECS.
                                                  2. Check whether the ECS NIC has an IP address assigned.
                                                    • Linux ECS: Use the ifconfig or ip address command to view the IP address of the NIC.
                                                    • Windows ECS: In the search box, enter cmd and press Enter. In the displayed command prompt, run the ipconfig command.
                                                    -

                                                    If the ECS NIC has no IP address assigned, see

                                                  3. Check whether the subnet gateway of the ECS can be pinged.
                                                    1. In the ECS list, click the ECS name.

                                                      The ECS details page is displayed.

                                                    2. On the ECS details page, click the hyperlink of VPC.

                                                      The Virtual Private Cloud page is displayed.

                                                    3. In the VPC list, locate the target VPC and click the number in the Subnets column.

                                                      The Subnets page is displayed.

                                                      diff --git a/docs/vpc/umn/vpc_faq_0074.html b/docs/vpc/umn/vpc_faq_0074.html index e0d040fc3..f47e6fe02 100644 --- a/docs/vpc/umn/vpc_faq_0074.html +++ b/docs/vpc/umn/vpc_faq_0074.html @@ -1,7 +1,13 @@ -

                                                      Does a Security Group Rule or a Firewall Rule Immediately Take Effect for Existing Connections After It Is Modified?

                                                      -
                                                      • Security groups are stateful. Responses to outbound traffic are allowed to go in to the instance regardless of inbound security group rules, and vice versa. Security groups use connection tracking to track traffic to and from instances. If a security group rule is added, deleted, or modified, or an instance in the security group is created or deleted, the connection tracking for all instances in the security group will be automatically cleared. In this case, the inbound or outbound traffic of the instance will be considered to be new connections, which need to match the inbound or outbound security group rules to ensure that the rules take effect immediately and ensure the security of incoming traffic.
                                                      • A modified firewall rule will not immediately take effect for its existing connections. It takes about 120 seconds for the new rule to take effect, and traffic will be interrupted during this period. To ensure that the traffic is immediately interrupted after the rule is changed, it is recommended that you configure security group rules.
                                                      +

                                                      Does a Modified Security Group Rule or a Firewall Rule Take Effect Immediately for Existing Connections?

                                                      +
                                                      • Security groups use connection tracking to track traffic to and from instances. If an inbound rule is modified, the modified rule immediately takes effect for the existing traffic. Changes to outbound security group rules do not affect existing persistent connections and take effect only for new connections.

                                                        If you add, modify, or delete a security group rule, or add or remove an instance to or from a security group, the inbound connections of all instances in the security group will be automatically cleared.

                                                        +
                                                        • The existing inbound persistent connections will be disconnected. All the new connections will match the new rules.
                                                        • The existing outbound persistent connections will not be disconnected, and the original rule will still be applied. All the new connections will match the new rules.
                                                        +
                                                      • 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.

                                                        +
                                                      +

                                                      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.

                                                      +
                                                      • 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.
                                                      +
                                                      diff --git a/docs/vpc/umn/vpc_faq_0075.html b/docs/vpc/umn/vpc_faq_0075.html index 5a3b44b31..157fa5f4f 100644 --- a/docs/vpc/umn/vpc_faq_0075.html +++ b/docs/vpc/umn/vpc_faq_0075.html @@ -5,77 +5,77 @@

                                                      Deleting Subnets

                                                      You can refer to Table 1 to delete subnets.

                                                      -
                                                      Table 1 Deleting subnets

                                                      Prompts

                                                      +
                                                      - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -151,7 +151,7 @@ - diff --git a/docs/vpc/umn/vpc_faq_0076.html b/docs/vpc/umn/vpc_faq_0076.html index d4010d8f6..da6f6123d 100644 --- a/docs/vpc/umn/vpc_faq_0076.html +++ b/docs/vpc/umn/vpc_faq_0076.html @@ -4,7 +4,7 @@

                                                      Users with IPv6 clients can call APIs to assign IPv6 EIPs and bind the EIPs to ECSs. Then, the users can use the EIP to access the ECSs in the VPC over the Internet.

                                                      For details, see Floating IP Address (IPv6) > Creating a Floating IP Address in the Virtual Private Cloud API Reference. The NAT64 gateway in the data center will convert the IPv6 EIP to the IPv4 address. (The last 32 bits of the obtained IPv6 EIP is the IPv4 EIP.)

                                                      After users who use IPv6 clients bind an IPv6 EIP to an ECS, the data flow is shown in Figure 1.

                                                      -
                                                      Figure 1 IPv6 data flow
                                                      +
                                                      Figure 1 IPv6 data flow

                                                      The IPv6 service has the following restrictions:

                                                      • ECSs use IPv4 addresses and cannot directly access public IPv6 addresses. Therefore, only public IPv6 addresses can access ECSs. That means ECSs cannot use IPv4 EIPs that are converted from IPv6 address to access the Internet. To enable the ECSs to access the Internet, you must bind IPv4 EIPs to them.
                                                      • Data packets from an IPv6 network on the Internet are converted to IPv4 packets on the NAT64 gateway. Both the source IP address and port number will be converted. (The source IP address is invisible.)
                                                      • The IPv6 client can access only the EIP and the ELB service.
                                                      • Only one EIP (IPv6 or IPv4) can be bound to each NIC.
                                                      • You can only make API calls to use an EIP to obtain the IPv6 address. The management console displays only IPv4 addresses.
                                                      • The security group function does not apply to IPv6 clients.
                                                      • Resources in internal networks on the cloud can access IPv4 addresses converted by NAT64 gateway.
                                                      • The public cloud does not provide IP spoofing protection for IPv6 traffic from the Internet.
                                                      • Currently, the Anti-DDoS service does not protect IPv6 addresses.
                                                      diff --git a/docs/vpc/umn/vpc_faq_0077.html b/docs/vpc/umn/vpc_faq_0077.html index 6fd633317..214252491 100644 --- a/docs/vpc/umn/vpc_faq_0077.html +++ b/docs/vpc/umn/vpc_faq_0077.html @@ -1,7 +1,7 @@ -

                                                      Which Security Group Rule Has Priority When Multiple Security Group Rules Conflict?

                                                      -

                                                      Security group rules use the whitelist mechanism. If multiple security group rules conflict, the rules are aggregated to take effect.

                                                      +

                                                      Which Security Group Rule Has a High Priority When Multiple Security Group Rules Conflict?

                                                      +

                                                      Security group rules use the whitelist mechanism. If multiple security group rules conflict, the rules are aggregated to take effect.

                                                      diff --git a/docs/vpc/umn/vpc_faq_0103.html b/docs/vpc/umn/vpc_faq_0103.html index 4c681f5e8..c613696db 100644 --- a/docs/vpc/umn/vpc_faq_0103.html +++ b/docs/vpc/umn/vpc_faq_0103.html @@ -2,17 +2,58 @@

                                                      Change History

                                                      -
                                                      Table 1 Deleting subnets

                                                      Prompts

                                                      Cause

                                                      +

                                                      Cause

                                                      Solution

                                                      +

                                                      Solution

                                                      You do not have permission to perform this operation.

                                                      +

                                                      You do not have permission to perform this operation.

                                                      Your account does not have permissions to delete subnets.

                                                      +

                                                      Your account does not have permissions to delete subnets.

                                                      Contact the account administrator to grant permissions to your account and then delete the subnet.

                                                      +

                                                      Contact the account administrator to grant permissions to your account and then delete the subnet.

                                                      Delete custom routes from the associated route table of the subnet and then delete the subnet.

                                                      +

                                                      Delete custom routes from the associated route table of the subnet and then delete the subnet.

                                                      The route table has custom routes with the following as the next hop type:
                                                      • Server
                                                      • Extension NIC
                                                      • Virtual IP address
                                                      • NAT gateway
                                                      +
                                                      The route table has custom routes with the following as the next hop type:
                                                      • Server
                                                      • Extension NIC
                                                      • Virtual IP address
                                                      • NAT gateway
                                                      Delete the custom routes from the route table and then delete the subnet.
                                                      1. Viewing the Route Table Associated with a Subnet
                                                      2. Deleting a Route
                                                      +
                                                      Delete the custom routes from the route table and then delete the subnet.
                                                      1. Viewing the Route Table Associated with a Subnet
                                                      2. Deleting a Route

                                                      Release any virtual IP addresses configured in the subnet and then delete the subnet.

                                                      +

                                                      Release any virtual IP addresses configured in the subnet and then delete the subnet.

                                                      The subnet has virtual IP addresses configured.

                                                      +

                                                      The subnet has virtual IP addresses configured.

                                                      Release the virtual IP addresses from the subnet and then delete the subnet.

                                                      +

                                                      Release the virtual IP addresses from the subnet and then delete the subnet.

                                                      Releasing a Virtual IP Address

                                                      Release any private IP addresses configured in the subnet and then delete the subnet.

                                                      +

                                                      Release any private IP addresses configured in the subnet and then delete the subnet.

                                                      The subnet has virtual IP addresses that are not used by any instance.

                                                      +

                                                      The subnet has virtual IP addresses that are not used by any instance.

                                                      On the IP Addresses tab, release these private IP addresses that are not required and then delete the subnet.

                                                      +

                                                      On the IP Addresses tab, release these private IP addresses that are not required and then delete the subnet.

                                                      1. Viewing IP Addresses in a Subnet
                                                      2. In the private IP address list, locate the IP address that is not being used and click Release in the Operation column.
                                                        NOTICE:

                                                        If you want to release an in-use private IP address, you need to delete the resource that uses the IP address first.

                                                      Delete the resource (ECS or load balancer) that is using the subnet and then delete the subnet.

                                                      +

                                                      Delete the resource (ECS or load balancer) that is using the subnet and then delete the subnet.

                                                      The subnet is being used by an ECS or a load balancer.

                                                      +

                                                      The subnet is being used by an ECS or a load balancer.

                                                      Delete the ECS or load balancer and then delete the subnet.

                                                      +

                                                      Delete the ECS or load balancer and then delete the subnet.

                                                      Viewing and Deleting Resources in a Subnet

                                                      Delete the load balancer that is using the subnet and then delete the subnet.

                                                      +

                                                      Delete the load balancer that is using the subnet and then delete the subnet.

                                                      The subnet is being used by a load balancer.

                                                      +

                                                      The subnet is being used by a load balancer.

                                                      Delete the load balancer and then delete the subnet.

                                                      +

                                                      Delete the load balancer and then delete the subnet.

                                                      Viewing and Deleting Resources in a Subnet

                                                      Delete the NAT gateway that is using the subnet and then delete the subnet.

                                                      +

                                                      Delete the NAT gateway that is using the subnet and then delete the subnet.

                                                      The subnet is being used by a NAT gateway.

                                                      +

                                                      The subnet is being used by a NAT gateway.

                                                      Delete the NAT gateway and then delete the subnet.

                                                      +

                                                      Delete the NAT gateway and then delete the subnet.

                                                      Viewing and Deleting Resources in a Subnet

                                                      Delete the resource that is using the subnet and then delete the subnet.

                                                      +

                                                      Delete the resource that is using the subnet and then delete the subnet.

                                                      The subnet is being used by cloud resources.

                                                      +

                                                      The subnet is being used by cloud resources.

                                                      On the IP Addresses tab, view the usage of the IP address, find the resource that is using the IP address, delete the resource, and delete the subnet.

                                                      +

                                                      On the IP Addresses tab, view the usage of the IP address, find the resource that is using the IP address, delete the resource, and delete the subnet.

                                                      1. Viewing IP Addresses in a Subnet
                                                      2. Locate resource based on the usage of the IP address.
                                                      3. Delete the resource and then delete the subnet.

                                                      In the current region, this is the last VPC and there are EIPs.

                                                      Release all EIPs and then delete the VPC.

                                                      +

                                                      Release all EIPs in this region and then delete this last VPC.

                                                      Unbinding an EIP from an ECS and Releasing the EIP

                                                      Released On

                                                      +
                                                      - + + + + + + + + + + + + + + + + + + + + +

                                                      Released On

                                                      Description

                                                      2023-12-19

                                                      +

                                                      2024-04-16

                                                      +
                                                      This release incorporates the following changes: +
                                                      +

                                                      2024-03-27

                                                      +
                                                      This release incorporates the following changes: +
                                                      +

                                                      2024-02-29

                                                      +
                                                      This release incorporates the following changes: +
                                                      +

                                                      2024-02-18

                                                      +

                                                      This release incorporates the following changes:

                                                      +

                                                      Added What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs?

                                                      +

                                                      2024-02-02

                                                      +

                                                      This release incorporates the following changes:

                                                      +

                                                      Modified figures in Creating a Custom Route Table and Adding a Custom Route.

                                                      +

                                                      2024-01-16

                                                      +

                                                      This release incorporates the following changes:

                                                      +

                                                      Modified the figure for creating a subnet in Creating a Subnet for the VPC, Step 2: Create a Subnet for the VPC, and Step 2: Create a Subnet for the VPC.

                                                      +

                                                      2024-01-02

                                                      +

                                                      This release incorporates the following changes:

                                                      +

                                                      Modified the parameter descriptions in sections Adding a Security Group Rule and Adding a Firewall Rule.

                                                      +

                                                      2023-12-19

                                                      This release incorporates the following changes:

                                                      -

                                                      Added screenshots in How Do I Configure a Security Group for Multi-Channel Protocols?.

                                                      -

                                                      Modified the table in Why Can't I Delete My VPCs and Subnets?.

                                                      +

                                                      2023-12-18

                                                      @@ -106,7 +147,7 @@

                                                      This release incorporates the following changes:

                                                      Updated the following content:

                                                      -

                                                      Modified links in What Is Virtual Private Cloud? and Can I Bind an EIP to Multiple ECSs?.

                                                      +

                                                      Modified links in What Is Virtual Private Cloud? and Can I Bind an EIP to Multiple ECSs?

                                                      2023-01-10

                                                      @@ -180,7 +221,7 @@

                                                      2021-03-16

                                                      Added the following FAQ:

                                                      - +

                                                      2020-12-16

                                                      @@ -200,7 +241,7 @@

                                                      Added the following content:

                                                      Added basic information to Security Groups and Security Group Rules and Firewall Overview.

                                                      Modified the following content:

                                                      - +

                                                      2020-02-25

                                                      diff --git a/docs/vpc/umn/vpc_faq_0106.html b/docs/vpc/umn/vpc_faq_0106.html index f178b409c..a5d04a854 100644 --- a/docs/vpc/umn/vpc_faq_0106.html +++ b/docs/vpc/umn/vpc_faq_0106.html @@ -1,7 +1,7 @@ -

                                                      Glossary

                                                      -

                                                      For details about the terms involved in this document, see Glossary.

                                                      +

                                                      Glossary

                                                      +

                                                      For details about the glossaries in this document, see Glossary.

                                                      diff --git a/docs/vpc/umn/vpc_peering_0001.html b/docs/vpc/umn/vpc_peering_0001.html index ab69dff25..b68cfc14c 100644 --- a/docs/vpc/umn/vpc_peering_0001.html +++ b/docs/vpc/umn/vpc_peering_0001.html @@ -4,7 +4,7 @@

                                                      Scenarios

                                                      This section describes how to view basic information about a VPC peering connection, including the connection name, status, and information about the local and peer VPCs.

                                                      If a VPC peering connection is created between two VPCs in different accounts, both the local and peer accounts can view information about the VPC peering connection.

                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      1. Click in the upper left corner and select the desired region and project.
                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                        The Virtual Private Cloud page is displayed.

                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        1. Click in the upper left corner and select the desired region and project.
                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                          The Virtual Private Cloud page is displayed.

                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                          The VPC peering connection list is displayed.

                                                        4. In the VPC peering connection list, click the name of the target VPC peering connection.

                                                          On the displayed page, view details about the VPC peering connection.

                                                        diff --git a/docs/vpc/umn/vpc_peering_0002.html b/docs/vpc/umn/vpc_peering_0002.html index 16c125d67..8ee1098a3 100644 --- a/docs/vpc/umn/vpc_peering_0002.html +++ b/docs/vpc/umn/vpc_peering_0002.html @@ -4,7 +4,7 @@

                                                        Scenarios

                                                        This section describes how to modify the name of a VPC peering connection.

                                                        Either owner of a VPC in a peering connection can modify the VPC peering connection in any state.

                                                        -

                                                        Procedure

                                                        1. Log in to the management console.
                                                        1. Click in the upper left corner and select the desired region and project.
                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                          The Virtual Private Cloud page is displayed.

                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          1. Click in the upper left corner and select the desired region and project.
                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                            The Virtual Private Cloud page is displayed.

                                                          3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                            The VPC peering connection list is displayed.

                                                          4. In the VPC peering connection list, locate the row that contains the target VPC peering connection and click Modify in the Operation column.

                                                            The Modify VPC Peering Connection dialog box is displayed.

                                                          5. Modify the VPC peering connection information and click OK.
                                                          diff --git a/docs/vpc/umn/vpc_peering_0003.html b/docs/vpc/umn/vpc_peering_0003.html index aedf2acec..7a4690075 100644 --- a/docs/vpc/umn/vpc_peering_0003.html +++ b/docs/vpc/umn/vpc_peering_0003.html @@ -6,7 +6,7 @@

                                                          Notes and Constraints

                                                          The owner of either VPC in a peering connection can delete the VPC peering connection at any time. Deleting a VPC peering connection will also delete all information about this connection, including the routes in the local and peer VPC route tables added for the connection.

                                                          -

                                                          Procedure

                                                          1. Log in to the management console.
                                                          1. Click in the upper left corner and select the desired region and project.
                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                            The Virtual Private Cloud page is displayed.

                                                            +

                                                            Procedure

                                                            1. Log in to the management console.
                                                            1. Click in the upper left corner and select the desired region and project.
                                                            2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                              The Virtual Private Cloud page is displayed.

                                                            3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                              The VPC peering connection list is displayed.

                                                            4. 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.

                                                            5. Click Yes.
                                                            diff --git a/docs/vpc/umn/vpc_peering_0004.html b/docs/vpc/umn/vpc_peering_0004.html index 55333238c..5a1374183 100644 --- a/docs/vpc/umn/vpc_peering_0004.html +++ b/docs/vpc/umn/vpc_peering_0004.html @@ -5,15 +5,15 @@

                                                            If two VPCs cannot communicate through a VPC peering connection, you can check the routes added for the local and peer VPCs by following the instructions provided in this section.

                                                          -

                                                          Viewing Routes of a VPC Peering Connection Between VPCs in the Same Account

                                                          1. Log in to the management console.
                                                          1. Click in the upper left corner and select the desired region and project.
                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                            The Virtual Private Cloud page is displayed.

                                                            +

                                                            Viewing Routes of a VPC Peering Connection Between VPCs in the Same Account

                                                            1. Log in to the management console.
                                                            1. Click in the upper left corner and select the desired region and project.
                                                            2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                              The Virtual Private Cloud page is displayed.

                                                            3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                              The VPC peering connection list is displayed.

                                                            4. 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.

                                                            5. View the routes added for the VPC peering connection:
                                                              1. Click the Local Routes tab to view the local route added for the VPC peering connection.
                                                              2. Click the Peer Routes tab to view the peer route added for the VPC peering connection.

                                                            Viewing Routes of a VPC Peering Connection Between VPCs in Different Accounts

                                                            Only the account owner of a VPC in a VPC peering connection can view the routes added for the connection.

                                                            -
                                                            1. Log in to the management console using the account of the local VPC and view the route of the local VPC:
                                                              1. Click in the upper left corner and select the desired region and project.
                                                              2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                The Virtual Private Cloud page is displayed.

                                                                -
                                                              3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                                The VPC peering connection list is displayed.

                                                                +
                                                                1. Log in to the management console using the account of the local VPC and view the route of the local VPC:
                                                                  1. Click in the upper left corner and select the desired region and project.
                                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                    The Virtual Private Cloud page is displayed.

                                                                    +
                                                                  3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                                    The VPC peering connection list is displayed.

                                                                  4. 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.

                                                                  5. Click the Local Routes tab to view the local route added for the VPC peering connection.
                                                                2. Log in to the management console using the account of the peer VPC and view the route of the peer VPC by referring to 1.
                                                                diff --git a/docs/vpc/umn/vpc_peering_0005.html b/docs/vpc/umn/vpc_peering_0005.html index f86189aa7..1205e22b8 100644 --- a/docs/vpc/umn/vpc_peering_0005.html +++ b/docs/vpc/umn/vpc_peering_0005.html @@ -4,8 +4,7 @@

                                                                Scenarios

                                                                If you create a VPC peering connection between two VPCs in different accounts, you can refer to this section to obtain the project ID of the region that the peer VPC resides.

                                                                Procedure

                                                                1. Log in to the management console.

                                                                  The owner of the peer account logs in to the management console.

                                                                  -
                                                                1. In the upper right corner of the page, select My Credentials from the username drop-down list.

                                                                  -
                                                                2. In the project list, obtain the project ID.
                                                                +
                                                              1. In the upper right corner of the page, select My Credentials from the username drop-down list.
                                                              2. In the project list, obtain the project ID.
                                                          diff --git a/docs/vpc/umn/vpc_peering_0006.html b/docs/vpc/umn/vpc_peering_0006.html index fcee19d72..07dd6fb48 100644 --- a/docs/vpc/umn/vpc_peering_0006.html +++ b/docs/vpc/umn/vpc_peering_0006.html @@ -4,7 +4,7 @@

                                                          Scenarios

                                                          This section describes how to delete routes from the route tables of the local and peer VPCs connected by a VPC peering connection.
                                                          -

                                                          Deleting Routes of a VPC Peering Connection Between VPCs in the Same Account

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select the desired region and project.
                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                            The Virtual Private Cloud page is displayed.

                                                            +

                                                            Deleting Routes of a VPC Peering Connection Between VPCs in the Same Account

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select the desired region and project.
                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                              The Virtual Private Cloud page is displayed.

                                                            4. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                              The VPC peering connection list is displayed.

                                                            5. 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.

                                                            6. Delete the route added to the route table of the local VPC:
                                                              1. Click the Local Routes tab and then click the Route Tables hyperlink.

                                                                The Summary tab of the default route table for the local VPC is displayed.

                                                                @@ -16,10 +16,10 @@

                                                            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.

                                                            -
                                                            1. Log in to the management console using the account of the local VPC and delete the route of the local VPC:
                                                              1. Click in the upper left corner and select the desired region and project.
                                                              2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                The Virtual Private Cloud page is displayed.

                                                                -
                                                              3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                                The VPC peering connection list is displayed.

                                                                +
                                                                1. Log in to the management console using the account of the local VPC and delete the route of the local VPC:
                                                                  1. Click in the upper left corner and select the desired region and project.
                                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                    The Virtual Private Cloud page is displayed.

                                                                    +
                                                                  3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                                    The VPC peering connection list is displayed.

                                                                  4. 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.

                                                                    -
                                                                  5. Delete the route added to the route table of the local VPC:
                                                                    1. Click the Local Routes tab and then click the Route Tables hyperlink.

                                                                      The Summary tab of the default route table for the local VPC is displayed.

                                                                      +
                                                                    2. Delete the route added to the route table of the local VPC:
                                                                      1. Click the Local Routes tab and then click the Route Tables hyperlink.

                                                                        The Summary tab of the default route table for the local VPC is displayed.

                                                                      2. Locate the row that contains the route to be deleted and click Delete in the Operation column.

                                                                        A confirmation dialog box is displayed.

                                                                      3. Click Yes.
                                                                    diff --git a/docs/vpc/umn/vpc_peering_0007.html b/docs/vpc/umn/vpc_peering_0007.html index 360a0e777..b382ebdec 100644 --- a/docs/vpc/umn/vpc_peering_0007.html +++ b/docs/vpc/umn/vpc_peering_0007.html @@ -5,7 +5,7 @@

                                                          You can follow the instructions provided in this section to modify routes based on your requirements.

                                                          -

                                                          Modifying Routes of a VPC Peering Connection Between VPCs in the Same Account

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select the desired region and project.
                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                            The Virtual Private Cloud page is displayed.

                                                            +

                                                            Modifying Routes of a VPC Peering Connection Between VPCs in the Same Account

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select the desired region and project.
                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                              The Virtual Private Cloud page is displayed.

                                                            4. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                              The VPC peering connection list is displayed.

                                                            5. 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.

                                                            6. Modify the route added to the route table of the local VPC:
                                                              1. Click the Local Routes tab and then click the Route Tables hyperlink.

                                                                The Summary tab of the default route table for the local VPC is displayed.

                                                                @@ -17,8 +17,8 @@

                                                            Modifying Routes of a VPC Peering Connection Between VPCs in Different Accounts

                                                            Only the account owner of a VPC can modify the routes added for the connection.

                                                            -
                                                            1. Log in to the management console using the account of the local VPC and modify the route of the local VPC:
                                                              1. Click in the upper left corner and select the desired region and project.
                                                              2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                The Virtual Private Cloud page is displayed.

                                                                -
                                                              3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                                The VPC peering connection list is displayed.

                                                                +
                                                                1. Log in to the management console using the account of the local VPC and modify the route of the local VPC:
                                                                  1. Click in the upper left corner and select the desired region and project.
                                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                    The Virtual Private Cloud page is displayed.

                                                                    +
                                                                  3. In the navigation pane on the left, choose Virtual Private Cloud > VPC Peering Connections.

                                                                    The VPC peering connection list is displayed.

                                                                  4. 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.

                                                                  5. Modify the route added to the route table of the local VPC:
                                                                    1. Click the Local Routes tab and then click the Route Tables hyperlink.

                                                                      The Summary tab of the default route table for the local VPC is displayed.

                                                                    2. Locate the row that contains the route to be modified and click Modify in the Operation column.

                                                                      The Modify Route dialog box is displayed.

                                                                      diff --git a/docs/vpc/umn/vpc_pro_0000.html b/docs/vpc/umn/vpc_pro_0000.html index b7c32f74c..5a4fa3a2b 100644 --- a/docs/vpc/umn/vpc_pro_0000.html +++ b/docs/vpc/umn/vpc_pro_0000.html @@ -18,6 +18,8 @@
                                                                    3. Basic Concepts
                                                                      4. +
                                                                    4. Region and AZ
                                                                      +
                                                                    5. Document Usage Instructions
                                                                      6. diff --git a/docs/vpc/umn/vpc_qs_0004.html b/docs/vpc/umn/vpc_qs_0004.html index f607cf682..2539147d4 100644 --- a/docs/vpc/umn/vpc_qs_0004.html +++ b/docs/vpc/umn/vpc_qs_0004.html @@ -2,7 +2,7 @@

                                                                      Overview

                                                                      If your ECSs do not require Internet access or need to access the Internet using IP addresses on the default network (100.64.0.0/11) with limited bandwidth (for example, the ECSs functioning as the database nodes or server nodes for deploying a website), you can follow the procedure shown in Figure 1 to configure a VPC for the ECSs.

                                                                      -
                                                                      Figure 1 Configuring the network
                                                                      +
                                                                      Figure 1 Configuring the network

                                                                      Table 1 describes the different tasks in the procedure for configuring the network.

                                                                      Table 1 Configuration process description

                                                                      Task

                                                                      diff --git a/docs/vpc/umn/vpc_qs_0005.html b/docs/vpc/umn/vpc_qs_0005.html index c930051bd..e6d1df352 100644 --- a/docs/vpc/umn/vpc_qs_0005.html +++ b/docs/vpc/umn/vpc_qs_0005.html @@ -1,19 +1,19 @@

                                                                      Step 1: Create a VPC

                                                                      -

                                                                      Scenarios

                                                                      A VPC provides an isolated virtual network for ECSs. You can configure and manage the network as required.

                                                                      +

                                                                      Scenarios

                                                                      A VPC provides an isolated virtual network for ECSs. You can configure and manage the network as required.

                                                                      You can create a VPC by following the procedure provided in this section. Then, create subnets, security groups, and assign EIPs by following the procedure provided in subsequent sections based on your actual network requirements.

                                                                      -

                                                                      Procedure

                                                                      1. Log in to the management console.
                                                                      2. Click in the upper left corner and select the desired region and project.
                                                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                        The Virtual Private Cloud page is displayed.

                                                                        +

                                                                        Procedure

                                                                        1. Log in to the management console.
                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                          The Virtual Private Cloud page is displayed.

                                                                        4. Click Create VPC.
                                                                        5. 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.

                                                                          - - - @@ -102,7 +102,7 @@ - - @@ -227,7 +227,6 @@
                                                                        6. Click Create Now.
                                                                          7. -

                                                                          diff --git a/docs/vpc/umn/vpc_qs_0006.html b/docs/vpc/umn/vpc_qs_0006.html index 8dd7cc542..5927d12d7 100644 --- a/docs/vpc/umn/vpc_qs_0006.html +++ b/docs/vpc/umn/vpc_qs_0006.html @@ -1,126 +1,126 @@

                                                                          Step 2: Create a Subnet for the VPC

                                                                          -

                                                                          Scenarios

                                                                          A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.

                                                                          +

                                                                          Scenarios

                                                                          A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.

                                                                          A subnet is configured with DHCP by default. When an ECS in this subnet starts, the ECS automatically obtains an IP address using DHCP.

                                                                          -

                                                                          Procedure

                                                                          1. Log in to the management console.
                                                                          1. Click in the upper left corner and select the desired region and project.
                                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                            The Virtual Private Cloud page is displayed.

                                                                            +

                                                                            Procedure

                                                                            1. Log in to the management console.
                                                                            1. Click in the upper left corner and select the desired region and project.
                                                                            2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                              The Virtual Private Cloud page is displayed.

                                                                            3. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
                                                                            4. Click Create Subnet.

                                                                              The Create Subnet page is displayed.

                                                                              -
                                                                            5. Set the parameters as prompted.
                                                                              Figure 1 Create Subnet
                                                                              -

                                                                              +
                                                                            6. Set the parameters as prompted.
                                                                              Figure 1 Create Subnet
                                                                              -
                                                                          Table 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.

                                                                          -

                                                                          @@ -112,7 +112,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
                                                                          Table 1 Parameter descriptions

                                                                          Parameter

                                                                          +
                                                                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                                                          Table 1 Parameter descriptions

                                                                          Parameter

                                                                          Description

                                                                          +

                                                                          Description

                                                                          Example Value

                                                                          +

                                                                          Example Value

                                                                          VPC

                                                                          +

                                                                          VPC

                                                                          The VPC for which you want to create a subnet.

                                                                          +

                                                                          The VPC for which you want to create a subnet.

                                                                          -

                                                                          +

                                                                          -

                                                                          Name

                                                                          +

                                                                          Name

                                                                          The 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.

                                                                          Subnet

                                                                          +

                                                                          Subnet

                                                                          IPv4 CIDR Block

                                                                          +

                                                                          IPv4 CIDR Block

                                                                          The CIDR block for the subnet. This value must be within the VPC CIDR block.

                                                                          +

                                                                          The CIDR block for the subnet. This value must be within the VPC CIDR block.

                                                                          +

                                                                          If the VPC has a secondary CIDR block, you can select the primary or the secondary CIDR block that the subnet will belong to based on service requirements.

                                                                          192.168.0.0/24

                                                                          +

                                                                          192.168.0.0/24

                                                                          IPv6 CIDR Block

                                                                          +

                                                                          IPv6 CIDR Block

                                                                          Specifies whether to set IPv6 CIDR Block to Enable.

                                                                          +

                                                                          Specifies whether to set IPv6 CIDR Block to Enable.

                                                                          If you select this option, 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.

                                                                          -

                                                                          +

                                                                          -

                                                                          Associated Route Table

                                                                          +

                                                                          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

                                                                          +

                                                                          Default

                                                                          Advanced Settings/Gateway

                                                                          +

                                                                          Advanced Settings/Gateway

                                                                          The gateway address of the subnet.

                                                                          +

                                                                          The gateway address of the subnet.

                                                                          192.168.0.1

                                                                          +

                                                                          192.168.0.1

                                                                          Advanced Settings/DNS Server Address

                                                                          +

                                                                          Advanced Settings/DNS Server Address

                                                                          By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

                                                                          +

                                                                          By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

                                                                          100.125.x.x

                                                                          +

                                                                          100.125.x.x

                                                                          Advanced Settings/NTP Server Address

                                                                          +

                                                                          Advanced Settings/NTP Server Address

                                                                          The IP address of the NTP server. This parameter is optional.

                                                                          +

                                                                          The IP address of the NTP server. This parameter is optional.

                                                                          You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added.

                                                                          A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).

                                                                          192.168.2.1

                                                                          +

                                                                          192.168.2.1

                                                                          Advanced Settings/Tag

                                                                          +

                                                                          Advanced Settings/Tag

                                                                          The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

                                                                          -

                                                                          The tag key and value must meet the requirements listed in Table 2.

                                                                          +

                                                                          The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

                                                                          +

                                                                          The tag key and value must meet the requirements listed in Table 2.

                                                                          • Key: subnet_key1
                                                                          • Value: subnet-01
                                                                          +
                                                                          • Key: subnet_key1
                                                                          • Value: subnet-01

                                                                          Advanced Settings/Description

                                                                          +

                                                                          Advanced Settings/Description

                                                                          Supplementary information about the subnet. This parameter is optional.

                                                                          +

                                                                          Supplementary information about the subnet. This parameter is optional.

                                                                          The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                                                          -

                                                                          +

                                                                          -
                                                                          -
                                                                          Table 2 Subnet tag key and value requirements

                                                                          Parameter

                                                                          +
                                                                          - - - - - - - - @@ -128,7 +128,7 @@
                                                                        7. Click OK.
                                                                          8. -

                                                                          Precautions

                                                                          When a subnet is created, there are five reserved IP addresses, which cannot be used. For example, in a subnet with CIDR block 192.168.0.0/24, the following IP addresses are reserved:

                                                                          +

                                                                          Precautions

                                                                          When a subnet is created, there are five reserved IP addresses, which cannot be used. For example, in a subnet with CIDR block 192.168.0.0/24, the following IP addresses are reserved:

                                                                          • 192.168.0.0: Network ID. This address is the beginning of the private IP address range and will not be assigned to any instance.
                                                                          • 192.168.0.1: Gateway address.
                                                                          • 192.168.0.253: Reserved for the system interface. This IP address is used by the VPC for external communication.
                                                                          • 192.168.0.254: DHCP service address.
                                                                          • 192.168.0.255: Network broadcast address.

                                                                          If you configured the default settings under Advanced Settings during subnet creation, the reserved IP addresses may be different from the default ones, but there will still be five of them. The specific addresses depend on your subnet settings.

                                                                          diff --git a/docs/vpc/umn/vpc_qs_0007.html b/docs/vpc/umn/vpc_qs_0007.html index a5d2916b3..e4124c34d 100644 --- a/docs/vpc/umn/vpc_qs_0007.html +++ b/docs/vpc/umn/vpc_qs_0007.html @@ -1,14 +1,14 @@

                                                                          Step 3: Create a Security Group

                                                                          -

                                                                          Scenarios

                                                                          A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                          +

                                                                          Scenarios

                                                                          A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                          If your instances have different Internet access requirements, you can allocate them to different security groups when creating them.

                                                                          Each ECS must be associated with at least one security group. If you do not have a security group when creating an ECS, the system provides a default security group.

                                                                          -

                                                                          Procedure

                                                                          1. Log in to the management console.
                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                            The Virtual Private Cloud page is displayed.

                                                                            +

                                                                            Procedure

                                                                            1. Log in to the management console.
                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                              The Virtual Private Cloud page is displayed.

                                                                            4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                                              The security group list is displayed.

                                                                            5. In the upper right corner, click Create Security Group.

                                                                              The Create Security Group page is displayed.

                                                                              -
                                                                            6. Configure the parameters as prompted.
                                                                              Figure 1 Create Security Group
                                                                              +
                                                                            7. Configure the parameters as prompted.
                                                                              Figure 1 Create Security Group
                                                                          Table 2 Subnet tag key and value requirements

                                                                          Parameter

                                                                          Requirements

                                                                          +

                                                                          Requirements

                                                                          Example Value

                                                                          +

                                                                          Example Value

                                                                          Key

                                                                          +

                                                                          Key

                                                                          • Cannot be left blank.
                                                                          • Must be unique for each subnet.
                                                                          • Can contain a maximum of 36 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)
                                                                            +
                                                                          • Cannot be left blank.
                                                                          • Must be unique for each subnet.
                                                                          • Can contain a maximum of 36 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)

                                                                          subnet_key1

                                                                          +

                                                                          subnet_key1

                                                                          Value

                                                                          +

                                                                          Value

                                                                          • Can contain a maximum of 43 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)
                                                                            +
                                                                          • Can contain a maximum of 43 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)

                                                                          subnet-01

                                                                          +

                                                                          subnet-01
                                                                          @@ -42,7 +42,7 @@ diff --git a/docs/vpc/umn/vpc_qs_0008.html b/docs/vpc/umn/vpc_qs_0008.html index 200165cfa..5c4b7b58b 100644 --- a/docs/vpc/umn/vpc_qs_0008.html +++ b/docs/vpc/umn/vpc_qs_0008.html @@ -1,27 +1,27 @@

                                                                          Step 4: Add a Security Group Rule

                                                                          -

                                                                          Scenarios

                                                                          A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                          +

                                                                          Scenarios

                                                                          A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                          Each ECS must be associated with at least one security group. If you do not have a security group when creating an ECS, the system provides a default security group.

                                                                          -
                                                                          Like whitelists, security group rules work as follows:
                                                                          • Inbound rules control incoming traffic to instances in the security group.

                                                                            If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                                                                            -

                                                                            By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                                                                            -
                                                                          • Outbound rules control outgoing traffic from instances in the security group.

                                                                            If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                                                                            -

                                                                            0.0.0.0/0 represents all IPv4 addresses.

                                                                            -

                                                                            ::/0 represents all IPv6 addresses.

                                                                            +
                                                                            Like whitelists, security group rules work as follows:
                                                                            • Inbound rules control incoming traffic to instances in the security group.

                                                                              If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                                                                              +

                                                                              By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                                                                              +
                                                                            • Outbound rules control outgoing traffic from instances in the security group.

                                                                              If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                                                                              +

                                                                              0.0.0.0/0 represents all IPv4 addresses.

                                                                              +

                                                                              ::/0 represents all IPv6 addresses.

                                                                            If the rules of the security group associated with your instance cannot meet your requirements, for example, you need to allow inbound traffic on a specific TCP port, you can add an inbound rule to allow traffic on the TCP port.

                                                                          -

                                                                          Procedure

                                                                          1. Log in to the management console.
                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                            The Virtual Private Cloud page is displayed.

                                                                            +

                                                                            Procedure

                                                                            1. Log in to the management console.
                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                              The Virtual Private Cloud page is displayed.

                                                                            4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                                              The security group list is displayed.

                                                                            5. 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.

                                                                            6. On the Inbound Rules tab, click Add Rule.

                                                                              The Add Inbound Rule dialog box is displayed.

                                                                            7. Configure required parameters.

                                                                              You can click + to add more inbound rules.

                                                                              -
                                                                              Figure 1 Add Inbound Rule
                                                                              +
                                                                              Figure 1 Add Inbound Rule
                                                                              -
                                                                          Table 1 Parameter description

                                                                          Parameter

                                                                          Mandatory

                                                                          A template comes with default security group rules, helping you quickly create security groups. The following templates are provided:

                                                                          -
                                                                          • Custom: This template allows you to create security groups with custom security group rules.
                                                                          • General-purpose web server (default value): The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389.
                                                                          • All ports open: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks.
                                                                          +
                                                                          • Custom: This template allows you to create security groups with custom security group rules.
                                                                          • General-purpose web server (default value): The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389.
                                                                          • All ports open: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks.

                                                                          General-purpose web server
                                                                          Table 1 Inbound rule parameter description

                                                                          Parameter

                                                                          +
                                                                          - @@ -51,7 +51,7 @@ @@ -72,11 +72,11 @@
                                                                        8. Click OK.

                                                                          The inbound rule list is displayed.

                                                                        9. On the Outbound Rules tab, click Add Rule.

                                                                          The Add Outbound Rule dialog box is displayed.

                                                                        10. Configure required parameters.

                                                                          You can click + to add more outbound rules.

                                                                          -
                                                                          Figure 2 Add Outbound Rule
                                                                          +
                                                                          Figure 2 Add Outbound Rule
                                                                          -
                                                                          11. Table 1 Inbound rule parameter description

                                                                          Parameter

                                                                          Description

                                                                          +

                                                                          Description

                                                                          Example Value

                                                                          Source
                                                                          Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example:
                                                                          • IP address:
                                                                            • Single IP address: 192.168.10.10/32
                                                                            • All IP addresses: 0.0.0.0/0
                                                                            • IP address range: 192.168.1.0/24
                                                                            -
                                                                          • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                                                                          • IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                                                          +
                                                                        11. Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.

                                                                          12. If the source is a security group, this rule will apply to all instances associated with the selected security group.

                                                                          Table 2 Outbound rule parameter description

                                                                          Parameter

                                                                          +
                                                                          - @@ -107,8 +107,8 @@ diff --git a/docs/vpc/umn/vpc_qs_0009.html b/docs/vpc/umn/vpc_qs_0009.html index 34a218905..508c9d0b1 100644 --- a/docs/vpc/umn/vpc_qs_0009.html +++ b/docs/vpc/umn/vpc_qs_0009.html @@ -4,16 +4,16 @@

                                                                          Scenarios

                                                                          A VPC provides an isolated virtual network for ECSs. You can configure and manage the network as required.

                                                                          You can create a VPC by following the procedure provided in this section. Then, create subnets, security groups, and assign EIPs by following the procedure provided in subsequent sections based on your actual network requirements.

                                                                          -

                                                                          Procedure

                                                                          1. Log in to the management console.
                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                            The Virtual Private Cloud page is displayed.

                                                                            +

                                                                            Procedure

                                                                            1. Log in to the management console.
                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                              The Virtual Private Cloud page is displayed.

                                                                            4. Click Create VPC.
                                                                            5. 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.

                                                                          Table 2 Outbound rule parameter description

                                                                          Parameter

                                                                          Description

                                                                          +

                                                                          Description

                                                                          Example Value

                                                                          Destination

                                                                          Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:

                                                                          -
                                                                          • IP address:
                                                                            • Single IP address: 192.168.10.10/32
                                                                            • All IP addresses: 0.0.0.0/0
                                                                            • IP address range: 192.168.1.0/24
                                                                            -
                                                                          • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                                                                          • IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                                                          +
                                                                          • IP address:
                                                                            • Single IP address: 192.168.10.10/32
                                                                            • All IP addresses: 0.0.0.0/0
                                                                            • IP address range: 192.168.1.0/24
                                                                            +
                                                                          • Security group: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. For example, instance A is in security group A and instance B is in security group B. If security group A has an outbound rule with Action set to Allow and Destination set to security group B, access from instance A is allowed to instance B.

                                                                          0.0.0.0/0

                                                                          - - - @@ -102,7 +102,7 @@ - - diff --git a/docs/vpc/umn/vpc_qs_0010.html b/docs/vpc/umn/vpc_qs_0010.html index 104a2ed16..92969b6ad 100644 --- a/docs/vpc/umn/vpc_qs_0010.html +++ b/docs/vpc/umn/vpc_qs_0010.html @@ -4,123 +4,123 @@

                                                                          Scenarios

                                                                          A VPC comes with a default subnet. If the default subnet cannot meet your requirements, you can create one.

                                                                          A subnet is configured with DHCP by default. When an ECS in this subnet starts, the ECS automatically obtains an IP address using DHCP.

                                                                          -

                                                                          Procedure

                                                                          1. Log in to the management console.
                                                                          1. Click in the upper left corner and select the desired region and project.
                                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                            The Virtual Private Cloud page is displayed.

                                                                            +

                                                                            Procedure

                                                                            1. Log in to the management console.
                                                                            1. Click in the upper left corner and select the desired region and project.
                                                                            2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                              The Virtual Private Cloud page is displayed.

                                                                            3. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
                                                                            4. Click Create Subnet.

                                                                              The Create Subnet page is displayed.

                                                                              -
                                                                            5. Set the parameters as prompted.
                                                                              Figure 1 Create Subnet
                                                                              -

                                                                              +
                                                                            6. Set the parameters as prompted.
                                                                              Figure 1 Create Subnet
                                                                              -
                                                                          Table 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.

                                                                          -

                                                                          @@ -112,7 +112,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

                                                                          Table 1 Parameter descriptions

                                                                          Parameter

                                                                          +
                                                                          - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                                                          Table 1 Parameter descriptions

                                                                          Parameter

                                                                          Description

                                                                          +

                                                                          Description

                                                                          Example Value

                                                                          +

                                                                          Example Value

                                                                          VPC

                                                                          +

                                                                          VPC

                                                                          The VPC for which you want to create a subnet.

                                                                          +

                                                                          The VPC for which you want to create a subnet.

                                                                          -

                                                                          +

                                                                          -

                                                                          Name

                                                                          +

                                                                          Name

                                                                          The 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.

                                                                          Subnet

                                                                          +

                                                                          Subnet

                                                                          IPv4 CIDR Block

                                                                          +

                                                                          IPv4 CIDR Block

                                                                          The CIDR block for the subnet. This value must be within the VPC CIDR block.

                                                                          +

                                                                          The CIDR block for the subnet. This value must be within the VPC CIDR block.

                                                                          +

                                                                          If the VPC has a secondary CIDR block, you can select the primary or the secondary CIDR block that the subnet will belong to based on service requirements.

                                                                          192.168.0.0/24

                                                                          +

                                                                          192.168.0.0/24

                                                                          IPv6 CIDR Block

                                                                          +

                                                                          IPv6 CIDR Block

                                                                          Specifies whether to set IPv6 CIDR Block to Enable.

                                                                          +

                                                                          Specifies whether to set IPv6 CIDR Block to Enable.

                                                                          If you select this option, 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.

                                                                          -

                                                                          +

                                                                          -

                                                                          Associated Route Table

                                                                          +

                                                                          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

                                                                          +

                                                                          Default

                                                                          Advanced Settings/Gateway

                                                                          +

                                                                          Advanced Settings/Gateway

                                                                          The gateway address of the subnet.

                                                                          +

                                                                          The gateway address of the subnet.

                                                                          192.168.0.1

                                                                          +

                                                                          192.168.0.1

                                                                          Advanced Settings/DNS Server Address

                                                                          +

                                                                          Advanced Settings/DNS Server Address

                                                                          By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

                                                                          +

                                                                          By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,).

                                                                          100.125.x.x

                                                                          +

                                                                          100.125.x.x

                                                                          Advanced Settings/NTP Server Address

                                                                          +

                                                                          Advanced Settings/NTP Server Address

                                                                          The IP address of the NTP server. This parameter is optional.

                                                                          +

                                                                          The IP address of the NTP server. This parameter is optional.

                                                                          You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added.

                                                                          A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,).

                                                                          192.168.2.1

                                                                          +

                                                                          192.168.2.1

                                                                          Advanced Settings/Tag

                                                                          +

                                                                          Advanced Settings/Tag

                                                                          The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

                                                                          -

                                                                          The tag key and value must meet the requirements listed in Table 2.

                                                                          +

                                                                          The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet.

                                                                          +

                                                                          The tag key and value must meet the requirements listed in Table 2.

                                                                          • Key: subnet_key1
                                                                          • Value: subnet-01
                                                                          +
                                                                          • Key: subnet_key1
                                                                          • Value: subnet-01

                                                                          Advanced Settings/Description

                                                                          +

                                                                          Advanced Settings/Description

                                                                          Supplementary information about the subnet. This parameter is optional.

                                                                          +

                                                                          Supplementary information about the subnet. This parameter is optional.

                                                                          The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).

                                                                          -

                                                                          +

                                                                          -
                                                                          -
                                                                          Table 2 Subnet tag key and value requirements

                                                                          Parameter

                                                                          +
                                                                          - - - - - - - - @@ -128,7 +128,7 @@
                                                                        12. Click OK.
                                                                          13. -

                                                                          Precautions

                                                                          When a subnet is created, there are five reserved IP addresses, which cannot be used. For example, in a subnet with CIDR block 192.168.0.0/24, the following IP addresses are reserved:

                                                                          +

                                                                          Precautions

                                                                          When a subnet is created, there are five reserved IP addresses, which cannot be used. For example, in a subnet with CIDR block 192.168.0.0/24, the following IP addresses are reserved:

                                                                          • 192.168.0.0: Network ID. This address is the beginning of the private IP address range and will not be assigned to any instance.
                                                                          • 192.168.0.1: Gateway address.
                                                                          • 192.168.0.253: Reserved for the system interface. This IP address is used by the VPC for external communication.
                                                                          • 192.168.0.254: DHCP service address.
                                                                          • 192.168.0.255: Network broadcast address.

                                                                          If you configured the default settings under Advanced Settings during subnet creation, the reserved IP addresses may be different from the default ones, but there will still be five of them. The specific addresses depend on your subnet settings.

                                                                          diff --git a/docs/vpc/umn/vpc_qs_0011.html b/docs/vpc/umn/vpc_qs_0011.html index 23d44fc4d..f905af6c3 100644 --- a/docs/vpc/umn/vpc_qs_0011.html +++ b/docs/vpc/umn/vpc_qs_0011.html @@ -1,13 +1,13 @@

                                                                          Step 3: Assign an EIP and Bind It to an ECS

                                                                          -

                                                                          Scenarios

                                                                          You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.

                                                                          +

                                                                          Scenarios

                                                                          You can assign an EIP and bind it to an ECS so that the ECS can access the Internet.

                                                                          Note the following when you use EIPs of the Dedicated Load Balancer (5_gray) type:
                                                                          • In eu-de, EIPs of the Dedicated Load Balancer (5_gray) type cannot be assigned anymore. You can assign EIPs of the BGP (5_bgp) type.
                                                                          • Existing EIPs of the Dedicated Load Balancer (5_gray) type can be bound to dedicated or shared load balancers.
                                                                            • The EIP console cannot be used to bind EIPs to or unbind them from dedicated load balancers.
                                                                            • You can use APIs to bind EIPs to or unbind them from dedicated load balancers. For details, see Binding an EIP and Unbinding an EIP.
                                                                            • EIPs of this type can be bound to or unbound from shared load balancers using the EIP console or APIs.
                                                                            • You are advised to bind BGP EIPs to or unbind them from dedicated load balancers.
                                                                          • 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.
                                                                          -

                                                                          Assigning an EIP

                                                                          1. Log in to the management console.
                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                          3. Click in the upper left corner and choose Network > Elastic IP.
                                                                          4. On the displayed page, click Assign EIP.
                                                                          5. Set the parameters as prompted.
                                                                            Figure 1 Assign EIP
                                                                            +

                                                                            Assigning an EIP

                                                                            1. Log in to the management console.
                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                            3. Click in the upper left corner and choose Network > Elastic IP.
                                                                            4. On the displayed page, click Assign EIP.
                                                                            5. Set the parameters as prompted.
                                                                              Figure 1 Assign EIP
                                                                          Table 2 Subnet tag key and value requirements

                                                                          Parameter

                                                                          Requirements

                                                                          +

                                                                          Requirements

                                                                          Example Value

                                                                          +

                                                                          Example Value

                                                                          Key

                                                                          +

                                                                          Key

                                                                          • Cannot be left blank.
                                                                          • Must be unique for each subnet.
                                                                          • Can contain a maximum of 36 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)
                                                                            +
                                                                          • Cannot be left blank.
                                                                          • Must be unique for each subnet.
                                                                          • Can contain a maximum of 36 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)

                                                                          subnet_key1

                                                                          +

                                                                          subnet_key1

                                                                          Value

                                                                          +

                                                                          Value

                                                                          • Can contain a maximum of 43 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)
                                                                            +
                                                                          • Can contain a maximum of 43 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)

                                                                          subnet-01

                                                                          +

                                                                          subnet-01
                                                                          @@ -26,7 +26,7 @@ - @@ -57,7 +57,7 @@ @@ -88,28 +88,28 @@
                                                                          Table 1 Parameter descriptions

                                                                          Parameter

                                                                          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

                                                                          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.

                                                                          +

                                                                          An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is default.

                                                                          default

                                                                          -
                                                                          Table 2 EIP tag requirements

                                                                          Parameter

                                                                          +
                                                                          - - - - - - - - @@ -117,12 +117,12 @@
                                                                        13. Click Create Now.
                                                                        14. Click Submit.
                                                                          15. -

                                                                          Binding an EIP

                                                                          1. On the EIPs page, locate the row that contains the target EIP, and click Bind.
                                                                          2. Select the instance that you want to bind the EIP to.
                                                                            Figure 2 Bind EIP
                                                                            +

                                                                            Binding an EIP

                                                                            1. On the EIPs page, locate the row that contains the target EIP, and click Bind.
                                                                            2. Select the instance that you want to bind the EIP to.
                                                                              Figure 2 Bind EIP
                                                                            3. 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?

                                                                            -

                                                                            Follow-Up Procedure

                                                                            After an ECS with an EIP bound is created, the system generates a domain name in the format of ecs-xx-xx-xx-xx.compute.xxx.com for the EIP by default. xx-xx-xx-xx indicates the EIP, and xxx indicates the domain name of the cloud service provider. You can use the domain name to access the ECS.

                                                                            +

                                                                            Follow-Up Procedure

                                                                            After an ECS with an EIP bound is created, the system generates a domain name in the format of ecs-xx-xx-xx-xx.compute.xxx.com for the EIP by default. xx-xx-xx-xx indicates the EIP, and xxx indicates the domain name of the cloud service provider. You can use the domain name to access the ECS.

                                                                            You can use any of the following commands to obtain the domain name of an EIP:
                                                                            • ping -a EIP
                                                                            • nslookup [-qt=ptr] EIP
                                                                            • dig -x EIP
                                                                            diff --git a/docs/vpc/umn/vpc_qs_0012.html b/docs/vpc/umn/vpc_qs_0012.html index 52c5b3ef2..f46aa4bc2 100644 --- a/docs/vpc/umn/vpc_qs_0012.html +++ b/docs/vpc/umn/vpc_qs_0012.html @@ -1,14 +1,14 @@

                                                                            Step 4: Create a Security Group

                                                                            -

                                                                            Scenarios

                                                                            A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                            +

                                                                            Scenarios

                                                                            A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                            If your instances have different Internet access requirements, you can allocate them to different security groups when creating them.

                                                                            Each ECS must be associated with at least one security group. If you do not have a security group when creating an ECS, the system provides a default security group.

                                                                            -

                                                                            Procedure

                                                                            1. Log in to the management console.
                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                              The Virtual Private Cloud page is displayed.

                                                                              +

                                                                              Procedure

                                                                              1. Log in to the management console.
                                                                              2. Click in the upper left corner and select the desired region and project.
                                                                              3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                The Virtual Private Cloud page is displayed.

                                                                              4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                                                The security group list is displayed.

                                                                              5. In the upper right corner, click Create Security Group.

                                                                                The Create Security Group page is displayed.

                                                                                -
                                                                              6. Configure the parameters as prompted.
                                                                                Figure 1 Create Security Group
                                                                                +
                                                                              7. Configure the parameters as prompted.
                                                                                Figure 1 Create Security Group
                                                                          Table 2 EIP tag requirements

                                                                          Parameter

                                                                          Requirement

                                                                          +

                                                                          Requirement

                                                                          Example Value

                                                                          +

                                                                          Example Value

                                                                          Key

                                                                          +

                                                                          Key

                                                                          • Cannot be left blank.
                                                                          • Must be unique for each EIP.
                                                                          • Can contain a maximum of 36 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)
                                                                            +
                                                                          • Cannot be left blank.
                                                                          • The key value must be unique for the same EIP.
                                                                          • Can contain up to 36 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)

                                                                          Ipv4_key1

                                                                          +

                                                                          Ipv4_key1

                                                                          Value

                                                                          +

                                                                          Value

                                                                          • Can contain a maximum of 43 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)
                                                                            +
                                                                          • Can contain up to 43 characters.
                                                                          • Can contain only the following character types:
                                                                            • Uppercase letters
                                                                            • Lowercase letters
                                                                            • Digits
                                                                            • Special characters, including hyphens (-) and underscores (_)

                                                                          3005eip

                                                                          +

                                                                          3005eip
                                                                          @@ -42,7 +42,7 @@ diff --git a/docs/vpc/umn/vpc_qs_0013.html b/docs/vpc/umn/vpc_qs_0013.html index 3ac78c472..cb611b7ed 100644 --- a/docs/vpc/umn/vpc_qs_0013.html +++ b/docs/vpc/umn/vpc_qs_0013.html @@ -1,27 +1,27 @@

                                                                          Step 5: Add a Security Group Rule

                                                                          -

                                                                          Scenarios

                                                                          A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                          +

                                                                          Scenarios

                                                                          A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules.

                                                                          Each ECS must be associated with at least one security group. If you do not have a security group when creating an ECS, the system provides a default security group.

                                                                          -
                                                                          Like whitelists, security group rules work as follows:
                                                                          • Inbound rules control incoming traffic to instances in the security group.

                                                                            If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                                                                            -

                                                                            By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                                                                            -
                                                                          • Outbound rules control outgoing traffic from instances in the security group.

                                                                            If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                                                                            -

                                                                            0.0.0.0/0 represents all IPv4 addresses.

                                                                            -

                                                                            ::/0 represents all IPv6 addresses.

                                                                            +
                                                                            Like whitelists, security group rules work as follows:
                                                                            • Inbound rules control incoming traffic to instances in the security group.

                                                                              If an inbound request matches the source in an inbound security group rule, the request is allowed and other requests are denied.

                                                                              +

                                                                              By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied.

                                                                              +
                                                                            • Outbound rules control outgoing traffic from instances in the security group.

                                                                              If the destination of an outbound security group rule is 0.0.0.0/0, all outbound requests are allowed.

                                                                              +

                                                                              0.0.0.0/0 represents all IPv4 addresses.

                                                                              +

                                                                              ::/0 represents all IPv6 addresses.

                                                                            If the rules of the security group associated with your instance cannot meet your requirements, for example, you need to allow inbound traffic on a specific TCP port, you can add an inbound rule to allow traffic on the TCP port.

                                                                          -

                                                                          Procedure

                                                                          1. Log in to the management console.
                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                            The Virtual Private Cloud page is displayed.

                                                                            +

                                                                            Procedure

                                                                            1. Log in to the management console.
                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                              The Virtual Private Cloud page is displayed.

                                                                            4. In the navigation pane on the left, choose Access Control > Security Groups.

                                                                              The security group list is displayed.

                                                                            5. 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.

                                                                            6. On the Inbound Rules tab, click Add Rule.

                                                                              The Add Inbound Rule dialog box is displayed.

                                                                            7. Configure required parameters.

                                                                              You can click + to add more inbound rules.

                                                                              -
                                                                              Figure 1 Add Inbound Rule
                                                                              +
                                                                              Figure 1 Add Inbound Rule
                                                                              -
                                                                          Table 1 Parameter description

                                                                          Parameter

                                                                          Mandatory

                                                                          A template comes with default security group rules, helping you quickly create security groups. The following templates are provided:

                                                                          -
                                                                          • Custom: This template allows you to create security groups with custom security group rules.
                                                                          • General-purpose web server (default value): The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389.
                                                                          • All ports open: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks.
                                                                          +
                                                                          • Custom: This template allows you to create security groups with custom security group rules.
                                                                          • General-purpose web server (default value): The security group that you create using this template is for general-purpose web servers and includes default rules that allow all inbound ICMP traffic and allow inbound traffic on ports 22, 80, 443, and 3389.
                                                                          • All ports open: The security group that you create using this template includes default rules that allow inbound traffic on any port. Note that allowing inbound traffic on any port poses security risks.

                                                                          General-purpose web server
                                                                          Table 1 Inbound rule parameter description

                                                                          Parameter

                                                                          +
                                                                          - @@ -51,7 +51,7 @@ @@ -72,11 +72,11 @@
                                                                        15. Click OK.

                                                                          The inbound rule list is displayed.

                                                                        16. On the Outbound Rules tab, click Add Rule.

                                                                          The Add Outbound Rule dialog box is displayed.

                                                                        17. Configure required parameters.

                                                                          You can click + to add more outbound rules.

                                                                          -
                                                                          Figure 2 Add Outbound Rule
                                                                          +
                                                                          Figure 2 Add Outbound Rule
                                                                          -
                                                                          18. Table 1 Inbound rule parameter description

                                                                          Parameter

                                                                          Description

                                                                          +

                                                                          Description

                                                                          Example Value

                                                                          Source
                                                                          Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example:
                                                                          • IP address:
                                                                            • Single IP address: 192.168.10.10/32
                                                                            • All IP addresses: 0.0.0.0/0
                                                                            • IP address range: 192.168.1.0/24
                                                                            -
                                                                          • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                                                                          • IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                                                          +
                                                                        18. Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.

                                                                          19. If the source is a security group, this rule will apply to all instances associated with the selected security group.

                                                                          Table 2 Outbound rule parameter description

                                                                          Parameter

                                                                          +
                                                                          - @@ -107,8 +107,8 @@ diff --git a/docs/vpc/umn/vpc_qs_0022.html b/docs/vpc/umn/vpc_qs_0022.html index 3d1f2f02f..61ceb7bd6 100644 --- a/docs/vpc/umn/vpc_qs_0022.html +++ b/docs/vpc/umn/vpc_qs_0022.html @@ -2,7 +2,7 @@

                                                                          Overview

                                                                          If your ECSs need to access the Internet (for example, the ECSs functioning as the service nodes for deploying a website), you can follow the procedure shown in Figure 1 to bind EIPs to the ECSs.

                                                                          -
                                                                          Figure 1 Configuring the network
                                                                          +
                                                                          Figure 1 Configuring the network

                                                                          Table 1 describes the different tasks in the procedure for configuring the network.

                                                                          Table 2 Outbound rule parameter description

                                                                          Parameter

                                                                          Description

                                                                          +

                                                                          Description

                                                                          Example Value

                                                                          Destination

                                                                          Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example:

                                                                          -
                                                                          • IP address:
                                                                            • Single IP address: 192.168.10.10/32
                                                                            • All IP addresses: 0.0.0.0/0
                                                                            • IP address range: 192.168.1.0/24
                                                                            -
                                                                          • Security group: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. Instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with Action set to Allow and Source set to security group B, access from instance B is allowed to instance A.
                                                                          • IP address group: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way.
                                                                          +
                                                                          • IP address:
                                                                            • Single IP address: 192.168.10.10/32
                                                                            • All IP addresses: 0.0.0.0/0
                                                                            • IP address range: 192.168.1.0/24
                                                                            +
                                                                          • Security group: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. For example, instance A is in security group A and instance B is in security group B. If security group A has an outbound rule with Action set to Allow and Destination set to security group B, access from instance A is allowed to instance B.

                                                                          0.0.0.0/0
                                                                          Table 1 Configuration process description

                                                                          Task

                                                                          diff --git a/docs/vpc/umn/vpc_route01_0000.html b/docs/vpc/umn/vpc_route01_0000.html index cfd916fd1..a86fe5f7c 100644 --- a/docs/vpc/umn/vpc_route01_0000.html +++ b/docs/vpc/umn/vpc_route01_0000.html @@ -6,27 +6,9 @@
                                                                          • Route Tables and Routes
                                                                            • -
                                                                          • Creating a Custom Route Table
                                                                            +
                                                                          • Managing Route Tables
                                                                            • -
                                                                          • Associating a Route Table with a Subnet
                                                                            -
                                                                            • -
                                                                          • Changing the Route Table Associated with a Subnet
                                                                            -
                                                                            • -
                                                                          • Viewing the Route Table Associated with a Subnet
                                                                            -
                                                                            • -
                                                                          • Viewing Route Table Information
                                                                            -
                                                                            • -
                                                                          • Exporting Route Table Information
                                                                            -
                                                                            • -
                                                                          • Deleting a Route Table
                                                                            -
                                                                            • -
                                                                          • Adding a Custom Route
                                                                            -
                                                                            • -
                                                                          • Modifying a Route
                                                                            -
                                                                            • -
                                                                          • Replicating a Route
                                                                            -
                                                                            • -
                                                                          • Deleting a Route
                                                                            +
                                                                          • Managing Routes
                                                                          • Configuring an SNAT Server
                                                                            • diff --git a/docs/vpc/umn/vpc_route01_0001.html b/docs/vpc/umn/vpc_route01_0001.html index ef82f9f26..bdbf98f8a 100644 --- a/docs/vpc/umn/vpc_route01_0001.html +++ b/docs/vpc/umn/vpc_route01_0001.html @@ -2,96 +2,96 @@

                                                                            Route Tables and Routes

                                                                            Route Tables

                                                                            A route table contains a set of routes that are used to determine where network traffic from your subnets in a VPC is directed. Each subnet must be associated with a route table. A subnet can only be associated with one route table, but you can associate multiple subnets with the same route table.

                                                                            -
                                                                            Figure 1 Route tables
                                                                            +
                                                                            Figure 1 Route tables
                                                                            • Default route table: When you create a VPC, the system automatically generates a default route table for the VPC. If you create a subnet in the VPC, the subnet automatically associates with the default route table. The default route table ensures that subnets in a VPC can communicate with each other.
                                                                              • You can add routes to, delete routes from, and modify routes in the default route table, but cannot delete the table.
                                                                              • When you create a VPC endpoint, VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or modified.
                                                                            • Custom route table: If you do not want to use the default route table, you can create a custom route table and associate it with the subnet. Custom route tables can be deleted if they are no longer required.

                                                                              The custom route table associated with a subnet affects only the outbound traffic. The default route table of a subnet controls the inbound traffic.

                                                                            -

                                                                            Route

                                                                            You can add routes to default and custom route tables and configure the destination, next hop type, and next hop in the routes to determine where network traffic is directed. Routes are classified into system routes and custom routes.

                                                                            -
                                                                            • System routes: These routes are automatically added by the system and cannot be modified or deleted.
                                                                              After a route table is created, the system automatically adds the following system routes to the route table, so that instances in a VPC can communicate with each other.
                                                                              • Routes whose destination is 100.64.0.0/10 or 198.19.128.0/20.
                                                                              • Routes whose destination is a subnet CIDR block.
                                                                                If you enable IPv6 when creating a subnet, the system automatically assigns an IPv6 CIDR block to the subnet. Then, you can view IPv6 routes in its route table. Example destinations of subnet CIDR blocks are as follows:
                                                                                • IPv4: 192.168.2.0/24
                                                                                • IPv6: 2407:c080:802:be7::/64
                                                                                +

                                                                                Route

                                                                                You can add routes to default and custom route tables and configure the destination, next hop type, and next hop in the routes to determine where network traffic is directed. Routes are classified into system routes and custom routes.

                                                                                +
                                                                                • System routes: These routes are automatically added by the system and cannot be modified or deleted.
                                                                                  After a route table is created, the system automatically adds the following system routes to the route table, so that instances in a VPC can communicate with each other.
                                                                                  • Routes whose destination is 100.64.0.0/10 or 198.19.128.0/20.
                                                                                  • Routes whose destination is a subnet CIDR block.
                                                                                    If you enable IPv6 when creating a subnet, the system automatically assigns an IPv6 CIDR block to the subnet. Then, you can view IPv6 routes in its route table. Example destinations of subnet CIDR blocks are as follows:
                                                                                    • IPv4: 192.168.2.0/24
                                                                                    • IPv6: 2407:c080:802:be7::/64
                                                                                    -

                                                                                    In addition to the preceding system routes, the system automatically adds a route whose destination is 127.0.0.0/8. This is the local loopback address.

                                                                                    +

                                                                                    In addition to the preceding system routes, the system automatically adds a route whose destination is 127.0.0.0/8. This is the local loopback address.

                                                                                  -
                                                                                • Custom routes: These are routes that you can add, modify, and delete. The destination of a custom route cannot overlap with that of a system route.

                                                                                  You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. Table 1 lists the supported types of next hops.

                                                                                  -

                                                                                  You cannot add two routes with the same destination to a VPC route table even if their next hop types are different. The route priority depends on the destination. According to the longest match routing rule, the destination with a higher matching degree is preferentially selected for packet forwarding.

                                                                                  +
                                                                                • Custom routes: These are routes that you can add, modify, and delete. The destination of a custom route cannot overlap with that of a system route.

                                                                                  You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. Table 1 lists the supported types of next hops.

                                                                                  +

                                                                                  You cannot add two routes with the same destination to a VPC route table even if their next hop types are different. The route priority depends on the destination. According to the longest match routing rule, the destination with a higher matching degree is preferentially selected for packet forwarding.

                                                                                  -
                                                                                  Table 1 Next hop type

                                                                                  Next Hop Type

                                                                                  +
                                                                                  - - - - - - - - - - - - - - - - - - - - - - - - - -
                                                                                  Table 1 Next hop type

                                                                                  Next Hop Type

                                                                                  Description

                                                                                  +

                                                                                  Description

                                                                                  Supported Route Table

                                                                                  +

                                                                                  Supported Route Table

                                                                                  Server

                                                                                  +

                                                                                  Server

                                                                                  Traffic intended for the destination is forwarded to an ECS in the VPC.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to an ECS in the VPC.

                                                                                  • Default route table
                                                                                  • Custom route table
                                                                                  +
                                                                                  • Default route table
                                                                                  • Custom route table

                                                                                  Extension NIC

                                                                                  +

                                                                                  Extension NIC

                                                                                  Traffic intended for the destination is forwarded to the extension NIC of an ECS in the VPC.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to the extension NIC of an ECS in the VPC.

                                                                                  • Default route table
                                                                                  • Custom route table
                                                                                  +
                                                                                  • Default route table
                                                                                  • Custom route table

                                                                                  BMS user-defined network

                                                                                  +

                                                                                  BMS user-defined network

                                                                                  Traffic intended for the destination is forwarded to a BMS user-defined network. Currently, this parameter is available only in eu-de.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to a BMS user-defined network. Currently, this parameter is available only in eu-de.

                                                                                  • Default route table
                                                                                  • Custom route table
                                                                                  +
                                                                                  • Custom route table

                                                                                  VPN connection

                                                                                  +

                                                                                  VPN connection

                                                                                  Traffic intended for the destination is forwarded to a VPN gateway.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to a VPN gateway.

                                                                                  Custom route table

                                                                                  +

                                                                                  Custom route table

                                                                                  Direct Connect gateway

                                                                                  +

                                                                                  Direct Connect gateway

                                                                                  Traffic intended for the destination is forwarded to a Direct Connect gateway.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to a Direct Connect gateway.

                                                                                  Custom route table

                                                                                  +

                                                                                  Custom route table

                                                                                  NAT gateway

                                                                                  +

                                                                                  NAT gateway

                                                                                  Traffic intended for the destination is forwarded to a NAT gateway.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to a NAT gateway.

                                                                                  • Default route table
                                                                                  • Custom route table
                                                                                  +
                                                                                  • Default route table
                                                                                  • Custom route table

                                                                                  VPC peering connection

                                                                                  +

                                                                                  VPC peering connection

                                                                                  Traffic intended for the destination is forwarded to a VPC peering connection.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to a VPC peering connection.

                                                                                  • Default route table
                                                                                  • Custom route table
                                                                                  +
                                                                                  • Default route table
                                                                                  • Custom route table

                                                                                  Virtual IP address

                                                                                  +

                                                                                  Virtual IP address

                                                                                  Traffic intended for the destination is forwarded to a virtual IP address and then sent to active and standby ECSs to which the virtual IP address is bound.

                                                                                  +

                                                                                  Traffic intended for the destination is forwarded to a virtual IP address and then sent to active and standby ECSs to which the virtual IP address is bound.

                                                                                  • Default route table
                                                                                  • Custom route table
                                                                                  +
                                                                                  • Default route table
                                                                                  • Custom route table
                                                                                  -

                                                                                  If you specify the destination when creating a resource, a system route is delivered. If you do not specify a destination when creating a resource, a custom route that can be modified or deleted is delivered.

                                                                                  -

                                                                                  For example, when you create a NAT gateway, the system automatically delivers a custom route without a specific destination (0.0.0.0/0 is used by default). In this case, you can change the destination. However, when you create a VPN connection or Direct Connect gateway, you need to specify the remote subnet, that is, the destination of a route. In this case, the system delivers this system route. Do not modify the route destination on the Route Tables page. If you do, the destination will be inconsistent with the configured remote subnet. To modify the route destination, go to the specific resource page and modify the remote subnet, then the route destination will be changed accordingly.

                                                                                  +

                                                                                  If you specify the destination when creating a resource, a system route is delivered. If you do not specify a destination when creating a resource, a custom route that can be modified or deleted is delivered.

                                                                                  +

                                                                                  For example, when you create a NAT gateway, the system automatically delivers a custom route without a specific destination (0.0.0.0/0 is used by default). In this case, you can change the destination. However, when you create a VPN connection or Direct Connect gateway, you need to specify the remote subnet, that is, the destination of a route. In this case, the system delivers this system route. Do not modify the route destination on the Route Tables page. If you do, the destination will be inconsistent with the configured remote subnet. To modify the route destination, go to the specific resource page and modify the remote subnet, then the route destination will be changed accordingly.

                                                                                  Custom Route Table Configuration Process

                                                                                  Figure 2 shows the process of creating and configuring a custom route table.

                                                                                  -
                                                                                  Figure 2 Route table configuration process
                                                                                  +
                                                                                  Figure 2 Route table configuration process
                                                                                  1. For details about how to create a custom route table, see Creating a Custom Route Table.
                                                                                  2. For details about how to add a custom route, see Adding a Custom Route.
                                                                                  3. For details about how to associate a subnet with a route table, see Associating a Route Table with a Subnet. After the association, the routes in the route table control the routing for the subnet.
                                                                                  diff --git a/docs/vpc/umn/vpc_route01_0005.html b/docs/vpc/umn/vpc_route01_0005.html index 6bd523081..d5ff010bb 100644 --- a/docs/vpc/umn/vpc_route01_0005.html +++ b/docs/vpc/umn/vpc_route01_0005.html @@ -5,8 +5,8 @@

                                                                                  Notes and Constraints

                                                                                  By default, each VPC can have up to 10 route tables, including the default route table.

                                                                                  -

                                                                                  Procedure

                                                                                  1. Log in to the management console.
                                                                                  1. Click in the upper left corner and select the desired region and project.
                                                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                    The Virtual Private Cloud page is displayed.

                                                                                    -
                                                                                  3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                  4. In the upper right corner, click Create Route Table. On the displayed page, configure parameters as prompted.
                                                                                    Figure 1 Create Route Table
                                                                                    +

                                                                                    Procedure

                                                                                    1. Log in to the management console.
                                                                                    1. Click in the upper left corner and select the desired region and project.
                                                                                    2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                      The Virtual Private Cloud page is displayed.

                                                                                      +
                                                                                    3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                    4. In the upper right corner, click Create Route Table. On the displayed page, configure parameters as prompted.
                                                                                      Figure 1 Create Route Table
                                                                                      @@ -59,7 +59,7 @@
                                                                                      -
                                                                                      Parent topic: Route Tables
                                                                                      +
                                                                                      Parent topic: Managing Route Tables
                                                                                      diff --git a/docs/vpc/umn/vpc_route01_0006.html b/docs/vpc/umn/vpc_route01_0006.html index bcfb701a8..8c38e6e1c 100644 --- a/docs/vpc/umn/vpc_route01_0006.html +++ b/docs/vpc/umn/vpc_route01_0006.html @@ -5,51 +5,51 @@

                                                                                      Notes and Constraints

                                                                                      A maximum of 200 routes can be added to each route table.

                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. In the route table list, click the name of the route table to which you want to add a route.
                                                                                        5. Click Add Route and set parameters as prompted.

                                                                                          You can click + to add more routes.

                                                                                          -
                                                                                          Figure 1 Add Route
                                                                                          +
                                                                                          Figure 1 Add Route
                                                                                          -
                                                                                      Table 1 Parameter descriptions

                                                                                      Parameter
                                                                                      Table 1 Parameter descriptions

                                                                                      Parameter

                                                                                      +
                                                                                      - - - - - - - - - - - - - - @@ -61,7 +61,7 @@
                                                                                      -
                                                                                      Parent topic: Route Tables
                                                                                      +
                                                                                      Parent topic: Managing Routes
                                                                                      diff --git a/docs/vpc/umn/vpc_route01_0007.html b/docs/vpc/umn/vpc_route01_0007.html index 1bbccb8cc..cedb18a6f 100644 --- a/docs/vpc/umn/vpc_route01_0007.html +++ b/docs/vpc/umn/vpc_route01_0007.html @@ -8,14 +8,14 @@

                                                                                      Notes and Constraints

                                                                                      • A subnet must have a route table associated and can only be associated with one route table.
                                                                                      • A route table can be associated with multiple subnets.
                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        -
                                                                                      3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                      4. In the route table list, locate the row that contains the target route table and click Associate Subnet in the Operation column.
                                                                                      5. Select the subnet to be associated.
                                                                                        Figure 1 Associate Subnet
                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                          +
                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. In the route table list, locate the row that contains the target route table and click Associate Subnet in the Operation column.
                                                                                        5. Select the subnet to be associated.
                                                                                          Figure 1 Associate Subnet
                                                                                        6. Click OK.
                                                                                      -
                                                                                      Parent topic: Route Tables
                                                                                      +
                                                                                      Parent topic: Managing Route Tables
                                                                                      diff --git a/docs/vpc/umn/vpc_route01_0008.html b/docs/vpc/umn/vpc_route01_0008.html index beb4ca248..55d02dfd6 100644 --- a/docs/vpc/umn/vpc_route01_0008.html +++ b/docs/vpc/umn/vpc_route01_0008.html @@ -3,14 +3,14 @@

                                                                                      Changing the Route Table Associated with a Subnet

                                                                                      Scenarios

                                                                                      You can change the route table for a subnet. If the route table for a subnet is changed, routes in the new route table will apply to all cloud resources in the subnet.

                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. Click the name of the target route table.
                                                                                        5. On the Associated Subnets tab page, click Change Route Table in the Operation column and select a new route table as prompted.
                                                                                        6. Click OK.

                                                                                          After the route table for a subnet is changed, routes in the new route table will apply to all cloud resources in the subnet.

                                                                                      -
                                                                                      Parent topic: Route Tables
                                                                                      +
                                                                                      Parent topic: Managing Route Tables
                                                                                      diff --git a/docs/vpc/umn/vpc_route01_0009.html b/docs/vpc/umn/vpc_route01_0009.html index 7aa1cf0b2..9f8b54c62 100644 --- a/docs/vpc/umn/vpc_route01_0009.html +++ b/docs/vpc/umn/vpc_route01_0009.html @@ -4,7 +4,7 @@

                                                                                      Scenarios

                                                                                      This section describes how to view detailed information about a route table, including:
                                                                                      • Basic information, such as name, type (default or custom), and ID of the route table
                                                                                      • Routes, such as destination, next hop, and route type (system or custom)
                                                                                      • Associated subnets
                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. Click the name of the target route table.

                                                                                          The route table details page is displayed.

                                                                                          1. On the Summary tab page, view the basic information and routes of the route table.
                                                                                          2. On the Associated Subnets tab page, view the subnets associated with the route table.
                                                                                        @@ -12,7 +12,7 @@
                                                                                        -
                                                                                        Parent topic: Route Tables
                                                                                        +
                                                                                        Parent topic: Managing Route Tables
                                                                                        diff --git a/docs/vpc/umn/vpc_route01_0010.html b/docs/vpc/umn/vpc_route01_0010.html index 48ff1e75d..295401a06 100644 --- a/docs/vpc/umn/vpc_route01_0010.html +++ b/docs/vpc/umn/vpc_route01_0010.html @@ -6,13 +6,13 @@

                                                                                        Notes and Constraints

                                                                                        • The default route table cannot be deleted.
                                                                                        • A custom route table with a subnet associated cannot be deleted directly.

                                                                                          If you want to delete such a route table, you can associate the subnet with another route table first by referring to Changing the Route Table Associated with a Subnet.

                                                                                        -

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud. The Virtual Private Cloud page is displayed.
                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. Locate the row that contains the route table you want to delete and click Delete in the Operation column.

                                                                                          A confirmation dialog box is displayed.

                                                                                          +

                                                                                          Procedure

                                                                                          1. Log in to the management console.
                                                                                          1. Click in the upper left corner and select the desired region and project.
                                                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud. The Virtual Private Cloud page is displayed.
                                                                                          3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                          4. Locate the row that contains the route table you want to delete and click Delete in the Operation column.

                                                                                            A confirmation dialog box is displayed.

                                                                                          5. Click Yes.
                                                                                        -
                                                                                        Parent topic: Route Tables
                                                                                        +
                                                                                        Parent topic: Managing Route Tables
                                                                                        diff --git a/docs/vpc/umn/vpc_route01_0011.html b/docs/vpc/umn/vpc_route01_0011.html index 9605d6629..0b234b02a 100644 --- a/docs/vpc/umn/vpc_route01_0011.html +++ b/docs/vpc/umn/vpc_route01_0011.html @@ -5,49 +5,49 @@

                                                                                      Notes and Constraints

                                                                                      • System routes cannot be modified.
                                                                                      • When you create a VPC endpoint, VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or modified.
                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. In the route table list, click the name of the target route table.
                                                                                        5. Locate the row that contains the route to be modified and click Modify in the Operation column.
                                                                                        6. Modify the route information in the displayed dialog box. -
                                                                                      Table 1 Parameter descriptions

                                                                                      Parameter

                                                                                      Description

                                                                                      +

                                                                                      Description

                                                                                      Example Value

                                                                                      +

                                                                                      Example Value

                                                                                      Destination

                                                                                      +

                                                                                      Destination

                                                                                      Mandatory

                                                                                      +

                                                                                      Mandatory

                                                                                      Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation.

                                                                                      The destination of each route in a route table must be unique. The destination cannot overlap with any subnet in the VPC.

                                                                                      IPv4: 192.168.0.0/16

                                                                                      +

                                                                                      IPv4: 192.168.0.0/16

                                                                                      Next Hop Type

                                                                                      +

                                                                                      Next Hop Type

                                                                                      Mandatory

                                                                                      +

                                                                                      Mandatory

                                                                                      Set the type of the next hop.

                                                                                      NOTE:

                                                                                      When you add or modify a custom route in a default route table, the next hop type of the route cannot be set to VPN connection or Direct Connect gateway.

                                                                                      VPC peering connection

                                                                                      +

                                                                                      VPC peering connection

                                                                                      Next Hop

                                                                                      +

                                                                                      Next Hop

                                                                                      Mandatory

                                                                                      +

                                                                                      Mandatory

                                                                                      Set the next hop. The resources in the drop-down list box are displayed based on the selected next hop type.

                                                                                      peer-AB

                                                                                      +

                                                                                      peer-AB

                                                                                      Description

                                                                                      +

                                                                                      Description

                                                                                      Optional

                                                                                      +

                                                                                      Optional

                                                                                      Enter the description of the route in the text box as required.

                                                                                      -

                                                                                      +

                                                                                      -
                                                                                      Table 1 Parameter descriptions

                                                                                      Parameter

                                                                                      +
                                                                                      - - - - - - - - - - - - - - @@ -58,7 +58,7 @@
                                                                                      -
                                                                                      Parent topic: Route Tables
                                                                                      +
                                                                                      Parent topic: Managing Routes
                                                                                      diff --git a/docs/vpc/umn/vpc_route01_0012.html b/docs/vpc/umn/vpc_route01_0012.html index d8358f503..ade12109d 100644 --- a/docs/vpc/umn/vpc_route01_0012.html +++ b/docs/vpc/umn/vpc_route01_0012.html @@ -7,7 +7,7 @@

                                                                                      The following figure shows a route with VPN gateway as Next Hop Type. If you want to delete such a route, click the next hop hyperlink to delete the corresponding resource.

                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. Locate the target route table and click its name.

                                                                                          The route table details page is displayed.

                                                                                        5. In the route list, locate the row that contains the route to be deleted and click Delete in the Operation column.

                                                                                          A confirmation dialog box is displayed.

                                                                                        6. Confirm the information and click Yes.
                                                                                        @@ -15,7 +15,7 @@
                                                                                        -
                                                                                        Parent topic: Route Tables
                                                                                        +
                                                                                        Parent topic: Managing Routes
                                                                                        diff --git a/docs/vpc/umn/vpc_route01_0013.html b/docs/vpc/umn/vpc_route01_0013.html index 33eab3c9a..f6f438813 100644 --- a/docs/vpc/umn/vpc_route01_0013.html +++ b/docs/vpc/umn/vpc_route01_0013.html @@ -3,10 +3,10 @@

                                                                                        Replicating a Route

                                                                                        Scenarios

                                                                                        This section describes how to replicate routes among all route tables of a VPC. VPC route tables include the default and custom route tables.

                                                                                        -

                                                                                        Notes and Constraints

                                                                                        Table 1 shows whether routes of different types can be replicated to default or custom route tables.

                                                                                        +

                                                                                        Notes and Constraints

                                                                                        Table 1 shows whether routes of different types can be replicated to default or custom route tables.

                                                                                        For example, if the next hop type of a route is a server, this route can be replicated to both default or custom route tables. If the next hop type of a route is a Direct Connect gateway, the route cannot be replicated to the default route table, but can be replicated to a custom route table.

                                                                                        -
                                                                                      Table 1 Parameter descriptions

                                                                                      Item

                                                                                      Description

                                                                                      +

                                                                                      Description

                                                                                      Example Value

                                                                                      +

                                                                                      Example Value

                                                                                      Destination

                                                                                      +

                                                                                      Destination

                                                                                      Mandatory

                                                                                      -

                                                                                      Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation.

                                                                                      -

                                                                                      The destination of each route in a route table must be unique. The destination cannot overlap with any subnet in the VPC.

                                                                                      +

                                                                                      Mandatory

                                                                                      +

                                                                                      Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation.

                                                                                      +

                                                                                      The destination of each route must be unique. The destination cannot overlap with any subnet CIDR block in the VPC.

                                                                                      IPv4: 192.168.0.0/16

                                                                                      +

                                                                                      Pv4: 192.168.0.0/16

                                                                                      Next Hop Type

                                                                                      +

                                                                                      Next Hop Type

                                                                                      Mandatory

                                                                                      -

                                                                                      Set the type of the next hop.

                                                                                      -
                                                                                      NOTE:

                                                                                      When you add or modify a custom route in a default route table, the next hop type of the route cannot be set to VPN connection or Direct Connect gateway.

                                                                                      +

                                                                                      Mandatory

                                                                                      +

                                                                                      Set the type of the next hop.

                                                                                      +
                                                                                      NOTE:

                                                                                      When you add or modify a custom route in a default route table, the next hop type of the route cannot be set to VPN connection or Direct Connect gateway.

                                                                                      VPC peering connection

                                                                                      +

                                                                                      VPC peering

                                                                                      Next Hop

                                                                                      +

                                                                                      Next Hop

                                                                                      Mandatory

                                                                                      -

                                                                                      Set the next hop. The resources in the drop-down list box are displayed based on the selected next hop type.

                                                                                      +

                                                                                      Mandatory

                                                                                      +

                                                                                      Set the next hop. The resources in the drop-down list box are displayed based on the selected next hop type.

                                                                                      peer-AB

                                                                                      +

                                                                                      peer-AB

                                                                                      Description

                                                                                      +

                                                                                      Description

                                                                                      Optional

                                                                                      -

                                                                                      Enter the description of the route in the text box as required.

                                                                                      +

                                                                                      Optional

                                                                                      +

                                                                                      Enter the description of the route in the text box as required.

                                                                                      -

                                                                                      +

                                                                                      -
                                                                                      Table 1 Route replication

                                                                                      Next Hop Type

                                                                                      +
                                                                                      @@ -21,49 +21,49 @@ - - - - - - - @@ -76,14 +76,14 @@
                                                                                      • Black hole routes cannot be replicated.
                                                                                      • If the Direct Connect service is enabled in the self-service mode, the routes delivered to the default route table can be replicated to a custom route table.
                                                                                      • If the Direct Connect service is enabled by call or email, the routes delivered to the default route table cannot be replicated to a custom route table.
                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. In the route table list, locate the row that contains the route table you want to replicate routes from and click Replicate Route in the Operation column.
                                                                                        5. Select the target route table that you want to replicate route to and the routes to be replicated as prompted.

                                                                                          The listed routes are those that do not exist in the target route table. You can select one or more routes to replicate to the target route table.

                                                                                        6. Click OK.
                                                                                      -
                                                                                      Parent topic: Route Tables
                                                                                      +
                                                                                      Parent topic: Managing Routes
                                                                                      diff --git a/docs/vpc/umn/vpc_route01_0014.html b/docs/vpc/umn/vpc_route01_0014.html index 07c54f0ae..03e8abe6f 100644 --- a/docs/vpc/umn/vpc_route01_0014.html +++ b/docs/vpc/umn/vpc_route01_0014.html @@ -3,14 +3,14 @@

                                                                                      Exporting Route Table Information

                                                                                      Scenarios

                                                                                      Information about all route tables under your account can be exported as an Excel file to a local directory. This file records the name, ID, VPC, type, and number of associated subnets of the route tables.

                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        -
                                                                                      3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                      4. On the displayed page, click in the upper right of the route table list.

                                                                                        The system will automatically export information about all route tables under your account in the current region as an Excel file to a local directory.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                          +
                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Route Tables.
                                                                                        4. In the route table list, select one or more route tables you want to export and click Export in the upper left corner.

                                                                                          The system will automatically export information about all of your route tables as an Excel file to a local directory.

                                                                                      -
                                                                                      Parent topic: Route Tables
                                                                                      +
                                                                                      Parent topic: Managing Route Tables
                                                                                      diff --git a/docs/vpc/umn/vpc_route01_0015.html b/docs/vpc/umn/vpc_route01_0015.html index c6be3bde1..cc7e0543c 100644 --- a/docs/vpc/umn/vpc_route01_0015.html +++ b/docs/vpc/umn/vpc_route01_0015.html @@ -3,7 +3,7 @@

                                                                                      Viewing the Route Table Associated with a Subnet

                                                                                      Scenarios

                                                                                      This section describes how to view the route table associated with a subnet.

                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      1. Click in the upper left corner and select the desired region and project.
                                                                                      2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        1. Click in the upper left corner and select the desired region and project.
                                                                                        2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        3. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                          The Subnets page is displayed.

                                                                                        4. Locate the target subnet and click its name.

                                                                                          The subnet details page is displayed.

                                                                                        5. In the right of the subnet details page, view the route table associated with the subnet.
                                                                                        6. Click the name of the route table.

                                                                                          The route table details page is displayed. You can further view the route information.

                                                                                          @@ -12,7 +12,7 @@
                                                                                        -
                                                                                        Parent topic: Route Tables
                                                                                        +
                                                                                        Parent topic: Managing Route Tables
                                                                                        diff --git a/docs/vpc/umn/vpc_route01_0016.html b/docs/vpc/umn/vpc_route01_0016.html new file mode 100644 index 000000000..888467095 --- /dev/null +++ b/docs/vpc/umn/vpc_route01_0016.html @@ -0,0 +1,31 @@ + + + +

                                                                                        Managing Route Tables

                                                                                        + +

                                                                                        +
                                                                                        + + + diff --git a/docs/vpc/umn/vpc_route01_0017.html b/docs/vpc/umn/vpc_route01_0017.html new file mode 100644 index 000000000..04fb23224 --- /dev/null +++ b/docs/vpc/umn/vpc_route01_0017.html @@ -0,0 +1,25 @@ + + + +

                                                                                        Managing Routes

                                                                                        + +

                                                                                        +
                                                                                        + + + diff --git a/docs/vpc/umn/vpc_route_0004.html b/docs/vpc/umn/vpc_route_0004.html index 45ee4ed8e..8bb85680d 100644 --- a/docs/vpc/umn/vpc_route_0004.html +++ b/docs/vpc/umn/vpc_route_0004.html @@ -1,12 +1,12 @@

                                                                                        Configuring an SNAT Server

                                                                                        -

                                                                                        Scenarios

                                                                                        Together with VPC route tables, you can configure SNAT on an ECS to enable other ECSs that have no EIPs bound in the same VPC to access the Internet through this ECS.

                                                                                        -

                                                                                        The configured SNAT takes effect for all subnets in a VPC.

                                                                                        +

                                                                                        Scenarios

                                                                                        Together with VPC route tables, you can configure SNAT on an ECS to enable other ECSs that have no EIPs bound in the same VPC to access the Internet through this ECS.

                                                                                        +

                                                                                        The configured SNAT takes effect for all subnets in a VPC.

                                                                                        -

                                                                                        Prerequisites

                                                                                        • You have an ECS where SNAT is to be configured.
                                                                                        • The ECS where SNAT is to be configured runs Linux.
                                                                                        • The ECS where SNAT is to be configured has only one network interface card (NIC).
                                                                                        +

                                                                                        Prerequisites

                                                                                        • You have an ECS where SNAT is to be configured.
                                                                                        • The ECS where SNAT is to be configured runs Linux.
                                                                                        • The ECS where SNAT is to be configured has only one network interface card (NIC).
                                                                                        -

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. In the upper left corner of the page, click . In the service list, choose Computing > Elastic Cloud Server.
                                                                                        4. On the displayed page, locate the target ECS in the ECS list and click the ECS name to switch to the page showing ECS details.
                                                                                        5. On the displayed ECS details page, click the NICs tab.
                                                                                        6. In the displayed area showing the NIC IP address details, disable Source/Destination Check.

                                                                                          This prevents packet spoofing and improves system security. If SNAT is used, the SNAT server needs to forward packets. This mechanism prevents the packet sender from receiving returned packets. To change this behavior, you can disable the source/destination check for SNAT servers.

                                                                                          +

                                                                                          Procedure

                                                                                          1. Log in to the management console.
                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                          3. In the upper left corner of the page, click . In the service list, choose Computing > Elastic Cloud Server.
                                                                                          4. On the displayed page, locate the target ECS in the ECS list and click the ECS name to switch to the page showing ECS details.
                                                                                          5. On the displayed ECS details page, click the NICs tab.
                                                                                          6. In the displayed area showing the NIC IP address details, disable Source/Destination Check.

                                                                                            This prevents packet spoofing and improves system security. If SNAT is used, the SNAT server needs to forward packets. This mechanism prevents the packet sender from receiving returned packets. To change this behavior, you can disable the source/destination check for SNAT servers.

                                                                                          7. Bind an EIP.
                                                                                          8. On the ECS console, use the remote login function to log in to the ECS where you plan to configure SNAT.
                                                                                          9. Run the following command and enter the password of user root to switch to user root:

                                                                                            su - root

                                                                                          10. Run the following command to check whether the ECS can successfully connect to the Internet:

                                                                                            Before running the command, you must disable the response iptables rule on the ECS where SNAT is configured and configure security group rules.

                                                                                            @@ -25,7 +25,7 @@ PING www.google.com (xxx.xxx.xxx.xxx) 56(84) bytes of data.
                                                                                          11. Use the vi editor to open the /etc/sysctl.conf file, change the value of net.ipv4.ip_forward to 1, and enter :wq to save the change and exit.
                                                                                          12. Run the following command to make the change take effect:

                                                                                            sysctl -p /etc/sysctl.conf

                                                                                          13. Configure the SNAT function.

                                                                                            Run the following command to enable all ECSs on the network (for example, 192.168.1.0/24) to access the Internet using the SNAT function:

                                                                                            iptables -t nat -A POSTROUTING -o eth0 -s subnet -j SNAT --to nat-instance-ip

                                                                                            -
                                                                                            Figure 1 Configuring SNAT
                                                                                            +
                                                                                            Figure 1 Configuring SNAT

                                                                                            To ensure that the rule will not be lost after the restart, write the rule into the /etc/rc.local file.

                                                                                            1. Switch to the /etc/sysctl.conf file:

                                                                                              vi /etc/rc.local

                                                                                            2. Perform 14 to configure SNAT.
                                                                                            3. Save the configuration and exit:

                                                                                              :wq

                                                                                              @@ -33,7 +33,7 @@ PING www.google.com (xxx.xxx.xxx.xxx) 56(84) bytes of data.
                                                                                          14. Check whether the configuration is successful. If information similar to Figure 2 (for example, 192.168.1.0/24) is displayed, the configuration was successful.

                                                                                            iptables -t nat --list

                                                                                            -
                                                                                            Figure 2 Verifying configuration
                                                                                            +
                                                                                            Figure 2 Verifying configuration
                                                                                          15. Add a route. For details, see section Adding a Custom Route.

                                                                                            Set the destination to 0.0.0.0/0, and the next hop to the private or virtual IP address of the ECS where SNAT is deployed. For example, the next hop is 192.168.1.4.

                                                                                          After these operations are complete, if the network communication still fails, check your security group and firewall configuration to see whether required traffic is allowed.

                                                                                          diff --git a/docs/vpc/umn/vpc_use_0001.html b/docs/vpc/umn/vpc_use_0001.html index 3fc579c80..b7c589bd2 100644 --- a/docs/vpc/umn/vpc_use_0001.html +++ b/docs/vpc/umn/vpc_use_0001.html @@ -2,7 +2,7 @@

                                                                                          Document Usage Instructions

                                                                                          Instructions for using this document are as follows:

                                                                                          -
                                                                                          • To facilitate your operations, the management console may provide more than one way for you to perform a task or an operation. This document describes only the main way.
                                                                                          • You can click next to some parameter values to quickly edit the values. This document does not describe this function.
                                                                                          +
                                                                                          • To facilitate your operations, the management console may provide more than one way for you to perform a task or an operation. This document describes only the main way.
                                                                                          • You can click next to some parameter values to quickly edit the values. This document does not describe this function.
                                                                                          diff --git a/docs/vpc/umn/vpc_vip_0000.html b/docs/vpc/umn/vpc_vip_0000.html index 6980d1c47..546321543 100644 --- a/docs/vpc/umn/vpc_vip_0000.html +++ b/docs/vpc/umn/vpc_vip_0000.html @@ -12,22 +12,22 @@
                                                                                        7. Binding a Virtual IP Address to an EIP
                                                                                          8. -
                                                                                        8. Using a VPN to Access a Virtual IP Address
                                                                                          -
                                                                                          9. -
                                                                                        9. Using a Direct Connect Connection to Access the Virtual IP Address
                                                                                          -
                                                                                          10. -
                                                                                        10. Using a VPC Peering Connection to Access the Virtual IP Address
                                                                                          -
                                                                                          11. -
                                                                                        11. Disabling IP Forwarding on the Standby ECS
                                                                                          -
                                                                                          12. -
                                                                                        12. Disabling Source and Destination Check (HA Load Balancing Cluster Scenario)
                                                                                          -
                                                                                        13. Unbinding a Virtual IP Address from an Instance
                                                                                        14. Unbinding a Virtual IP Address from an EIP
                                                                                        15. Releasing a Virtual IP Address
                                                                                          16. +
                                                                                        16. Disabling IP Forwarding on the Standby ECS
                                                                                          +
                                                                                          17. +
                                                                                        17. Disabling Source and Destination Check (HA Load Balancing Cluster Scenario)
                                                                                          +
                                                                                          18. +
                                                                                        18. Using a VPN to Access a Virtual IP Address
                                                                                          +
                                                                                          19. +
                                                                                        19. Using a Direct Connect Connection to Access the Virtual IP Address
                                                                                          +
                                                                                          20. +
                                                                                        20. Using a VPC Peering Connection to Access the Virtual IP Address
                                                                                          +
                                                                                        diff --git a/docs/vpc/umn/vpc_vip_0001.html b/docs/vpc/umn/vpc_vip_0001.html index 1c2f958e4..a5376f0e0 100644 --- a/docs/vpc/umn/vpc_vip_0001.html +++ b/docs/vpc/umn/vpc_vip_0001.html @@ -6,10 +6,10 @@

                                                                                        Networking

                                                                                        Virtual IP addresses are used for high availability and can work together with Keepalived to make active/standby ECS switchover possible. This way if one ECS goes down for some reason, the other one can take over and services continue uninterrupted. ECSs can be configured for HA or as load balancing clusters.

                                                                                        • Networking mode 1: HA

                                                                                          If you want to improve service availability and avoid single points of failure, you can deploy ECSs in the active/standby mode or deploy one active ECS and multiple standby ECSs. In this arrangement, the ECSs all use the same virtual IP address. If the active ECS becomes faulty, a standby ECS takes over services from the active ECS and services continue uninterrupted.

                                                                                          -
                                                                                          Figure 1 Networking diagram of the HA mode
                                                                                          +
                                                                                          Figure 1 Networking diagram of the HA mode
                                                                                          • In this configuration, a single virtual IP address is bound to two ECSs in the same subnet.
                                                                                          • Keepalived is then used to configure the two ECSs to work in the active/standby mode. Follow industry standards for configuring Keepalived. The details are not included here.
                                                                                        • Networking mode 2: HA load balancing cluster

                                                                                          If you want to build a high-availability load balancing cluster, use Keepalived and configure LVS nodes as direct routers.

                                                                                          -
                                                                                          Figure 2 HA load balancing cluster
                                                                                          +
                                                                                          Figure 2 HA load balancing cluster
                                                                                          • Bind a single virtual IP address to two ECSs.
                                                                                          • Configure the two ECSs as LVS nodes working as direct routers and use Keepalived to configure the nodes in the active/standby mode. The two ECSs will evenly forward requests to different backend servers.
                                                                                          • Configure two more ECSs as backend servers.
                                                                                          • Disable the source/destination check for the two backend servers.

                                                                                          Follow industry standards for configuring Keepalived. The details are not included here.

                                                                                          diff --git a/docs/vpc/umn/vpc_vip_0002.html b/docs/vpc/umn/vpc_vip_0002.html index 89eca2b2f..f278c4220 100644 --- a/docs/vpc/umn/vpc_vip_0002.html +++ b/docs/vpc/umn/vpc_vip_0002.html @@ -3,7 +3,7 @@

                                                                                          Assigning a Virtual IP Address

                                                                                          Scenarios

                                                                                          If an ECS requires a virtual IP address or if a virtual IP address needs to be reserved, you can assign a virtual IP address from the subnet.

                                                                                          -

                                                                                          Procedure

                                                                                          1. Log in to the management console.
                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                            The Virtual Private Cloud page is displayed.

                                                                                            +

                                                                                            Procedure

                                                                                            1. Log in to the management console.
                                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                              The Virtual Private Cloud page is displayed.

                                                                                            4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
                                                                                            5. In the subnet list, click the name of the subnet where a virtual IP address is to be assigned.
                                                                                            6. Click the IP Addresses tab and click Assign Virtual IP Address.
                                                                                            7. Select an IP address type. This parameter is available only in regions supporting IPv6.
                                                                                              • IPv4
                                                                                              • IPv6
                                                                                            8. Select a virtual IP address assignment mode.
                                                                                              • Automatic: The system assigns an IP address automatically.
                                                                                              • Manual: You can specify an IP address.
                                                                                            9. Select Manual and enter a virtual IP address.
                                                                                            10. Click OK.
                                                                                            diff --git a/docs/vpc/umn/vpc_vip_0003.html b/docs/vpc/umn/vpc_vip_0003.html index 5287b5a12..9b2af5fb5 100644 --- a/docs/vpc/umn/vpc_vip_0003.html +++ b/docs/vpc/umn/vpc_vip_0003.html @@ -5,7 +5,7 @@

                                                                                            Prerequisites

                                                                                            • You have assigned an EIP.
                                                                                            -

                                                                                            Procedure

                                                                                            1. Log in to the management console.
                                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                                            3. Click in the upper left corner and choose Network > Elastic IP.

                                                                                              The EIP list page is displayed.

                                                                                              +

                                                                                              Procedure

                                                                                              1. Log in to the management console.
                                                                                              2. Click in the upper left corner and select the desired region and project.
                                                                                              3. Click in the upper left corner and choose Network > Elastic IP.

                                                                                                The EIP list page is displayed.

                                                                                              4. Locate the row that contains the EIP to be bound to the virtual IP address, and click Bind in the Operation column.
                                                                                              5. In the Bind EIP dialog box, set Instance Type to Virtual IP address.
                                                                                              6. In the virtual IP address list, select the virtual IP address to be bound and click OK.
                                                                                            diff --git a/docs/vpc/umn/vpc_vip_0008.html b/docs/vpc/umn/vpc_vip_0008.html index 531d6595f..28f7981e4 100644 --- a/docs/vpc/umn/vpc_vip_0008.html +++ b/docs/vpc/umn/vpc_vip_0008.html @@ -3,7 +3,7 @@

                                                                                            Disabling Source and Destination Check (HA Load Balancing Cluster Scenario)

                                                                                            Scenarios

                                                                                            If a virtual IP address is used in an HA load balancing cluster, you need to disable source/destination check for ECS NICs.

                                                                                            -

                                                                                            Procedure

                                                                                            1. Log in to the management console.
                                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                                            3. In the upper left corner of the page, click . In the service list, choose Computing > Elastic Cloud Server.
                                                                                            4. In the ECS list, click the ECS name.
                                                                                            5. On the displayed ECS details page, click the NICs tab.
                                                                                            6. Click the IP address to view the NIC details.
                                                                                            7. Check that Source/Destination Check is disabled.
                                                                                            +

                                                                                            Procedure

                                                                                            1. Log in to the management console.
                                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                                            3. In the upper left corner of the page, click . In the service list, choose Computing > Elastic Cloud Server.
                                                                                            4. In the ECS list, click the ECS name.
                                                                                            5. On the displayed ECS details page, click the NICs tab.
                                                                                            6. Click the IP address to view the NIC details.
                                                                                            7. Check that Source/Destination Check is disabled.
                                                                                            diff --git a/docs/vpc/umn/vpc_vip_0009.html b/docs/vpc/umn/vpc_vip_0009.html index cd0253fa4..5548d67e4 100644 --- a/docs/vpc/umn/vpc_vip_0009.html +++ b/docs/vpc/umn/vpc_vip_0009.html @@ -12,9 +12,9 @@
                                                                                      - @@ -28,7 +28,7 @@ -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      2. Click in the upper left corner and select the desired region and project.
                                                                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
                                                                                        5. Click the name of the subnet that the virtual IP address belongs to.
                                                                                        6. Click the IP Addresses tab, locate the row that contains the virtual IP address to be released, click More in the Operation column, and select Release.

                                                                                          A confirmation dialog box is displayed.

                                                                                        7. Confirm the information and click Yes.
                                                                                        diff --git a/docs/vpc/umn/vpc_vip_0010.html b/docs/vpc/umn/vpc_vip_0010.html index e61307001..280ae132c 100644 --- a/docs/vpc/umn/vpc_vip_0010.html +++ b/docs/vpc/umn/vpc_vip_0010.html @@ -3,11 +3,11 @@

                                                                                        Unbinding a Virtual IP Address from an Instance

                                                                                        Scenarios

                                                                                        This section describes how to unbind a virtual IP address from an ECS.

                                                                                        -

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                          +

                                                                                          Procedure

                                                                                          1. Log in to the management console.
                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                            The Virtual Private Cloud page is displayed.

                                                                                          4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                            The Subnets page is displayed.

                                                                                          5. Click the name of the subnet that the virtual IP address belongs to.

                                                                                            The Summary page is displayed.

                                                                                          6. Click the IP Addresses tab.

                                                                                            The virtual IP address list is displayed.

                                                                                            -
                                                                                            Figure 1 Virtual IP addresses
                                                                                            +
                                                                                            Figure 1 Virtual IP addresses
                                                                                          7. Locate the row that contains the virtual IP address, click More in the Operation column, and select Unbind from Server.

                                                                                            The Bound Server dialog box is displayed.

                                                                                          8. Unbind the virtual IP address from the instance.
                                                                                            1. Select the type of the instance bound to the virtual IP address.
                                                                                            2. Locate the row that contains the instance and click Unbind in the Operation column.

                                                                                              A confirmation dialog box is displayed.

                                                                                            3. Confirm the information and click Yes.
                                                                                            diff --git a/docs/vpc/umn/vpc_vip_0011.html b/docs/vpc/umn/vpc_vip_0011.html index d8ec93bf4..f8bfd2e64 100644 --- a/docs/vpc/umn/vpc_vip_0011.html +++ b/docs/vpc/umn/vpc_vip_0011.html @@ -3,7 +3,7 @@

                                                                                            Unbinding a Virtual IP Address from an EIP

                                                                                            Scenarios

                                                                                            This section describes how to unbind a virtual IP address from an EIP.

                                                                                            -

                                                                                            Procedure

                                                                                            1. Log in to the management console.
                                                                                            2. Click in the upper left corner and select the desired region and project.
                                                                                            3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                              The Virtual Private Cloud page is displayed.

                                                                                              +

                                                                                              Procedure

                                                                                              1. Log in to the management console.
                                                                                              2. Click in the upper left corner and select the desired region and project.
                                                                                              3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                The Virtual Private Cloud page is displayed.

                                                                                              4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                                The Subnets page is displayed.

                                                                                              5. Click the name of the subnet that the virtual IP address belongs to.

                                                                                                The Summary page is displayed.

                                                                                              6. Click the IP Addresses tab.

                                                                                                The virtual IP address list is displayed.

                                                                                                diff --git a/docs/vpc/umn/vpc_vpc_0001.html b/docs/vpc/umn/vpc_vpc_0001.html index 867827d05..4311f2229 100644 --- a/docs/vpc/umn/vpc_vpc_0001.html +++ b/docs/vpc/umn/vpc_vpc_0001.html @@ -3,10 +3,10 @@

                                                                                                Modifying a Subnet

                                                                                                Scenarios

                                                                                                Modify the subnet name, NTP server address, and DNS server address.

                                                                                                -

                                                                                                Procedure

                                                                                                1. Log in to the management console.
                                                                                                1. Click in the upper left corner and select the desired region and project.
                                                                                                2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                  The Virtual Private Cloud page is displayed.

                                                                                                  +

                                                                                                  Procedure

                                                                                                  1. Log in to the management console.
                                                                                                  1. Click in the upper left corner and select the desired region and project.
                                                                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                    The Virtual Private Cloud page is displayed.

                                                                                                  3. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                                    The Subnets page is displayed.

                                                                                                  4. In the subnet list, locate the target subnet and click its name.

                                                                                                    The subnet details page is displayed.

                                                                                                    -
                                                                                                  5. On the Summary tab, click on the right of the parameter to be modified and modify the parameter as prompted. +
                                                                                                  6. On the Summary tab, click on the right of the parameter to be modified and modify the parameter as prompted.
                                                                                      Table 1 Route replication

                                                                                      Next Hop Type

                                                                                      Can Be Replicated to Default Route Table

                                                                                      No

                                                                                      Server

                                                                                      +

                                                                                      Server

                                                                                      Yes

                                                                                      Yes

                                                                                      Extension NIC

                                                                                      +

                                                                                      Extension NIC

                                                                                      Yes

                                                                                      Yes

                                                                                      VPN connection

                                                                                      +

                                                                                      VPN connection

                                                                                      No

                                                                                      Yes

                                                                                      Direct Connect gateway

                                                                                      +

                                                                                      Direct Connect gateway

                                                                                      No

                                                                                      Yes

                                                                                      NAT gateway

                                                                                      +

                                                                                      NAT gateway

                                                                                      Yes

                                                                                      Yes

                                                                                      VPC peering connection

                                                                                      +

                                                                                      VPC peering connection

                                                                                      Yes

                                                                                      Yes

                                                                                      Virtual IP address

                                                                                      +

                                                                                      Virtual IP address

                                                                                      Yes

                                                                                      This operation cannot be performed because the IP address is bound to an instance or an EIP. Unbind the IP address and try again.

                                                                                      This virtual IP address is being by an EIP or an ECS.

                                                                                      +

                                                                                      This virtual IP address is being used by an EIP or an ECS.

                                                                                      Unbind the virtual IP address first.

                                                                                      - +

                                                                                      Release the virtual IP address.
                                                                                      Table 1 Parameter descriptions

                                                                                      Parameter

                                                                                      Description

                                                                                      diff --git a/docs/vpc/umn/vpc_vpc_0002.html b/docs/vpc/umn/vpc_vpc_0002.html index 33c3b6725..083d1c640 100644 --- a/docs/vpc/umn/vpc_vpc_0002.html +++ b/docs/vpc/umn/vpc_vpc_0002.html @@ -6,10 +6,10 @@

                                                                                      Notes and Constraints

                                                                                      If you want to delete a subnet that has custom routes, virtual IP addresses, or other resources, you need to delete these resources as prompted on the console first and then delete the subnet.

                                                                                      You can refer to Why Can't I Delete My VPCs and Subnets?

                                                                                      -

                                                                                      Procedure

                                                                                      1. Log in to the management console.
                                                                                      2. Click in the upper left corner and select the desired region and project.
                                                                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                        4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                          The Subnets page is displayed.

                                                                                        5. In the subnet list, locate the row that contains the subnet you want to delete and click Delete in the Operation column.

                                                                                          A confirmation dialog box is displayed.

                                                                                          -
                                                                                        6. Click Yes.

                                                                                          If a VPC cannot be deleted, a message will be displayed on the console. Delete the resources that are in the VPC by referring to Why Can't I Delete My VPCs and Subnets?

                                                                                          +
                                                                                        7. Click Yes.

                                                                                          If a subnet cannot be deleted, a message will be displayed on the console. Delete the resources that are in the subnet by referring to Why Can't I Delete My VPCs and Subnets?

                                                                                        diff --git a/docs/vpc/umn/vpc_vpc_0003.html b/docs/vpc/umn/vpc_vpc_0003.html index ca5259f45..4344d3f41 100644 --- a/docs/vpc/umn/vpc_vpc_0003.html +++ b/docs/vpc/umn/vpc_vpc_0003.html @@ -6,7 +6,7 @@

                                                                                        Notes and Constraints

                                                                                        If you want to delete a VPC that has subnets, custom routes, or other resources, you need to delete these resources as prompted on the console first and then delete the VPC.

                                                                                        You can refer to Why Can't I Delete My VPCs and Subnets?

                                                                                        -

                                                                                        Procedure

                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                          +

                                                                                          Procedure

                                                                                          1. Log in to the management console.
                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                            The Virtual Private Cloud page is displayed.

                                                                                          4. On the Virtual Private Cloud page, locate the row that contains the VPC to be deleted and click Delete in the Operation column.

                                                                                            A confirmation dialog box is displayed.

                                                                                          5. Confirm the information and click Yes.

                                                                                            If a VPC cannot be deleted, a message will be displayed on the console. Delete the resources that are in the VPC by referring to Why Can't I Delete My VPCs and Subnets?

                                                                                            diff --git a/docs/vpc/umn/vpc_vpc_0004.html b/docs/vpc/umn/vpc_vpc_0004.html index 21290da4f..26725c9fd 100644 --- a/docs/vpc/umn/vpc_vpc_0004.html +++ b/docs/vpc/umn/vpc_vpc_0004.html @@ -33,13 +33,13 @@
                                                                                      -

                                                                                      Procedure

                                                                                      Search for VPCs by tag key and value on the page showing the VPC list.
                                                                                      1. Log in to the management console.
                                                                                      2. Click in the upper left corner and select the desired region and project.
                                                                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                        The Virtual Private Cloud page is displayed.

                                                                                        -
                                                                                      4. In the search box above the VPC list, click anywhere in the search box.

                                                                                        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 VPCs, the VPCs containing all specified tags will be displayed.

                                                                                        +

                                                                                        Procedure

                                                                                        Search for VPCs by tag key and value on the page showing the VPC list.
                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                          +
                                                                                        4. In the search box above the VPC list, click anywhere in the search box.

                                                                                          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 VPCs, the VPCs containing all specified tags will be displayed.

                                                                                        -
                                                                                        Add, delete, edit, and view tags on the Tags tab of a VPC.
                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                          +
                                                                                          Add, delete, edit, and view tags on the Tags tab of a VPC.
                                                                                          1. Log in to the management console.
                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                            The Virtual Private Cloud page is displayed.

                                                                                          4. On the Virtual Private Cloud page, locate the VPC whose tags are to be managed and click the VPC name.

                                                                                            The page showing details about the particular VPC is displayed.

                                                                                          5. 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 VPC, including the number of tags and the key and value of each tag.

                                                                                            • Add a tag.

                                                                                              Click Add Tag in the upper left corner. In the displayed Add Tag dialog box, enter the tag key and value, and click OK.

                                                                                              diff --git a/docs/vpc/umn/vpc_vpc_0005.html b/docs/vpc/umn/vpc_vpc_0005.html index 254576706..2bf2d5b1c 100644 --- a/docs/vpc/umn/vpc_vpc_0005.html +++ b/docs/vpc/umn/vpc_vpc_0005.html @@ -33,17 +33,17 @@
                                                                                        -

                                                                                        Procedure

                                                                                        Search for subnets by tag key and value on the page showing the subnet list.
                                                                                        1. Log in to the management console.
                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                          The Virtual Private Cloud page is displayed.

                                                                                          -
                                                                                        4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                          The Subnets page is displayed.

                                                                                          +

                                                                                          Procedure

                                                                                          Search for subnets by tag key and value on the page showing the subnet list.
                                                                                          1. Log in to the management console.
                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                            The Virtual Private Cloud page is displayed.

                                                                                            +
                                                                                          4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                            The Subnets page is displayed.

                                                                                          5. In the search box above the subnet list, click the search box.

                                                                                            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 VPCs, the VPCs containing all specified tags will be displayed.

                                                                                          -
                                                                                          Add, delete, edit, and view tags on the Tags tab of a subnet.
                                                                                          1. Log in to the management console.
                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                            The Virtual Private Cloud page is displayed.

                                                                                            -
                                                                                          4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                            The Subnets page is displayed.

                                                                                            -
                                                                                          5. In the subnet list, locate the target subnet and click its name.
                                                                                          6. On the subnet details page, 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 subnet, 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.

                                                                                              +
                                                                                              Add, delete, edit, and view tags on the Tags tab of a subnet.
                                                                                              1. Log in to the management console.
                                                                                              2. Click in the upper left corner and select the desired region and project.
                                                                                              3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                The Virtual Private Cloud page is displayed.

                                                                                                +
                                                                                              4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                                The Subnets page is displayed.

                                                                                                +
                                                                                              5. In the subnet list, locate the target subnet and click its name.
                                                                                              6. On the subnet details page, 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 subnet, 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 key and value, and click OK.

                                                                                                • 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.

                                                                                                diff --git a/docs/vpc/umn/vpc_vpc_0006.html b/docs/vpc/umn/vpc_vpc_0006.html index 3710c191c..10cc12361 100644 --- a/docs/vpc/umn/vpc_vpc_0006.html +++ b/docs/vpc/umn/vpc_vpc_0006.html @@ -4,8 +4,8 @@

                                                                                                Scenarios

                                                                                                Information about all VPCs under your account can be exported as an Excel file to a local directory.

                                                                                                This file records the names, ID, status, CIDR blocks, and the number of subnets of your VPCs.

                                                                                                -

                                                                                                Procedure

                                                                                                1. Log in to the management console.
                                                                                                2. Click in the upper left corner and select the desired region and project.
                                                                                                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                  The Virtual Private Cloud page is displayed.

                                                                                                  -
                                                                                                4. In the upper right corner of the VPC list, click .

                                                                                                  The system will automatically export information about all VPCs under your account in the current region as an Excel file to a local directory.

                                                                                                  +

                                                                                                  Procedure

                                                                                                  1. Log in to the management console.
                                                                                                  2. Click in the upper left corner and select the desired region and project.
                                                                                                  3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                    The Virtual Private Cloud page is displayed.

                                                                                                    +
                                                                                                  4. In the VPC list, select one or more VPCs you want to export and click Export in the upper left corner.

                                                                                                    The system will automatically export information about all of your VPCs as an Excel file to a local directory.

                                                                                                diff --git a/docs/vpc/umn/vpc_vpc_0007.html b/docs/vpc/umn/vpc_vpc_0007.html new file mode 100644 index 000000000..71c8d0b8f --- /dev/null +++ b/docs/vpc/umn/vpc_vpc_0007.html @@ -0,0 +1,47 @@ + + +

                                                                                                Adding a Secondary IPv4 CIDR Block to a VPC

                                                                                                +

                                                                                                Scenarios

                                                                                                When you create a VPC, you specify a primary IPv4 CIDR block for the VPC, which cannot be changed. To extend the IP address range of your VPC, you can add a secondary CIDR block to the VPC. Five secondary CIDR blocks can be added.

                                                                                                +

                                                                                                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. You can call an API to modify VPC CIDR block by referring to Updating VPC Information.

                                                                                                +
                                                                                                +
                                                                                                +

                                                                                                Notes and Constraints

                                                                                                • You can allocate a subnet from either a primary or a secondary CIDR block of a VPC. A subnet cannot use both the primary and the secondary CIDR blocks.

                                                                                                  Subnets in the same VPC can communicate with each other by default, even if some subnets are allocated from the primary CIDR block and some are from the secondary CIDR block of a VPC.

                                                                                                  +
                                                                                                • If a subnet in a secondary CIDR block of your VPC is the same as or overlaps with the destination of an existing route in the VPC route table, the existing route does not take effect.

                                                                                                  If you create a subnet in a secondary CIDR block of your VPC, a route (the destination is the subnet CIDR block and the next hop is Local) is automatically added to your VPC route table. This route allows communications within the VPC and has a higher priority than any other routes in the VPC route table. For example, if a VPC route table has a route with the VPC peering connection as the next hop and 100.20.0.0/24 as the destination, and a route for the subnet in the secondary CIDR block has a destination of 100.20.0.0/16, 100.20.0.0/16 and 100.20.0.0/24 overlaps and traffic will be forwarded through the route of the subnet.

                                                                                                  +
                                                                                                • Table 1 lists the secondary CIDR blocks that are not supported. +
                                                                                                  + + + + + + + + + + + + + +
                                                                                                  Table 1 Restricted secondary CIDR blocks

                                                                                                  Type

                                                                                                  +

                                                                                                  CIDR Block (Not Supported)

                                                                                                  +

                                                                                                  Reserved private CIDR blocks

                                                                                                  +
                                                                                                  • 172.31.0.0/16
                                                                                                  • 192.168.0.0/16
                                                                                                  • In-use primary CIDR blocks
                                                                                                  +

                                                                                                  Reserved system CIDR blocks

                                                                                                  +
                                                                                                  • 100.64.0.0/10
                                                                                                  • 214.0.0.0/7
                                                                                                  • 198.18.0.0/15
                                                                                                  • 169.254.0.0/16
                                                                                                  +

                                                                                                  Reserved public CIDR blocks

                                                                                                  +
                                                                                                  • 0.0.0.0/8
                                                                                                  • 127.0.0.0/8
                                                                                                  • 240.0.0.0/4
                                                                                                  • 255.255.255.255/32
                                                                                                  +
                                                                                                  +
                                                                                                  +
                                                                                                +
                                                                                                +

                                                                                                Procedure

                                                                                                1. Log in to the management console.
                                                                                                2. Click in the upper left corner and select the desired region and project.
                                                                                                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                  The Virtual Private Cloud page is displayed.

                                                                                                  +
                                                                                                4. In the VPC list, locate the target VPC and click Edit CIDR Block in the Operation column.

                                                                                                  The Edit CIDR Block dialog box is displayed.

                                                                                                  +
                                                                                                5. Click Add Secondary IPv4 CIDR Block.
                                                                                                6. Enter the secondary CIDR block and click OK.
                                                                                                +
                                                                                                +
                                                                                                +
                                                                                                +
                                                                                                +
                                                                                                Parent topic: VPC
                                                                                                +
                                                                                                +
                                                                                                + diff --git a/docs/vpc/umn/vpc_vpc_0008.html b/docs/vpc/umn/vpc_vpc_0008.html new file mode 100644 index 000000000..2879371f4 --- /dev/null +++ b/docs/vpc/umn/vpc_vpc_0008.html @@ -0,0 +1,17 @@ + + +

                                                                                                Deleting a Secondary IPv4 CIDR Block from a VPC

                                                                                                +

                                                                                                Scenarios

                                                                                                If a secondary CIDR block of a VPC is no longer required, you can delete it.
                                                                                                • A secondary IPv4 CIDR block of a VPC can be deleted, but the primary CIDR block cannot be deleted.
                                                                                                • If you want to delete a secondary CIDR block that contains subnets, you need to delete the subnets first.
                                                                                                +
                                                                                                +
                                                                                                +

                                                                                                Procedure

                                                                                                1. Log in to the management console.
                                                                                                2. Click in the upper left corner and select the desired region and project.
                                                                                                3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                  The Virtual Private Cloud page is displayed.

                                                                                                  +
                                                                                                4. In the VPC list, locate the target VPC and click Edit CIDR Block in the Operation column.

                                                                                                  The Edit CIDR Block dialog box is displayed.

                                                                                                  +
                                                                                                5. Locate the row that contains the secondary CIDR block to be deleted and click Delete in the Operation column.
                                                                                                6. Click OK.
                                                                                                +
                                                                                                +
                                                                                                +
                                                                                                +
                                                                                                +
                                                                                                Parent topic: VPC
                                                                                                +
                                                                                                +
                                                                                                + diff --git a/docs/vpc/umn/vpc_vpc_0009.html b/docs/vpc/umn/vpc_vpc_0009.html index b6b1e2a0e..7ba7178d9 100644 --- a/docs/vpc/umn/vpc_vpc_0009.html +++ b/docs/vpc/umn/vpc_vpc_0009.html @@ -3,7 +3,7 @@

                                                                                                Viewing a VPC Topology

                                                                                                Scenarios

                                                                                                This section describes how to view the topology of a VPC. The topology displays the subnets in a VPC and the ECSs in the subnets.

                                                                                                -

                                                                                                Procedure

                                                                                                1. Log in to the management console.
                                                                                                1. Click in the upper left corner and select the desired region and project.
                                                                                                2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                  The Virtual Private Cloud page is displayed.

                                                                                                  +

                                                                                                  Procedure

                                                                                                  1. Log in to the management console.
                                                                                                  1. Click in the upper left corner and select the desired region and project.
                                                                                                  2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                    The Virtual Private Cloud page is displayed.

                                                                                                  3. In the VPC list, click the name of the VPC for which the topology is to be viewed.

                                                                                                    The VPC details page is displayed.

                                                                                                  4. Click the Topology tab to view the VPC topology.

                                                                                                    The topology displays the subnets in the VPC and the ECSs in the subnets.

                                                                                                    You can also perform the following operations on subnets and ECSs in the topology:
                                                                                                    • Modify or delete a subnet.
                                                                                                    • Add an ECS to a subnet, bind an EIP to the ECS, and change the security group of the ECS.
                                                                                                    diff --git a/docs/vpc/umn/vpc_vpc_0010.html b/docs/vpc/umn/vpc_vpc_0010.html index bb70f9b84..33ec0957e 100644 --- a/docs/vpc/umn/vpc_vpc_0010.html +++ b/docs/vpc/umn/vpc_vpc_0010.html @@ -3,9 +3,9 @@

                                                                                                    Exporting Subnet List

                                                                                                    Scenarios

                                                                                                    Information about all subnets under your account can be exported as an Excel file to a local directory. This file records the name, ID, VPC, CIDR block, and associated route table of each subnet.

                                                                                                    -

                                                                                                    Procedure

                                                                                                    1. Log in to the management console.
                                                                                                    2. Click in the upper left corner and select the desired region and project.
                                                                                                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                      The Virtual Private Cloud page is displayed.

                                                                                                      +

                                                                                                      Procedure

                                                                                                      1. Log in to the management console.
                                                                                                      2. Click in the upper left corner and select the desired region and project.
                                                                                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                        The Virtual Private Cloud page is displayed.

                                                                                                      4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                                        The Subnets page is displayed.

                                                                                                        -
                                                                                                      5. In the upper right corner of the subnet list, click .

                                                                                                        The system will automatically export information about all subnets under your account in the current region as an Excel file to a local directory.

                                                                                                        +
                                                                                                      6. In the subnet list, select one or more subnets you want to export and click Export in the upper left corner.

                                                                                                        The system will automatically export information about all of your subnets as an Excel file to a local directory.

                                                                                                    diff --git a/docs/vpc/umn/vpc_vpc_0011.html b/docs/vpc/umn/vpc_vpc_0011.html index ccef6276c..813660af3 100644 --- a/docs/vpc/umn/vpc_vpc_0011.html +++ b/docs/vpc/umn/vpc_vpc_0011.html @@ -6,11 +6,11 @@

                                                                                                    After you delete all resources in a subnet by referring to this section, the message "Delete the resource that is using the subnet and then delete the subnet." is displayed when you delete the subnet, you can refer to Viewing IP Addresses in a Subnet.

                                                                                                    -

                                                                                                    Procedure

                                                                                                    1. Log in to the management console.
                                                                                                    2. Click in the upper left corner and select the desired region and project.
                                                                                                    3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                      The Virtual Private Cloud page is displayed.

                                                                                                      +

                                                                                                      Procedure

                                                                                                      1. Log in to the management console.
                                                                                                      2. Click in the upper left corner and select the desired region and project.
                                                                                                      3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                        The Virtual Private Cloud page is displayed.

                                                                                                      4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                                        The Subnets page is displayed.

                                                                                                      5. Locate the target subnet and click its name.

                                                                                                        The subnet details page is displayed.

                                                                                                      6. On the Summary page, view the resources in the subnet.
                                                                                                        1. In the VPC Resources area, view the quantities of resources, such as ECSs, BMSs, network interfaces, and load balancers, in the subnet. Click the resource quantity with a hyperlink to view the resources in the subnet.
                                                                                                        2. In the Networking Components area on the right of the page, view the NAT gateway, route table, and subnet.
                                                                                                        -
                                                                                                        Figure 1 Viewing resources in a subnet
                                                                                                        +
                                                                                                        Figure 1 Viewing resources in a subnet
                                                                                                      7. Delete resources from the subnet.
                                                                                                        @@ -43,7 +43,7 @@ diff --git a/docs/vpc/umn/vpc_vpc_0012.html b/docs/vpc/umn/vpc_vpc_0012.html index 52285c322..079ae11c4 100644 --- a/docs/vpc/umn/vpc_vpc_0012.html +++ b/docs/vpc/umn/vpc_vpc_0012.html @@ -7,13 +7,13 @@

                                                                                                        Notes and Constraints

                                                                                                        • A subnet cannot be deleted if its IP addresses are used by cloud resources.
                                                                                                        • A subnet can be deleted if its IP addresses are used by itself.
                                                                                                        -

                                                                                                        Procedure

                                                                                                        1. Log in to the management console.
                                                                                                        2. Click in the upper left corner and select the desired region and project.
                                                                                                        3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                          The Virtual Private Cloud page is displayed.

                                                                                                          +

                                                                                                          Procedure

                                                                                                          1. Log in to the management console.
                                                                                                          2. Click in the upper left corner and select the desired region and project.
                                                                                                          3. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                            The Virtual Private Cloud page is displayed.

                                                                                                          4. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.

                                                                                                            The Subnets page is displayed.

                                                                                                          5. Locate the target subnet and click its name.

                                                                                                            The subnet details page is displayed.

                                                                                                          6. Click the IP Addresses tab to view the IP addresses in the subnet.
                                                                                                            1. In the virtual IP address list, you can view the virtual IP addresses assigned from the subnet.
                                                                                                            2. In the private IP address list in the lower part of the page, you can view the private IP addresses used by the subnet (gateway, system interface, and DHCP).
                                                                                                          -

                                                                                                          Follow-up Operations

                                                                                                          If you want to view and delete the resources in a subnet, refer to Why Can't I Delete My VPCs and Subnets?

                                                                                                          +

                                                                                                          Follow-up Operations

                                                                                                          If you want to view and delete the resources in the subnet, refer to Why Can't I Delete My VPCs and Subnets?

                                                                                                          diff --git a/docs/vpc/umn/vpc_vpc_0013.html b/docs/vpc/umn/vpc_vpc_0013.html index f88b2f141..29df0342b 100644 --- a/docs/vpc/umn/vpc_vpc_0013.html +++ b/docs/vpc/umn/vpc_vpc_0013.html @@ -4,9 +4,9 @@

                                                                                                          Scenarios

                                                                                                          This section describes how to view and obtain a VPC ID.

                                                                                                          If you create a VPC peering connection between two VPCs in different accounts, you need to obtain the project ID of the region that the peer VPC resides. You can recommend this section to the user of the peer VPC to obtain the project ID.

                                                                                                          -

                                                                                                          Procedure

                                                                                                          1. Log in to the management console.
                                                                                                          1. Click in the upper left corner and select the desired region and project.
                                                                                                          2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                            The Virtual Private Cloud page is displayed.

                                                                                                            +

                                                                                                            Procedure

                                                                                                            1. Log in to the management console.
                                                                                                            1. Click in the upper left corner and select the desired region and project.
                                                                                                            2. Click in the upper left corner and choose Network > Virtual Private Cloud.

                                                                                                              The Virtual Private Cloud page is displayed.

                                                                                                            3. On the Virtual Private Cloud page, locate the VPC and click its name.

                                                                                                              The VPC details page is displayed.

                                                                                                              -
                                                                                                            4. In the VPC Information area, view the VPC ID.

                                                                                                              Click next to ID to copy the VPC ID.

                                                                                                              +
                                                                                                            5. In the VPC Information area, view the VPC ID.

                                                                                                              Click next to ID to copy the VPC ID.

                                                                                                        Table 1 Viewing and deleting resources in a subnet

                                                                                                        Resource

                                                                                                        You can directly switch to NAT gateways from the subnet details page.

                                                                                                        1. Click the NAT gateway name in the Networking Components area.

                                                                                                          The NAT gateway details page is displayed.

                                                                                                          -
                                                                                                        2. Click to return to the NAT gateway list.
                                                                                                        3. Locate the row that contains the NAT gateway and click Delete in the Operation column. +
                                                                                                        4. Click to return to the NAT gateway list.
                                                                                                        5. Locate the row that contains the NAT gateway and click Delete in the Operation column.