sgode/virtual-private-cloud
1
0
Fork 0
forked from docs/virtual-private-cloud
Code Pull Requests Activity

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2024-04-22 11:40:58 +00:00
parent 698e9d1f14
commit c76420195d
23 changed files with 1118 additions and 1094 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
umn/source/access_control/security_group/managing_a_security_group/creating_a_security_group.rst
View File

File diff suppressed because it is too large Load Diff

2
umn/source/access_control/security_group/managing_security_group_rules/importing_and_exporting_security_group_rules.rst
View File

@ -19,6 +19,8 @@ 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.
- If you want to import rules of the security group in one region to another under one account, only rules with both **Source** and **Destination** set to **IP address** can be applied.
- If you want to import rules of the security group in one account to the security group in another account, only rules with both **Source** and **Destination** set to **IP address** can be applied.
Procedure
---------

210
umn/source/change_history.rst
View File

File diff suppressed because it is too large Load Diff

14
umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst
View File

@ -81,9 +81,9 @@ Assigning an EIP
.. table:: **Table 2** EIP tag requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirement | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | Ipv4_key1 |
| | - The key value must be unique for the same EIP. | |
| | - Can contain up to 36 characters. | |
@ -92,16 +92,16 @@ Assigning an EIP
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain up to 43 characters. | 3005eip |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
#. Click **Create Now**.
@ -122,7 +122,7 @@ Binding an EIP
#. Click **OK**.
An IPv6 client on the Internet can access the ECS that has an EIP bound in a VPC. For details, see :ref:`How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? <vpc_faq_0076>`
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? <https://docs.otc.t-systems.com/virtual-private-cloud/umn/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.html#vpc-faq-0076>`__
Follow-Up Procedure
-------------------

12
umn/source/elastic_ip/managing_eip_tags.rst
View File

@ -16,9 +16,9 @@ A tag consists of a key and value pair. :ref:`Table 1 <en-us_topic_0068145818__t
.. table:: **Table 1** EIP tag requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirement | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | Ipv4_key1 |
| | - Must be unique for each EIP. | |
| | - Can contain a maximum of 36 characters. | |
@ -27,16 +27,16 @@ A tag consists of a key and value pair. :ref:`Table 1 <en-us_topic_0068145818__t
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | 3005eip |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
Procedure
---------

8
umn/source/faq/routing/how_many_routes_can_a_route_table_contain.rst
View File

@ -1,8 +0,0 @@
:original_name: vpc_faq_0063.html
.. _vpc_faq_0063:
How Many Routes Can a Route Table Contain?
==========================================
Currently, a route table can contain 100 routes.

8
umn/source/faq/routing/how_many_routes_can_i_add_to_a_route_table.rst Normal file
View File

@ -0,0 +1,8 @@
:original_name: vpc_faq_0063.html
.. _vpc_faq_0063:
How Many Routes Can I Add to a Route Table?
===========================================
A maximum of 200 routes can be added to each route table.

4
umn/source/faq/routing/index.rst
View File

@ -5,7 +5,7 @@
Routing
=======
- :ref:`How Many Routes Can a Route Table Contain? <vpc_faq_0063>`
- :ref:`How Many Routes Can I Add to a Route Table? <vpc_faq_0063>`
- :ref:`Are There Any Restrictions on Using a Route Table? <vpc_faq_0064>`
- :ref:`Do the Same Routing Priorities Apply to Direct Connect Connections and Custom Routes in the Same VPC? <vpc_faq_0066>`
- :ref:`Are There Different Routing Priorities of the VPN and Custom Routes in the Same VPC? <vpc_faq_00001>`
@ -14,7 +14,7 @@ Routing
:maxdepth: 1
:hidden:
how_many_routes_can_a_route_table_contain
how_many_routes_can_i_add_to_a_route_table
are_there_any_restrictions_on_using_a_route_table
do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc
are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc

16
umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_1_create_a_vpc.rst
View File

