forked from docs/virtual-private-cloud
Update content
This commit is contained in:
parent
0b15f652d1
commit
0bc1e75222
Binary file not shown.
|
Before Width: | Height: | Size: 1004 B |
Binary file not shown.
|
Before Width: | Height: | Size: 1004 B |
Binary file not shown.
|
Before Width: | Height: | Size: 128 B |
Binary file not shown.
|
Before Width: | Height: | Size: 128 B |
@ -23,7 +23,7 @@ For details, see :ref:`Figure 1 <en-us_topic_0052003963__fig9582182315479>`.
|
||||
|
||||
.. _en-us_topic_0052003963__table53053071174845:
|
||||
|
||||
.. table:: **Table 1** Differences between security groups firewalls
|
||||
.. table:: **Table 1** Differences between security groups and firewalls
|
||||
|
||||
+-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Category | Security Group | Firewall |
|
||||
|
||||
@ -8,7 +8,7 @@ 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.
|
||||
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 :ref:`Default Security Group and Its Rules <securitygroup_0003>`.
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ Change History
|
||||
+===================================+====================================================================================================================================================================================================================================================================================================================================+
|
||||
| 2024-02-18 | This release incorporates the following changes: |
|
||||
| | |
|
||||
| | Added :ref:`Adding a Secondary IPv4 CIDR Block to a VPC <vpc_vpc_0007>`, :ref:`Deleting a Secondary IPv4 CIDR Block from a VPC <vpc_vpc_0008>`, and :ref:`What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs? <en-us_topic_0000001799161498>` |
|
||||
| | Added :ref:`What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs? <en-us_topic_0000001799161498>` |
|
||||
+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2024-02-02 | This release incorporates the following changes: |
|
||||
| | |
|
||||
|
||||
@ -5,9 +5,9 @@
|
||||
What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth?
|
||||
==============================================================================
|
||||
|
||||
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 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 workloads.
|
||||
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.
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@
|
||||
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.
|
||||
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:
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ A subnet is a unique CIDR block with a range of IP addresses in a VPC. All resou
|
||||
|
||||
- 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.
|
||||
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.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ If you bind a virtual IP address to ECSs that work in active/standby pairs and b
|
||||
Notes and Constraints
|
||||
---------------------
|
||||
|
||||
- Each virtual IP address can be bound to only one EIP.
|
||||
- A virtual IP address can only be bound to one EIP.
|
||||
|
||||
Binding a Virtual IP Address to an EIP or ECS on the Console
|
||||
------------------------------------------------------------
|
||||
@ -61,7 +61,7 @@ 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.
|
||||
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
|
||||
|
||||
@ -1,64 +0,0 @@
|
||||
:original_name: vpc_vpc_0007.html
|
||||
|
||||
.. _vpc_vpc_0007:
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
- :ref:`Table 1 <vpc_vpc_0007__table1060431941314>` lists the secondary CIDR blocks that are not supported.
|
||||
|
||||
.. _vpc_vpc_0007__table1060431941314:
|
||||
|
||||
.. table:: **Table 1** Restricted secondary CIDR blocks
|
||||
|
||||
+-----------------------------------+-----------------------------------+
|
||||
| Type | CIDR Block (Not Supported) |
|
||||
+===================================+===================================+
|
||||
| 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
|
||||
---------
|
||||
|
||||
#. Log in to the management console.
|
||||
|
||||
#. Click |image1| in the upper left corner and select the desired region and project.
|
||||
|
||||
#. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**.
|
||||
|
||||
The **Virtual Private Cloud** page is displayed.
|
||||
|
||||
#. 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.
|
||||
|
||||
#. Click **Add Secondary IPv4 CIDR Block**.
|
||||
|
||||
#. Enter the secondary CIDR block and click **OK**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001429281925.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001626574374.png
|
||||
@ -1,36 +0,0 @@
|
||||
:original_name: vpc_vpc_0008.html
|
||||
|
||||
.. _vpc_vpc_0008:
|
||||
|
||||
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
|
||||
---------
|
||||
|
||||
#. Log in to the management console.
|
||||
|
||||
#. Click |image1| in the upper left corner and select the desired region and project.
|
||||
|
||||
#. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**.
|
||||
|
||||
The **Virtual Private Cloud** page is displayed.
|
||||
|
||||
#. 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.
|
||||
|
||||
#. Locate the row that contains the secondary CIDR block to be deleted and click **Delete** in the **Operation** column.
|
||||
|
||||
#. Click **OK**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001429973081.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001627054074.png
|
||||
@ -7,8 +7,6 @@ VPC
|
||||
|
||||
- :ref:`Creating a VPC <en-us_topic_0013935842>`
|
||||
- :ref:`Modifying a VPC <en-us_topic_0030969462>`
|
||||
- :ref:`Adding a Secondary IPv4 CIDR Block to a VPC <vpc_vpc_0007>`
|
||||
- :ref:`Deleting a Secondary IPv4 CIDR Block from a VPC <vpc_vpc_0008>`
|
||||
- :ref:`Deleting a VPC <vpc_vpc_0003>`
|
||||
- :ref:`Managing VPC Tags <vpc_vpc_0004>`
|
||||
- :ref:`Exporting VPC List <vpc_vpc_0006>`
|
||||
@ -21,8 +19,6 @@ VPC
|
||||
|
||||
creating_a_vpc
|
||||
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
|
||||
exporting_vpc_list
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user