diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index f530781..88a52e7 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -8,6 +8,13 @@ Change History +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Released On | Description | +===================================+====================================================================================================================================================================================================================================================================================================================================+ +| 2023-04-20 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | - Added description that BMS user-defined network is available only in eu-de. | +| | - Added the step for viewing NIC details to :ref:`Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) `. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2023-02-15 | This release incorporates the following changes: | | | | | | Updated the following content: | @@ -283,7 +290,7 @@ Change History | | | | | Deleted the following content: | | | | -| | - Deleted "What Is a Security Group?", "Which Protocols Does a Security Group Support?", "What Are the Functions of the Default Security Group Rule?", and "How Can I Configure Security Group Rules?" in :ref:`FAQs `. | +| | - Deleted "What Is a Security Group?", "Which Protocols Does a Security Group Support?", "What Are the Functions of the Default Security Group Rule?", and "How Can I Configure Security Group Rules?" in :ref:`FAQ `. | +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2019-04-17 | Accepted in OTC-4.0/Agile-04.2019. | +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ @@ -307,7 +314,7 @@ Change History | | Deleted the following content: | | | | | | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts `. | -| | - Deleted the FAQs related to VPN in :ref:`FAQs `. | +| | - Deleted the FAQs related to VPN in :ref:`FAQ `. | | | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started `. | | | | | | Modified the following content: | @@ -345,7 +352,7 @@ Change History | | Deleted the following content: | | | | | | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts `. | -| | - Deleted the FAQs related to VPN in :ref:`FAQs `. | +| | - Deleted the FAQs related to VPN in :ref:`FAQ `. | | | | | | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started `. | | | | diff --git a/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst b/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst index a39abd8..63e3fd2 100644 --- a/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst +++ b/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst @@ -14,12 +14,13 @@ You can assign an EIP and bind it to an ECS so that the ECS can access the Inter 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 created anymore. + - 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" in "API V3" section in the *Elastic IP API Reference*. + - 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. diff --git a/umn/source/elastic_ip/unbinding_an_eip_from_an_ecs_and_releasing_the_eip.rst b/umn/source/elastic_ip/unbinding_an_eip_from_an_ecs_and_releasing_the_eip.rst index efe7a76..d277041 100644 --- a/umn/source/elastic_ip/unbinding_an_eip_from_an_ecs_and_releasing_the_eip.rst +++ b/umn/source/elastic_ip/unbinding_an_eip_from_an_ecs_and_releasing_the_eip.rst @@ -13,12 +13,13 @@ If you no longer need an EIP, unbind it from the ECS and release the EIP to avoi Notes and Constraints --------------------- -- In **eu-de**, EIPs of the Dedicated Load Balancer (5_gray) type cannot be created anymore. +- 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" in "API V3" section in the *Elastic IP API Reference*. + - 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. - You can only release EIPs that are not bound to any resources. diff --git a/umn/source/faqs/bandwidth/index.rst b/umn/source/faq/bandwidth/index.rst similarity index 100% rename from umn/source/faqs/bandwidth/index.rst rename to umn/source/faq/bandwidth/index.rst diff --git a/umn/source/faqs/bandwidth/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.rst b/umn/source/faq/bandwidth/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.rst similarity index 100% rename from umn/source/faqs/bandwidth/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.rst rename to umn/source/faq/bandwidth/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.rst diff --git a/umn/source/faqs/bandwidth/what_bandwidth_types_are_available.rst b/umn/source/faq/bandwidth/what_bandwidth_types_are_available.rst similarity index 100% rename from umn/source/faqs/bandwidth/what_bandwidth_types_are_available.rst rename to umn/source/faq/bandwidth/what_bandwidth_types_are_available.rst diff --git a/umn/source/faqs/bandwidth/what_is_the_bandwidth_size_range.rst b/umn/source/faq/bandwidth/what_is_the_bandwidth_size_range.rst similarity index 100% rename from umn/source/faqs/bandwidth/what_is_the_bandwidth_size_range.rst rename to umn/source/faq/bandwidth/what_is_the_bandwidth_size_range.rst diff --git a/umn/source/faqs/connectivity/does_a_vpn_allow_communication_between_two_vpcs.rst b/umn/source/faq/connectivity/does_a_vpn_allow_communication_between_two_vpcs.rst similarity index 100% rename from umn/source/faqs/connectivity/does_a_vpn_allow_communication_between_two_vpcs.rst rename to umn/source/faq/connectivity/does_a_vpn_allow_communication_between_two_vpcs.rst diff --git a/umn/source/faqs/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst b/umn/source/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst similarity index 100% rename from umn/source/faqs/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst rename to umn/source/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst diff --git a/umn/source/faqs/connectivity/index.rst b/umn/source/faq/connectivity/index.rst similarity index 100% rename from umn/source/faqs/connectivity/index.rst rename to umn/source/faq/connectivity/index.rst diff --git a/umn/source/faqs/connectivity/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.rst b/umn/source/faq/connectivity/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.rst similarity index 100% rename from umn/source/faqs/connectivity/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.rst rename to umn/source/faq/connectivity/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.rst diff --git a/umn/source/faqs/connectivity/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.rst b/umn/source/faq/connectivity/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.rst similarity index 100% rename from umn/source/faqs/connectivity/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.rst rename to umn/source/faq/connectivity/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.rst diff --git a/umn/source/faqs/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst b/umn/source/faq/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst similarity index 100% rename from umn/source/faqs/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst rename to umn/source/faq/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst diff --git a/umn/source/faqs/eips/can_i_bind_an_eip_to_a_cloud_resource_in_another_region.rst b/umn/source/faq/eips/can_i_bind_an_eip_to_a_cloud_resource_in_another_region.rst similarity index 100% rename from umn/source/faqs/eips/can_i_bind_an_eip_to_a_cloud_resource_in_another_region.rst rename to umn/source/faq/eips/can_i_bind_an_eip_to_a_cloud_resource_in_another_region.rst diff --git a/umn/source/faqs/eips/can_i_bind_an_eip_to_multiple_ecss.rst b/umn/source/faq/eips/can_i_bind_an_eip_to_multiple_ecss.rst similarity index 100% rename from umn/source/faqs/eips/can_i_bind_an_eip_to_multiple_ecss.rst rename to umn/source/faq/eips/can_i_bind_an_eip_to_multiple_ecss.rst diff --git a/umn/source/faqs/eips/can_i_change_the_region_of_my_eip.rst b/umn/source/faq/eips/can_i_change_the_region_of_my_eip.rst similarity index 100% rename from umn/source/faqs/eips/can_i_change_the_region_of_my_eip.rst rename to umn/source/faq/eips/can_i_change_the_region_of_my_eip.rst diff --git a/umn/source/faqs/eips/how_do_i_access_an_ecs_with_an_eip_bound_from_the_internet.rst b/umn/source/faq/eips/how_do_i_access_an_ecs_with_an_eip_bound_from_the_internet.rst similarity index 100% rename from umn/source/faqs/eips/how_do_i_access_an_ecs_with_an_eip_bound_from_the_internet.rst rename to umn/source/faq/eips/how_do_i_access_an_ecs_with_an_eip_bound_from_the_internet.rst diff --git a/umn/source/faqs/eips/index.rst b/umn/source/faq/eips/index.rst similarity index 100% rename from umn/source/faqs/eips/index.rst rename to umn/source/faq/eips/index.rst diff --git a/umn/source/faqs/eips/what_is_an_eip.rst b/umn/source/faq/eips/what_is_an_eip.rst similarity index 100% rename from umn/source/faqs/eips/what_is_an_eip.rst rename to umn/source/faq/eips/what_is_an_eip.rst diff --git a/umn/source/faqs/general_questions/index.rst b/umn/source/faq/general_questions/index.rst similarity index 100% rename from umn/source/faqs/general_questions/index.rst rename to umn/source/faq/general_questions/index.rst diff --git a/umn/source/faqs/general_questions/what_is_a_quota.rst b/umn/source/faq/general_questions/what_is_a_quota.rst similarity index 100% rename from umn/source/faqs/general_questions/what_is_a_quota.rst rename to umn/source/faq/general_questions/what_is_a_quota.rst diff --git a/umn/source/faqs/index.rst b/umn/source/faq/index.rst similarity index 98% rename from umn/source/faqs/index.rst rename to umn/source/faq/index.rst index c0e0239..1bc15eb 100644 --- a/umn/source/faqs/index.rst +++ b/umn/source/faq/index.rst @@ -2,8 +2,8 @@ .. _vpc_faq_0000: -FAQs -==== +FAQ +=== - :ref:`General Questions ` - :ref:`VPCs and Subnets ` diff --git a/umn/source/faqs/routing/are_there_any_restrictions_on_using_a_route_table.rst b/umn/source/faq/routing/are_there_any_restrictions_on_using_a_route_table.rst similarity index 100% rename from umn/source/faqs/routing/are_there_any_restrictions_on_using_a_route_table.rst rename to umn/source/faq/routing/are_there_any_restrictions_on_using_a_route_table.rst diff --git a/umn/source/faqs/routing/are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc.rst b/umn/source/faq/routing/are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc.rst similarity index 100% rename from umn/source/faqs/routing/are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc.rst rename to umn/source/faq/routing/are_there_different_routing_priorities_of_the_vpn_and_custom_routes_in_the_same_vpc.rst diff --git a/umn/source/faqs/routing/do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc.rst b/umn/source/faq/routing/do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc.rst similarity index 100% rename from umn/source/faqs/routing/do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc.rst rename to umn/source/faq/routing/do_the_same_routing_priorities_apply_to_direct_connect_connections_and_custom_routes_in_the_same_vpc.rst diff --git a/umn/source/faqs/routing/how_many_routes_can_a_route_table_contain.rst b/umn/source/faq/routing/how_many_routes_can_a_route_table_contain.rst similarity index 100% rename from umn/source/faqs/routing/how_many_routes_can_a_route_table_contain.rst rename to umn/source/faq/routing/how_many_routes_can_a_route_table_contain.rst diff --git a/umn/source/faqs/routing/index.rst b/umn/source/faq/routing/index.rst similarity index 100% rename from umn/source/faqs/routing/index.rst rename to umn/source/faq/routing/index.rst diff --git a/umn/source/faqs/security/can_i_change_the_security_group_of_an_ecs.rst b/umn/source/faq/security/can_i_change_the_security_group_of_an_ecs.rst similarity index 100% rename from umn/source/faqs/security/can_i_change_the_security_group_of_an_ecs.rst rename to umn/source/faq/security/can_i_change_the_security_group_of_an_ecs.rst diff --git a/umn/source/faqs/security/does_a_security_group_rule_or_a_firewall_rule_immediately_take_effect_for_existing_connections_after_it_is_modified.rst b/umn/source/faq/security/does_a_security_group_rule_or_a_firewall_rule_immediately_take_effect_for_existing_connections_after_it_is_modified.rst similarity index 100% rename from umn/source/faqs/security/does_a_security_group_rule_or_a_firewall_rule_immediately_take_effect_for_existing_connections_after_it_is_modified.rst rename to umn/source/faq/security/does_a_security_group_rule_or_a_firewall_rule_immediately_take_effect_for_existing_connections_after_it_is_modified.rst diff --git a/umn/source/faqs/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst b/umn/source/faq/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst similarity index 100% rename from umn/source/faqs/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst rename to umn/source/faq/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst diff --git a/umn/source/faqs/security/how_many_firewalls_can_i_create.rst b/umn/source/faq/security/how_many_firewalls_can_i_create.rst similarity index 100% rename from umn/source/faqs/security/how_many_firewalls_can_i_create.rst rename to umn/source/faq/security/how_many_firewalls_can_i_create.rst diff --git a/umn/source/faqs/security/how_many_security_groups_can_i_create.rst b/umn/source/faq/security/how_many_security_groups_can_i_create.rst similarity index 100% rename from umn/source/faqs/security/how_many_security_groups_can_i_create.rst rename to umn/source/faq/security/how_many_security_groups_can_i_create.rst diff --git a/umn/source/faqs/security/index.rst b/umn/source/faq/security/index.rst similarity index 100% rename from umn/source/faqs/security/index.rst rename to umn/source/faq/security/index.rst diff --git a/umn/source/faqs/security/which_security_group_rule_has_priority_when_multiple_security_group_rules_conflict.rst b/umn/source/faq/security/which_security_group_rule_has_priority_when_multiple_security_group_rules_conflict.rst similarity index 100% rename from umn/source/faqs/security/which_security_group_rule_has_priority_when_multiple_security_group_rules_conflict.rst rename to umn/source/faq/security/which_security_group_rule_has_priority_when_multiple_security_group_rules_conflict.rst diff --git a/umn/source/faqs/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst b/umn/source/faq/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst similarity index 100% rename from umn/source/faqs/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst rename to umn/source/faq/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst diff --git a/umn/source/faqs/vpc_peering_connections/how_many_vpc_peering_connections_can_i_create_in_an_account.rst b/umn/source/faq/vpc_peering_connections/how_many_vpc_peering_connections_can_i_create_in_an_account.rst similarity index 100% rename from umn/source/faqs/vpc_peering_connections/how_many_vpc_peering_connections_can_i_create_in_an_account.rst rename to umn/source/faq/vpc_peering_connections/how_many_vpc_peering_connections_can_i_create_in_an_account.rst diff --git a/umn/source/faqs/vpc_peering_connections/index.rst b/umn/source/faq/vpc_peering_connections/index.rst similarity index 100% rename from umn/source/faqs/vpc_peering_connections/index.rst rename to umn/source/faq/vpc_peering_connections/index.rst diff --git a/umn/source/faqs/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst b/umn/source/faq/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst similarity index 100% rename from umn/source/faqs/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst rename to umn/source/faq/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst diff --git a/umn/source/faqs/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst b/umn/source/faq/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst rename to umn/source/faq/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst diff --git a/umn/source/faqs/vpcs_and_subnets/how_many_subnets_can_i_create.rst b/umn/source/faq/vpcs_and_subnets/how_many_subnets_can_i_create.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/how_many_subnets_can_i_create.rst rename to umn/source/faq/vpcs_and_subnets/how_many_subnets_can_i_create.rst diff --git a/umn/source/faqs/vpcs_and_subnets/index.rst b/umn/source/faq/vpcs_and_subnets/index.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/index.rst rename to umn/source/faq/vpcs_and_subnets/index.rst diff --git a/umn/source/faqs/vpcs_and_subnets/what_are_the_differences_between_the_network_id_and_subnet_id_of_a_subnet.rst b/umn/source/faq/vpcs_and_subnets/what_are_the_differences_between_the_network_id_and_subnet_id_of_a_subnet.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/what_are_the_differences_between_the_network_id_and_subnet_id_of_a_subnet.rst rename to umn/source/faq/vpcs_and_subnets/what_are_the_differences_between_the_network_id_and_subnet_id_of_a_subnet.rst diff --git a/umn/source/faqs/vpcs_and_subnets/what_is_virtual_private_cloud.rst b/umn/source/faq/vpcs_and_subnets/what_is_virtual_private_cloud.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/what_is_virtual_private_cloud.rst rename to umn/source/faq/vpcs_and_subnets/what_is_virtual_private_cloud.rst diff --git a/umn/source/faqs/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst b/umn/source/faq/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst rename to umn/source/faq/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst diff --git a/umn/source/faqs/vpcs_and_subnets/which_cidr_blocks_are_available_for_the_vpc_service.rst b/umn/source/faq/vpcs_and_subnets/which_cidr_blocks_are_available_for_the_vpc_service.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/which_cidr_blocks_are_available_for_the_vpc_service.rst rename to umn/source/faq/vpcs_and_subnets/which_cidr_blocks_are_available_for_the_vpc_service.rst diff --git a/umn/source/faqs/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst b/umn/source/faq/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst similarity index 100% rename from umn/source/faqs/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst rename to umn/source/faq/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst diff --git a/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 b/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 index 09fd885..e394c4b 100644 --- a/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 +++ b/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 @@ -14,12 +14,13 @@ You can assign an EIP and bind it to an ECS so that the ECS can access the Inter 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 created anymore. + - 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" in "API V3" section in the *Elastic IP API Reference*. + - 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. diff --git a/umn/source/index.rst b/umn/source/index.rst index 7dd8710..25cf7f3 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -18,6 +18,6 @@ Virtual Private Cloud - User Guide virtual_ip_address/index monitoring/index permissions_management/index - faqs/index + faq/index change_history glossary diff --git a/umn/source/route_tables/configuring_an_snat_server.rst b/umn/source/route_tables/configuring_an_snat_server.rst index 704a8c8..0426160 100644 --- a/umn/source/route_tables/configuring_an_snat_server.rst +++ b/umn/source/route_tables/configuring_an_snat_server.rst @@ -34,7 +34,7 @@ Procedure #. In the displayed area showing the NIC IP address details, disable **Source/Destination Check**. - By default, the source/destination check is enabled. When this check is enabled, the system checks whether source IP addresses contained in the packets sent by ECSs are correct. If the IP addresses are incorrect, the system does not allow the ECSs to send the packets. This mechanism prevents packet spoofing, thereby improving system security. If the SNAT function is used, the SNAT server needs to forward packets. This mechanism prevents the packet sender from receiving returned packets. Therefore, you need to disable the source/destination check for SNAT servers. + 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. #. Bind an EIP. diff --git a/umn/source/route_tables/deleting_a_route_table.rst b/umn/source/route_tables/deleting_a_route_table.rst index be2d88e..54060dc 100644 --- a/umn/source/route_tables/deleting_a_route_table.rst +++ b/umn/source/route_tables/deleting_a_route_table.rst @@ -15,9 +15,9 @@ Notes and Constraints - The default route table cannot be deleted. -- A custom route table cannot be deleted if it is associated with a subnet. +- A custom route table with a subnet associated cannot be deleted directly. - You associate the subnet with another route table by referring to :ref:`Changing the Route Table Associated with a Subnet ` and then delete the route table. + If you want to delete such a route table, you can associate the subnet with another route table first by referring to :ref:`Changing the Route Table Associated with a Subnet `. Procedure --------- diff --git a/umn/source/route_tables/modifying_a_route.rst b/umn/source/route_tables/modifying_a_route.rst index bb13ae6..2162ac2 100644 --- a/umn/source/route_tables/modifying_a_route.rst +++ b/umn/source/route_tables/modifying_a_route.rst @@ -14,7 +14,7 @@ Notes and Constraints --------------------- - System routes cannot be modified. -- When you create a VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or 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 --------- diff --git a/umn/source/route_tables/replicating_a_route.rst b/umn/source/route_tables/replicating_a_route.rst index 4c1ede9..ac3643c 100644 --- a/umn/source/route_tables/replicating_a_route.rst +++ b/umn/source/route_tables/replicating_a_route.rst @@ -13,39 +13,39 @@ This section describes how to replicate routes among all route tables of a VPC. Notes and Constraints --------------------- -:ref:`Table 1 ` shows the types of routes that can be replicated. +:ref:`Table 1 ` shows whether routes of different types can be replicated to default or custom route tables. -For example, if the next hop of a route is a server, this route can be replicated to the default or custom route table. If the next hop 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. +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. .. _vpc_route01_0013__route_0001_table1727714140542: -.. table:: **Table 1** Route replication description +.. table:: **Table 1** Route replication - +------------------------+-----------------------------------+----------------------------------+ - | Next Hop Type | Replicated to Default Route Table | Replicated to Custom Route Table | - +========================+===================================+==================================+ - | Local | Not supported | Not supported | - +------------------------+-----------------------------------+----------------------------------+ - | Server | Supported | Supported | - +------------------------+-----------------------------------+----------------------------------+ - | Extension NIC | Supported | Supported | - +------------------------+-----------------------------------+----------------------------------+ - | VPN connection | Not supported | Supported | - +------------------------+-----------------------------------+----------------------------------+ - | Direct Connect gateway | Not supported | Supported | - +------------------------+-----------------------------------+----------------------------------+ - | NAT gateway | Supported | Supported | - +------------------------+-----------------------------------+----------------------------------+ - | VPC peering connection | Supported | Supported | - +------------------------+-----------------------------------+----------------------------------+ - | Virtual IP address | Supported | Supported | - +------------------------+-----------------------------------+----------------------------------+ + +------------------------+------------------------------------------+-----------------------------------------+ + | Next Hop Type | Can Be Replicated to Default Route Table | Can Be Replicated to Custom Route Table | + +========================+==========================================+=========================================+ + | Local | No | No | + +------------------------+------------------------------------------+-----------------------------------------+ + | Server | Yes | Yes | + +------------------------+------------------------------------------+-----------------------------------------+ + | Extension NIC | Yes | Yes | + +------------------------+------------------------------------------+-----------------------------------------+ + | VPN connection | No | Yes | + +------------------------+------------------------------------------+-----------------------------------------+ + | Direct Connect gateway | No | Yes | + +------------------------+------------------------------------------+-----------------------------------------+ + | NAT gateway | Yes | Yes | + +------------------------+------------------------------------------+-----------------------------------------+ + | VPC peering connection | Yes | Yes | + +------------------------+------------------------------------------+-----------------------------------------+ + | Virtual IP address | Yes | Yes | + +------------------------+------------------------------------------+-----------------------------------------+ .. note:: - 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 the 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 the custom route table. + - 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 --------- @@ -58,11 +58,11 @@ Procedure #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. -#. In the route table list, locate the row that contains the target route table and click **Replicate Route** in the **Operation** column. +#. 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. -#. Select the target route table and then the route to be replicated as prompted. +#. Select the target route table that you want to replicate route to and the routes to be replicated as prompted. - The routes listed on the page 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. + 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. #. Click **OK**. diff --git a/umn/source/route_tables/route_table_overview.rst b/umn/source/route_tables/route_table_overview.rst index 5e1efba..6bcad36 100644 --- a/umn/source/route_tables/route_table_overview.rst +++ b/umn/source/route_tables/route_table_overview.rst @@ -16,7 +16,7 @@ Default Route Table and Custom 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. - 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 VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or 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. If you do not want to use the default route table, you can now create a custom route table and associate it with the subnet. You can delete the custom route table if it is no longer required. @@ -44,7 +44,7 @@ A route is configured with the destination, next hop type, and next hop to deter 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. :ref:`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. + You cannot add two routes with the same destination to a VPC route table even if their next hop types are different, because the destination determines the route priority. According to the longest match routing rule, the destination with a higher matching degree is preferentially selected for packet forwarding. .. _vpc_route01_0001__table1727714140542: @@ -59,7 +59,7 @@ A route is configured with the destination, next hop type, and next hop to deter | Extension NIC | Traffic intended for the destination is forwarded to the extension NIC of an ECS in the VPC. | - Default route table | | | | - Custom route table | +--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ - | BMS user-defined network | Traffic intended for the destination is forwarded to a BMS user-defined network. | - Default route table | + | 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. | - Default route table | | | | - Custom route table | +--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ | VPN connection | Traffic intended for the destination is forwarded to a VPN gateway. | Custom route table | diff --git a/umn/source/security/firewall/adding_a_firewall_rule.rst b/umn/source/security/firewall/adding_a_firewall_rule.rst index 8b664b6..57fa634 100644 --- a/umn/source/security/firewall/adding_a_firewall_rule.rst +++ b/umn/source/security/firewall/adding_a_firewall_rule.rst @@ -19,7 +19,7 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. diff --git a/umn/source/security/firewall/associating_subnets_with_a_firewall.rst b/umn/source/security/firewall/associating_subnets_with_a_firewall.rst index 80ed752..eb4a1e2 100644 --- a/umn/source/security/firewall/associating_subnets_with_a_firewall.rst +++ b/umn/source/security/firewall/associating_subnets_with_a_firewall.rst @@ -8,7 +8,7 @@ Associating Subnets with a Firewall Scenarios --------- -On the page showing firewall details, associate desired subnets with a firewall. After a firewall is associated with a subnet, the firewall denies all traffic to and from the subnet until you add rules to allow traffic. +On the page showing firewall details, you can associate desired subnets with a firewall. After a firewall is associated with a subnet, the firewall denies all traffic to and from the subnet until you add rules to allow traffic. Procedure --------- @@ -17,7 +17,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. 6. On the displayed page, click the **Associated Subnets** tab. 7. On the **Associated Subnets** page, click **Associate**. @@ -25,7 +25,7 @@ Procedure .. note:: - Subnets that have already been associated with firewalls will not be displayed on the page for you to select. One-click subnet association and disassociation are not currently supported. Furthermore, a subnet can only be associated with one firewall. If you want to reassociate a subnet that has already been associated with another firewall, you must first disassociate the subnet from the original firewall. + Subnets with firewalls 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. .. |image1| image:: /_static/images/en-us_image_0141273034.png .. |image2| image:: /_static/images/en-us_image_0000001500905066.png diff --git a/umn/source/security/firewall/changing_the_sequence_of_a_firewall_rule.rst b/umn/source/security/firewall/changing_the_sequence_of_a_firewall_rule.rst index 508e535..4708ccf 100644 --- a/umn/source/security/firewall/changing_the_sequence_of_a_firewall_rule.rst +++ b/umn/source/security/firewall/changing_the_sequence_of_a_firewall_rule.rst @@ -21,7 +21,7 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. diff --git a/umn/source/security/firewall/creating_a_firewall.rst b/umn/source/security/firewall/creating_a_firewall.rst index a2c1163..e339786 100644 --- a/umn/source/security/firewall/creating_a_firewall.rst +++ b/umn/source/security/firewall/creating_a_firewall.rst @@ -8,7 +8,7 @@ Creating a Firewall Scenarios --------- -You can create a custom firewall, but any newly created firewall will be disabled by default. It will not have any inbound or outbound rules, or have any subnets associated. Each user can create up to 200 firewalls by default. +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. Each user can create up to 200 firewalls by default. Procedure --------- @@ -19,11 +19,11 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. -5. In the right pane displayed, click **Create firewall**. +5. In the right pane displayed, click **Create Firewall**. -6. On the **Create firewall** page, configure parameters as prompted. +6. On the **Create Firewall** page, configure parameters as prompted. .. figure:: /_static/images/en-us_image_0129304042.png diff --git a/umn/source/security/firewall/deleting_a_firewall.rst b/umn/source/security/firewall/deleting_a_firewall.rst index b3d9b0a..83438d3 100644 --- a/umn/source/security/firewall/deleting_a_firewall.rst +++ b/umn/source/security/firewall/deleting_a_firewall.rst @@ -17,13 +17,13 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. -5. Locate the target firewall in the right pane, click **More** in the **Operation** column, and click **Delete**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. +5. Locate the firewall in the right pane, click **More** in the **Operation** column, and click **Delete**. 6. Click **Yes**. .. note:: - After a firewall is deleted, associated subnets are disassociated and added rules are deleted from the firewall. + Deleting a firewall will also disassociate its associated subnets and delete the firewall rules. .. |image1| image:: /_static/images/en-us_image_0141273034.png .. |image2| image:: /_static/images/en-us_image_0000001500905066.png diff --git a/umn/source/security/firewall/deleting_a_firewall_rule.rst b/umn/source/security/firewall/deleting_a_firewall_rule.rst index 901adf5..618b29e 100644 --- a/umn/source/security/firewall/deleting_a_firewall_rule.rst +++ b/umn/source/security/firewall/deleting_a_firewall_rule.rst @@ -17,7 +17,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. 6. On the **Inbound Rules** or **Outbound Rules** tab, locate the row that contains the target rule and click **Delete** in the **Operation** column. 7. Click **Yes** in the displayed dialog box. diff --git a/umn/source/security/firewall/disassociating_a_subnet_from_a_firewall.rst b/umn/source/security/firewall/disassociating_a_subnet_from_a_firewall.rst index 413094d..848807e 100644 --- a/umn/source/security/firewall/disassociating_a_subnet_from_a_firewall.rst +++ b/umn/source/security/firewall/disassociating_a_subnet_from_a_firewall.rst @@ -17,7 +17,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. 6. On the displayed page, click the **Associated Subnets** tab. 7. On the **Associated Subnets** page, locate the row that contains the target subnet and click **Disassociate** in the **Operation** column. @@ -25,7 +25,7 @@ Procedure **Disassociating subnets from a firewall** -Select multiple subnets and click **Disassociate** above the subnet list to disassociate the subnets from the current firewall at a time. +Select multiple subnets and click **Disassociate** above the subnet list to disassociate the subnets from a firewall at a time. .. |image1| image:: /_static/images/en-us_image_0141273034.png .. |image2| image:: /_static/images/en-us_image_0000001500905066.png diff --git a/umn/source/security/firewall/enabling_or_disabling_a_firewall.rst b/umn/source/security/firewall/enabling_or_disabling_a_firewall.rst index bd56be3..e2fa5ca 100644 --- a/umn/source/security/firewall/enabling_or_disabling_a_firewall.rst +++ b/umn/source/security/firewall/enabling_or_disabling_a_firewall.rst @@ -19,8 +19,8 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. -5. Locate the row that contains the target firewall in the right pane, click **More** in the **Operation** column, and click **Enable** or **Disable**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. +5. Locate the row that contains the firewall in the right pane, click **More** in the **Operation** column, and click **Enable** or **Disable**. 6. Click **Yes** in the displayed dialog box. .. |image1| image:: /_static/images/en-us_image_0141273034.png diff --git a/umn/source/security/firewall/enabling_or_disabling_a_firewall_rule.rst b/umn/source/security/firewall/enabling_or_disabling_a_firewall_rule.rst index 5d30583..1684a77 100644 --- a/umn/source/security/firewall/enabling_or_disabling_a_firewall_rule.rst +++ b/umn/source/security/firewall/enabling_or_disabling_a_firewall_rule.rst @@ -19,7 +19,7 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. diff --git a/umn/source/security/firewall/firewall_overview.rst b/umn/source/security/firewall/firewall_overview.rst index d12d29d..de893bb 100644 --- a/umn/source/security/firewall/firewall_overview.rst +++ b/umn/source/security/firewall/firewall_overview.rst @@ -34,7 +34,7 @@ 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 +- 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. @@ -44,7 +44,7 @@ By default, each firewall has preset rules that allow the following packets: - 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 ones. :ref:`Table 1 ` shows the default firewall rules. You cannot modify or delete the default rules. +- A firewall denies all traffic in and out of a subnet excepting the preceding packets. :ref:`Table 1 ` shows the default rules. You cannot modify or delete the default rules. .. _acl_0001__table1034601475112: diff --git a/umn/source/security/firewall/modifying_a_firewall.rst b/umn/source/security/firewall/modifying_a_firewall.rst index 7ad07ea..8e8dfc7 100644 --- a/umn/source/security/firewall/modifying_a_firewall.rst +++ b/umn/source/security/firewall/modifying_a_firewall.rst @@ -17,7 +17,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. 6. On the displayed page, click |image3| on the right of **Name** and edit the firewall name. 7. Click Y to save the new firewall name. diff --git a/umn/source/security/firewall/modifying_a_firewall_rule.rst b/umn/source/security/firewall/modifying_a_firewall_rule.rst index 784d13a..7e217db 100644 --- a/umn/source/security/firewall/modifying_a_firewall_rule.rst +++ b/umn/source/security/firewall/modifying_a_firewall_rule.rst @@ -19,7 +19,7 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. diff --git a/umn/source/security/firewall/viewing_a_firewall.rst b/umn/source/security/firewall/viewing_a_firewall.rst index 4595dd2..238258b 100644 --- a/umn/source/security/firewall/viewing_a_firewall.rst +++ b/umn/source/security/firewall/viewing_a_firewall.rst @@ -17,7 +17,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. In the navigation pane on the left, choose **Access Control** > **firewalls**. +4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. 6. 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. diff --git a/umn/source/security/security_group/security_group_overview.rst b/umn/source/security/security_group/security_group_overview.rst index 49d8a14..f470b83 100644 --- a/umn/source/security/security_group/security_group_overview.rst +++ b/umn/source/security/security_group/security_group_overview.rst @@ -69,7 +69,6 @@ Security Group Constraints - By default, you can create a maximum of 100 security groups in your cloud account. - By default, you can add up to 50 security group rules to a security group. -- By default, you can add an ECS or extension NIC to up to five security groups. In such a case, the rules of all the selected security groups are aggregated to take effect. - When creating a private network load balancer, you need to select a desired security group. Do not delete the default security group rules or ensure that the following requirements are met: - Outbound rules: only allow data packets to the selected security group or only data packets from the peer load balancer. diff --git a/umn/source/service_overview/basic_concepts/route_table.rst b/umn/source/service_overview/basic_concepts/route_table.rst index 37810de..e4d01a3 100644 --- a/umn/source/service_overview/basic_concepts/route_table.rst +++ b/umn/source/service_overview/basic_concepts/route_table.rst @@ -22,7 +22,7 @@ Default Route Table and Custom 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. - 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 VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or 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. If you do not want to use the default route table, you can now create a custom route table and associate it with the subnet. You can delete the custom route table if it is no longer required. @@ -65,7 +65,7 @@ A route is configured with the destination, next hop type, and next hop to deter | Extension NIC | Traffic intended for the destination is forwarded to the extension NIC of an ECS in the VPC. | - Default route table | | | | - Custom route table | +--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ - | BMS user-defined network | Traffic intended for the destination is forwarded to a BMS user-defined network. | - Default route table | + | 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. | - Default route table | | | | - Custom route table | +--------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ | VPN connection | Traffic intended for the destination is forwarded to a VPN gateway. | Custom route table | diff --git a/umn/source/service_overview/basic_concepts/snat.rst b/umn/source/service_overview/basic_concepts/snat.rst index 7c5a8a2..1581b54 100644 --- a/umn/source/service_overview/basic_concepts/snat.rst +++ b/umn/source/service_overview/basic_concepts/snat.rst @@ -5,7 +5,7 @@ SNAT ==== -In addition to services provided by the system, some ECSs need to access the Internet to obtain information or download software. You can bind EIPs to virtual NICs (ports) of ECSs to enable the ECSs to access the Internet. However, assigning an EIP to each ECS consumes already-limited IPv4 addresses, incurs additional costs, and may increase the attack surface for a virtual environment. Therefore, SNAT is introduced to enable multiple ECSs to share one EIP. +In addition to services provided by the system, some ECSs need to access the Internet to obtain information or download software. You can bind EIPs to virtual NICs (ports) of ECSs to enable the ECSs to access the Internet. However, assigning an EIP to each ECS consumes IPv4 addresses, incurs additional costs, and may increase the attack surface for a virtual environment. Therefore, SNAT is introduced to enable multiple ECSs to share one EIP. On a public cloud, an EIP can be assigned to an ECS that serves as the SNAT router or gateway for other ECSs from the same subnet or VPC. diff --git a/umn/source/service_overview/notes_and_constraints.rst b/umn/source/service_overview/notes_and_constraints.rst index a3706fd..2209681 100644 --- a/umn/source/service_overview/notes_and_constraints.rst +++ b/umn/source/service_overview/notes_and_constraints.rst @@ -10,7 +10,6 @@ Security Group - By default, you can create a maximum of 100 security groups in your cloud account. - By default, you can add up to 50 security group rules to a security group. -- By default, you can add an ECS or extension NIC to up to five security groups. In such a case, the rules of all the selected security groups are aggregated to take effect. - When creating a private network load balancer, you need to select a desired security group. Do not delete the default security group rules or ensure that the following requirements are met: - Outbound rules: only allow data packets to the selected security group or only data packets from the peer load balancer. @@ -28,7 +27,7 @@ Route Table ----------- - 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 VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or 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. VPC Peering Connection ---------------------- @@ -49,13 +48,6 @@ Virtual IP Address - Virtual IP addresses are not recommended when multiple NICs in the same subnet are configured on an ECS. It is too easy for there to be route conflicts on the ECS, which would cause communication failure using the virtual IP address. -- It is recommended that no more than eight virtual IP addresses be bound to an ECS. -- A virtual IP address can be bound to up to 10 ECSs. - - .. note:: - - If you bind a virtual IP address to an ECS, the virtual IP address is also associated with the security groups of the ECS. A virtual IP address can be associated with up to 10 security groups. - EIP --- diff --git a/umn/source/shared_bandwidth/shared_bandwidth_overview.rst b/umn/source/shared_bandwidth/shared_bandwidth_overview.rst index 13f5bca..8be79a2 100644 --- a/umn/source/shared_bandwidth/shared_bandwidth_overview.rst +++ b/umn/source/shared_bandwidth/shared_bandwidth_overview.rst @@ -15,7 +15,7 @@ When you host a large number of applications on the cloud, if each EIP uses a ba - Flexible Operations - You can add EIPs (excepting for **5_gray** EIPs) to or remove them from a shared bandwidth regardless of the type of instances that they are bound to. + 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. .. note:: diff --git a/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst b/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst index 277e1dc..d8c4e5a 100644 --- a/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst +++ b/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst @@ -10,6 +10,7 @@ Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) #. Under **Computing**, click **Elastic Cloud Server**. #. In the ECS list, click the ECS name. #. On the displayed ECS details page, click the **NICs** tab. +#. Click the IP address to view the NIC details. #. Check that **Source/Destination Check** is disabled. .. |image1| image:: /_static/images/en-us_image_0141273034.png diff --git a/umn/source/virtual_ip_address/virtual_ip_address_overview.rst b/umn/source/virtual_ip_address/virtual_ip_address_overview.rst index 4be367c..79fff81 100644 --- a/umn/source/virtual_ip_address/virtual_ip_address_overview.rst +++ b/umn/source/virtual_ip_address/virtual_ip_address_overview.rst @@ -88,9 +88,3 @@ Notes and Constraints sysctl -p /etc/sysctl.conf - Each virtual IP address can be bound to only one EIP. -- It is recommended that no more than eight virtual IP addresses be bound to an ECS. -- A virtual IP address can be bound to up to 10 ECSs. - - .. note:: - - If you bind a virtual IP address to an ECS, the virtual IP address is also associated with the security groups of the ECS. A virtual IP address can be associated with up to 10 security groups.