@ -108,7 +108,7 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | vpc-01 |
| | - Can contain only the following character types: | |
@ -116,16 +116,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
.. _vpc_qs_0009__en-us_topic_0013935842_table6536185812515:
.. table:: **Table 3** Subnet tag key and value requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirements | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | subnet_key1 |
| | - Must be unique for each subnet. | |
| | - Can contain a maximum of 36 characters. | |
@ -134,16 +134,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
#. Click **Create Now**.

12
umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_2_create_a_subnet_for_the_vpc.rst
View File

@ -81,9 +81,9 @@ Procedure
.. table:: **Table 2** Subnet tag key and value requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirements | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | subnet_key1 |
| | - Must be unique for each subnet. | |
| | - Can contain a maximum of 36 characters. | |
@ -92,16 +92,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
7. Click **OK**.

14
umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_3_assign_an_eip_and_bind_it_to_an_ecs.rst
View File

@ -81,9 +81,9 @@ Assigning an EIP
.. table:: **Table 2** EIP tag requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirement | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | Ipv4_key1 |
| | - The key value must be unique for the same EIP. | |
| | - Can contain up to 36 characters. | |
@ -92,16 +92,16 @@ Assigning an EIP
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain up to 43 characters. | 3005eip |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
#. Click **Create Now**.
@ -122,7 +122,7 @@ Binding an EIP
#. Click **OK**.
An IPv6 client on the Internet can access the ECS that has an EIP bound in a VPC. For details, see :ref:`How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? <vpc_faq_0076>`
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? <https://docs.otc.t-systems.com/virtual-private-cloud/umn/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.html#vpc-faq-0076>`__
Follow-Up Procedure
-------------------

18
umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_4_create_a_security_group.rst
View File

@ -43,9 +43,9 @@ Procedure
.. table:: **Table 1** Parameter description
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Parameter | Description | Example Value |
+=======================+=======================================================================================================================================================================================================================================================================+============================+
+=======================+================================================================================================================================================================================================================================+============================+
| Name | Mandatory | sg-AB |
| | | |
| | Enter the security group name. | |
@ -55,27 +55,25 @@ Procedure
| | .. note:: | |
| | | |
| | You can change the security group name after a security group is created. It is recommended that you give each security group a different name. | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Enterprise Project | Mandatory | default |
| | | |
| | When creating a security group, you can add the security group to an enabled enterprise project. | |
| | | |
| | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Template | Mandatory | General-purpose web server |
| | | |
| | A template comes with default security group rules, helping you quickly create security groups. The following templates are provided: | |
| | The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. | |
| | | |
| | - **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. | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| | :ref:`Table 1 <en-us_topic_0013748715__table117828131111>` describes the security group templates. | |
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Description | Optional | N/A |
| | | |
| | Supplementary information about the security group. This parameter is optional. | |
| | | |
| | The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
#. Confirm the inbound and outbound rules of the template and click **OK**.

16
umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_1_create_a_vpc.rst
View File

@ -108,7 +108,7 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | vpc-01 |
| | - Can contain only the following character types: | |
@ -116,16 +116,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
.. _vpc_qs_0005__en-us_topic_0013935842_table6536185812515:
.. table:: **Table 3** Subnet tag key and value requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirements | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | subnet_key1 |
| | - Must be unique for each subnet. | |
| | - Can contain a maximum of 36 characters. | |
@ -134,16 +134,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
#. Click **Create Now**.

12
umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_2_create_a_subnet_for_the_vpc.rst
View File

@ -81,9 +81,9 @@ Procedure
.. table:: **Table 2** Subnet tag key and value requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirements | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | subnet_key1 |
| | - Must be unique for each subnet. | |
| | - Can contain a maximum of 36 characters. | |
@ -92,16 +92,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
7. Click **OK**.

18
umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_3_create_a_security_group.rst
View File

