forked from docs/virtual-private-cloud
Update content
This commit is contained in:
parent
8073cc0fb6
commit
70096c5d6a
@ -16,7 +16,6 @@ After users who use IPv6 clients bind an IPv6 EIP to an ECS, the data flow is sh
|
||||
.. figure:: /_static/images/en-us_image_0118499144.png
|
||||
:alt: **Figure 1** IPv6 data flow
|
||||
|
||||
|
||||
**Figure 1** IPv6 data flow
|
||||
|
||||
The IPv6 service has the following restrictions:
|
||||
|
@ -13,5 +13,4 @@ Each EIP can be used by only one cloud resource at a time.
|
||||
.. figure:: /_static/images/en-us_image_0209583952.png
|
||||
:alt: **Figure 1** Accessing the Internet using an EIP
|
||||
|
||||
|
||||
**Figure 1** Accessing the Internet using an EIP
|
||||
|
@ -21,5 +21,4 @@ The following figure provides an example of the security group rule configuratio
|
||||
.. figure:: /_static/images/en-us_image_0129473334.png
|
||||
:alt: **Figure 1** Security group rules
|
||||
|
||||
|
||||
**Figure 1** Security group rules
|
||||
|
@ -13,5 +13,4 @@ Within your own VPC, you can create security groups and VPNs, configure IP addre
|
||||
.. figure:: /_static/images/en-us_image_0209606948.png
|
||||
:alt: **Figure 1** VPC components
|
||||
|
||||
|
||||
**Figure 1** VPC components
|
||||
|
@ -5,4 +5,4 @@
|
||||
What Subnet CIDR Blocks Are Available?
|
||||
======================================
|
||||
|
||||
A subnet CIDR block must be included in its VPC CIDR block. Supported VPC CIDR blocks are **10.0.0.0/8–24**, **172.16.0.0/12–24**, and **192.168.0.0/16–24**. The allowed block size of a subnet is between the netmask of its VPC CIDR block and the /29 netmask.
|
||||
A subnet CIDR block must be included in its VPC CIDR block. Supported VPC CIDR blocks are **10.0.0.0/8-24**, **172.16.0.0/12-24**, and **192.168.0.0/16-24**. The allowed block size of a subnet is between the netmask of its VPC CIDR block and the /29 netmask.
|
||||
|
@ -12,7 +12,6 @@ If your ECSs need to access the Internet (for example, the ECSs functioning as t
|
||||
.. figure:: /_static/images/en-us_image_0162332046.png
|
||||
:alt: **Figure 1** Configuring the network
|
||||
|
||||
|
||||
**Figure 1** Configuring the network
|
||||
|
||||
:ref:`Table 1 <vpc_qs_0022__en-us_topic_0118499056_t5143cea7d59f4c31b1c56ab35e86f71f>` describes the different tasks in the procedure for configuring the network.
|
||||
|
@ -33,7 +33,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001197228903.png
|
||||
:alt: **Figure 1** Create Subnet
|
||||
|
||||
|
||||
**Figure 1** Create Subnet
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -35,7 +35,6 @@ Assigning an EIP
|
||||
.. figure:: /_static/images/en-us_image_0000001117669274.png
|
||||
:alt: **Figure 1** Assign EIP
|
||||
|
||||
|
||||
**Figure 1** Assign EIP
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
@ -102,7 +101,6 @@ Binding an EIP
|
||||
.. figure:: /_static/images/en-us_image_0000001166028070.png
|
||||
:alt: **Figure 2** Bind EIP
|
||||
|
||||
|
||||
**Figure 2** Bind EIP
|
||||
|
||||
#. Click **OK**.
|
||||
|
@ -29,7 +29,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001197426329.png
|
||||
:alt: **Figure 1** Create Security Group
|
||||
|
||||
|
||||
**Figure 1** Create Security Group
|
||||
|
||||
.. _vpc_qs_0012__en-us_topic_0118646265_en-us_topic_0118534004_table65377617111335:
|
||||
|
@ -38,7 +38,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0284920908.png
|
||||
:alt: **Figure 1** Add Inbound Rule
|
||||
|
||||
|
||||
**Figure 1** Add Inbound Rule
|
||||
|
||||
.. table:: **Table 1** Inbound rule parameter description
|
||||
@ -72,7 +71,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0284993717.png
|
||||
:alt: **Figure 2** Add Outbound Rule
|
||||
|
||||
|
||||
**Figure 2** Add Outbound Rule
|
||||
|
||||
.. table:: **Table 2** Outbound rule parameter description
|
||||
|
@ -12,7 +12,6 @@ If your ECSs do not require Internet access or need to access the Internet using
|
||||
.. figure:: /_static/images/en-us_image_0162329244.png
|
||||
:alt: **Figure 1** Configuring the network
|
||||
|
||||
|
||||
**Figure 1** Configuring the network
|
||||
|
||||
:ref:`Table 1 <vpc_qs_0004__en-us_topic_0118498946_t1b39acc5d1d449eabbea2aab68bfab25>` describes the different tasks in the procedure for configuring the network.
|
||||
|
@ -33,7 +33,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001197228903.png
|
||||
:alt: **Figure 1** Create Subnet
|
||||
|
||||
|
||||
**Figure 1** Create Subnet
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -29,7 +29,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001197426329.png
|
||||
:alt: **Figure 1** Create Security Group
|
||||
|
||||
|
||||
**Figure 1** Create Security Group
|
||||
|
||||
.. _vpc_qs_0007__en-us_topic_0118646263_en-us_topic_0118534004_table65377617111335:
|
||||
|
@ -38,7 +38,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0284920908.png
|
||||
:alt: **Figure 1** Add Inbound Rule
|
||||
|
||||
|
||||
**Figure 1** Add Inbound Rule
|
||||
|
||||
.. table:: **Table 1** Inbound rule parameter description
|
||||
@ -72,7 +71,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0284993717.png
|
||||
:alt: **Figure 2** Add Outbound Rule
|
||||
|
||||
|
||||
**Figure 2** Add Outbound Rule
|
||||
|
||||
.. table:: **Table 2** Outbound rule parameter description
|
||||
|
@ -35,7 +35,6 @@ Assigning an EIP
|
||||
.. figure:: /_static/images/en-us_image_0000001117669274.png
|
||||
:alt: **Figure 1** Assign EIP
|
||||
|
||||
|
||||
**Figure 1** Assign EIP
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
@ -102,7 +101,6 @@ Binding an EIP
|
||||
.. figure:: /_static/images/en-us_image_0000001166028070.png
|
||||
:alt: **Figure 2** Bind EIP
|
||||
|
||||
|
||||
**Figure 2** Bind EIP
|
||||
|
||||
#. Click **OK**.
|
||||
|
@ -23,19 +23,19 @@ Monitoring Metrics
|
||||
+----------------------+--------------------+-------------------------------------------------+-------------+------------------+--------------------------------+
|
||||
| ID | Name | Description | Value Range | Monitored Object | Monitoring Interval (Raw Data) |
|
||||
+======================+====================+=================================================+=============+==================+================================+
|
||||
| upstream_bandwidth | Outbound Bandwidth | Network rate of outbound traffic | ≥ 0 bit/s | Bandwidth or EIP | 1 minute |
|
||||
| upstream_bandwidth | Outbound Bandwidth | Network rate of outbound traffic | >= 0 bit/s | Bandwidth or EIP | 1 minute |
|
||||
| | | | | | |
|
||||
| | | Unit: bit/s | | | |
|
||||
+----------------------+--------------------+-------------------------------------------------+-------------+------------------+--------------------------------+
|
||||
| downstream_bandwidth | Inbound Bandwidth | Network rate of inbound traffic | ≥ 0 bit/s | Bandwidth or EIP | 1 minute |
|
||||
| downstream_bandwidth | Inbound Bandwidth | Network rate of inbound traffic | >= 0 bit/s | Bandwidth or EIP | 1 minute |
|
||||
| | | | | | |
|
||||
| | | Unit: bit/s | | | |
|
||||
+----------------------+--------------------+-------------------------------------------------+-------------+------------------+--------------------------------+
|
||||
| up_stream | Outbound Traffic | Network traffic going out of the cloud platform | ≥ 0 bytes | Bandwidth or EIP | 1 minute |
|
||||
| up_stream | Outbound Traffic | Network traffic going out of the cloud platform | >= 0 bytes | Bandwidth or EIP | 1 minute |
|
||||
| | | | | | |
|
||||
| | | Unit: byte | | | |
|
||||
+----------------------+--------------------+-------------------------------------------------+-------------+------------------+--------------------------------+
|
||||
| down_stream | Inbound Traffic | Network traffic going into the cloud platform | ≥ 0 bytes | Bandwidth or EIP | 1 minute |
|
||||
| down_stream | Inbound Traffic | Network traffic going into the cloud platform | >= 0 bytes | Bandwidth or EIP | 1 minute |
|
||||
| | | | | | |
|
||||
| | | Unit: byte | | | |
|
||||
+----------------------+--------------------+-------------------------------------------------+-------------+------------------+--------------------------------+
|
||||
|
@ -31,7 +31,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0173155793.png
|
||||
:alt: **Figure 1** Add Route
|
||||
|
||||
|
||||
**Figure 1** Add Route
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -34,7 +34,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0173155870.png
|
||||
:alt: **Figure 1** Associate Subnet
|
||||
|
||||
|
||||
**Figure 1** Associate Subnet
|
||||
|
||||
#. Click **OK**.
|
||||
|
@ -97,7 +97,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0118498992.png
|
||||
:alt: **Figure 1** Configuring SNAT
|
||||
|
||||
|
||||
**Figure 1** Configuring SNAT
|
||||
|
||||
.. note::
|
||||
@ -129,7 +128,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0118499109.png
|
||||
:alt: **Figure 2** Verifying configuration
|
||||
|
||||
|
||||
**Figure 2** Verifying configuration
|
||||
|
||||
16. Add a route. For details, see section :ref:`Adding a Custom Route <vpc_route_0006>`.
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0173155804.png
|
||||
:alt: **Figure 1** Create Route Table
|
||||
|
||||
|
||||
**Figure 1** Create Route Table
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -16,7 +16,6 @@ A route table contains a set of routes that are used to determine where network
|
||||
.. figure:: /_static/images/en-us_image_0167573711.png
|
||||
:alt: **Figure 1** Route table
|
||||
|
||||
|
||||
**Figure 1** Route table
|
||||
|
||||
Default Route Table and Custom Route Table
|
||||
@ -95,7 +94,6 @@ Custom Route Table Configuration Process
|
||||
.. figure:: /_static/images/en-us_image_0163203842.png
|
||||
:alt: **Figure 2** Route table configuration process
|
||||
|
||||
|
||||
**Figure 2** Route table configuration process
|
||||
|
||||
#. For details about how to create a custom route table, see :ref:`Creating a Custom Route Table <vpc_route_0005>`.
|
||||
|
@ -17,7 +17,6 @@ For details, see :ref:`Figure 1 <en-us_topic_0052003963__en-us_topic_0118534001_
|
||||
.. figure:: /_static/images/en-us_image_0148244691.png
|
||||
:alt: **Figure 1** Security groups and firewalls
|
||||
|
||||
|
||||
**Figure 1** Security groups and firewalls
|
||||
|
||||
:ref:`Table 1 <en-us_topic_0052003963__en-us_topic_0118534001_table53053071174845>` describes the differences between security groups and firewalls.
|
||||
|
@ -32,7 +32,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0152238989.png
|
||||
:alt: **Figure 1** Add Inbound Rule
|
||||
|
||||
|
||||
**Figure 1** Add Inbound Rule
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -29,7 +29,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0129304042.png
|
||||
:alt: **Figure 1** Create Firewall
|
||||
|
||||
|
||||
**Figure 1** Create Firewall
|
||||
|
||||
.. _en-us_topic_0051746698__en-us_topic_0118499011_table145313414319:
|
||||
|
@ -14,7 +14,6 @@ A firewall is an optional layer of security for your subnets. After you associat
|
||||
.. figure:: /_static/images/en-us_image_0148244691.png
|
||||
:alt: **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.
|
||||
@ -94,7 +93,6 @@ Configuration Procedure
|
||||
.. figure:: /_static/images/en-us_image_0162335382.png
|
||||
:alt: **Figure 2** firewall configuration procedure
|
||||
|
||||
|
||||
**Figure 2** firewall configuration procedure
|
||||
|
||||
#. Create a firewall by following the steps described in :ref:`Creating a Firewall <en-us_topic_0051746698>`.
|
||||
|
@ -29,7 +29,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0285048674.png
|
||||
:alt: **Figure 1** Modify Rule
|
||||
|
||||
|
||||
**Figure 1** Modify Rule
|
||||
|
||||
.. _vpc_acl_0005__en-us_topic_0118498887_table59686157164549:
|
||||
|
@ -38,7 +38,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0284920908.png
|
||||
:alt: **Figure 1** Add Inbound Rule
|
||||
|
||||
|
||||
**Figure 1** Add Inbound Rule
|
||||
|
||||
.. table:: **Table 1** Inbound rule parameter description
|
||||
@ -72,7 +71,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0284993717.png
|
||||
:alt: **Figure 2** Add Outbound Rule
|
||||
|
||||
|
||||
**Figure 2** Add Outbound Rule
|
||||
|
||||
.. table:: **Table 2** Outbound rule parameter description
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0122999741.png
|
||||
:alt: **Figure 1** Change Security Group
|
||||
|
||||
|
||||
**Figure 1** Change Security Group
|
||||
|
||||
#. Select the target NIC and security groups as prompted.
|
||||
|
@ -29,7 +29,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001197426329.png
|
||||
:alt: **Figure 1** Create Security Group
|
||||
|
||||
|
||||
**Figure 1** Create Security Group
|
||||
|
||||
.. _en-us_topic_0013748715__en-us_topic_0118534004_table65377617111335:
|
||||
|
@ -14,7 +14,6 @@ Your account automatically comes with a default security group. The default secu
|
||||
.. figure:: /_static/images/en-us_image_0000001230120807.png
|
||||
:alt: **Figure 1** Default security group
|
||||
|
||||
|
||||
**Figure 1** Default security group
|
||||
|
||||
:ref:`Table 1 <securitygroup_0003__en-us_topic_0118534003_table493045171919>` describes the default rules for the default security group.
|
||||
|
@ -29,7 +29,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0211552164.png
|
||||
:alt: **Figure 1** Fast-Add Inbound Rule
|
||||
|
||||
|
||||
**Figure 1** Fast-Add Inbound Rule
|
||||
|
||||
7. On the **Outbound Rules** tab, click **Fast-Add Rule**. In the displayed dialog box, select required protocols and ports to add multiple rules at a time.
|
||||
@ -38,7 +37,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0211560998.png
|
||||
:alt: **Figure 2** Fast-Add Outbound Rule
|
||||
|
||||
|
||||
**Figure 2** Fast-Add Outbound Rule
|
||||
|
||||
8. Click **OK**.
|
||||
|
@ -34,7 +34,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001211006359.png
|
||||
:alt: **Figure 1** Add EIP
|
||||
|
||||
|
||||
**Figure 1** Add EIP
|
||||
|
||||
6. Click **OK**.
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001163949251.png
|
||||
:alt: **Figure 1** Assigning Shared Bandwidth
|
||||
|
||||
|
||||
**Figure 1** Assigning Shared Bandwidth
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001117669524.png
|
||||
:alt: **Figure 1** Modify Bandwidth
|
||||
|
||||
|
||||
**Figure 1** Modify Bandwidth
|
||||
|
||||
6. Click **Next**.
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001211445065.png
|
||||
:alt: **Figure 1** Remove EIP
|
||||
|
||||
|
||||
**Figure 1** Remove EIP
|
||||
|
||||
6. Click **OK**.
|
||||
|
@ -105,7 +105,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001179761510.png
|
||||
:alt: **Figure 1** Configuring private IP address
|
||||
|
||||
|
||||
**Figure 1** Configuring private IP address
|
||||
|
||||
f. Click **Advanced**.
|
||||
@ -118,7 +117,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001225081545.png
|
||||
:alt: **Figure 2** Configuring virtual IP address
|
||||
|
||||
|
||||
**Figure 2** Configuring virtual IP address
|
||||
|
||||
h. Click **OK**.
|
||||
|
@ -27,7 +27,6 @@ Virtual IP addresses are used for high availability and can work together with K
|
||||
.. figure:: /_static/images/en-us_image_0209608153.png
|
||||
:alt: **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.
|
||||
@ -41,7 +40,6 @@ Virtual IP addresses are used for high availability and can work together with K
|
||||
.. figure:: /_static/images/en-us_image_0240332622.png
|
||||
:alt: **Figure 2** HA load balancing cluster
|
||||
|
||||
|
||||
**Figure 2** HA load balancing cluster
|
||||
|
||||
- Bind a single virtual IP address to two ECSs.
|
||||
|
@ -33,7 +33,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001197228903.png
|
||||
:alt: **Figure 1** Create Subnet
|
||||
|
||||
|
||||
**Figure 1** Create Subnet
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -17,12 +17,12 @@ Notes and Constraints
|
||||
|
||||
- When modifying the VPC CIDR block:
|
||||
|
||||
- The VPC CIDR block to be modified must be in the supported CIDR blocks: 10.0.0.0 – 10.255.255.255, 172.16.0.0 – 172.31.255.255, and 192.168.0.0 – 192.168.255.255
|
||||
- The VPC CIDR block to be modified must be in the supported CIDR blocks: 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, and 192.168.0.0 - 192.168.255.255
|
||||
- If the VPC has subnets, the VPC CIDR block to be modified must contain all subnet CIDR blocks.
|
||||
|
||||
When modifying the VPC CIDR block:
|
||||
|
||||
- The VPC CIDR block to be modified must be in the supported CIDR blocks: 10.0.0.0 – 10.255.255.255, 172.16.0.0 – 172.31.255.255, and 192.168.0.0 – 192.168.255.255
|
||||
- The VPC CIDR block to be modified must be in the supported CIDR blocks: 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, and 192.168.0.0 - 192.168.255.255
|
||||
- If the VPC has subnets, the VPC CIDR block to be modified must contain all subnet CIDR blocks.
|
||||
|
||||
Procedure
|
||||
@ -46,7 +46,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0000001151300782.png
|
||||
:alt: **Figure 1** Modify CIDR Block
|
||||
|
||||
|
||||
**Figure 1** Modify CIDR Block
|
||||
|
||||
#. Click **OK**.
|
||||
|
@ -37,7 +37,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0191544038.png
|
||||
:alt: **Figure 1** Create VPC Flow Log
|
||||
|
||||
|
||||
**Figure 1** Create VPC Flow Log
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
|
@ -31,7 +31,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0191594527.png
|
||||
:alt: **Figure 1** Deleting a VPC flow log
|
||||
|
||||
|
||||
**Figure 1** Deleting a VPC flow log
|
||||
|
||||
6. Click **Yes** in the displayed dialog box.
|
||||
|
@ -33,14 +33,12 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0191577030.png
|
||||
:alt: **Figure 1** Viewing a log record
|
||||
|
||||
|
||||
**Figure 1** Viewing a log record
|
||||
|
||||
|
||||
.. figure:: /_static/images/en-us_image_0191588554.png
|
||||
:alt: **Figure 2** Flow log record
|
||||
|
||||
|
||||
**Figure 2** Flow log record
|
||||
|
||||
The flow log record is in the following format:
|
||||
|
@ -14,7 +14,6 @@ VPC flow logs must be used together with the Log Tank Service (LTS). Before you
|
||||
.. figure:: /_static/images/en-us_image_0162336264.png
|
||||
:alt: **Figure 1** Configuring the VPC flow log function
|
||||
|
||||
|
||||
**Figure 1** Configuring the VPC flow log function
|
||||
|
||||
Notes and Constraints
|
||||
|
@ -29,7 +29,6 @@ Creating a VPC Peering Connection
|
||||
.. figure:: /_static/images/en-us_image_0167840073.png
|
||||
:alt: **Figure 1** Create VPC Peering Connection
|
||||
|
||||
|
||||
**Figure 1** Create VPC Peering Connection
|
||||
|
||||
.. table:: **Table 1** Parameter descriptions
|
||||
@ -76,7 +75,6 @@ To request a VPC peering connection with a VPC in another account, the owner of
|
||||
.. figure:: /_static/images/en-us_image_0162391155.png
|
||||
:alt: **Figure 2** VPC peering connection list
|
||||
|
||||
|
||||
**Figure 2** VPC peering connection list
|
||||
|
||||
#. Click **Yes** in the displayed dialog box.
|
||||
|
@ -34,7 +34,6 @@ Creating a VPC Peering Connection
|
||||
.. figure:: /_static/images/en-us_image_0167839112.png
|
||||
:alt: **Figure 1** Create VPC Peering Connection
|
||||
|
||||
|
||||
**Figure 1** Create VPC Peering Connection
|
||||
|
||||
.. _en-us_topic_0046655037__en-us_topic_0118498960_table1215761020244:
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0162391187.png
|
||||
:alt: **Figure 1** VPC peering connection list
|
||||
|
||||
|
||||
**Figure 1** VPC peering connection list
|
||||
|
||||
6. Locate the target VPC peering connection and click **Delete** in the **Operation** column.
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0162391187.png
|
||||
:alt: **Figure 1** VPC peering connection list
|
||||
|
||||
|
||||
**Figure 1** VPC peering connection list
|
||||
|
||||
6. Locate the target VPC peering connection and click **Modify** in the **Operation** column. In the displayed dialog box, modify information about the VPC peering connection.
|
||||
|
@ -27,7 +27,6 @@ Procedure
|
||||
.. figure:: /_static/images/en-us_image_0162391187.png
|
||||
:alt: **Figure 1** VPC peering connection list
|
||||
|
||||
|
||||
**Figure 1** VPC peering connection list
|
||||
|
||||
6. Click the VPC peering connection name. On the displayed page, view detailed information about the VPC peering connection.
|
||||
|
@ -50,7 +50,6 @@ For example, VPC 1 and VPC 2 have matching CIDR blocks, but the subnets in the t
|
||||
.. figure:: /_static/images/en-us_image_0194358487.png
|
||||
:alt: **Figure 1** VPC peering connection between Subnet A and Subnet X
|
||||
|
||||
|
||||
**Figure 1** VPC peering connection between Subnet A and Subnet X
|
||||
|
||||
:ref:`Figure 2 <en-us_topic_0046809840__en-us_topic_0118499087_fig13211186151514>` shows the routes configured for the VPC peering connection between Subnet A and Subnet X. After the routes are configured, Subnet A and Subnet X can communicate with each other.
|
||||
@ -60,7 +59,6 @@ For example, VPC 1 and VPC 2 have matching CIDR blocks, but the subnets in the t
|
||||
.. figure:: /_static/images/en-us_image_0194358495.png
|
||||
:alt: **Figure 2** Route tables for the VPC peering connection between Subnet A and Subnet X
|
||||
|
||||
|
||||
**Figure 2** Route tables for the VPC peering connection between Subnet A and Subnet X
|
||||
|
||||
If two VPCs have overlapping subnets, a VPC peering connection created between the two subnets will not take effect, and the subnets cannot communicate with each other.
|
||||
@ -72,7 +70,6 @@ As shown in :ref:`Figure 3 <en-us_topic_0046809840__en-us_topic_0118499087_fig12
|
||||
.. figure:: /_static/images/en-us_image_0194358504.png
|
||||
:alt: **Figure 3** Invalid VPC peering connection
|
||||
|
||||
|
||||
**Figure 3** Invalid VPC peering connection
|
||||
|
||||
If peering connections are used to link VPC 1 to multiple VPCs, for example, VPC 2, VPC 3, and VPC 4, the subnets of VPC 1 cannot overlap with those of VPC 2, VPC 3, and VPC 4. If VPC 2, VPC 3, and VPC 4 have overlapping subnets, a VPC peering connection can be created between only one of these overlapping subnets and a subnet of VPC 1. If a VPC peering connection is created between a subnet and the other *N* subnets, none of the subnets can overlap.
|
||||
|
@ -13,7 +13,6 @@ A VPC peering connection is a network connection between two VPCs in one region
|
||||
.. figure:: /_static/images/en-us_image_0162335561.png
|
||||
:alt: **Figure 1** Creating a VPC peering connection between VPCs in your account
|
||||
|
||||
|
||||
**Figure 1** Creating a VPC peering connection between VPCs in your account
|
||||
|
||||
If you create a VPC peering connection between two VPCs in your account, the system accepts the connection by default. You need to add routes for the local and peer VPCs to enable communication between the two VPCs.
|
||||
@ -24,7 +23,6 @@ A VPC peering connection is a network connection between two VPCs in one region
|
||||
.. figure:: /_static/images/en-us_image_0162335565.png
|
||||
:alt: **Figure 2** Creating a VPC peering connection with a VPC in another account
|
||||
|
||||
|
||||
**Figure 2** Creating a VPC peering connection with a VPC in another account
|
||||
|
||||
If you create a VPC peering connection between your VPC and a VPC that is in another account, the VPC peering connection will be in the **Awaiting acceptance** state. After the owner of the peer account accepts the connection, the connection status changes to **Accepted**. The owners of both the local and peer accounts must configure the routes required by the VPC peering connection to enable communication between the two VPCs.
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user