@ -43,9 +43,9 @@ Procedure
.. table:: **Table 1** Parameter description
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Parameter | Description | Example Value |
+=======================+=======================================================================================================================================================================================================================================================================+============================+
+=======================+================================================================================================================================================================================================================================+============================+
| Name | Mandatory | sg-AB |
| | | |
| | Enter the security group name. | |
@ -55,27 +55,25 @@ Procedure
| | .. note:: | |
| | | |
| | You can change the security group name after a security group is created. It is recommended that you give each security group a different name. | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Enterprise Project | Mandatory | default |
| | | |
| | When creating a security group, you can add the security group to an enabled enterprise project. | |
| | | |
| | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Template | Mandatory | General-purpose web server |
| | | |
| | A template comes with default security group rules, helping you quickly create security groups. The following templates are provided: | |
| | The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. | |
| | | |
| | - **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. | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| | :ref:`Table 1 <en-us_topic_0013748715__table117828131111>` describes the security group templates. | |
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
| Description | Optional | N/A |
| | | |
| | Supplementary information about the security group. This parameter is optional. | |
| | | |
| | The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | |
+-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
+-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+
#. Confirm the inbound and outbound rules of the template and click **OK**.

12
umn/source/vpc_and_subnet/subnet/creating_a_subnet_for_the_vpc.rst
View File

@ -81,9 +81,9 @@ Procedure
.. table:: **Table 2** Subnet tag key and value requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirements | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | subnet_key1 |
| | - Must be unique for each subnet. | |
| | - Can contain a maximum of 36 characters. | |
@ -92,16 +92,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
7. Click **OK**.

12
umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst
View File

@ -18,9 +18,9 @@ A tag consists of a key and value pair. :ref:`Table 1 <vpc_vpc_0005__ted9687ca14
.. table:: **Table 1** Subnet tag key and value requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirements | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | subnet_key1 |
| | - Must be unique for each subnet. | |
| | - Can contain a maximum of 36 characters. | |
@ -29,16 +29,16 @@ A tag consists of a key and value pair. :ref:`Table 1 <vpc_vpc_0005__ted9687ca14
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
Procedure
---------

16
umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst
View File

@ -108,7 +108,7 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | vpc-01 |
| | - Can contain only the following character types: | |
@ -116,16 +116,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
.. _en-us_topic_0013935842__table6536185812515:
.. table:: **Table 3** Subnet tag key and value requirements
+-----------------------+---------------------------------------------------------------------+-----------------------+
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Parameter | Requirements | Example Value |
+=======================+=====================================================================+=======================+
+=======================+========================================================================+=======================+
| Key | - Cannot be left blank. | subnet_key1 |
| | - Must be unique for each subnet. | |
| | - Can contain a maximum of 36 characters. | |
@ -134,16 +134,16 @@ Procedure
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | subnet-01 |
| | - Can contain only the following character types: | |
| | | |
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
+-----------------------+---------------------------------------------------------------------+-----------------------+
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
#. Click **Create Now**.

4
umn/source/vpc_and_subnet/vpc/managing_vpc_tags.rst
View File

@ -29,7 +29,7 @@ A tag consists of a key and value pair. :ref:`Table 1 <vpc_vpc_0004__ted9687ca14
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only hyphens (-), underscores (_), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
| Value | - Can contain a maximum of 43 characters. | vpc-01 |
| | - Can contain only the following character types: | |
@ -37,7 +37,7 @@ A tag consists of a key and value pair. :ref:`Table 1 <vpc_vpc_0004__ted9687ca14
| | - Uppercase letters | |
| | - Lowercase letters | |
| | - Digits | |
| | - Special characters, including hyphens (-) and underscores (_) | |
| | - Only underscores (_), hyphens (-), and at signs (@) are allowed. | |
+-----------------------+------------------------------------------------------------------------+-----------------------+
Procedure

22
umn/source/vpc_peering_connection/deleting_routes_configured_for_a_vpc_peering_connection.rst
View File

@ -34,29 +34,11 @@ Deleting Routes of a VPC Peering Connection Between VPCs in the Same Account
The page showing the VPC peering connection details is displayed.
#. Delete the route added to the route table of the local VPC:
a. 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.
b. Locate the row that contains the route to be deleted and click **Delete** in the **Operation** column.
#. In the route list, locate the route and click **Delete** in the **Operation** column.
A confirmation dialog box is displayed.
c. Click **Yes**.
#. Delete the route added to the route table of the peer VPC:
a. Click the **Peer Routes** tab and then click the **Route Tables** hyperlink.
The **Summary** tab of the default route table for the peer VPC is displayed.
b. Locate the row that contains the route to be deleted and click **Delete** in the **Operation** column.
A confirmation dialog box is displayed.
c. Click **Yes**.
#. Confirm the information and click **OK**.
.. _vpc_peering_0006__section47866392497:

2
umn/source/vpc_peering_connection/modifying_a_vpc_peering_connection.rst
View File

@ -8,7 +8,7 @@ Modifying a VPC Peering Connection
Scenarios
---------
This section describes how to modify the name of a VPC peering connection.
This section describes how to modify the basic information about a VPC peering connection, including its name and description.
Either owner of a VPC in a peering connection can modify the VPC peering connection in any state.

36
umn/source/vpc_peering_connection/modifying_routes_configured_for_a_vpc_peering_connection.rst
View File

@ -36,29 +36,13 @@ Modifying Routes of a VPC Peering Connection Between VPCs in the Same Account
The page showing the VPC peering connection details is displayed.
#. Modify the route added to the route table of the local VPC:
#. In the route list, click the route table hyperlink of the route.
a. Click the **Local Routes** tab and then click the **Route Tables** hyperlink.
The route table details page is displayed.
The **Summary** tab of the default route table for the local VPC is displayed.
#. In the route list, locate the route and click **Modify** in the **Operation** column.
b. Locate the row that contains the route to be modified and click **Modify** in the **Operation** column.
The **Modify Route** dialog box is displayed.
c. Modify the route and click **OK**.
#. Modify the route added to the route table of the peer VPC:
a. Click the **Peer Routes** tab and then click the **Route Tables** hyperlink.
The **Summary** tab of the default route table for the peer VPC is displayed.
b. Locate the row that contains the route to be modified and click **Modify** in the **Operation** column.
The **Modify Route** dialog box is displayed.
c. Modify the route and click **OK**.
#. Modify the route and click **OK**.
.. _vpc_peering_0007__section47866392497:
@ -85,17 +69,13 @@ Only the account owner of a VPC can modify the routes added for the connection.
The page showing the VPC peering connection details is displayed.
e. Modify the route added to the route table of the local VPC:
e. In the route list, click the route table hyperlink of the route.
#. Click the **Local Routes** tab and then click the **Route Tables** hyperlink.
The route table details page is displayed.
The **Summary** tab of the default route table for the local VPC is displayed.
f. In the route list, locate the route and click **Modify** in the **Operation** column.
#. Locate the row that contains the route to be modified and click **Modify** in the **Operation** column.
The **Modify Route** dialog box is displayed.
#. Modify the route and click **OK**.
g. Modify the route and click **OK**.
#. Log in to the management console using the account of the peer VPC and modify the route of the peer VPC by referring to :ref:`1 <vpc_peering_0007__li4105938135810>`.

9
umn/source/vpc_peering_connection/viewing_routes_configured_for_a_vpc_peering_connection.rst
View File

@ -36,10 +36,9 @@ Viewing Routes of a VPC Peering Connection Between VPCs in the Same Account
The page showing the VPC peering connection details is displayed.
6. View the routes added for the VPC peering connection:
6. In the route list, view the route information.
a. Click the **Local Routes** tab to view the local route added for the VPC peering connection.
b. Click the **Peer Routes** tab to view the peer route added for the VPC peering connection.
You can view the route destination, VPC, next hop, route table, and more.
.. _vpc_peering_0004__section92403501475:
@ -66,7 +65,9 @@ Only the account owner of a VPC in a VPC peering connection can view the routes
The page showing the VPC peering connection details is displayed.
e. Click the **Local Routes** tab to view the local route added for the VPC peering connection.
e. In the route list, view the route information.
You can view the route destination, VPC, next hop, route table, and more.
#. Log in to the management console using the account of the peer VPC and view the route of the peer VPC by referring to :ref:`1 <vpc_peering_0004__li4105938135810>`.