From fd5fb0dad41d47b13e63a4918a165e3ac21d8003 Mon Sep 17 00:00:00 2001 From: OpenTelekomCloud Proposal Bot Date: Tue, 19 Sep 2023 10:50:34 +0000 Subject: [PATCH] Update content --- .../images/en-us_image_0000001151300782.png | Bin 7846 -> 0 bytes .../images/en-us_image_0000001229959315.png | Bin 35050 -> 0 bytes .../images/en-us_image_0000001267230305.png | Bin 391 -> 0 bytes .../images/en-us_image_0000001267350317.png | Bin 391 -> 0 bytes ...6.png => en-us_image_0000001626574358.png} | Bin ...0.png => en-us_image_0000001626574362.png} | Bin ...4.png => en-us_image_0000001626574366.png} | Bin ...2.png => en-us_image_0000001626574370.png} | Bin ...0.png => en-us_image_0000001626575750.png} | Bin ...4.png => en-us_image_0000001626576382.png} | Bin ...2.png => en-us_image_0000001626576858.png} | Bin ...4.png => en-us_image_0000001626578706.png} | Bin ...8.png => en-us_image_0000001626734158.png} | Bin ...8.png => en-us_image_0000001626734162.png} | Bin ...6.png => en-us_image_0000001626734166.png} | Bin ...0.png => en-us_image_0000001626734174.png} | Bin ...3.png => en-us_image_0000001626735566.png} | Bin ...7.png => en-us_image_0000001626735570.png} | Bin ...3.png => en-us_image_0000001626736198.png} | Bin ...7.png => en-us_image_0000001626736678.png} | Bin ...1.png => en-us_image_0000001626736794.png} | Bin ...5.png => en-us_image_0000001626738526.png} | Bin ...9.png => en-us_image_0000001626894086.png} | Bin .../images/en-us_image_0000001626894090.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001626894094.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001626894098.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001626894106.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001626894110.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001626895486.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001626896590.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001626897562.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627052380.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627054054.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627054058.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627054062.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627054082.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627055450.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627055454.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627056086.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627056574.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627056686.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001627174280.png | Bin 0 -> 356 bytes .../images/en-us_image_0000001627334080.png | Bin 0 -> 222 bytes .../images/en-us_image_0000001627493158.png | Bin 0 -> 8699 bytes .../images/en-us_image_0000001627653972.png | Bin 0 -> 8727 bytes .../images/en-us_image_0000001627744152.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675254013.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675254017.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675254021.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675254033.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675255405.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675256029.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675256529.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675256657.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675258381.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675258889.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675373901.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675373905.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675373909.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675373913.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675373917.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675375297.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675375405.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675378241.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675413821.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675413825.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675413829.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675413833.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675413841.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675413845.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675415213.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675415841.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675416345.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675418673.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675613933.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675613937.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675613941.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675613945.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675613953.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675613957.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675615337.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675616433.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675616561.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675618277.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675619157.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001675813933.png | Bin 0 -> 356 bytes .../images/en-us_image_0000001676063997.png | Bin 0 -> 128 bytes .../images/en-us_image_0000001681512581.png | Bin 0 -> 128 bytes ..._between_security_groups_and_firewalls.rst | 0 .../firewall/adding_a_firewall_rule.rst | 9 +- .../associating_subnets_with_a_firewall.rst | 17 ++- ...anging_the_sequence_of_a_firewall_rule.rst | 4 +- .../firewall/creating_a_firewall.rst | 6 +- .../firewall/deleting_a_firewall.rst | 10 +- .../firewall/deleting_a_firewall_rule.rst | 9 +- ...isassociating_a_subnet_from_a_firewall.rst | 10 +- .../enabling_or_disabling_a_firewall.rst | 10 +- .../enabling_or_disabling_a_firewall_rule.rst | 4 +- .../firewall_configuration_examples.rst | 0 .../firewall/firewall_overview.rst | 4 +- .../firewall/index.rst | 0 .../firewall/modifying_a_firewall.rst | 11 +- .../firewall/modifying_a_firewall_rule.rst | 4 +- .../firewall/viewing_a_firewall.rst | 8 +- .../{security => access_control}/index.rst | 4 +- .../adding_a_security_group_rule.rst | 30 +++-- ...ing_an_instance_from_a_security_group.rst} | 26 +++- .../changing_the_security_group_of_an_ecs.rst | 0 .../cloning_a_security_group.rst | 12 +- .../creating_a_security_group.rst | 78 ++++++------ .../default_security_group.rst} | 4 +- .../deleting_a_security_group.rst | 10 +- .../deleting_a_security_group_rule.rst | 9 +- .../fast-adding_security_group_rules.rst | 88 ++++++------- ...ing_and_exporting_security_group_rules.rst | 18 ++- .../security_group/index.rst | 40 +++--- .../modifying_a_security_group.rst | 22 +++- .../modifying_a_security_group_rule.rst | 10 +- .../replicating_a_security_group_rule.rst | 4 +- .../security_group_configuration_examples.rst | 0 ...curity_groups_and_security_group_rules.rst | 107 ++++++++++++++++ .../viewing_the_security_group_of_an_ecs.rst | 3 +- umn/source/change_history.rst | 22 +++- ..._eip_from_an_ecs_and_releasing_the_eip.rst | 2 +- .../how_do_i_buy_a_shared_bandwidth.rst | 15 --- umn/source/faq/bandwidth/index.rst | 2 - .../how_many_firewalls_can_i_create.rst | 8 -- .../how_many_security_groups_can_i_create.rst | 10 -- umn/source/faq/security/index.rst | 6 +- .../why_cant_i_delete_a_security_group.rst | 16 +++ ...an_subnets_communicate_with_each_other.rst | 3 +- .../what_subnet_cidr_blocks_are_available.rst | 4 +- .../why_cant_i_delete_my_vpcs_and_subnets.rst | 4 +- .../index.rst | 116 +++++++++--------- .../step_1_create_a_vpc.rst | 116 +++++++++--------- .../step_2_create_a_subnet_for_the_vpc.rst | 66 +++++----- .../step_4_create_a_security_group.rst | 74 +++++------ .../step_5_add_a_security_group_rule.rst | 26 ++-- .../step_1_create_a_vpc.rst | 116 +++++++++--------- .../step_2_create_a_subnet_for_the_vpc.rst | 66 +++++----- .../step_3_create_a_security_group.rst | 74 +++++------ .../step_4_add_a_security_group_rule.rst | 26 ++-- umn/source/index.rst | 2 +- .../monitoring/creating_an_alarm_rule.rst | 3 +- umn/source/monitoring/viewing_metrics.rst | 6 +- ...ng_a_user_and_granting_vpc_permissions.rst | 7 +- .../route_tables/adding_a_custom_route.rst | 9 +- ...ssociating_a_route_table_with_a_subnet.rst | 15 ++- ...e_route_table_associated_with_a_subnet.rst | 4 +- .../creating_a_custom_route_table.rst | 11 +- umn/source/route_tables/deleting_a_route.rst | 4 +- .../route_tables/deleting_a_route_table.rst | 14 ++- .../exporting_route_table_information.rst | 4 +- umn/source/route_tables/modifying_a_route.rst | 9 +- .../route_tables/replicating_a_route.rst | 16 +-- .../viewing_route_table_information.rst | 4 +- ...e_route_table_associated_with_a_subnet.rst | 4 +- .../security_group_overview.rst | 85 ------------- .../basic_concepts/route_table.rst | 13 +- .../basic_concepts/security_group.rst | 32 +++-- .../basic_concepts/shared_snat.rst | 10 +- umn/source/service_overview/index.rst | 2 - .../notes_and_constraints.rst | 69 ----------- umn/source/service_overview/permissions.rst | 4 +- .../adding_eips_to_a_shared_bandwidth.rst | 10 +- .../deleting_a_shared_bandwidth.rst | 1 + .../shared_bandwidth_overview.rst | 4 + .../assigning_a_virtual_ip_address.rst | 11 +- ...binding_a_virtual_ip_address_to_an_eip.rst | 10 +- ..._a_virtual_ip_address_to_an_eip_or_ecs.rst | 14 ++- ...bling_ip_forwarding_on_the_standby_ecs.rst | 57 +++++++++ ...eck_ha_load_balancing_cluster_scenario.rst | 16 --- ...ource_destination_check_for_an_ecs_nic.rst | 25 ++++ umn/source/virtual_ip_address/index.rst | 6 +- .../releasing_a_virtual_ip_address.rst | 4 +- ...nding_a_virtual_ip_address_from_an_eip.rst | 4 +- ..._a_virtual_ip_address_from_an_instance.rst | 4 +- .../virtual_ip_address_overview.rst | 25 +--- .../subnet/creating_a_subnet_for_the_vpc.rst | 66 +++++----- .../subnet/deleting_a_subnet.rst | 6 +- .../subnet/exporting_subnet_list.rst | 4 +- .../subnet/managing_subnet_tags.rst | 16 ++- .../subnet/modifying_a_subnet.rst | 8 +- ...ing_and_deleting_resources_in_a_subnet.rst | 4 +- .../viewing_ip_addresses_in_a_subnet.rst | 6 +- .../vpc_and_subnet/vpc/creating_a_vpc.rst | 116 +++++++++--------- .../vpc_and_subnet/vpc/deleting_a_vpc.rst | 4 +- .../vpc_and_subnet/vpc/exporting_vpc_list.rst | 10 +- .../vpc_and_subnet/vpc/managing_vpc_tags.rst | 15 ++- .../vpc_and_subnet/vpc/modifying_a_vpc.rst | 94 ++++++++------ .../vpc_and_subnet/vpc/obtaining_a_vpc_id.rst | 6 +- .../vpc/viewing_a_vpc_topology.rst | 4 +- .../vpc_flow_log/creating_a_vpc_flow_log.rst | 4 +- .../vpc_flow_log/deleting_a_vpc_flow_log.rst | 4 +- .../enabling_or_disabling_vpc_flow_log.rst | 4 +- .../vpc_flow_log/viewing_a_vpc_flow_log.rst | 4 +- .../vpc_flow_log/vpc_flow_log_overview.rst | 5 +- ...nnection_with_a_vpc_in_another_account.rst | 10 +- ...ction_with_another_vpc_in_your_account.rst | 10 +- .../deleting_a_vpc_peering_connection.rst | 3 +- ...onfigured_for_a_vpc_peering_connection.rst | 8 +- .../modifying_a_vpc_peering_connection.rst | 3 +- ...onfigured_for_a_vpc_peering_connection.rst | 8 +- ...project_id_of_a_vpc_peering_connection.rst | 2 +- ...onfigured_for_a_vpc_peering_connection.rst | 8 +- .../viewing_vpc_peering_connections.rst | 3 +- .../vpc_peering_connection_usage_examples.rst | 7 +- 207 files changed, 1320 insertions(+), 983 deletions(-) delete mode 100644 umn/source/_static/images/en-us_image_0000001151300782.png delete mode 100644 umn/source/_static/images/en-us_image_0000001229959315.png delete mode 100644 umn/source/_static/images/en-us_image_0000001267230305.png delete mode 100644 umn/source/_static/images/en-us_image_0000001267350317.png rename umn/source/_static/images/{en-us_image_0000001500905066.png => en-us_image_0000001626574358.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503011070.png => en-us_image_0000001626574362.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503011074.png => en-us_image_0000001626574366.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503159042.png => en-us_image_0000001626574370.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503170970.png => en-us_image_0000001626575750.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503170974.png => en-us_image_0000001626576382.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503318922.png => en-us_image_0000001626576858.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503330854.png => en-us_image_0000001626578706.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503330858.png => en-us_image_0000001626734158.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503478818.png => en-us_image_0000001626734162.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503490746.png => en-us_image_0000001626734166.png} (100%) rename umn/source/_static/images/{en-us_image_0000001503490750.png => en-us_image_0000001626734174.png} (100%) rename umn/source/_static/images/{en-us_image_0000001553650753.png => en-us_image_0000001626735566.png} (100%) rename umn/source/_static/images/{en-us_image_0000001553650757.png => en-us_image_0000001626735570.png} (100%) rename umn/source/_static/images/{en-us_image_0000001553770733.png => en-us_image_0000001626736198.png} (100%) rename umn/source/_static/images/{en-us_image_0000001553770737.png => en-us_image_0000001626736678.png} (100%) rename umn/source/_static/images/{en-us_image_0000001553930581.png => en-us_image_0000001626736794.png} (100%) rename umn/source/_static/images/{en-us_image_0000001554010645.png => en-us_image_0000001626738526.png} (100%) rename umn/source/_static/images/{en-us_image_0000001554010649.png => en-us_image_0000001626894086.png} (100%) create mode 100644 umn/source/_static/images/en-us_image_0000001626894090.png create mode 100644 umn/source/_static/images/en-us_image_0000001626894094.png create mode 100644 umn/source/_static/images/en-us_image_0000001626894098.png create mode 100644 umn/source/_static/images/en-us_image_0000001626894106.png create mode 100644 umn/source/_static/images/en-us_image_0000001626894110.png create mode 100644 umn/source/_static/images/en-us_image_0000001626895486.png create mode 100644 umn/source/_static/images/en-us_image_0000001626896590.png create mode 100644 umn/source/_static/images/en-us_image_0000001626897562.png create mode 100644 umn/source/_static/images/en-us_image_0000001627052380.png create mode 100644 umn/source/_static/images/en-us_image_0000001627054054.png create mode 100644 umn/source/_static/images/en-us_image_0000001627054058.png create mode 100644 umn/source/_static/images/en-us_image_0000001627054062.png create mode 100644 umn/source/_static/images/en-us_image_0000001627054082.png create mode 100644 umn/source/_static/images/en-us_image_0000001627055450.png create mode 100644 umn/source/_static/images/en-us_image_0000001627055454.png create mode 100644 umn/source/_static/images/en-us_image_0000001627056086.png create mode 100644 umn/source/_static/images/en-us_image_0000001627056574.png create mode 100644 umn/source/_static/images/en-us_image_0000001627056686.png create mode 100644 umn/source/_static/images/en-us_image_0000001627174280.png create mode 100644 umn/source/_static/images/en-us_image_0000001627334080.png create mode 100644 umn/source/_static/images/en-us_image_0000001627493158.png create mode 100644 umn/source/_static/images/en-us_image_0000001627653972.png create mode 100644 umn/source/_static/images/en-us_image_0000001627744152.png create mode 100644 umn/source/_static/images/en-us_image_0000001675254013.png create mode 100644 umn/source/_static/images/en-us_image_0000001675254017.png create mode 100644 umn/source/_static/images/en-us_image_0000001675254021.png create mode 100644 umn/source/_static/images/en-us_image_0000001675254033.png create mode 100644 umn/source/_static/images/en-us_image_0000001675255405.png create mode 100644 umn/source/_static/images/en-us_image_0000001675256029.png create mode 100644 umn/source/_static/images/en-us_image_0000001675256529.png create mode 100644 umn/source/_static/images/en-us_image_0000001675256657.png create mode 100644 umn/source/_static/images/en-us_image_0000001675258381.png create mode 100644 umn/source/_static/images/en-us_image_0000001675258889.png create mode 100644 umn/source/_static/images/en-us_image_0000001675373901.png create mode 100644 umn/source/_static/images/en-us_image_0000001675373905.png create mode 100644 umn/source/_static/images/en-us_image_0000001675373909.png create mode 100644 umn/source/_static/images/en-us_image_0000001675373913.png create mode 100644 umn/source/_static/images/en-us_image_0000001675373917.png create mode 100644 umn/source/_static/images/en-us_image_0000001675375297.png create mode 100644 umn/source/_static/images/en-us_image_0000001675375405.png create mode 100644 umn/source/_static/images/en-us_image_0000001675378241.png create mode 100644 umn/source/_static/images/en-us_image_0000001675413821.png create mode 100644 umn/source/_static/images/en-us_image_0000001675413825.png create mode 100644 umn/source/_static/images/en-us_image_0000001675413829.png create mode 100644 umn/source/_static/images/en-us_image_0000001675413833.png create mode 100644 umn/source/_static/images/en-us_image_0000001675413841.png create mode 100644 umn/source/_static/images/en-us_image_0000001675413845.png create mode 100644 umn/source/_static/images/en-us_image_0000001675415213.png create mode 100644 umn/source/_static/images/en-us_image_0000001675415841.png create mode 100644 umn/source/_static/images/en-us_image_0000001675416345.png create mode 100644 umn/source/_static/images/en-us_image_0000001675418673.png create mode 100644 umn/source/_static/images/en-us_image_0000001675613933.png create mode 100644 umn/source/_static/images/en-us_image_0000001675613937.png create mode 100644 umn/source/_static/images/en-us_image_0000001675613941.png create mode 100644 umn/source/_static/images/en-us_image_0000001675613945.png create mode 100644 umn/source/_static/images/en-us_image_0000001675613953.png create mode 100644 umn/source/_static/images/en-us_image_0000001675613957.png create mode 100644 umn/source/_static/images/en-us_image_0000001675615337.png create mode 100644 umn/source/_static/images/en-us_image_0000001675616433.png create mode 100644 umn/source/_static/images/en-us_image_0000001675616561.png create mode 100644 umn/source/_static/images/en-us_image_0000001675618277.png create mode 100644 umn/source/_static/images/en-us_image_0000001675619157.png create mode 100644 umn/source/_static/images/en-us_image_0000001675813933.png create mode 100644 umn/source/_static/images/en-us_image_0000001676063997.png create mode 100644 umn/source/_static/images/en-us_image_0000001681512581.png rename umn/source/{security => access_control}/differences_between_security_groups_and_firewalls.rst (100%) rename umn/source/{security => access_control}/firewall/adding_a_firewall_rule.rst (98%) rename umn/source/{security => access_control}/firewall/associating_subnets_with_a_firewall.rst (71%) rename umn/source/{security => access_control}/firewall/changing_the_sequence_of_a_firewall_rule.rst (91%) rename umn/source/{security => access_control}/firewall/creating_a_firewall.rst (95%) rename umn/source/{security => access_control}/firewall/deleting_a_firewall.rst (76%) rename umn/source/{security => access_control}/firewall/deleting_a_firewall_rule.rst (89%) rename umn/source/{security => access_control}/firewall/disassociating_a_subnet_from_a_firewall.rst (90%) rename umn/source/{security => access_control}/firewall/enabling_or_disabling_a_firewall.rst (82%) rename umn/source/{security => access_control}/firewall/enabling_or_disabling_a_firewall_rule.rst (90%) rename umn/source/{security => access_control}/firewall/firewall_configuration_examples.rst (100%) rename umn/source/{security => access_control}/firewall/firewall_overview.rst (93%) rename umn/source/{security => access_control}/firewall/index.rst (100%) rename umn/source/{security => access_control}/firewall/modifying_a_firewall.rst (89%) rename umn/source/{security => access_control}/firewall/modifying_a_firewall_rule.rst (99%) rename umn/source/{security => access_control}/firewall/viewing_a_firewall.rst (87%) rename umn/source/{security => access_control}/index.rst (92%) rename umn/source/{security => access_control}/security_group/adding_a_security_group_rule.rst (78%) rename umn/source/{security/security_group/adding_instances_to_and_removing_them_from_a_security_group.rst => access_control/security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst} (87%) rename umn/source/{security => access_control}/security_group/changing_the_security_group_of_an_ecs.rst (100%) rename umn/source/{security => access_control}/security_group/cloning_a_security_group.rst (66%) rename umn/source/{security => access_control}/security_group/creating_a_security_group.rst (74%) rename umn/source/{security/security_group/default_security_groups_and_security_group_rules.rst => access_control/security_group/default_security_group.rst} (96%) rename umn/source/{security => access_control}/security_group/deleting_a_security_group.rst (73%) rename umn/source/{security => access_control}/security_group/deleting_a_security_group_rule.rst (93%) rename umn/source/{security => access_control}/security_group/fast-adding_security_group_rules.rst (83%) rename umn/source/{security => access_control}/security_group/importing_and_exporting_security_group_rules.rst (78%) rename umn/source/{security => access_control}/security_group/index.rst (79%) rename umn/source/{security => access_control}/security_group/modifying_a_security_group.rst (87%) rename umn/source/{security => access_control}/security_group/modifying_a_security_group_rule.rst (88%) rename umn/source/{security => access_control}/security_group/replicating_a_security_group_rule.rst (90%) rename umn/source/{security => access_control}/security_group/security_group_configuration_examples.rst (100%) create mode 100644 umn/source/access_control/security_group/security_groups_and_security_group_rules.rst rename umn/source/{security => access_control}/security_group/viewing_the_security_group_of_an_ecs.rst (80%) delete mode 100644 umn/source/faq/bandwidth/how_do_i_buy_a_shared_bandwidth.rst delete mode 100644 umn/source/faq/security/how_many_firewalls_can_i_create.rst delete mode 100644 umn/source/faq/security/how_many_security_groups_can_i_create.rst create mode 100644 umn/source/faq/security/why_cant_i_delete_a_security_group.rst delete mode 100644 umn/source/security/security_group/security_group_overview.rst delete mode 100644 umn/source/service_overview/notes_and_constraints.rst create mode 100644 umn/source/virtual_ip_address/disabling_ip_forwarding_on_the_standby_ecs.rst delete mode 100644 umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst create mode 100644 umn/source/virtual_ip_address/disabling_source_destination_check_for_an_ecs_nic.rst diff --git a/umn/source/_static/images/en-us_image_0000001151300782.png b/umn/source/_static/images/en-us_image_0000001151300782.png deleted file mode 100644 index eb1ae9b407d67278bf665b2e7c981a42794b7101..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 7846 zcmc(Ec{r5+_xG)Z2(6YR<5N@!l`Xr97(&RtmTeeI_I2>7kR@BB$d)Ze_H}HPP}VSJ zG-9%48Dk&IFg)-1e6MHu?>Ce&rY=c$U3NZM;;6HemLB`wR%ES+hKd4=Q#^=tJo|5+hFmYYJ4*`&UviJ9Ut}39Bt0EJec9sE z^ViPr_cRV!-8{qAlkhZPUt{*otNV98*=6ndx8fed`((W~Gkb5Ye;+4S4Hf3(ux1OiHW$ zi3{56i~Kd`m6kSdb;o$PD5Nm9OcprIV}I3OKA?S5@8A?tUR|H2NZgm9`p zxKf#G(7INgC3wfQze^KG!62ygc`k#17moG9wGef6B5`z5cO6;<+ou9EKH5LW9a0&} zf1Z|>4eY$BxQbm*;t5@AofxgFYv@@a)XErwYb90Ngw%f2?N_Y&idh;vAP`IQqY=v$ z^Qir%*;WE2?OFTsRj>kF-*C7{#BEpnU`PEW3|~L&*527E9&n;)CP@c5h4+q{(Lc}` zSRxVz&qCR=^PH{69jsUX=G3~H_+TLM(BIjcWRXNHw-V>UM#$*SGVyIubbLIzcp-V8 zJl{Fv+gSR+>Y``X-piwex-wPZZ>zGxyW?#$E41zx()~<_Zi@!nRIu}jRb3D#v=|67 zu{%vst%YTslJh#kZYj^65@}LX0Ol2MZ~Mno#F|jhK3zl;ez@7rul|p_3{ar7`eBWM z%?v%#HG!hvGDsiVbQDYY7pijjr~rJbGau2`T9$+-Me%5+c{N&6XS(du)_UQAlSQ+x zW$^`2qL=j|it%e9p^D}8m2953k^mHPcm4T#q(OE1+wCFd}- z+E{T^R)Os~?V+F9Ov?v}QW6uC!0PQpCIL9`Qc-0wVbh)dv1C^#Yg79rEcHFUu4(YG z!&FpZW}QPtW{?B(#9=7#tr$!tjYszJ8!|~t^sfzp#K2?`(NfnXaF+YJQ)WTc?cPq* z5B{=<%j|mg!$KLdXAl%Vyl&=)FT@#Z&w!$4iX;@4ncK~oBe#0SqY0mjZn>eMzcKls zsKO!V(q`9-UkAnRtj-mZ1Kt)Fs}y$59~awQCE_|{^pEUzlI1UmQk&csYk1Obsj2~2 z#JewfmH>3GV}@D3RZLxRwXWL|irZWZRK)C4CE)|gE0?5>(@z|S&C~`NRQ=iHfR#JL z?!|InPDNABy=+%*CUV}n@A`XKGFA$$_GK3LO?|f;AY*Nd}ZSRedqSTry zr@V+9#oaK0D=!DTW<$pR(Bz6wdVk(q^c9tA7!#u{XZ>;WxL;E8Us?@ub%xv2r$LNm33w^a^^Un9ueS^zW2<*b92o~Hn) z12czTU`=|q|C~R_0d6j_J^sgWRC>d?yS@T%mhKN9T%EeY!Ctq|5CRgf_GN3D@OCdj z-13;5q{oZ#;3;J>QsVe@o?hU}J`AoOiM@Yz&w(uHc)rOho+UJuIO&wzV=7TSpQ2#y z57*(z2MB)b>d9GQ6S67TN&0iX&}py!ERypG^kbdkgg_vkV9tPY<~PqN!4F;?{{jW+ zzoxGLS89g;%(b6t5o%r2GlSRQ;cbsbSDTs?W@cv8P%nwgc+}Qdq0M!~`xq$9EdqKf zGP$)&SwNS`jj=&0GHTF#!P?qdwd<%fiR3z3D}ba4-xZ&`DU#l&9!c0#Tbm-=uU6C403JyJI_tK7e3dxSr_IDvv5z39;g3s zltOmpf_?;TNR8P5y|KCYGk0OZ8K@?>{?)VkrlxQ8_4TJc8wB98va*_5T2+0sGc!eb zd8$rMPQpS$0|naY8{1Ry-Lvbavw}hr5r>g(&A!a_@HAJs$hEB?&u)~ zHXg}uJdyK5g~+X?vEt%leQoWRjO@H0zJ67O>$|zRVT15kEaJ;^W}uf+x@QJ2`2EVk zTZdZe+uo7|*1G}g%&)Q@ITRfeGqf>3Bq+5nAH4FJDT(K>UJ&6Zw87WmsB-%B>9a6c z+2Ei)$;8K}#@X39IW3KcBIQ69H9o8dh_PZ5@^b|5gZY0B@&U*d}q#_ zk$U{~*f175_ao;nhPr^BS@joy^Tn%MmDRN)b>7_?m^8V?i+iQ3R0Mx@86W@-;AV~` zUBvJ2Z?)o^0@h2ix%CVTatQ>&hcYBN1W4-cZPpi~WFt+@=&r6V@AY08KqKht>WAOI ze_z`P);p|vo%>-xK*QkBkU5)(QkJe(s+bf-ns?T-K{8;?4vo85xpz@2&Y1sXLg$no z|H<+W@9mWdVKFf`k1XI^B;onv}Ee)hj~_i;|h{ROI4F1s(MkVyVGO zS)8I~c_k&+;DbGHB`DLcbZhI&fS=slNo^Y)DKG3xm@YpN#M`W{ot8Df1G#L zW&(fz%_JGT{RHmp*9c;it9$qE-DhXmWJGQ5-@jiSefb&4W&eqzz)xyy{E1J8l9SJx ze|Eagjg4SCU;Sj_i`9kuz+KgW6lX=+#!z!0F9cbp+wO+t6&4~7_GviD&>&!#y`3Eb zUuucl=gfJaabDUb0Z*E_%LVx7Q=%X@TvJn1A7n|BRT)667^x=lZ6b$=kxA!e?X*0Q z;@${Ys#EppH{2pegY<@=sd;+KT_rhb^oN z<-9j6RcJqu9?|SD(qtCE&uaZ@}c_*6S>Us zooy}&hyQQgtjdXM(BbXSLJAuhs-r@!h*6mLI~P`Q5kQDo1@ti5xXwSh?*02a-LFN5D($W z`K1SdqW(V2^ls_3E%%AW(p!9gtEhl7sHv;FTpo1K8BVVuz*QoOik9gz?zNU@*duE^ zrtW3PdKI)0)cWs1e|L3v*Z3`4y*wvz549U|L&yk(_&Ar?)f+eTlIZz=^x17-wCu3q z)WX67w$9y}jZeYk#*G_13jXCfSxO(N)WE{VKgT-SN=4$-L6wNahk(owk&(eu1G|!i z)^=&2a^WiK#sjs02Y+PWekND#x?vF~`Z+l{89}2`aQ~2!gF``Hhf|Ywy7YWbBwvz1 z^U9aw#YIIG%}Q6U&@YRlAaNynSI<^jN;nM)h?dCwZQ~U$$9Lu?C7mV{ zYP1>}8d94h2-VAD_JyDG@&p701&c5kGg#)@l0f03nwu)m7UbA$g zkUxdQ#B@62E*JoSm6=B;amW9`O!{xrLV7b58x2Np0n&>&0TWB@7A#ub9bX!2^Z@}` z_?CDngW&6BUhARC#IKH3JoW&QpA#*ZF7!hRYw&ye@)s}-1fP9fpZ zx>-tQ^-ppxk?}a3+@KrsAMBS_R_X)B0jp==?g6=C6-1U2HLvYq;Rh6q*%}YxfWe4P z|vq6HgffbNqM6LTyZ zeQVxOUaa^l(D@7GMk6&PGqY5M|HotqSX0Ef^r4PU93Wp8xI8zj^YUc$Ndhv%34*-V)a<@Yr z#9<@7?Rvk@&<*8?$m@Vz&tS<%C{JaH0T2Q_IISv2f!Z{fuO%qOsb{GPB+On&D7sbU zDmSZ@(O<8L%f?`@F@mXJqy!&a7)JX{e>>$$sD=YMz|71{D1Y>RnnPC}F|u-Jd(HM00e9a^wFcJ3)^KP88@xe!BQ=|AYmER3 zD&~FuVJi_)QF8T-)m@qy#=8h;GZ)?Zrro8+K+3T3$18RMLNYSOAPyOW@rYk;b(~@r zAGoZ8_4IA|Cr(Y5_9w#J$K2|gtlT5VC3xA9?a>^ywxB@AVfIdwsX#>8J35Y*GKb$` zIdTY;@B}a_s=-^KL0vAcuExs2-Y&S9wO)jWZnwc)IvaD}yy2#hM~w{)4K+11eymP) z0zng~O^d{Ge-X2&&mJn&6}f!*UZHMQEem_lC3?QTq$gHkuzLzmYgzO5WQ^z+aI*Bp zqs7{=HYr!2i-3x$+>Zkrg--9-9Nbh(1MD*KWQ2-w(pCpxWjTIa3i#H@n%Kmc2Q*^8 z!g?%U(BchJ8X$#Hm-|Bp4e52nCilbx#%G`13}Oiu_wUCR=wuZ8jR&Z!$Me-}GR$k! z-F@Dz{&vvTlA(u31*ngb9+RqtjWgW;dyAsac;&n`^7Hd?Oifs-6~B(B=ec94{r(VK zL*oIct3Zyp!sP%2+alP=R(0r-l4Lx|(8a|ihMtjtfVOBy8eCX=F}-6Uq#R97s4VUKvxNu;n7cSm8`9K!e1Kx z25D41oOeH6S{tZW-0qREzE3#PTpX|I(6plC=X$h!kaQgI{={hpR^sec^OYHe(dsu>#F)>qp8{fynb%3fg+RGdr& zdc^_M+)(mGx0R^dtSS*372wj&4vm=v1O!C7H?zO_y(eY>g^9e*%3{=H%{vHm_i#&5dhW&#lY%e zV))Q-`@hu3g<5;5sYl>!AV4S-3U!xwFuvf{*R1X0QgSbzZwwilA7=0`N$}d{zf(f- z{#&XIj|WqE%YkrPhKx*Vl33;kAB;%GACa~xNxS943-UKxdPxf;lF!DRUWRh$_=A2- zE5IW7_IUu1)G5G28aO} zEP81f#2VCP9vQcHLzWDfYp-p>t_I%SP9SV4kw_$FSZYz|!G3XBnIGo7O6tA;i2nRk zzMWbn`TkJ~#c`!H9M=%CmFKiw*e|?4Q^MI9k?F5rA!A8aO_lHc{EW$`TeQw3)OT@Y zLIY-0Vv_UZmP?aswv6qSho7=PH*yO9p(e_C0gdS974_I1WA;pXEdTkSx?u)2h7-Tl zctv|ve5{Cy>hzYgeRf!JNrCAEAGX*Ky|LCUj-39M2%2Sj&miFRr{^vE7Q2e0E#r~v zc|=7gDq%Z^>Ou)!`1R*Bd~jzBcD3HFu|>{5Y%;T9*cY{^ZQQ-SSHgEr>B~gDtYHbJ*KaNfNs#}I8auNz8z#i0W_#6r*qk^r0GN=&P&eMm;bINSnP>vlM& zxK&9VF~oeTGaireA({9x@Tx)#yuKk@Ow=aa{_T1|9 z;w=bE373)UqdUxJE`OWxbi#hnT$FtIt9ec{G@^jLK0ybjxVO}TpCQ!EZwTw7Z^eDZV=^Uvm>Iv*FHdT~V1 zq?&tu1y@Ia^v%W}h?Cil{Mv|T4?V+)kFlDP4 zE^%CZ=$;~lXGli@!Btwiyx ze#Z|oieL;74u%~WON>A4D~=rgkKS%P*=~HANp9@uCBnLr?c>MZn~SE0o9AWwG8NH) z^gsjW?c}1$sJa^8nmJgsyl2K%xbSXCvv8*?fq`eQFl!EpXLnl1tk3q7<_2;BiOFEA zmc)Vf0iCN6C<^}&-oNg33UbqLvi)1U{NLPrAHZzo>|7L&w|0SXE(BN8Q7ye=^YniJ DhE2W$ diff --git a/umn/source/_static/images/en-us_image_0000001229959315.png b/umn/source/_static/images/en-us_image_0000001229959315.png deleted file mode 100644 index 4c0b0da4799d8df17d1f54bbe4681fb68b822d9e..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 35050 zcmb5WWmH|w)+Kx(2_!)ioFGAh2X_zd?(XjHkf6aexCM6$?!nzcaCZ;x&_(Wj?%UmO zkFUS}!C;KdIeXWxTD8_(bI#(cjFd3KYwXt$2n0b?L_iJ#f&L7EKsmpJ0as>iq6omR zS2iN5_7DhS$I}l~k9EEQ1o9ptD)33cC1roX(E(NYUE9jiemCw{f){*W+-+X|FbQ+B z4X%RvA|9enj@bU{Esk38$=Iq~3ZKvSF0Rin{fIlAw{D4a#l?JxMc&_XZ`mLw*4rO( zR3#@nANIZ=@I&T%scRP-uc}&KUl<~k8327mMu8a27y9}QMT%WhN8$oe+>8u%E2 zUvCnIG_;~(0b@j&>^9UdFQGn6MZ;#Hj`{bgc31v$XiuL(R=wa8)rn&(4Akn-%NW)V z>G{+!gLAt*aRepFf*3e65tTh4tg8GcLQZOjDo&v(S0zVo)QAL=~@vaeW=eoL_=&Gl{B z$?4>{+B3?}C;5K58JiV{{W-;*f4@RdNire2JY}wMu;HEp>4!L@`bT_m=&u<3B}*sc zsPuN`S**;mgohPHs%asy5i|O~pOZ9bWyAIbF`L-ujoPzn`eX<+&QXS6f#@&Njc6Ow z5O?@K3*5giPPj+U^j5_x(aaou;6vMsIHU+i#hNCOHMFflZHm`>KA7SRuW|RY=iQ@j zo@SjupxeNNxcm%z^82bsb*U>A9E4@ry7`+r&Fs~2X}{Ytp-z0{V2YT%0{#(X@=kE? zU(-8sF&M>r1gZ9G=am-BM9_(simJ*lo-|jzb;j6`P=d~9R6YphYtyd~ATOsC9rzKG z8iygp=>PP<&X{pYXnC63@E2~8^lB!M@QgpC6lf6R_o(?WtT|TSNC>D{lpX1OoiMMK zz`WHPzgWS|K!2fDNP!=9!u<&WxrncIt);&yzB2Fc3;*2yN<7NJ`?0Xl0=mgZMbWS{ z@$-&w10@R-#gKe5WFg|3;wY<7tP3Ir&BQ44EWebGd>Mx#itN|(RfT+yd1bcbD4)VX zB{&lE?Hn?P7ZyGrdJadUqJmdG98~>{w>}2IvPj-! zC&(ixD$1aqv!;C5So;2p9p|$d#hK(nr&yK@d-b4w4oUJo2#@+gvG=2;(eFfiG6vud z3jW@emOlLXZ3N6nG2cu1| z=WmY`zA#FQLQ@XQ@0p;!#+e|`(h~C{Li1In{|LqZ{Y9#lSnA(LlSn<&k-0+TmBqY_ zPk(znUxNC@XZKN4LpN>rMJ&>ZVt4c4`^OV`LR5d-*A8BZ=dYihmp~!8GgF8=iYx++ zZe&2j^z}WOSPu7dXx>RxGrTadNwB3Wxjmo$ZjHy95+`8G5ELvVqK}FkXQPLGNCM6hN9do>fb@C=0Pn&$;jne z4}`u)Yk`!*uchj1#--A5)IG|re2=ELO#QngE>K{;RTK*HV>NQz^iQK5tMIfK3IYBlqK+*O$e5I6Lsm;7>1fCU&DSAjXW`#@$0y5;~#6UJ4t<&)21f==1u{rvu(MGO&jBl z(%0_rYT{1X1DpA2x(8$bsyN>M9YSq746m&GA`>sLg&O3FULeRpdy62C^riX54~qDOv8Q42t;1tOPz4XPeZ!QD z$fX}jxnhQ7bAm$y@sj1VL?^1n#0bg$CZNj0u|2&(ypJv;z8pLz8IMYstw^OpeCgOa zrG04->A;`0bIVfj9vbjTee&&mK@K>qErvv9GgT zBe}mhgVyO8)(pjE`FwM}XgD4DX?kYH_WlOJ>0mLe-ZhC@{w2YpSvQ_!-bC2TmoGE4 z-u&r(k>!-f8A`V)joFIP-}vd1aIZcB_Qu8w9T|D*+kl?jAI>z?hV{*Y{U3C&piucZ zLzIegKHa-nELFrDYC4)!tF1NY_k`O%E_z}!nf$SK4f{4YP1)$BKy3o6a@2@?Lu=S6_4rnsC~MLu25r4s z)b-7erlrlkpz@2<4}w&VyE)#2lVcE32xk}gXdnZFp{7+_^(U0z;pORO>`R~m$) z6d#y+Q-jQBPz1lQtY;3zq&;zF!}l@@4UDn(d)tT3t}b0m%b|y7u(FDA?2cx6&#u?HmTPRqhz_&TEkA{9|uCFXJ^L0yUMFon?d=6g(1kwj+Jpa0rY|x z{rok7ou5X%oouz3VU5+C)VZ1B^Gn^h*k@NNTSz~v%cvKOD zf+|%`xW}(v*@>#Wj9SBTZxxPt1xL_1w|n0m_LAKxC9Kt&(0Y+GmPVO*!S46(-|Iuk zERxVKM>D**qN8I}D-CA$UMjyNsEiAJdU&WBlevz$dB;gy(bY{6jZExd^GKmgrt_%d zVP}dflwW}VvDcc=`fzG;P>{_9K5J)Qx`%`;QiL*UGkA5p0)~LlSYogw`U%O&@<$8K z*XQ2vTw7&3s3ymXca%}dHG-<&c^U239dmkMil=eblPlLyp`)KHQV<9X>vBpeDLN9< z65jH?`I}72lBDwVAMUP$H!EI5L;h7CUJjjx{7oVt9Y*s$Ws{dE#82}MF1~U-Q{xqd z{);6fB8fl$y$Okk)*B)}7hMkL1EblqL{zuD_fD~!k#&{UiT7=SRoQ&2N zOzF(m({&GC2E?b(=r(^wbyrtc$u>6xm6wKN$u(~Z4i+Lp4R(L*?9Vht6vU7$A83*f zx%n1W8Xd4RTiy9KW@du9jgR2=NdNs&e)DCECr5&+{ifYr=Mo4P!y~aP$J4IKNv4I1 zQtj6EUpow}&WHFQ#a!Q2NryT%i?}K(UKgs0cZcCh($SP{;febcO_f&Y=)NbFPUTa~ zH2AuDw!Ij}=fCJ`#>w~c7(WYD5DRQNz96a)X%U_2AX$m?bg9KA*EAJx7RK0?`_`_3 zfshSx^syXy*v&zN<*7$Y#&1~6dZ@wBC_NE|5A!qY16x9mpM75<@G^@XRq0{{bP!7(WKnqz+QdN+vV<| z@ozc;vKt>(yTtEmj-3M#a3w%`x3RU&HH+*2VHL;z8WTstM&u>#Tx}Nb=eu=#=RCs@ zBd`VI^0&81cjp=`Iq2x<;J2q>ot;_Ce&-Jd;x~;*n@{D;c^UN|fkfqp)y zEpoitwLLiz@#V#9nK~JQ7Sn}bLVvhCb*+~KX@VeD1-_97e<>?va6MUgX4AV+@|BDI1>qGwe=>EF zdx3s7Ypr6ck8JiA#kMooa2U4s_Fap^hhI;6r0*nm0xv9dc_DaR}C-e^|5eYjAk(Q-mJQJOlGo zTvD>LP(&(!pJ%_huZn|%Gu`OSlO+rC>>oJ24`)I?DZWBNG9H|^%`X(=v-q*~`PF){%_N4w=c=chBrM>he)ACB{?JAHuu@~9~kb%x4;Ia zG8&;F1ns7LqmrarwZ(8k#TqRp{PgVX$#q^jM913tQQ$gfKCx|! zn3V=UWM~7BtdD~o52rtewcZa(7kxY33#e8o(?WoN$}%3S-stsg@3*y1fA%pe2ZwPz zm$EVj9;ZvBQDTU=m?zyB-Tr)aa`XprnM@Bh2qQKEF2@fd=QPf{^Qke?U3*(65>8IS zp-K*CIcnR+#zw;e50PG6zQg$(xtw6EB^nG2AJWUAnZ#`eJd-zkL3vSF`~Xpe#pQe$ z9v(Jf#AbeYfb9x##S*T9cxhC9i=$L#u-r8Wc5~s(%H1m3*ZdkoDh<$yzJ}AmtRt#m zJ6AeKK80h_qFj8~aF$U>rX-(&xz84khf2?<= zVKP_f8Khdn&`(KCb=^w+vd?2fJ9J_`RT{(N{Qy5jsLtyi zW~x-16u`-vqiIp3*28Z4ka%kS<7mUPy}5UA_V!lub$wuO*SqeaM@I8XCecs2@GPAI z1b}E|Wfgk!09&frI_w{Uk;vi=Rc$^=3<8hQL?(h#xvT=j9o4oxY1*8&5e4`a>SQJR*&PQIm zSHFhOj`ycqaErXvIshgD`CY%Oa8jeeBasB(J7EW``%f3_Bz8tJhJcp@T1naK2E+HK zNZ?WYWmEE%2BLR)65kaHqIvuIQN_Pe!|H7Ri88GjN+w0xn|kOy-(z8Q+J7!8DypKQ z!dWXBCe*S1buEF;9C6{!Epv?Q*YROG&{=1o8PWVSEgV4@iFRTCG~T-T%BrL1A;cW7X11b5Sn5nm@Tb zTv!8GPN78Y!$i;NLW84-h=|U0aGXREeH_3=I{OK-((^r_ZNMU!=mv=0{A|zqajkdk zeG5JpeIx%Hz67#Vsh+#*Q?z;F$??J96a!v{*c$u1<4>3J+J1-_sU!K`Ck# zUC!$B13;pQ-BPVq;<7-Gz|UpjX|n*t@$ur1~Eaxc^cRM(@6V53I2_gg#LY_-mEETv47rC%VoCitXQQcc5kY*Ik?cjckDG9 zwZxwFtdTP&+v13LuKn$7*FGYDP_5R(Pc4tdQe~$=g38{6=erIKZ=j%{XmZBEH|Y%O zBzOr0jKXj~)^4^S)|P2@TCW%X{n}!2l-CUI7Z)fyHUI{x38ecgbWjcynjDTu+EM`r|q#s>pP8b>|zMBUZaYT6;@hMwNWA)-?VZiC0&* zAzUWiJ=y%;(&JW7-#k9&hB}=mOuw{g-O+YH<{H=AVtM3atM2IDS2r8{ym?nBlPS;l zcwJ&#vJbz{DRFq3B3>(|??)is*T>DC^Yq&6d*gGpbyp9J?Zs3$_X@sSYQYNU$O5JG z>Y%49<^Gn8?DfS(IOE>3@Mk_etWqL!@+kRFf%yu}!{T9*LCSpz&vOwGlGagvepF-3 zay#Gk3kaY$8AWbtrqnexP26!KBqEw=aupAV;Vn@b_*D=CmB8VQXV@Rx-P1!labTpV zqw{`oG4AUAQnIWV0KK9y0K*~F8g*^^Gxl_t@Cv2-_rENqQdmFvzuqvNEZl&r^*)^E z@$>ToX@1eoHFW`#UYEMCu+nS=zQ$UkhjeJxu%Pr=W6iSW+5$YO{5j9vmm7SqPtyxJ zMh~FxuSH8oiV)`W3v#n%0 zmseB_8KhiJ*Y6mMLU*ZmtqVirZ|(1gDiwWTW=0nm7r!`M=)w24-~);HM?UPqTy4kC zpU|np@v2oudRA7$Ao;5NFnNxywRB1~>VvdIfhx6h3-8EciclUTEKZjU6b*hni zvsQYh6D<6;w2R9Xr6e@IahcdQug)r zX*4>e67a*&dEUT(|Nb51SlR0T|sNS`Gv3HueE7BU4f& z?Bw3!doKixqZLB_EI)8T=Y|rl|8{(h_Hmd+^EPubw}gS{;D+(4_sScoEc&k6*%&=S z$;X^A09VP!<)UZ+G`YU!_vx!?(dCk@fqRjMyKCW}Vk+)4w5moU)??USvNA zYs(e5;d*IRM>3Fxe=meF`(-K6L86U<=N4EWBeblUg*Zi{{hnkODxKMSq$SlG8T{dU zm)NOcGBu4OzW-I(uPNy8SYq0^b{(C)-eE|HYV)K*I^Lo}^-{o7+i71h-rXl>|P z?@lNslfCYLvA5jpQiApV*&9V}T#(FS-TwP`0D#L+@VqG|_AmYt$;=;yYUXMzN9-EQk^%!^+uI2sR3PDX zhrN@{dLYNKC{6tABRH<8!&_jsXiBxK*>U zy)EJkbN;mELrF}YIkz7=_w0BGLp!{!vP^FeA;qff@p?G}S$iyB${X7yu*TwbW43r4 zZ=($=9TA@yc6iLNA-7IUzEh0d~g z36SRDP*=6CG@l|eQ2U48{mHe(jVqcaY(U= zgL=T_JSU$gRbf1$H8?m3a3BFE=g+!Qktjk)EQMlpLIS3q-uR-yJ>kK_RKBb}XjI&- z>igrG!$jw*w$J;zS*6msCH3?O)oZQzK~f*5zrU)nm;qg7d__4eDIML{pr9c551;wg ziQlX^W3l9Ow6m0rRZQt{if4x&rgJ}F49TPL8BckjQtkJ3+2_$~9F^?FyJDgYo%j?$ zI(xW@owefOE#Ki|41fe51nL0;gZ-g@Aodhn<3M1uwuRIfm{+XZPkHR^BGcJ z1b*(wAJQXj?n-M?^~YLfe!5%FORn(x6HM>ld*=q6_u?zxTHk|=HF&2>8^&WURUx;L zMrMC=rL9mlhb$;tUS8hWD1|LktmoKc2yNu6Z&H&dzZ!~zheID?uI`N>v-^G2SZ?8YYwo0|i z01;y(Et@YcHjrAumq79{gNcD(7ByDlOuimO^=+*_J?;elJ0(5yBi;$81={WNvx6(a zhK;knzJx?|gZhPc$~4Clt25g-IiXY!%Anfj%Qb4{uEE;S{6TDFz6a4P9SXyJfC<`2 zdYvCUd0!AK+{WNrEEc-1$_I(un(=(O50)ZBy-3VREC@Lm$x6p%H1!m zqGMv9g1)*YWU2tJth}7IXLvaL>dIv}ohRL@-WL{0HeZIIxVU)Kgpv5ehZdQ}vgpD> z95%bygE{9vT^Q-l$Zf6WY8F&BS2{@7Lc_xe01*dR>BIT@j)lg@a7NApdl5Et@=Gi= zHMO^BXy=7a;z3h~r{7Xpy*Hodh2z3xxFo*DxwEH)ARP+ZobG-IMyK&@&O*5)`souJ zNXcilKzkvH{!K|hSP(k0H4--Jk|;DQ(9M(n)$s`aJ**2RuAml%Gi3PAlX!vt>(^J$ zap(EJR+3x4kdeDB46Sj$zQg)Wl^AB-`ewa`v%2ShR}l0e7)y0adAq$?^zEAj{{2Ue-?4cN%#8tQdsSL*{BwD>rGAb%6GL1S~Q21Xg$4DnFAMvDqc>yPrE%N3q ziaa|aXuszd7Iv1r-ygN8$0KpOq(?>~-(2DcrKWxa?d8?Aqqh}KX=!OJne3O(&sqW9 z7zX{~HTK9^a}y^h0@T=HUvhHL*fskRI@8k9iZvUC>lc()z>24ETq3zOr~UMY zqca(GX649pSjT1mLG)e+3KkKk?dQ*EKvFQy+!>c{8RiSB{aWw;;-CS+ z;BY;vNxm~?6W6_*P=^B6$-2FNHsD*TyRPvOZ(^|GOqC^(JqaSIGM@1~Tob?C?vY3} zJAw+R5UJjG5@nfdrbm|_c|N9veJ3*+8oc^$NE#eR{W!0(%Y5UPV^31yd@DquP~h*n zYmzR1*yI;5uh$>c0%(4@oZs%TRO+vMD&q?2^!MKjNvX$XI&DedgxA-z$qS#eQ17wW zi6x0Q(C}rAjan{adZ{)C(cL#@OeX2-ns((4&4HDNS*q*bZBtE1Ow={BVYz!-S9K-Nicx5DTbfKcAD*yCE3hl&R_Z6BCRs>owYts(#)SADFH4wd! z(T02mv`?m732E#e8o-a1Ti4K0{(Wzq#~VKCBF3Eix)*eQWF zt5aRtD_#p9g9D-TVm4lJflN?VsDDG}f1}0eNj^uAprHS4^4QX!cz)0&CPeSqM|OVIN)Q5Jb%v}#1Vf6icZ2VXD3^jR9?);3DfwF1L*QZBe^NI zqFN~2Mbgim{?obsFAe8EgZlKJraC(6-%LN@6Jzl-PTK#_{Qoq4U+e}&mM4p*Oh&h# z&Hgyxt@>7CI+e-5Q>q%$uG8zFIahNeQl%Lv#XhWEmylD($9HIR@{4?JME>5m+^b_m zwQx_8*<;X>(!#PK_#-d9M8l7s;LH*Hj z_Y5nk#zb-gy~MTblYWcE?3dh+YNr!Pjx-vz$m7z@SlO*_3A-p0>4+Qa8XK!TOy5JC zj}{I0>t6Z!`;TS0*Gf!Q0e;_c?@C8k7pkrH+3lKaw#_#^_T$T?`8wAaJHr9!(WV_` zm90@zr|{9X_Iu(3p zPab+HHMQw)e}8{EuT@mQ6G36JU#S;cT8v&h8TYThs%xwt%TmUl^_mDcf9JK?KWXl8 zd>~Ynt1aKU=$;r%M1KN>LLy1R%KE%SNj!cSw?M0eBAMCRaIeOam7V=9Hg-T`<2&Eh zcR@-;o>r;Nw}{IFG~69|P9?FP2cwDYzA%+u9Wnjqto?IjBnJ+UEwnoahtbFxDHT;{TJvp%+Xg)# z$a-d(iYh992$W4_O`54zm@!ou-@F?s#|I4bGHCw6>PXI6t5w;ZN8H`ChB+J+W{DYE z1HKBeZKU;Q4NZUh#2%{SktkvY&Ev?&(wIr0tNPL-t+b< z3u(I2@f~-yx$Q>3A|RE!nwkI(Z0jG7Ch+z68WE9am|S!9t8}R48SMCd%d2DUacM)O zoiec5*j$MJL;*U}qPT?BjyR~d_ZI%j2^peR@@;xr<*9!e)@&HB6lB0=F}oUUKz#v} z2{Oe(Vu)2~sYZ*(3m^4b>ne{f3V4`jNO+uWJ`y-b*vCX98Q7sMJ}k`bRPV!CQi2FOHqi1 zrY0>53v7nRwH??k1pKLH3+&v3Y43O)9N;;e4p%#n7FkLuWy&ECuwz|Z-RxFYyYjr2 zEbOj6Fh?efg6rVH7_wGQtB^oRA2gvx1uv%~AmyMl;N%LS&+yjnmQ3+$*Jus?J&FdoY9H`3K8Z-2!{QziGm|vzVl*qAloHJi<^DC9!ym``A4(_ahQV=(w zOeWuOCf{n!$0>DFuupm)ccz@XJ!TGN|7&9zfICpid_FNnawuE5U2I!5)mQIKY1^%B z0!7Ixq}iA21stkQ@AA?1ob`JcUns$L7pME3Jjp+MGs$neLKut`x?zM{O(%juo>^Vp z=R4n33^N{?EK=OatKKsK)sgG&!SiP1=g%)=M1gdZ-s}MW0qK*@qBkSnL!eR`WX-Cz ziYbz_qq$`KZfS$Pivtx^wefsiezU2<2S5iGlI>`7>hIK`4t@!0Fv)$FG#6e(hVs^UQsmN1E6wrsW z6&12aQ~iUWQkX(Z zu^`?&S0Xt)&sdh*^5j_jt1R$W8MxfE283T+u(D4Z7q&Exx$)`KKO#1ySp61h#W`(8 zC%2Q+eqk-_{erw_0T9^nO6e}_f8p1NH#;Yh13NCTvnUVZsnZgY-b24St^|7e7|(gY zj%-ID7KZ{*5hlRE>4}6j5z$vwLB}NtrmpYI2@w%-Fr9;A!7<(A?v0dGI1P3ZGG8{q zeVhv}fI}o5lU*BMt>hr<4H-? zS8_a$dhz7t@c1CAV_;wq?q-@tK440t<2liXUoi!0Xp2XgJ?2hPW#E~rHA_9|zjcu( z&Ev^^@-(Cr>3`IO|8ipdW7zmV!#IgWAXc%uUuXbe>xVo7me(awt8d`DcHD&VFs;{5 z10XyPv^{u2(dJWB8I5cJL03ghZM4A<4*OS`uz~~Q)5Tu}6A(~#h}0OZzh$yRfwbEB zy{&8e9H!W^7>maV9@IFCt7{BkuKAo;j|EE0_M##Xr-o!wBQ#p<{6Ulxlaqh_j)&*L zQO*PKOZPblA3{#fFNKN}YdrcSx+^OQ$%zxq$ux>Z3e4XaFyVorfxj=hYiF!^E(CX; zW&Tf8R)Km?ATV*c?>Ig>uD_J=m&*}rIcxCWaaF%5s6XATGCtxiE-u-guXqOZN9ii9 zn}Xt)2eGCdt({PUGCt671EiB}g^PbEEQB3zJy(-Dpj=vRcl{Qxn=?CETUrd2COlXS zu-lk-3%q#T9wN6=>=f?qYa1Ka^X%3O4MV`LC6UhT5B=f<1?TOTX5VM+?d`>?wP`t@ z;VORoF!(dN0<3Z`(`T#G)VJ11q|fv8Z=HS>%cg?L58!L{56g+!ICj&}<6N2b}d+{t@jw~LJd{FUB}9v^?l z_U=>+zA|-3e}BJ<&<#0(T}$m|S{tXUU7nNEi*c$}hwImqg$kdt$UxQ|18$^?!#Ux0 z=oc_H7f@!6hD7hxS<1WI0~>7 z5YP$q0@23gSN^BmaDAyN*8!zj$9;+98r&=0JAqY{w?46JYjY*AxEy=iV?{I|IfB}= zJXOWgQ0f(m$rO;izHSk&wa#cQ&U3z%*34)&ja;G>0^lQovEXJS~Ksvd-kq zl5{#^Z*FI)bT(hDvMpT;Dj*_nS(%t5(T|PMJq2E+VZTBC@H-akx45|cAX}NvwV<40 zP(jPFuWb$`j~6wV;zJWV=C zM3QH}LHd9G%b57K=^($7?O56cpHxSPY=uAgng~-D}fSXvRB6X1eNrrv;Gs#c9`8 zdd>_9pz46Hir(VSd&uSsstnhvTvj$Vqq>EZ?LXSW`C27~$M*Mse7hymcBO&bK+C|A z#dmE7=@!=joyBoa?hvr1+23~~9L_f>ikiiQv9_-{II$$0|QKFyMmXaIB{_kBGQ3 zUw`@}fCD!Y#9?#U3y>vdv({q+KRU@SSge!Hdubk2?BI~9)7HJ5bhjOVkFCEyZNWU? za%EVg@_e{^@g*ELFI?IZ(0JEg`>fy%B|wvrH?x_3x|ObKjEj%|WWf;a>+9_4v0puk z0T?ry(wTZVg$uZCpjaenbS$M60)3fn(_bb-kP z(iX1Sn6Fm-T97Lk*=~zEo?079PDnxzzgy2#_p7h(Gr%vTaJu%ZLB)hw7f=l#x%!ucl0kUbVFxl#`{u&4x2i@FYw)zVE=8)#a)LvaDi|MoZY?@(NZ z*RZg#UTRh03*Lt-z?}d}gfcK-sK+B7%+b4S+dyLsdhZ$ri=k2eksiW!*e@m`r~8V; zCemNd2`p#4tWw`EZrS9iW?5tOLgaO>c zACUJL`Yo%OD;)76vGB<1N7^W6$H2>v!ik_0X_-cW|F&j)`sY&_$|sd3q@<({>=T|09#VS$R{#WFKWlR&{n0GC zt+!Xi)zlb~03e{|^@!=cH(0LPEmLfvXNoiYH^sHd8i;?{HQN72%Ibf1B>b=Fhp$QL ziF_;T-(fJulwDDXi67J96R~@2VwE?TlRZRj(g1Vxi<`+v#768d!>PU z^8yj^IV^0I(SqAI80t=tTiW>p?U$DcJj|x(t={3hsRDC>Dm04Q5Z`u9}IPWqo=DIl{=i5`ePAfpg#F~ z;KAg^4hv{$c9$!)nAuAE0X>+?lFsFR2}onXt#I6Y)vOzo+ml=T($&>PXE^Hs&rxOvjn5)S z7H}c|L0RZehDySE`@B?^3Z)_J?nn3kU?>X<3&_iep!dYAe%O;mP@{FW{JA43mJ-na z1-#Y=;*Sa(Q(JAK2I9*`^JSj_xOTbL;!ahF8lU9J~5658>lar&jvMPngrGIH(RlBLo+hhpVLFhn@=^A)2yA7o|OdWv> z7PPX!@|-zlhDB$`*m`%tljL=tV><_yf`pXxbYVI3%4sK5`aq2{Gz_3XI)2g;Z(O#1 zP()QKEa);bbsf(4`XVUfbqx&-sZIf=OJVm609ikKrq$;K+;M>-&}2LYfuQ=tKzxRK z_IEu>9!wFOoNB1F-v$*H0%tx;#~ii-TG)5s48fRD3aa($j=Z~`XY<^I2M98-qC%t5 zD;1cIKy7O&kjWduFS0Lhw%nh4wN@|x*Fb$+nB)qlBTNsU(gS0Ha%r` zx7wUavn4w5VM3*a5!v3}{@X|O&st^1(|@9_cG;^;K0#tg?tFkr&+yb}Flj})ZC(|! z4`im~OWt*ZnC?g3Y6``1D)(8@BEa1YC3*RSU)X|~3Vm+@m7OakMCCErJ%~|Aq=o~U(b&4wdEie(V!^jLyV(Pl3=*G6j4w> zt=b$koL>H9`mLxCO7QeZHTjd`ghtxa!4PeahZ%;wB#d&O&7q{#_4S0z`@RCiM@K(! z^az`03W>*L5agy`CF-yY_6!uUG_X22ldQnK%EN5g4S+j9H8xvT-6OyJU9e8J?6=B@ zgva*IJ4uOcfMFP5!89`G0Tuxb%W|WnbLe;7=EKUbj zF1Pa>$D&PzA~iIhbnknF|3+vJ4t)f^x9;p$Yvn(FtpDs12eIS>0-zlDl6QX}uk22m zTP)Rw%rN9-6;j}`@3_=jX#y6I4II`2%s7iy!COKGIc+%B6M(_-7amV~r)}5BHR_Nf zqje-x7_n%irMYkZ_`*-^tgcGX(a@}QU<049EeETg{noHN5LN;C^=!0&-<{cd=0@Nx zCLo!deFMjalmi2WqZs#2Hv9Npu3C++GM)KBc4h8%2SoFls)L*32V&xKz}Dd)uy?1_ zLkS2A#}rEgzrgsAa{P+t;Hxt?uA6m(wGksV2Gl3%p~7q54!!NZSA;}5wR_e7)Yiel zK=-NS-tQr*Ce&@E{(uH;Hy-GQKznYSKb*ZzjMv@$L>_`6bi|rYsMg;I10#M1C<%oy zzQ={nvpFp;mfT^|jeueIsUv?%H#DvH5o7vZI>W^~-2*Ms9B+mTaP|)pnLM#!k#LP3 zz6gQ?De0i<*sO~n0|^f6k7d6tkWM;t!>^buMj->gS{VRJSgU=s%$Dtd*?+J{0ygb6 z6B*>oqou96Py7&ChKaX0IPgBsIl<9@*}nKq`WZ|Mh^EMazOR58e&Xr?5lqC!mI(Nf zY!y11B$j*jA?C*v9&3s9@uvwF{48!Vnt=yqN9xWq`tltM5MGLK*d3-_kh<%=hhuoo zTbhL(g#_mHw}Ya#*&VY1soedyZ?LPxQ&v_^!AS*&m2i&4(5^ivjDUq1X8CMqBKD*F zY@MW=qpF(P$v}Yj5uF`U$t$T^(4XQ)vk#NMIO)B;9@cKx6 zM3d_YM5fdN3-A&nfS5{iA5UUA@|F_g2QlO1Wt9x$`+4c%lEd5L4&?gL=Av-s19lr= zMCarT<~$W(%`1{^#s)^9@Gx8@YBd>Fxar1L%HVicuEhD)?~*x?KIIz} z$ivgGlCi<5!=gOxq)Nazxy3cUmk6SJ^$Q#%1wv9K!#Ao|aBxqj8-S5Q*HV9Inl8)6 z#%4K>>CyP8rQv6Io!=3-*%brcWcV;|r= zrd#weAVW!vMs2Y7iHwF6+GWS0H5}Em>WbI3TADD3Cxq-2N#NMt-{ThXlmnXahu!~p z0e}~N=dqo)nCW-ZvCymT@arI8d+OlEpi&zIE|3H+=N4UWq5y=I2VdCdurC-KdUZ%7 z@BCa(F_2MlBmnomJzkFj5e~=6((O?8t%;da_Q;~ERV_DpCElXYead7u?PH4{k*l4) z=z{R>b4l38v^2vjmou{c{r!ZiKGxikgsjS>b50N*VoMLZL zFa(Pgt6&C{i=XW7;Dj7CWfhqMbv=Fw1gOQ!KY1{&JvKw1vry$+WL3LWn-yyu__jXE z&(FWMSzRaZkEITasgf_`QQMm=8K^nnFj;EB1y-Z=!{%FsQn^I%nxKnKuy{5M@F=Kh zHupD<{c#_~d3hm#j$5aRg8{PX8eJHe?2+H@R@R~B=* zXqIz7=s7`CifP`YOfp+)9O1k@vzAJHS>d^dM1F{pA$^o~wv%e3^$EE5r|Ix>>PBc* zyWiwyJCGxJD3MB?<_yGRv7adl(0shzT|78YsFn2{$(5EoxgJhsAFr415g1{ykl|_9 zjD(^!cdt1=~nhlmST~k z0kAlLqUs;i`?BB7ZM@l?g;7bV;K9UlI)fYZ_?yiS&qlM1=XEc7Ep%XED< zg@3CvpI|m(Vbaply1Kej$#-AP#mRQqk(()n`g^?K{A)V84EDcHG1f;i{>z(hmxv8M!=%I>M%s&HQN+MO)Xcd>eWSTdb! zs9rf9?}7tFqv444Z32ro!9c6V&&xd)8^Bk!Xfy>ixu(8CK={DQI!$E?OoSfvUQ~D= zmS_i#f$H$m{^a5!ZDnnZ2n<#YMCDph^%62VdceQvqC3}hGV>{7yhiz~8+Di4VgeG9 zfRF06$LC3t>qC3+WWFu9xVR|IdBR6tjAknvn-H%_8$z9h=kz{+kbxWVD_W{2k4$)DUd^LH+B`%xDl4CcI3&` ze!K(%>{>|uDHwlO_wR3w&WDxuw@N5!l0fhH>5|Q%k`NmcgECpz+=U^|%qo%-?6zyM;V)twSc$u|kGd2+NwEIil-2tT1ccATLw{J}lJl&L>IX|_6 ze4|$XG=x2=TCIm=Z#1-SC?K#Yo$z#?gd{*jXFixK6x( zsmvwnA6z`|I{N_pm93Zi&>f1`HIXM>Q7&@(5Q6scHSbJi8mIR~%JQ-fa1n|N2oM8u zj+mW2fYWs!677kX0kns&7nZu2j0Q^{Rh*C)3k&s*0~j*cKRN;_^xu^f7mues8JY;+ zMIP$t+Bxq1GHU<+VZOyP5U{B9hU0$E%SLYX&;j=t(3AA##Vf?u-6JD3l4ETy?5W|~ z37Ft4;@8QYgo_>Gl$4aW7BTauJDF2^P(i`LKgY%hI&Pni8dvf?y-(c7B0|PnIbtk8j)VkG_an4j!#x_f@H}lGrQV9DHt~2G2IE6$3gyzys|tO{bp0M_ zjpdT*^roN;vLrT(-e}-6l@>iT3>q!y4Edgmv%^US$=m03kIPVS=pR?EPq%>LMZcN# z_%zcUd*D!q$Hlb;9;b(h)>e~58tapJk97L-qqeruNTM*XYUXfqUK!k}>|0nOl;MMa zkKp6OYc^Tj9!(Q}%=jK+9>&xWh>!_-`hWvK;SoKsB%N#w(A!;=OQZ>&g1yMZV>Q>_ zlf@%8als!5Z?q5)26PYXRH=yW{$OTHwXs^~GJ!cSW^-nUQ%#M;odG9AzsI8!{M&`; z%iE*rnc49|LvgnY7t)z62EDWVsKGRb2247LK|;DqN?KZw zMp8PYyQI78j;-JOp6{M}e%JqG!`^GpHP@VDJT*mwbfa2=o?XG9{I*LPujsn=V+@$72u$?Yu zy=RUeC-C&9+fX;o0mRx<`SSX^ckjNaWpac)3_wVCaQOE=gRut?AMQc7<{v+pboy@l zV37(nqVHe5j>9?ripZj|xfA3F@fBJfv(qU8(Y2P$AMv|nzIMJ7mLNE)KOM+X^A-LW zwbK}xca?uS_#R*LG!BO4X_tmb5P|fvJn1;>GreTNdP6~E*kq{C@{x0Mk3OO93jn`H z(~Q^YExya$E;BK63sB`=I-F7+Qypn3P|JLF+}6FCNU!+i{?EwA;w5I*-36x`tEj=X z=gxsMn`UYpgcs(()59!Bt4j^XSgpN8e+xxEEU(^*{d7Xsg3q77s(HaU2lrBM*Jrb^*oD1}y*Nn}unj;fe|RjkCJ{j4R%E*^=-)hX^V4muDMYy}S15=E+qroE!$4$22^@$= z9-#Ht?$Et}+j@4ML`D{K&Rgla;6EesW#AzFZXrB-uzOrI2!l@jVMQm*{vE^P z9X5-}a4q+du>5lYmxBPSBuRa6Vg?YgMn1N1z^Lo)4wg$5Fa+a2)(%m#Usxv6@V8}* zM08Xp*LhKRh7i*qb_Cs{)?fl&eF6acsbJa$X;c#SeK$WB$&gGif3o;VhoZuMoqH-z zt^32J+xwv&T*)}*FjzKgPTl#m9%~s7+i&+7ycs#stK6X+cp%Dw(y!Z+pY(e?>-py; z;1??vRwdH?@AQ{|pK@dF_wTwALRP}96#Ra}4oSA4wdH=K@riLHgR{7gAFq3Qc4HNs zo(iNt^+ZwmF|o6vl#Jww?CCSq9nU8U7CAhU)3u6PT7?X@gM$N5nig3Pnur9SXvOv= zsJXJ4P?~R;zp`F?2x<}7$8wY(>m5f)(5U@lmFRmgP(O7^Yi?e!Qly5=iGp(Fmig`; z?MA_%11BdZ%4M;Xp+GQTh$5-q$f~o}C8V;e_wT~WIJ~3RSAFZd$8kg?Lu`MMla2ei znMF}xQyL{_f}$r1no5Z_DSZ^9LEn#U7|$zDL7&wYMvX%s$)NN5Q~lcT{w-BeQKd&} z4Y@I_DkYAzAmV_a2!9~!kt`R-xuE)g0ZT9x`>6cafAkk)xjFCa!!>Vdmfm}-*K+Y$ zW9-+xlQ|~fv3}cf2a%qBjAWqt_KA35nAwvS){v#&g|!4L>@@Ye+|`K{yZB7g=Z8He zw`6$Z!=cgzZk&+Q9_x5_L2qU@{mpPm%mXh0*V3usVbnQ}J!g$~w9ogPN$y4#Eb{g) z?_bpvu-+rEa99tW{stF>P-V(cOQC9)9uhh4uZ6sJuO82LE-f$OzA8xIEnU#KQ(6&n zams~~JhY4z$SK>5dFc?>;ZAyPvrVpPm1Kb!L;yoz^U(P;Bnxu7=;_jy;3Ui4NJg+N zHmIi7L&dM>L6Ql8gYl??b-x(sHH#18EF2HkxS*4vc6S%6x!hYWu5#Rthl$O$1}eIE zXS-GFlf75)aQjP*$7dOJpG&Ez5ZIXvH3O^*8jzjU#3^uCE^bu2@NVy>ip`0@aL2+6 zx&{Wqu(03Sx4denu=3**{^*~raoY=p--w{{)mL*-HzeZz>ZS!Z|Q)K_!k0mc$ zkCDEpXOW8rkxG1(syRD`MdWGWXJJ1-zXwlfqFs+QrJO05s7RdY(<{snn}zNu z99Xw}THG%R_^GkR<}bUA{AvZv(eTW}V!A2dCD7`R_iRa+X_?HW4YC|HdOlJw35R8f zF!9o$n-sR?E9f`S?^CjcCplb(E{bTwV7i^29|GsS-Fqp5M@%fSYEKg8S}Tn&F~whf zi(PtkFsCt~+feRnGLN0<5Mn#Hcd<(&Cnv{d))&3RsQFd9SGVT49mB}TsOIE^_&I9v z^V71m%X1_sTT4vG9!eeGTuE);m?rt|{@JEQS)(3+a##M<>ywUi*eA77TOwW_1sW1o zTA(AF+uX&6&EOi%oISL|Qi_VH-_h zuEbN~w^|2hhDTeVD8Y-Mt5HoMXWAl6l8kMD4N$gN#O`Sfi^0-CUhe6J=`XiKcDK`m z47;4jKBU`%!U*Bn)Dq(sRAOL3toV%X z)b9?PxVX3>vrD}pdM&Sqr(ZTctZ>VEwQDHV`#Kjy8kEUGYKLcK!A;kf2>HD@b5A4T z@!gph>kIjQDQ?c4m7J{Y|6{_8M1Yh@laz<2QOX~5KRSm6E+2yYkncaCM1>vW8ZHS* zr>B=MR0lU+W-HEsQT^<6lRdloWyIE3%Qt3kKz9WaqIi#sir2#))s=RL6oJbNm%!0d z6T^AMt9O{#Q0A1d+O`oxBZ`3m`@4ao`Pf0inbnaD#0&@rPoDqo{Z5usJ#-VG%rsgB zr)_eYk#pnHAcWfOYFI|k(!>R?clm z?YFVG6S}q>|2A+G*A*zOS@H4leXt2TzA)=KZF+f@yq?7BW--8Xm1ch<3!FHgQ^6(D zL%5&cf<^W6defG7UpLWNbe+4AzPQ-^4gC6mqnWF<^{M=K=2TH!qU?Zke!CMabF`hg zSBrxhjW-SsO3X*zP1Ih*W}F9-vWJ#xc}QI1@XvRQ6#Kkb9n<)}HBq^bMZzBn4Zhy# zC>vh_kAwb?Oa9q@W7glj)x?jTcKe|3hyJwTbCU%2*kG2%$GSSB+jNRIO#^*qoBZW+ zqx<;O(_ZNO2N7b@TYU5f5gPh5@S06AUp=JK&NQd&qgGlM6BB5%WvH+GY(_)#y?OgE zhjKEv+whY@MqHc8bKhY7rX9vx0ch>gRaI4rYLS498=N0b5s(uP1v_~)M1fPcUC4U;9)r~oQD*(d z!h&~jaIiOB3+m!+==(qGw}pgm#I z)!fq)32x~66**$FIJ2?XTzz`zbauoH94sg>J=c!S7@>q{nw&&DVA=)-P2-G)I(fZ_ zuH3aoe({W6r6GL1FAF{)uoU%CX9N{rAt=y-m{mQHHO*-L_`KPNkoZJ$bJz# zG`BFa!&A(G9g59(oF*qs=aWKeb;A*s9?IO^TX!4ur4xCjfV#v|z(s_-?F<;N4CEU` z7iA(U0)Z^7*0Qf(lMMrj;7&mpS)ha_eqvJ|m3mn&_2b8nk#0Xy`SkWJlKEtnn5-p} zR!2hjH<^dCE~gwISP&!SY_iP=&2Y9``9U(o*UM{;Xg#GLggn*ZfE~b(NE@n+AI;c` z=shaNU+;TwSh?-UtlDw|rpe^7fqzv~t=wHN8@o0jL##mN;WNY^b7Z#D>IxkwrZmKX zc_9>BeotRLE)Xd-xhLQhntXrZ#`+cC8*=ns{dd5m3esDo#@kr1V^p~wv$V|#Hqa7i z8g;N;g${lsLI}ls1TiT9n9-}d&lq1K4XQk^XJj{$|2Ka71#5i@rec=D!(zv_sCJ|` zrr3=>j#Mt=N3;Y0qW2OViTdqcmfQ`|KM{E zjQ<152^Rgu=>R$VYhU`H{^I|G=HXgcY!coN{9|wWpf2|B>nXSdWJG@>Dp#og`Ewy9 ztUtkMtxajTe-Ofu>&CN}071qsuCJSgCyb7a>YAGBg}Yr1iG%tX7njgDQjcp`W%@OJ z?G@oJJfbX$N8(9qtMUcH(&4Jr9CxHv;?k1x^02#9^JwiE-e;rX>XwNlr{+%yEPZiyS}X4g~hV9IoLUcC+D2nuBHb4p4#1cAU=fRb{I&jjB$I5)t(JfA5ETvM)& zm*r@#)sMHepfPK9=~QMj>y1U|=JtmLqeG<&j0R1}xb570?Mb*j777%cmU@?r9WI9Y8K5_hwlS-oYMMgSn2%1pChBVp|Py(Az zxNPrkXa(5639)||LoKU6nb|LpsvPW~Qe{aBZHwd4@05}Lo4AB+GXlX|%kzG1=B&o; zitx}(&xQ^K(B2~7h2VznELJ0x>RAcEnZ8*s&_Op~DANM^(jIOqfr6DT4T1ht7tWPm zS)H()M6($X-Jz@U`yLlZs6cD&A1`0PsQ&Fm+^@Xo^J610qj(4NlZti{vD2vZOax@z z1^~|WwXA+M_*l-)&$FP=0FpcfG+hJvFR#CKx_-CNZp^;1Ov~*Y`=?Sa8?XB|`G>Y7 z=~Oe{u7EfuzfYfJk(6?G5aZYpQ~s8J^Pt7_H)f)M#|@g^D){T(JQv2vb%D3L_!r39 zvuU)zeD)Vga5l?C$Lp(710Mq%%d^x%j<$-M4T_`!?vgQm>A=S_0k}Mn{W8q;Sl#Jl zk9M8gp7{+v6r^*83;=Pm^OieYZtku12S1*0{%UcFj8L=~|0=?!mQHMdkFT`bYziK; zCz!N37@yj^oPIvJF&PF3>rGEEZp4o%gx8T_;~3yfFQBGktGWhc@ElV zTKP04D95E74TYp56;|xVIPzZieZ!56j8x23K|bYma=e(WxY`}?!rvCd=s6fcIZIg!t{| zkQwyaNn{*(MrXs!l9y{XpHowhZFhtKSv+=H;#lmAiJ0G3-w{WZotKn~V_Q5z>|STj zE0v955EfPoT!DyES!7iIv5U|6wXE;~2S;S>1$URffrLucYkq#MJStGMLaI}S^kqPA zs>se9P8>wO=mQW0Hy3)s*xgB&^CS2q$ZrUpwbIko#dIV>v?{D&b}71Cd78f7zQsCo zhW>ZxMPA8tcNl7=g|VR&XKm}X^n7+=ZI+4eIJz3Py?ZFre+uB=vsc|L&>8iYN*E#P zO{D7**JC+N1xJe7g_UYtxk&k)QR`9!ZtO~z=L4Mr!7?9|R$FU_^5ZDA1oiQ$Bx>r5 z(mx(8%~ClZZ2Zhma+lt9`EIxV&a0XaEKZ+QdOxd!WlG}ubtJ@&E0UVxSf~r{15G&> zB!me2-_9@@qyrSQuT07`DCtSe2Ajo1S%S&nH)wCxNyreSu`< zW=md&Q;mI)DzNxa52ctEQc@@>jLj7rGLQulww!F%NDuLss4_5W)kyBJ1JnW- zEfS{dK|n-K^|47_(dCB^m_U)SL?J)0e#1Pxq7^|61SKjd^i-1*$RmLHM$H8oZqv$Je_ z!D;;jplNAkZsBG}7nkm>?d=c|ZF?gqE|PIDzM7rh02bh>o`Lsc4l@VK+$g=2-MUfk}+!f_=wp{@JoVG3=5+8g(opZdR_H*pH);^QWBXtntV+cEG&+@ojV;# ztUSG@ca5JkXDMX9TCeswwlPW_h1B^8d`gJz@7Gf7yuu|40Xc+=ic!QPhmii|EUbMkIc{F;P$}nY>YV!oqN1V6LBg3~XS`>r$n!Xk zyyM+gxs$4~q@u*c67#`O{BA8I*$i9bAW}Y&sPgY1BGJR(F0qJO*+$2{R|l|pZ>oa; zkc^1OV2L#YhP^LG83)}7JN3nkV6MiTS%dm@9Zg2fD(%K*DJWUV0Col|iU3A%(>c~oA5O%I`lVtNw1m{ z5=x$!h9!}`zziu#{&e%*yRgL4DQH}{yq(HJXYuhqdc5w_c)FoVKYlNr_38YhixloN z!BC6n7u9#U3_<=D5J|7ZcADN(0|dI9REfBDP@ub74YRuiEw z{v>t%Wg77y^;EYvl(CqbQ1HuW&kTjr!P+Y&>gSlLq0VOfeVA-107A@Fg~x2_Qre`z-cCCjLpfq;&SsF4zuj-7=~3#_Y9M_PQ~zUX?1TO>&=< zf*mo8H}Yni-~YRqN%XjwMVq6R%#b>jt`e}ki4O>Y<9chaUe%Zf5`${FUhCJ8@v4Qm z`I;+Nl9;V_GD}`3IL4;48g=ia49Sj`Z2rI?yRkTBI)wDi;gTOn?F@~U$9qoY0ti&= zux2jZo}tDOS14E77u?_Fo8vn3UzkhY^e0ZbP0ax%fw#^`&Jv3FPuymW%t17{ORL{L zcixnid_l4AH)G^<+}CtKMd_XxCG7$peKoPx>1Wgey%Mv_B39WO)$Zz39F=k%3M7wv z7h!l*{>5`GWGdCVgcvtSX6x#o`yEv4^c%XL92@ce442-6hVJ8spddpa4Mr-RymX3w z7aMgW$}W|;>QIugGRR)*%;;3ZtM(Z2e+lSTq3IF_V3S>Ygsgr+rfJRJfdqp%!nxh< zjP1r|JN0Vkh=j{mNju|HOIZg>FJbv=0T|%bYO%kW8s{x|Gm|9tt7X`jnA$&onHfLH z5u{{;n(dvJmz7mp-1M>c$H?iG*eH#$a+WQxLs-MvfcOBd$U>CXA(Pq4?Sr*R;c92Q zXnsAz&*whAzO4F3m|(n0{9QWcu(8z?e;h!-{a(vqQ}-lOp*4w-3~6_fF%4GiwF_g6 zB;6*(!kag>=!q~JO}-Oa4Jhb3Mvt%-;FrKP^}=r>Lgmr zUtL&Socbc9VIWVz7h+l;jykj)tRGn~>yD3)QI>%4yC8B5MC|xjQ178Y^twDKt4A{g2nQvan1l>DFSQ{2QF5>&rc>(Ut zkXVu)_t?7M>yHk+z)`NISX5U69*GU$V^zCdV-N|62GxdmIE^#}2q07WZ!3-OCK|MB zLtNZ%QAP37pr}aG?H^)Pqc@nG2VOupH~2+TfVqRXU;+d(Yj#;}A2?QS(f{??xox~g z$VmPpBR;PD}(p$0|=|c4$UXeo7Yy-RVMdQ2S=RIUz_cO}+3!Hnr z@8O9CC{o(m<$?TcD5u5eC4h>V3kzRseZOdr+@C*481pN0J3I25!H`frz_wi8F@O?i zi-`LjP(aK!zwn_$MCpN!WRX#&1KJuUqe+y?>It+=%7DCM@d(Ict_6%|| zSDpfyge-G~Myccr$TJwDSPl2S+zzHK3XWGT(25%PGg_kLo`y<=vvKiHto%V;0E^#( zZ=L{3`!}B<4FE?VbFS~R@QUeWGb8{n!nm=S55FbjFhf8<9r62Uy}iANnF;p2e2wqT zIBI3O#>RfqNtXAfAdj(4&mw6W4o+}sED|iRFuEMIKX6)u#gv7Y-)i=@oynkhcuh}_ zY}xv-SV1Bm*7C$&<6R#|Y;hY>?-zl<=`XZLE@V#B-h?cB&?Y@O7_x$5QgBb;%jr+8aa3K z)JhQ+%x{(7da@0!L*fsfx}r?t5wlAdZ-z|5yM#Qm*h4c@QwhN6vR+E~HLx3xe-M_a zLFmfvaXE)a;o?5hd_wkipO}N$^gtbOC|$=|rPb&!r}x<&b$s1&e7CMCLRldtq)&Mv zb55(tJHuE9S~Ns=fiNIchGQT>i#YFfu{on{A(Ixcd{czYeT`tTBd%LUU_C>(>Dq02 z)!Uhuk1EOy*N31}$Q)*fyRAm7Ho4J92>ux)sArl%41sz5x?aN%T0}A^x$w2!wGq}T zpTJ~LkeMhJB_G9tz}5$_@hwY)ICPkWzi5QF=l#f%B;z}xds7iypT;QzsM;J*PsoGds7#3MP$1?fRIxI+>JqpkOLB-JW0WubL>ed3OlujIo20rqKcp9IAOcsn%e-Rj;y* zfg~B~VUAQM{8#kfhgJvv4iO+qF~Y*aR)Cs3t?<+xTw&i^+rEJWVHNu0@BPj!<}I@o z^M&5L$<hj zZywcd90&SaaR&a_9Q*Yv@&rnLn9UIAIK1EA4TgPL03RWQcWGFw1^M-82{RNJjYEeV z-AMvQrw0kZaHGhYyJl&u4m#FBv-ME&A{-3U{W+ozfUm-?+B7;E+lX;Ue6fDCje&H7 zY#ff22{DGDx=&924(Mk0;T;OFR{J04zbT@r~iAIv&Q%LF^n_#B?r(rbltDca``(YkqvRd>}; z;=MMkfAHXuTE#WkES_)~FHaQv>JZ^?vTIp^%mhq?7Q;2#&m7!`za>r`tY_wCQUkLb zI#HhPjaJMb*M)C`zjb~Rc$-1~J)wdCns(jkW+7-eo%c2{ocSW?Ug|e|D@3|_z^6NW z)3EF09n`P#RVs2B(ut^bQ}~Z9VS8K|%8_W}oJ9O3v-8>$Xl-Fr#s;84sf@?NQ>W2~ zpl=U|Q83QmgRj|W)T!FItHzPnGBGjn!sz9P_ZP=Yc(K`>=|5ra?X_L&Ni>v-1D|1i zfN@fhbp&UU8~=6ilkxw)B(lZE;<`N|1B2Y==3zGaReHsa!|+>^Ep#W&fQQ;{-luu;KKaup z)NU>wV=L)}t_Lan4jYpO$Nn!NDV;heEL0E8`#tD`L+4GqR2jOYm%rzq3F>a+3{oA( ze*bliQ?!EfQDzK>-a|xuNkg24p`Coudyg+SYCi#<8ReY7DpoCBp?T#Sm+EYODNFk{ z&@<4m7k;7_Cg^Mn%gjpnk*xXPy%mrIa8$!H5FrMgD1#=>G;`%?slF^*Oc*&t{?x=-UZ))C*ueKK0TfcrWbfh5e1|sW9il zW&GNR#8C@Q;(I!$;&OB&9-8%Q>FRZKzMQ**>h=hbUrFAKV#@$)?b|h;f`+`MHVfr; zH0~&`{DlZ~Md@S=_gb_##``rmP!)xNHw3)ItBY$vx?-bnM3k&R>V`Dt@ z{km)}77d^0Zr;r2Eh~C|4J}!c-?GSi`o%X~%%~)~zyRTvnbYe`8IMaICzKk?bT(>7 zUtq+$lTpPsW`3NDKMZV&>~ac)i>TzNM9`ai9K+yB5<(2bIEd* z5LNi8V@YW3yCB&SzEdr=EIFHznAq6vgguU|xNLGyXYDpCmCN9r;XXmX+t^vi$LqH& z$Zp=q>8{K7h^VC|c`I?jltHQz&Awo4(?%w;?un0^wIr44Tf5OXv^4#WY^^q3y;WlL ztr7ojCLg;ABM-ZR%ltv8z?*6;3=4Yf+Id9=%xXG1fp6B=N~02JvyR8bEW*gCBQ=}} zYZ$?iklX!&lIg!E@h=nBq)J;=t7|nEYR6-&WF00qNFQg_ZvL`~wnoawpbN&RLTfaQ zd7MCKwS?ySRl)ClI<7(wW;mLxnXwp+q$?F5|6vzZ2^Spy zkt=85I-Weh8p%7;=tKKuD^J90yw8imKc3E3hNNWoR#iA4sVkrdw3fl*oQfhl=wHw2 zIxZB9F(a)#u{Yn^aa^6tsaWfy&tyYky;U)|9If0 zsn0T-!-aa4hj@g9!upDe@0OsGDJ(ASbj9n}8F$CTQg%=A7`(beCHIB4Emf{z^wcfF z3VGzKBJ7{%n(iN|hMBjR&4bZ$fD=~Z@`}1)%dFtm60RiGW zr2*>7I&#hppZCOS7GInCc}X?%cPS;l+k8yp;j*YeG@0;|YRW*@0y|LrsSVDzEmRb( z24Rm6y#}@Dr|0(x&cb%6v_0{Vqx%TNpU@9U$zR0P`aTdpwCd-)Z^7;HHAYpM@q73R zn|{7#=EKaS@8J->ttmj?yIwNi*?{8D^E}g9T=DG36)JJZ9{kuy#b#_n>XGU-`J5r7 z8yt6^j1sM5bj=X58lHtn={}3G;k%iSM&se3j&n`llF0}e{Zb6qxT z`&3LDG0j}W%I%jIlUp(kvhGUoOl1u&`xaDgNL1Ff-!NXS#GtxXU38@?MA_+Vf68(t z#kem9x0n0K(PA8jO52*^w;I=a?U`1$mL+At)Fqw&Cz3A}Ym!o(OVXLjD<+ouC%cB8 z)`5~HX=mrWf)zfW!#3Ww;+Z`D-qGGm?<2H2y{5OtmBagZBUk7>OKOF05!qYzrSNkj zVS}LVu_fOKni%FC^ewR~Ukl~Yzj;`pUbyF;6)|(NMy~3XcCQk9;|5c9kkx@ec2H66^YVyu&T|ni z&9i7$g%gWO_wQL}l`C38!%`!hL_W78Z&7w_FV zVnK)V;f#G}H^zIPqjCOLx%-fVW%B+S=Z@ejkZ)&xH$L=qSCUIydPzo-`%xDqGt_`4(_GZbFb=dD1AyLUsEEr*uvJd zv}yIlI&h&gjQv|M=>oQn3=WP-;he=H*0MEwhphzsugm0T z&U1tJoZ!yYAhS79Xo!jRkvV8j_A1N$<|TT)d9|9pn#fC!&RwT{PmJf{r8x}>l^}na z`{L)f1!Gos44Wn*a27k0RDX8ebHK>iAAi>8RQ&WRhb^s9yxyA{)ayaj*@rhcdP?u@ zW#z_;Dzs-AP%HdMn_grks8ow7&w&;87o};<4>Huo0D8&T;-?iAkg` z-gkbr^v27oq#11OXYiv7NjdwBPZ~s?jC$b}#2(+$&X~TI$ddmk{Yckqtmppe)SFiB zcNored%tqasvNS&fD*rc;5yvzn;$+9ET}A8r*S|jqcuA_IliyrM|!WqH1RB}dQEZ! zQ*pOK;;{v`l=|jnRqDJUE=lot#n20vZJBpMk4uf`Yj&vOng&ut!2h9NK z<-W7^hqr$qMV!0)th!r*w0cK(;|Swx=jkoAq}b2roR7^6PaJ9B?BorA@p@$2!icxr#+ zvZ&=gt&pMR&9c%67V~6RWSUUH9Xsdrh6Kmt_fhy|UBlbpx|1c6S5Bgf;N@O$4t=B+ z7+N0dt-${)$w6n&qJ3@o`zcMzSpYn-G2%*`D1)RG2~H|84y;Lh9p;I4HU`-h%Jl{L8Kgk82Jn zoOCH?*Mk(BB@AGvkj{HYq0?c}?rR*^*Y2yLeoqW(#MoDO5Z!K-_a>uaE^DK%k ztA0NH1^wmbuB6eQUEu?8kqVPfD;AX;6!Yszlp{1_I$EWVe;V)eLkW2+V3;Y|9vupEf5)3DjTa<7fO>*S>z`8%F`!P@p^0UyLQ^It0XJsG0C#u{hfrmw1( zl{P2*99}%a!D$ zYu%BUum^Yq_(YP2x0y4nXRZo03GO$vSH5qn!2OcjZ5$x-gZeb0cB$lTWP12MP60ZN z@eBW7=-HL@^a^L^1S|M5V}*UOgdk%B4`tw)Q34N=oB2o8Ig?0X!CYEXclvYLO5&{njfh$A%*+hR>i7EA(Vo8NF?0)i&lkqiDQoHpLc2DQVG}265;f1c z&8DSa`O}cfnRqJtwY%bjpj^s`;dvxvYw{4u&xfl!RHL z7g=u4@OuTnvxqw$jQs2%DK?-@ueY7?!)xDAPdezx*@W`r_sM75ny50sN= zC@&{%?oyOI#yQM(M67E7%BZ%!dK`4yE52>V)a_>m zv~4f+Ro4xS#Fv)~kM@#7hdOLynh#aNt=ZkGU&vU5F|Rg-e81`vhn~5^^(JUCBVNgV zF%lMmL@S2P-C%`H8HW-%bj>c4i%2w~3I)Bnh`6C3BPf&zIW{QL_=vP>Ylg z;yQkdhbzs%LUP#@IoWFFdLjRv_3H;EzfT4HVKwKMQN;;(cHOV_x%q}X|17xUdJn3l z{Nq&+SGjcc(JU%ee1z;qjan8X&>tz|S7XN~k~6*@hq8RC5}F*KKV4PdtyA+3-?ofn zr0xAWaNAb0x`D92M(t*vgvZ~3{(CKrsXCidTOCPdrgiZl%Q*IQIXLFgOa$ebvD1}YzD%|kMPWRQ;ojNEsuALsr{9~|130wg4N&> z5dI|o@_lXKA-}chMr(-#DHTdQ2}M7JiNVH@iwH%3D0B=IXAKH0nLtA zF~9qwA3dt$k6FBo{8{i>pRn`KcctOCrVlaRb>U-47>#-*KcH!!5w5TTi#b&W6noT- z>O+4RY!zn8KP~tBZ9^k!hA!1PcDGEDcN0SqwWrE2YpN8kH^nw2;EUg;t-o0w-HGZ(~oDf?waJ@B_^y86pNUu#M z#>u8ER4du|ujDp6?WCS}(S9FTVSgK!O0}VyD(r0t0I6j6uaG*&Fydz}G7FoVUC$30 zw#KABv`!0x>VgLKE{SiV+AR+9hnXx4f~supR~E|@(Q_u9^Y7`&sXOFy3H_j1DmsmP z56YBz>;VmXlO5-Ij`Y@&iWpY-CSOihLyUO>Svtj?iQgt){4-y}ju+AU7NTUD z#EA-j{qihc(4J`F2ET*of_cjPFPe@ID%C~dft$O^UOY1|n^s@-I<}xt$+O?~VIM?7 z!h9np^h|LM=cq-->5V6guYwrqidZvp{ZX4; z_z)AI--(aK%ozE)Dy;w}>+^L3{O)M@?jwboZ}<y;a-0#zUTh5!=<(^^vtA#m#V$ zA3h%8^~nyMPr6csG}A3=Ee!h0)`G{qrSNCg^cEJ;Y?zcMVKOy;8Vs!aqH=U5b40cA z{H0zNTdd1VNjG~}y$>He1vY4G_M2qLaLFn*9ZdIHO?uKML%~$rl;$@_6c7x z{}>Of8{)%~`-P5$sr-;4kX<*mtzACGlC`$l+NHc=bK~mAch}v;h3N0AYdBr8i_$RE zx1(U1^q?rmi|P6{Pu?Ff5pf42fFwfBWhCY^E&(IY0PNH4(eax02zXIHPUQX<0qeLs z$NegFUJEYD?|i5v9qz$%NlWaRykUa@HTkvXRxKrVl;V9}I7%}&wN$S1rO$w@(fqIY z2M`@6R zALf%FfnqeNbjtN7h%w<=4YnHtA<`r~mY4NcYShc#fm`E4X&^gL$xQYgqPHKb zKcO!Q{Sdp0zS0c=yqF;x#`05?MhHLBP?7@?shSGivo7!>fKK2AcbSE6clI5iO=eeJ z;(%vI>WJq02su(a%OE}1wF83ZDjb;fsO`D+Ks=|c#{~ieUZXTuty|7EMnxGO9;S5e z8e5_#V$bdFdEkZJ4X%>jt;1AbaPnCqNvkp-0a?!JCdm4<)9K3ok_^KDX~j#M3wSRD zh207To5`o=$3GvvWJkG_$n3Y;nWtUsib+`Gu&ABzKK^)jw-&cCORJU?jsP%})M?J* zvPix-ThKQN9?$;wR{s5=fzN*o|(XyHU>f8Ee@Np61l);8ZfCzwGJLSK(g=`T{ zQx8^N14ypHB6@aDQI zbRNT(|ARRF85qVq#ePgle^7cgU9%{aX>c^n3C~D9se1twpohu?Mwb7 zKHur-Pi(^G)#z@m@LkenY7gPm?@xpZ3HBykNwK?z2+YW&i};IxM@&jKvnN7uxb*~1 zt-;zR`XQ><3@H*XmbysboZ_ab?j*IE8ieI40en<&BpN~#z~iuK1!C8#u>zU93-_J= zzLSYA95}w|;vu!AZYvq^z*_CI(6;{67)Un}OsiIl%+~Q57p(O?xyH9{Wj=8mh!KuSh@$ckeX&4)G@d3w&Gm$6Up%UY%wyj~+RGrI7tt^!k6!0)CoZ78!1M?rns3m{j z!<~rji_E#RT?L4FAfOa)iw$Y1$_YWufF`WFA)fN@J&Pi)BCW_%Efvomt0k@Iyh`@v ze-D9iy1$4v96ZP6YUxo_5VilP5sZ+bu4Ze|!IBY=Qf2?lLk0R$QS-t7eaY}F0D;jV zx*np&z9iG>#LCW|#KXRXJ&;t}!6ccRF|?W)<|*=T_J)mp-|RgHiPD?o>+b{wF|XYa z+hP9`wXvt6?Eawe$ae+6a1B%MxYX=T>|1p6WZ8|3lpG^N>6#zoX-b{3rx#!QegD-? z)3Up>)6mk=BA9>sKg7#_EAGpq|3qE9Z$OW+T!~+h?nURVZps8Y1F%h<+eVf2V80(dLpzL1Owq_8bWbofQ=Y3CkA8(}f)q zsqS(F@jrb`R3w7m!@eC=m8SuY{P?@}FLV2sZMhSqGf$P2U*5qjMCw`Mea?-)oPz}a N#Dt}V@&&cu{XaV3;j{n% diff --git a/umn/source/_static/images/en-us_image_0000001267230305.png b/umn/source/_static/images/en-us_image_0000001267230305.png deleted file mode 100644 index 806c94cdcfdd3d6eef2a9668455fd0cb2b38a553..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 391 zcmV;20eJq2P)P000*V1^@s6{^R5m0003_Nkl+b=R9w{BQfMRuqhMqhKR3j zla89`sz%*4(gk#y>$xmy*@v`{AmR$K1Tq|58%Qf#tS?Vn4)2e+1o|Tb0PK-BjpG3T zwn#I7N0kJMOTY$cQ`9RkJI9Pm0KnI~xkRN1lL>gdI-&4Tp!$L%zy=8t2*T_A1-a32 zr05c|l43D7B@BSw+to5@w*7?1EY=~A?ipGoZZ27;$)uCLkFp2yPUE>qxg~~# lCsLMu&YpU~{PCYrAm3NvqhNmXJSPAE002ovPDHLkV1oR%sHXq` diff --git a/umn/source/_static/images/en-us_image_0000001267350317.png b/umn/source/_static/images/en-us_image_0000001267350317.png deleted file mode 100644 index 806c94cdcfdd3d6eef2a9668455fd0cb2b38a553..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 391 zcmV;20eJq2P)P000*V1^@s6{^R5m0003_Nkl+b=R9w{BQfMRuqhMqhKR3j zla89`sz%*4(gk#y>$xmy*@v`{AmR$K1Tq|58%Qf#tS?Vn4)2e+1o|Tb0PK-BjpG3T zwn#I7N0kJMOTY$cQ`9RkJI9Pm0KnI~xkRN1lL>gdI-&4Tp!$L%zy=8t2*T_A1-a32 zr05c|l43D7B@BSw+to5@w*7?1EY=~A?ipGoZZ27;$)uCLkFp2yPUE>qxg~~# lCsLMu&YpU~{PCYrAm3NvqhNmXJSPAE002ovPDHLkV1oR%sHXq` diff --git a/umn/source/_static/images/en-us_image_0000001500905066.png b/umn/source/_static/images/en-us_image_0000001626574358.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001500905066.png rename to umn/source/_static/images/en-us_image_0000001626574358.png diff --git a/umn/source/_static/images/en-us_image_0000001503011070.png b/umn/source/_static/images/en-us_image_0000001626574362.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503011070.png rename to umn/source/_static/images/en-us_image_0000001626574362.png diff --git a/umn/source/_static/images/en-us_image_0000001503011074.png b/umn/source/_static/images/en-us_image_0000001626574366.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503011074.png rename to umn/source/_static/images/en-us_image_0000001626574366.png diff --git a/umn/source/_static/images/en-us_image_0000001503159042.png b/umn/source/_static/images/en-us_image_0000001626574370.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503159042.png rename to umn/source/_static/images/en-us_image_0000001626574370.png diff --git a/umn/source/_static/images/en-us_image_0000001503170970.png b/umn/source/_static/images/en-us_image_0000001626575750.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503170970.png rename to umn/source/_static/images/en-us_image_0000001626575750.png diff --git a/umn/source/_static/images/en-us_image_0000001503170974.png b/umn/source/_static/images/en-us_image_0000001626576382.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503170974.png rename to umn/source/_static/images/en-us_image_0000001626576382.png diff --git a/umn/source/_static/images/en-us_image_0000001503318922.png b/umn/source/_static/images/en-us_image_0000001626576858.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503318922.png rename to umn/source/_static/images/en-us_image_0000001626576858.png diff --git a/umn/source/_static/images/en-us_image_0000001503330854.png b/umn/source/_static/images/en-us_image_0000001626578706.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503330854.png rename to umn/source/_static/images/en-us_image_0000001626578706.png diff --git a/umn/source/_static/images/en-us_image_0000001503330858.png b/umn/source/_static/images/en-us_image_0000001626734158.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503330858.png rename to umn/source/_static/images/en-us_image_0000001626734158.png diff --git a/umn/source/_static/images/en-us_image_0000001503478818.png b/umn/source/_static/images/en-us_image_0000001626734162.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503478818.png rename to umn/source/_static/images/en-us_image_0000001626734162.png diff --git a/umn/source/_static/images/en-us_image_0000001503490746.png b/umn/source/_static/images/en-us_image_0000001626734166.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503490746.png rename to umn/source/_static/images/en-us_image_0000001626734166.png diff --git a/umn/source/_static/images/en-us_image_0000001503490750.png b/umn/source/_static/images/en-us_image_0000001626734174.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001503490750.png rename to umn/source/_static/images/en-us_image_0000001626734174.png diff --git a/umn/source/_static/images/en-us_image_0000001553650753.png b/umn/source/_static/images/en-us_image_0000001626735566.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001553650753.png rename to umn/source/_static/images/en-us_image_0000001626735566.png diff --git a/umn/source/_static/images/en-us_image_0000001553650757.png b/umn/source/_static/images/en-us_image_0000001626735570.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001553650757.png rename to umn/source/_static/images/en-us_image_0000001626735570.png diff --git a/umn/source/_static/images/en-us_image_0000001553770733.png b/umn/source/_static/images/en-us_image_0000001626736198.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001553770733.png rename to umn/source/_static/images/en-us_image_0000001626736198.png diff --git a/umn/source/_static/images/en-us_image_0000001553770737.png b/umn/source/_static/images/en-us_image_0000001626736678.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001553770737.png rename to umn/source/_static/images/en-us_image_0000001626736678.png diff --git a/umn/source/_static/images/en-us_image_0000001553930581.png b/umn/source/_static/images/en-us_image_0000001626736794.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001553930581.png rename to umn/source/_static/images/en-us_image_0000001626736794.png diff --git a/umn/source/_static/images/en-us_image_0000001554010645.png b/umn/source/_static/images/en-us_image_0000001626738526.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001554010645.png rename to umn/source/_static/images/en-us_image_0000001626738526.png diff --git a/umn/source/_static/images/en-us_image_0000001554010649.png b/umn/source/_static/images/en-us_image_0000001626894086.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001554010649.png rename to umn/source/_static/images/en-us_image_0000001626894086.png diff --git a/umn/source/_static/images/en-us_image_0000001626894090.png b/umn/source/_static/images/en-us_image_0000001626894090.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001626894094.png b/umn/source/_static/images/en-us_image_0000001626894094.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001626894098.png b/umn/source/_static/images/en-us_image_0000001626894098.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001626894106.png b/umn/source/_static/images/en-us_image_0000001626894106.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001626894110.png b/umn/source/_static/images/en-us_image_0000001626894110.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001626895486.png b/umn/source/_static/images/en-us_image_0000001626895486.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001626896590.png b/umn/source/_static/images/en-us_image_0000001626896590.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001626897562.png b/umn/source/_static/images/en-us_image_0000001626897562.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627052380.png b/umn/source/_static/images/en-us_image_0000001627052380.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627054054.png b/umn/source/_static/images/en-us_image_0000001627054054.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627054058.png b/umn/source/_static/images/en-us_image_0000001627054058.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627054062.png b/umn/source/_static/images/en-us_image_0000001627054062.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627054082.png b/umn/source/_static/images/en-us_image_0000001627054082.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627055450.png b/umn/source/_static/images/en-us_image_0000001627055450.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627055454.png b/umn/source/_static/images/en-us_image_0000001627055454.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627056086.png b/umn/source/_static/images/en-us_image_0000001627056086.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627056574.png b/umn/source/_static/images/en-us_image_0000001627056574.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627056686.png b/umn/source/_static/images/en-us_image_0000001627056686.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627174280.png b/umn/source/_static/images/en-us_image_0000001627174280.png new file mode 100644 index 0000000000000000000000000000000000000000..39fad0065dcfc9aafd50ee82937d09a913802d1e GIT binary patch literal 356 zcmV-q0h|7bP)=pun&2Bk>n5L~(lVh5pJg5Y97JNW|}AqZcI z^oZ$QN-i{TF-Q{73fM zz5h$DuKr(i_s;(>C`zClJcfW&Ai3zz{}&H8{|~)_#V`Vfpcw?>Vlj*eL$DZxZrGLo z2f+c0873f=$NsIh}=9Won_LCDGovj?9+ Y0I~tk(id%VrT_o{07*qoM6N<$f*lE7ApigX literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627493158.png b/umn/source/_static/images/en-us_image_0000001627493158.png new file mode 100644 index 0000000000000000000000000000000000000000..29a2351277718c1b8e42f9cce3ed9cb6ce174dc5 GIT binary patch literal 8699 zcmdU#WmKD8*XL6x(4uW|DA1N-rMP>cE!;qHcc*A6MFPPZ+-Y%l*Ww!7A-D%Zu?BYt z&Rl(-=bd*x&3v0RlMh*0>pJIT=bZiD=ePGxh_a##0WK9T2m~UK{pW)!2!!zj_?+_y z19(@@`SlhAdf6%aK~mjqVQI`i8esc~D--?rkHVM}&fX zE)FH}L7?Al!StLU(D%m=u|XhC-*ynlidjxh&cZyGfq~&Nzj}W6_!!sSy)l_w#uxHl(0*IRc%<|2sxmy^XQ> z%0-Ru-M`GWu-JHjqvS8K(#E)*G5pKQjK@B;wDc2!?Y|$BP)HWAj~RECMzAbbn3@t> z&vAJVfBm}^o>-57-7$U$tO*K#@pp%w{?8o(Nk5?gf!h1)@$ey8!TpJ4ch@AOr23j{ z(_c#CjFb~oZ-(15lbVukXf(Ce)l+Z9WmKi43=ASX{7idf;-aIY`HU3wD~gMY_ZJDy zmPw86<~qH5Fi1%^n#zLCm40Vs+6wHCR3?eeHA!f^DGddIx*y_)A0LN)Z#Qez1D_~p zsaRfq`MNU?t8Qoz1iylfm5HDeDx7VnC)~OqR>p8SP`^*=5e>rAaZHqOiW6O zhKh~7_s1ay8l>b26mA#Yjd(8?L()X*GVFPZ)NsPy%P38pe@Z_*8Qj2Q=D*;tC@NR< zz&rV3ATm~`V(L|dt45qNlJ*vxVAs~#gprNSz>E5u(}}(q|DF4WFp5Q9w#Y2V_4dk{ z&U`wdGpdgBV$p&r!DU9%%Rs9_Swo`;vG0`;v$Oig>GsdEt=MxJd}@EdQ&x%-+Q(*R z5l!QMzEH3!9Qu-;ZEvl4?KCNDrzI6z?=0>@%IPgDE0MU*yvN$PZ>JPQuEeyuBsyAc z^Jq~>4K?>k2y)|00PUFmq%_;{MP(Vel$)E|s*V-mFKVzS;bApOPNA{*&8CQBdoy4Ix@c7;o-Lm3Iw=Oot@dWNN;iugR+;LRs=*+U7CUoZ9{{! z60TDf)%jz=P;9QLRtIFGgSnNloz>xW$J#We--)`MT(mT&bp6ZCw5IFK^T_HzgJ~reRdEl2zA`3NJ;-fm?N!?A}29ya|frP z`573nB#bzCs^bCIdm?s5O<~7>Eo;6zf09tK+)$FAUz}U`gX?IgM!OpVP)%%$?LVH7M@7hs-pPEmw%$6-(u6^rvoHc~ z?;d=|&ZWi7$L7*BY(j}12O;9#+r#9D;nRb zfovb)o_?AZ1vRB|X?oj5!nN*lcDCuh!}Zx#rRltbUj5!J6K9~V%4LZG%xv`;YBY_j z&$22z+m{o`2^#zAmDX-$i-cT^LAkl7skJKzHn*8lGGKV9r%UDYz zt?jEt+z@#ijLsk3~IwEprsOd2A`k6F#)%x%b|3e+$@a z8BK>??8-V2n{{0}6%cLC%FF473UD$@TL1dCFBNwo&YZc-eFXacV%ye#yxg9;jpmw=PV5X( zF}W42t*I&9-dLpR{Lu5k5fKhMiVgnG)b?ReKkK; zR87z3D6p!H2!%^xUVlmxJzqEziKUAt`vU}PJqq4?yOn7rh?A0sHo@lFcGc=g8qQ*S z{}6|^O+9cKc*R87R?r#j}2DXKGc} z>j_%ljJ9N9fDYkPTE?-lu~&8r-s=}zSSOYvDLe{?PXp%)a*pF7X;+l8(`f9OBCm_C z*j(^2{W^!iL*+S=pP64S&X%gHs;{T932-d;ETLxhu8DhZYZhJ8L%B-|7zuM2?E+dx&>vq1~ z4b3j{;_%`QQwCV41(tesx~-`*@Fz_{QSn@5j<`7r?9l?&sdWaVHXTz0F&>L0NCDqD zZr>>H+?Axot00w)@w3~%8cMRBB3d&H9WRtirX%I2r_{v_$VjUe;6biE!ciLF12N~5 z#Sdmw9AF$IYl!I#4#j;GHtn3Qre!aijD9;qK36K%O386;+qKE+$0XerZ+FyCD)>W>nKmuqw-sv zjJ~I;8Jhwwsl7csG4UZ)5k9r>nAx7?z83}Wb4S-R?R{YI*e^;LRs%lvjJr#=%nxiuPFe@M z+;1<##vIY1s1)r#RAnQLSJACd?5(E?VV6@R^g%!rd&wa9|Z%8OQ z$jeXn=cnO4iuED<2UOx7aU^hA#8{3V6V*>qk2_!NCnSoYp}0uH5zMPI&qK~dclgz5 zxIk)>wQ|+4D>633Oc4DT*?b?2P02Ai(P*2Ko5W>*6R3c2cUZ*pqG;_L7Zcfm<=n20 zdb8kwlzkrJ;_LFC?1>0(7reJaZcX(kZ*Pws@xc#8&n(Qw;g8#gs!4OZ)`7r-qqt5?8KfxEvGMUL&{TrV*}OOs5|Y7z0sd)w-|A)1A=}D*7YOtp zdVd5Y4 z|Ll1X(FRVM4F=XC^;lGDYHRB*4uA}c?;Q0seWxCOceX@pls%RK8l>dbv`|vWjMvNv zB(D#tOconlB*c%l7Ik8P9Cp)M({*G77UYv6CUooaXXA%n9iIK`*WE<4VmU=w{NEa; zuhESuw`e`0-N_t1oMa&Z0V8QmX%$JsIgjr}H@;FbsM;{{xx{3OakcGPRaI335xxEU z+r;wn^Q7PMgKrrG$VHs0H8(a$Wg;`gzwMG>b#1D=|E!qtg5_n0K}c8$IvcAR(16-1 zq!htz(@-1Ow4h5T;lS~kk1uY$U^EIl%~8AZN8pRfqmUu8QBrd9sPIq`M{c*P*dyxt z-Sy#KgLs~I4?q{#4{^f<9FX=1(grJ}v%S3nrVVBkWtx8U(hh5pP)nuvp)-SK3>oW~2pA`ljnQ0-Utv6&xyM=0iX zuEZe_BvGO7akM&}eOaBGmp5m}5AQN~Z(~CxK)t!u3l}*%JCi1?KG$vQ>2Bx&c-;dt zQh8ll?`)~c-eEFd_*9oy51`aD>RZ&kuvcIDJGzSLREtJx`dt_Xh#=q{w8K(s59yPu zU>hSY);zX$3zghM)b3AZ(FnX|=6sdjjclS8_W0w!*GxoMz5jWpSAC9QmWF1FPQ=kN z;^a6yT!8o2SJxV^TgDh&p@I<9`g)o3v38ZQ>$~4a^E^zoUo2F;2vTQ8?XQ51$j?YT zjrC=cXv@qi`WbWk%)o$VzoJ3D%vJvnY}^N#S`^EyGk*Y^ao8J&5d(3cl~Pg(GFiBa z^g9Ho@z2Jed+&>Nz5phU2njZ4bK;7|8QWmI7goqmT7Y#1-jZ1*ebR`J zPT6LwPAA7qN*752AVDbC{Vb)(`SY*Zm198u#ipvMx!>%frQO{($zKi7u*rwB_Fpxe z=#ypCy0JWcU^AMQ7Eic(#Eg`H?*hXw9&&yYP=d-24Gl$#HItE$xo+8AP6l^$B3Xgz z#v>|J?j@j*pOHE1!26569UD#-#EI@n)XS;jQ6?A%^B|~AF z(fVj&-1<3nilF7GvKlcxvc2CsV{N@^#Pw)#PXv>UBhlW@T-ocWrNvVw!G$$pq=55x zdXU@Qs)e^96doSJ`(9RdOP8*VQmyY}A7gHQzKURo7u9^KAm#3AP3k$*XEBDny!4$q zWm7NL=a?X6x`zb#x;IwJU+D?XatlUr&hG`IGecU8WRFIqiM%(R0E-~?%jaGS$yOo@ zY^usXP}qUR#m8IKKGGli%BqZ>J#h=~H123gdiLy@CyLWb!c!QXc{H?XGN6=kFz59* zRqI}lHIw`-HUnUw>L)qxI{Q9vC9Uh08;lGEgn=g8DuDEQNVpRaqgWJSZuxA$F#Ao4ZyeS>^F5 zDfM2n&>tlNd3kvS3X~%D$J$7~v3LI1IDoz(O$zbsNwzZ!u~Hj1JwI-7BIV`fRZiIr z1ydL&mN!)UBkU3ANx$)&z)u;%imFnk=+>^!qXyZqg&aK;;F%@G#g9CEK<_Y*NilL7 z8qB-?hyfy^6o?FgLJxVpq2_VWHmY^<_|No6dF zGM>#Pp{@H7w-_UPQE93E+(%EWsw!@PQIiEGNzVfxQDWqfO-%5_>4Z+GMt35A_^7K_ zo#2I@I#cJ6O&!zBd^naavl`@?5umV@#C1dD+PmtIQqO8q~zbdzw zZKa1a33mmaqSBa6X*9bBi>Mz;v)yFUSx))tZr76WHxF8-FU1qE+Z5k7y^!k`E)9-T z6L=J^d+}6axDcy$3d{z;ek=Ng-9}ZT=j6xIuF!uQ8bEjS*8q91+10h?W{fa;AbfUY^0|gQf zs@?o)kRmDTzgKY-w?GbC>B+ z@l7aS6WSJ)S4Gp1#vF<>p}TM#ml$=`!x|bIUa;B;)~>Iw&zCzB&27-L4ER*P>>^Bw zyY;><$8>ZIX}<9i1YeF{qxNAzcOn>@G1-ML4pwX&Oc$koJZr^$7)XJUqiJ(yl5ZCr zsi3Z5VeuJNXNw3;e!I8bx5CBEJ@Lo>6Vd_}rSy;W(xA4Klqjo6P^TYRNO)vH2F*eW z*K)4IWMc8`u{FV#b%mi`VtuxM&RogWVOC4as;qiyQ6<#X4Bowt5)x{RWuLwd{%U(! z+TdRRl=W!X5I}fVspsRjD@T0L`$5W|s(aVs>4(I2`m9uZ$I3{M+OhHZ(s+KBik{N?rY~t;4N|57uWXXM4_f`Tg+*Djw)WtIQTIw#px`}3%yeGdq_v; zATCbF5Bv1S+W%~N2RzAx98TsE=cs76-$o$U5T5yOu* zNFs#q(#W`*Ni>heKv?JN=g0^p_P1~H+l}vNqzLFNnPwwSCx=`Mvf3b(9`wQ7ouC2?U*wwlX!*Z1Ux(di~paU0#&mj;j<{gCN-9UmKecxSMk37v|* zT8*n%7H?B1&$zW;!tg^{vX>+O{3*L@f?S`a3}^Y_uqQjbUwZ%JS@Fs7d4VJky2zbc zjp;gokHfe92{9+9)jX?~gG5MpiiqvA+dS4ctjleqc{z%54quGzju9fZR~LWa&Mdn7 zLDH$h9@YcCNmuX`Ra#|%dIPKXGMVW2T?dOE=FRPa0@!Y!1)X>C`Eq2}r0>R{9YR;O zx#gCocFMY%w3MVujqSIbldYlQAp$nzEg_0*cUb}^SlD9uIkSuly6SilE3^SJMa-uaDX)!4p>I*th9XLJ|;IzWt$92c_i(f!{ zJh>g%Qs6)E!6Zp;5cn+!LlqXW-Pl8h3;Z78;tP{3)S~-agknmTqXtvIE5uj#trDv; zi&$R^CCxUPiCpQZs$RW*qo|@X-Vz~Orl^9u!^)y)W@BwyxYY1-?p|6Re(D^frn+UU zpb>D!yJ69rGE7Kj9~+yP-bFq$E4bV+5UR=+me9W%iH|V+W++073ZbYP8scKA;8iWwwqF*oIA*eIGPwvUehd z?x6&CreIofmB0T(REnI|xPNAY6>!*Lk9eM0G;ak_JxkIjLJjO498#XaM&V4cU*3>j6R9+4U#&6!R3VSXL ztMe?yfy^BMddB z+zu$6RAZxM@rH7;_k3?U;GjR*gD|JC!T;E25cq-cZUTH^TB5MvbP?OC+}sa3?w55m z&{$?(Ch#k;d}wG`Mqd6n)dfZo;X|TupenDUqqERL&cQQbXi>vwE9+M*To90Wi1B`R za$0cyz)8frDSyY&Ej%(Z-@m~PBAsvH!SfO85(q*{88EBma)O;^I+NhrgWabeX{ITN z6F$&0u_?GnYR)~enTH)P)1U}$kA0r1)VF6AB$Vp|Q4~p45T&xd-DrK<-?7x>N|Nhe zfdPHVXl(pJGz11&`%)%NvH0=XGc_xI$P-U-e?l#$2)drV9~|vg1bvFBF+ZMU2zpOtK7c)3)bSOVFHGznuGgtSY?$Zi zc{M3OBjH9CEh{4&EG)9~y_e}hk6&VAqaZ$m_;M>iQz!KVaTLOmp6ZYc3bO~$T`mD;%s(t7EG^c+vVOM~=o zeKNQmYbt+=AIP}@&!LTg{)u}dGq+OP-42;w@w12UBo-EyE>>QTeQ#Z=cKQ|*oeobI zf?hw);u{;+M3=|kiD07ONfVzcLSBgM$h6>*|0SlvjgjT3{h&atd(=C(kbe`EbY?pM zjFH$_lMjwllZZEslQiSv(sIi4k7sL}r!jL%TW%&cQU*p<$w$%{IXL=KaO(H{#oZ_* zJGwkP2oLaqa~A}9*?rC|Z^S)scB8R)wm5CVeAglVl*586q z!~6$A;T?Wg{`$?tG%>%vBAx%#3#y}YJQG#I#zH*V#9N!2!FyxX9tz7O|7GCV^8h>|i1Dx2G(J?8XZBewpY%!N-`#nGW zn;TF3mbTdRCAxtzobC^E`xG&{flwK@^Zfes14R00{)J`aD(iBjtfCLc{5D<|j5W0YXARXyaq(gvE10hNk6;XNzrFW!v1f&ys z@1eIqfIw)0v)p^1J@y!9?>o-@bnlmpWUe{pdNS8je*b5#P<1s$axz9T5C}xB^y0ZD z2y~SO_?|&>75J1^y|)7bvCb(ym(li`!pwR@w9hVyv0Z8&ybm;=-{769;2Ub3amuI5 zb<$K~eSY7NMrmp(%eYFlr*P(|R`~`OjiW(%EJEb8!F~tY2>Z6x`!Z$^elcjV`fRP& zJN4wazHg1k4tuzzM+e-En*0_R1o}nOat#E!Bj*K-SddVHKyPlMuYf?GSs@_MJN`go z5a>xT7P!{_x5;;a$!U_^{d`{|B53I8`2>A{fjnDpEo9pW9+dG;bku@AP zZ!fMFl?g4i??=<~4IAC1f5h3TS4spdDUHD0Lu+7ToR_{}YEGJ!zDyiHPrP3C`R4RL zR!LbzQNj%mm*4!cVpBlPuY3?HU(AvT$v1Z``D4hT(K#U_?dub`SzTwTMTm!v5gA~$ zI?|;G_PpcwkbNY${cTaI-qk;Yul7t>v#b96r1jMmozxMYTH%menD?W%gA4{ckVGoc(^G5d z=%6L<=%1^GR#$ticyeEAXJ%%O7j*(O6DhwBzY4Ke{lGoiTedPTD(hC73ms#_KI zGd3w{Vd5T`&^uBd$7CJsxEMGAhkMDO&(NlP$<6IyYpbd0dORn`p(gLb;jugAU9?i} zWGsf6M8;Ki_;&O4VCXahqbBQD6Bv`l84fomgDS&@wiI>ltZ%vRj@hn%z0#h1lbxNt z2P&takX5%DR?WIaOlyTSIgTDbKbRSM9CDejzd&N=vDbb$Atc zaAL@1TMzQgODr5LN&`Fsp{?wYkS|}xg56VSsOqV?DJi*>lrDdv6vLB`4m}vG#H6>0 zncte3X)Je@`E3cmU0WV7G@wm1PS`)@YDkfSwnKV0&M3i!4v(a<4TRWft$Qp)uHS7CJ45pQ~YdWn4M^ zF>|F~+@)n{#x%A8lGOf1xTm|X#_OcEcwWKVyJkTeD%UCu#Of`HQF^e0@R^D4;$EaR zpGj@ej~_hq>W`1+0#atf2)??)np&bv?i)kV>n0L)2^5>25@J@06OAF^V6F1?@_`>0 z@G)FyZK0djxB{XapO9wp&H5ohtlezGe;)yl$8b@DXHY$SoD&t|<_N6EQXli!X_3QJ zhD-e9L}n(3S_(|RBFk`G?Lx9hP%fTwkv!bRB1Eg|;<)P|lOkUdc|mn|eYB=*u&V8n z8C>qjUu6-V`b>pi&OMAl$gO%ZtvzhyVp1bBlaeLtZrHiN<~gl_Axq?rl^pSAmD9=! z({FOhpG4$Tkr9*^xAoQ4pV$T3&d*8Y{7P_A0jY;;Yk2`F=+XrjH9vK0v%otW)*`2> z^Hy_CDsH?I;T+}z5&=zXKkf4BDuiE!{a7b@b5lD+tH zw5uhg$S5O{_ANt`r-9fUKdFhwZMTb?e4kWSR;GA<7mqWRGM{)89(@!Y4&j7Muy40^ zsA(w97ZqNJnTqf_qMou*GU{mvI!%K6>LQAa#cJ!Os>bY?k?f+k%flWs?#rLa~dLvnJbA;>+J1qbxS2K8Ne)(zCWsK8DQf+6$efu=!Q@$uq+0IkNS74FCizZ}H*So|+doMadtWJ|rY6j~_w9#& zeNoYu5IqnFWQuX!+lv@*dZ;abbW8fa4^S8Vf>ZsPeQ}-Nx$ipmrPRG3%%)vwkeFr8 zwcv%J0z@D&JSi%~vm*@`%!o6^amXJ>e3fj7K5Erc;(3VP+Z(o~uM&zaR?u3L^y|f9 z8$xV^rycM4NPn@Np-Qb;29=d*^aQ$Hpi5Fg8TWWV{WzpSu zd7zHVXm@m`TZ9}nCwlJ8A}yPtW$Q2W4GffjVL5quC15*0BJ(}ZJRGl%RomLxY5(mp z*xEudNxD+Lak4BTImlh(c|~x2eu4z7bhKXo(IZ;V;Th~}2gk`KXz{DmVT+|5#q--r zObaV$8)3JF++n0kD_c|ASAmkWUZ$rxENc!-XV=_;WGqk}tQ8J9N?Lg^oyr1S9aSS~MZ%;dfOM0SG@ z*_`AP|J%(O=_zt%Kknq($|k_=liQl7S3Gp}eD>^UrQ~-4GbwO1cTLZFIybUC8tGg75iQe9ccCBuo=>z=EsOrrs%vI@%{4dxAa43Fz zu+6#x22%|i8X79oh)ps^0B93K8Sa06b@NO5W1|&}Sr6yq$5~)x*k$`eRYo9kz>u8c zg5Jyhd*a-NI;zq5AZeNxF=X3`h5==x9eZ z&YRFy47H|u1QoA++#0Nc)L*qJSZbIG#qU_otwD&61V|_MeEN+37-O!aFYdT^@>7=F zspu51nCrRQ33kB=92VjjIWLN&8F(7(PuJ0yK$!EcSv$lY}>OX7{Bd&~N_tn1gWmvh^Q=L$ah zY9)zSt$%%upE33`gAi_`jJ`+D>!HL;+o=rx>z`}kOM!ukg8mGm<{z^A;X5#};7b>G zd>sP}uNYnf0-bA15uCU;3j(e}>fD5XeEZA2bYyhsIVmaWX3)|S_4J+f>!)=hPBR}w zAQ_n%J2PRPZhP?LqZq5KK15h-k8_#KN`L>r-to~uLmmD?CV*+@`KCwqtHdWj(n|k^ zyjV-+U>N9Mt`Z%tvDHH#he`&uuW0Ql2ANrbDZJNqrQA8n zd8M2_z3`)AemHzACnJ+G>|-YceaOzU?j>nmjDaSj;nL zc{kb8%1Qzeb9yvO%-AhxJCu{I;X_NyKJ_`4Z+NcJr#LI?$Fy?Dn7-A44XF9#*_@(C zwGQW_&U|~pl@$JTE*43@4EiY8+lw8(L{!$-^zf{=8(KEvwx4AK;+`7bp-+`QxZ}B# zHiw%IYlF@;hKJRqMkaD_aSe{82?cTPTB&2IcH4(F$yb)e?o^HrjhzE&IaO0#{l#@x z;dhd;x)I6AY;0_^Mr8~|N!O&^TQ1lB&noCYG5^1nO#k0cR#ffo>6xz<-5!c=dTW`X zC&q^{pLzdqF05g<&cnjY?3!T(So2kn;pZ6=q%?ot0nY;?YsGFjrS% z+?J@zIf=eLLjsx*^6HH3{_bzdv~hT$L2rtvMz;Jx!W`4+M~^`uN&rzNfZ~w!PS~t^ z{CgZ06qpg1UzgfCbe)C>sP^;qv?|419KPqm>a{ufBBW%K-{;D^ew!-z6p}JNErHHU zN^t76;KBQ@p4yt41se&Vw8mRgol8T}Oq7wSy{Q(DA3s)rN+HzdOD%T&YgTQc^QmFA z=5?K#FAJJ?2px?1xt|%{p0230pMF&@Vh1Uw1_Jwj0L?I9~zf5Xs&Eimas53}fSjT}&<90`7C>lg*)1zILS{+9K8;HWsUqLCe0ZHezw|Hp2B^nVyK(wZ#Z=!UY08ur+}F(8oOOzBTlX=?)Fp1y5CM6do_`)1Bp5rWc9l7}A>yL5VVZvinWz#~s!k zhsXgzI;s#y-)mcb8zC?TzxdqyxnLd-PLZ-s_~8!`fvl4t4vr)Oh>x7?)97#22N1FI zmJ8X}`d++!yH@Q}RAvm>m1$}H+{<&o)r1Yc!T~8jmQB_=HvnWj>(m_wl=~k zuD7piV{q1MX5CDvLGO=yTY0IoFxGE)GQO^d6OOuuwfpqB$ijix)6t2xUFLV4_$B#p zHiwd&jFd^pS3Mc*UDBA!Gc;h65ElnAJ14n@keI_BpR>=lp~lCoF0y#dgm0`>j@j$` z?e+HZSc}ZBs1$PDsUGJ|Y4VDXj&}qQ-s%sj?NL_7@o&g1rjLy1(P$U!vZcs{0EuOYcjWA)s>sJWtL$bOtCoYHDsk92~Xc?P=|rzObAC z!GfCh@GdBS<#&#g{_WDQ(*x+qEQnvF3oIwL&caH!68Y<46>ZPRh_=5-P$mBWlaug= zQbnMejls}E75U>9y3eLMyE{j4kFUHtmF?{Jejw?4w-H|gA8x;~s=784VJHdd?9qdc zIZp7qoI6LR82@f-19YCU@`SQ7nNWjB+;^0Rv&rmqhB)(KS!1etslhTQJG)Zxq2X4o z*mPcQo~5Ow(^M_@=J{JCrLOp4jy}QE&N?E-w1G6%J+smntFla$Ri;XTw0EN3VvpR$ zWt5aiKbj@V!))&(6s>-= zTmc<^_}a?G$A`q6Vv@xxnFP9{1TtH&_n`BLi3RE!e=CfqM{8+J&?i33-s>LNG=$KN*`L0{Q^?cP+vHclB*y_*1McsS+2^#uI8_ zz5E&z^VA`GUe>TIWjrD|GWJ_M$|`ou?e^s@dU`EgP4%y_`D+y;mBJ56WTvt?WxTK( zxJi|V5}yGmwu8%Ed`n4TV5SxaA_H#HlV6ViNJh@i{@cFx1Cl1Tq^uNHA(%LJU|?s+ zL>+h!qZM@za_lC!Kf`B%vV(I6mMQ(vR@v;SQf1^C$E{xWguG%9n_@hyk1?2N|BKap z1xt)>&Ni5U-vaXtZaT~7{@;yn+3@D_nQWEYm{^(fI#~GM`ssQcfL+kyb&w#T)J?|x zS+GzXZ)0frZDm2ev?x{UXbIv-2 z>C$y~-vsC7Rbn|!Z&dsMM2W0$$ja)9NL1vZo9760cGGDaF<-%Sg@Idn`^$u0-vG$Lj1(Eb|AN)_lS2-^%uf2AFJGNb$7(>r(T@Bp?+*TX_r}blh z)zt8$o7O0Hy&}SG$$ttAV#%04s42@PWT;Y^^9t?({kIfCh@RNA=9I=hf|rm0WVy|q zwGuZO6=qD2UOIH{W9InE8O`_c`(7c5xOF8fD_y-Mib>I$kprMj*vxsrS-W$}&iiR~dX zxw9K9!zVTpZbk~M=uJzNCR!XfW_@v`q}QM-nu74b|G9BPSM^|PwZMEWHT_-(DIcYx zeth0Vp7xq8_ng6m!_m~CArbldY=gb^&duE1V&C%sLcOtVaL22Z-SB6tmQ6Vy=cDdb zkW8TI=woMUnTiL?UGih5a7Sv}*BESVTaQkCi@)l?&>Dn_YWQC-Pv2S+rwgwjwGa7l zQi(CngvPaS7}A(mV6eA*ew%@sTb~TwOy%S?Ac8nNEoA#`DaDpviA-(+q|4du)?l8> z%BZhjvHuD;3=EY*0?hZKW(~c0uXxLkXv%ue`LR+`Mb<#WrkJXqJED6aRzxCKM-BbdNfQb3xm%CDBmS~4$IusXE zj&+r>B^NupH`~J_1DxY@P)z-|U*fGP*E(`65`=AECR2njE}FlZPXi<+1$ZJmE$xYy zR!(*G9T5m{9^r{Ms+xdPqz~5#(SmXCJVltO%$%0uesr&R`DLVuID0T3mc2WMd zbyK*iVvdQE2M)UO3Gi>(n}7O3!49*IglU`=g=rO3J=)wWQN6%vm^$H|xOz zc3A0q^LvLYTXG?<_(~JHe0-b9DHGn;$st0~En-S*{xE^)# z89d=epEX|(B4)l1@NK_ciucLdn|!rj6tQ!XuMjoeu-Q61%T$%nz}Qg6?O@EJx1a=2 zF@c8nrZbX3#D8!Fl_2IQU(9S=ugg<4I5=odxa9mOEcwhb`%|Q2xE{ zStX@C>v7F0F(ZwhUP+|e1sT7#S(aI%gv(e^FnXV_os&=khc*GH z_?!bhN4mb4nA7oRX%SejeL;8R^W{?ZgA_@h=C0s~hzLT6n)*0YID-Y+)J0CY`MN5E z`Ht08F>vfPgH1!9w4>^*`jcLe<2Aa6fnAw=-T#r1D z#=mUI$##VE3+z~OzG(0dA*M%Mf8RV^>$dYGEmcWFV{eQZ&B(Y(-5!?acrlsyAj-go zW@U*U0v}Nqdz8V#EafdMbf|N%%BUYd8AGRKtL*3ZJ{(!n_E{+j<|b7^cSYQ2>XP4c zu|jZEH2F<(ltjd zr__eiOuz}O7rCPgNWXGXFjWB}%H#JML5>e5;U33*lNRE(B7uK9_rGVLv0F8ViN z-{_2#!wr7wH7G!Gp0AbKEGJ5K`|Jo_Mzu5=1 zbP*83(QjmA?zqP;5lIb>Et*+C6%H8RPCC2Y6Ub1A{`H;O+?+g14J_{FY9!qmGVU~M`LTc?{MBJ`MeZmO91Os@y#f)FtY506yRW?j^ISC6hhC6k#zL&3DkTLgL(rC|4{d*z#X)H(y+MngxNEb4Qz zS2iMlVBOu_jkRixw&xdtwrP;;Ns|2*Zv{@&JTRi?ytb|fM_@=JkXOa($;e0(C15{H z^6C1uOfjE6WQ?w^tPw+}+G-y4`JgN&1}-${i-1#s@=iP5Q5JE|;=l9Kj@#dPNf?j` zr*YaI!T?A8ovCiG!oYz4((}zf^LzA>C}l`fQ^LosGVX#qNakb>Vk0f)CB6HtmAI?> zMcG9%dDLHm{u`4Gu**h?YWr1_gR~bm1zBRlzW#n&F#rN5R_y}k@A{RNbBQ9mt$60H z-d;^Do$rIex-jy*Eg)KE&%S7?=jL$^cQ5U*mo|nF^WG^Hn&~VFyT?&%XSOBdRkEoT z!u_-&!`gC6tbk&=wz4;O^{Jg10K6ZfTT{i(1HDoI;6%2+apGxjo1QJSa5X`%@y)+5 z;6JdGdBa)0AcpL6>(@WmUPe*JYHl0>S4Ds8QH!o0PRy_0JOh2 mqhbGFy%X`j7C;l1SE_aouDOSbp8+pbfRyCbo)^i!@&7Np{wK}= literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001627744152.png b/umn/source/_static/images/en-us_image_0000001627744152.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675254013.png b/umn/source/_static/images/en-us_image_0000001675254013.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675254017.png b/umn/source/_static/images/en-us_image_0000001675254017.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675254021.png b/umn/source/_static/images/en-us_image_0000001675254021.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675254033.png b/umn/source/_static/images/en-us_image_0000001675254033.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675255405.png b/umn/source/_static/images/en-us_image_0000001675255405.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675256029.png b/umn/source/_static/images/en-us_image_0000001675256029.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675256529.png b/umn/source/_static/images/en-us_image_0000001675256529.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675256657.png b/umn/source/_static/images/en-us_image_0000001675256657.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675258381.png b/umn/source/_static/images/en-us_image_0000001675258381.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675258889.png b/umn/source/_static/images/en-us_image_0000001675258889.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675373901.png b/umn/source/_static/images/en-us_image_0000001675373901.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675373905.png b/umn/source/_static/images/en-us_image_0000001675373905.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675373909.png b/umn/source/_static/images/en-us_image_0000001675373909.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675373913.png b/umn/source/_static/images/en-us_image_0000001675373913.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675373917.png b/umn/source/_static/images/en-us_image_0000001675373917.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675375297.png b/umn/source/_static/images/en-us_image_0000001675375297.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675375405.png b/umn/source/_static/images/en-us_image_0000001675375405.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675378241.png b/umn/source/_static/images/en-us_image_0000001675378241.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675413821.png b/umn/source/_static/images/en-us_image_0000001675413821.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675413825.png b/umn/source/_static/images/en-us_image_0000001675413825.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675413829.png b/umn/source/_static/images/en-us_image_0000001675413829.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675413833.png b/umn/source/_static/images/en-us_image_0000001675413833.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675413841.png b/umn/source/_static/images/en-us_image_0000001675413841.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675413845.png b/umn/source/_static/images/en-us_image_0000001675413845.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675415213.png b/umn/source/_static/images/en-us_image_0000001675415213.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675415841.png b/umn/source/_static/images/en-us_image_0000001675415841.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675416345.png b/umn/source/_static/images/en-us_image_0000001675416345.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675418673.png b/umn/source/_static/images/en-us_image_0000001675418673.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675613933.png b/umn/source/_static/images/en-us_image_0000001675613933.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675613937.png b/umn/source/_static/images/en-us_image_0000001675613937.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675613941.png b/umn/source/_static/images/en-us_image_0000001675613941.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675613945.png b/umn/source/_static/images/en-us_image_0000001675613945.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675613953.png b/umn/source/_static/images/en-us_image_0000001675613953.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675613957.png b/umn/source/_static/images/en-us_image_0000001675613957.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675615337.png b/umn/source/_static/images/en-us_image_0000001675615337.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675616433.png b/umn/source/_static/images/en-us_image_0000001675616433.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675616561.png b/umn/source/_static/images/en-us_image_0000001675616561.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675618277.png b/umn/source/_static/images/en-us_image_0000001675618277.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675619157.png b/umn/source/_static/images/en-us_image_0000001675619157.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001675813933.png b/umn/source/_static/images/en-us_image_0000001675813933.png new file mode 100644 index 0000000000000000000000000000000000000000..39fad0065dcfc9aafd50ee82937d09a913802d1e GIT binary patch literal 356 zcmV-q0h|7bP)=pun&2Bk>n5L~(lVh5pJg5Y97JNW|}AqZcI z^oZ$QN-i{TO?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/_static/images/en-us_image_0000001681512581.png b/umn/source/_static/images/en-us_image_0000001681512581.png new file mode 100644 index 0000000000000000000000000000000000000000..d8f9804a86ba17c29671c2e708ea7d8a55e9e102 GIT binary patch literal 128 zcmeAS@N?(olHy`uVBq!ia0vp^l0YoR!3HEv_nU76QtqBEjv*eM$$$R;|6k80#jF+; z?O^U55wJ5{BC7O~q*zc+j>O?r+CO>N0_0+A4p~TjRK7gvqKc1@gq@&$jgF-6A(h65 b!XFtDtmNgH8Ra{GMlyK1`njxgN@xNAeY7O< literal 0 HcmV?d00001 diff --git a/umn/source/security/differences_between_security_groups_and_firewalls.rst b/umn/source/access_control/differences_between_security_groups_and_firewalls.rst similarity index 100% rename from umn/source/security/differences_between_security_groups_and_firewalls.rst rename to umn/source/access_control/differences_between_security_groups_and_firewalls.rst diff --git a/umn/source/security/firewall/adding_a_firewall_rule.rst b/umn/source/access_control/firewall/adding_a_firewall_rule.rst similarity index 98% rename from umn/source/security/firewall/adding_a_firewall_rule.rst rename to umn/source/access_control/firewall/adding_a_firewall_rule.rst index b7e7dd6..d309d5a 100644 --- a/umn/source/security/firewall/adding_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/adding_a_firewall_rule.rst @@ -10,6 +10,11 @@ Scenarios Add an inbound or outbound rule based on your network security requirements. +Notes and Constraints +--------------------- + +A firewall can contain no more than 20 rules in one direction, or performance will deteriorate. + Procedure --------- @@ -19,6 +24,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. @@ -85,4 +92,4 @@ Procedure 7. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627054054.png diff --git a/umn/source/security/firewall/associating_subnets_with_a_firewall.rst b/umn/source/access_control/firewall/associating_subnets_with_a_firewall.rst similarity index 71% rename from umn/source/security/firewall/associating_subnets_with_a_firewall.rst rename to umn/source/access_control/firewall/associating_subnets_with_a_firewall.rst index eb4a1e2..9b7409a 100644 --- a/umn/source/security/firewall/associating_subnets_with_a_firewall.rst +++ b/umn/source/access_control/firewall/associating_subnets_with_a_firewall.rst @@ -8,7 +8,12 @@ Associating Subnets with a Firewall Scenarios --------- -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. +You can associate a firewall with a subnet to protect resources in the subnet. 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. + +Notes and Constraints +--------------------- + +You can associate a firewall with multiple subnets. However, a subnet can only be associated with one firewall at a time. Procedure --------- @@ -16,11 +21,19 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 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**. + 8. On the displayed page, select the subnets to be associated with the firewall, and click **OK**. .. note:: @@ -28,4 +41,4 @@ Procedure 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 +.. |image2| image:: /_static/images/en-us_image_0000001626734158.png diff --git a/umn/source/security/firewall/changing_the_sequence_of_a_firewall_rule.rst b/umn/source/access_control/firewall/changing_the_sequence_of_a_firewall_rule.rst similarity index 91% rename from umn/source/security/firewall/changing_the_sequence_of_a_firewall_rule.rst rename to umn/source/access_control/firewall/changing_the_sequence_of_a_firewall_rule.rst index 4708ccf..f56ccf5 100644 --- a/umn/source/security/firewall/changing_the_sequence_of_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/changing_the_sequence_of_a_firewall_rule.rst @@ -21,6 +21,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. @@ -32,4 +34,4 @@ Procedure The rule is inserted. The procedure for inserting an outbound rule is the same as that for inserting an inbound rule. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626894110.png diff --git a/umn/source/security/firewall/creating_a_firewall.rst b/umn/source/access_control/firewall/creating_a_firewall.rst similarity index 95% rename from umn/source/security/firewall/creating_a_firewall.rst rename to umn/source/access_control/firewall/creating_a_firewall.rst index e339786..f622d20 100644 --- a/umn/source/security/firewall/creating_a_firewall.rst +++ b/umn/source/access_control/firewall/creating_a_firewall.rst @@ -8,7 +8,7 @@ Creating a Firewall Scenarios --------- -You can create a custom firewall. By default, a newly created firewall is disabled and has no inbound or outbound rules, or any subnets associated. 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. Procedure --------- @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. In the right pane displayed, click **Create Firewall**. @@ -48,4 +50,4 @@ Procedure 7. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626574358.png diff --git a/umn/source/security/firewall/deleting_a_firewall.rst b/umn/source/access_control/firewall/deleting_a_firewall.rst similarity index 76% rename from umn/source/security/firewall/deleting_a_firewall.rst rename to umn/source/access_control/firewall/deleting_a_firewall.rst index 83438d3..057b698 100644 --- a/umn/source/security/firewall/deleting_a_firewall.rst +++ b/umn/source/access_control/firewall/deleting_a_firewall.rst @@ -16,9 +16,15 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 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**. + +5. Locate the firewall, click **More** in the **Operation** column, and click **Delete**. + 6. Click **Yes**. .. note:: @@ -26,4 +32,4 @@ Procedure 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 +.. |image2| image:: /_static/images/en-us_image_0000001675613953.png diff --git a/umn/source/security/firewall/deleting_a_firewall_rule.rst b/umn/source/access_control/firewall/deleting_a_firewall_rule.rst similarity index 89% rename from umn/source/security/firewall/deleting_a_firewall_rule.rst rename to umn/source/access_control/firewall/deleting_a_firewall_rule.rst index 618b29e..278b692 100644 --- a/umn/source/security/firewall/deleting_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/deleting_a_firewall_rule.rst @@ -16,10 +16,17 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 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. **Deleting Multiple Firewall Rules at a Time** @@ -27,4 +34,4 @@ Procedure You can also select multiple firewall rules and click **Delete** above the firewall rule list to delete multiple rules at a time. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627054082.png diff --git a/umn/source/security/firewall/disassociating_a_subnet_from_a_firewall.rst b/umn/source/access_control/firewall/disassociating_a_subnet_from_a_firewall.rst similarity index 90% rename from umn/source/security/firewall/disassociating_a_subnet_from_a_firewall.rst rename to umn/source/access_control/firewall/disassociating_a_subnet_from_a_firewall.rst index 848807e..808b884 100644 --- a/umn/source/security/firewall/disassociating_a_subnet_from_a_firewall.rst +++ b/umn/source/access_control/firewall/disassociating_a_subnet_from_a_firewall.rst @@ -16,11 +16,19 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 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. + 8. Click **Yes** in the displayed dialog box. **Disassociating subnets from a firewall** @@ -28,4 +36,4 @@ Procedure 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 +.. |image2| image:: /_static/images/en-us_image_0000001675413845.png diff --git a/umn/source/security/firewall/enabling_or_disabling_a_firewall.rst b/umn/source/access_control/firewall/enabling_or_disabling_a_firewall.rst similarity index 82% rename from umn/source/security/firewall/enabling_or_disabling_a_firewall.rst rename to umn/source/access_control/firewall/enabling_or_disabling_a_firewall.rst index e2fa5ca..37c5b56 100644 --- a/umn/source/security/firewall/enabling_or_disabling_a_firewall.rst +++ b/umn/source/access_control/firewall/enabling_or_disabling_a_firewall.rst @@ -18,10 +18,16 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 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**. + +5. Locate the row that contains the firewall, 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 -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626894106.png diff --git a/umn/source/security/firewall/enabling_or_disabling_a_firewall_rule.rst b/umn/source/access_control/firewall/enabling_or_disabling_a_firewall_rule.rst similarity index 90% rename from umn/source/security/firewall/enabling_or_disabling_a_firewall_rule.rst rename to umn/source/access_control/firewall/enabling_or_disabling_a_firewall_rule.rst index 1684a77..6d66828 100644 --- a/umn/source/security/firewall/enabling_or_disabling_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/enabling_or_disabling_a_firewall_rule.rst @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. @@ -30,4 +32,4 @@ Procedure The rule is enabled or disabled. The procedure for enabling or disabling an outbound rule is the same as that for enabling or disabling an inbound rule. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675254033.png diff --git a/umn/source/security/firewall/firewall_configuration_examples.rst b/umn/source/access_control/firewall/firewall_configuration_examples.rst similarity index 100% rename from umn/source/security/firewall/firewall_configuration_examples.rst rename to umn/source/access_control/firewall/firewall_configuration_examples.rst diff --git a/umn/source/security/firewall/firewall_overview.rst b/umn/source/access_control/firewall/firewall_overview.rst similarity index 93% rename from umn/source/security/firewall/firewall_overview.rst rename to umn/source/access_control/firewall/firewall_overview.rst index 27fe3a7..cc21f49 100644 --- a/umn/source/security/firewall/firewall_overview.rst +++ b/umn/source/access_control/firewall/firewall_overview.rst @@ -102,7 +102,5 @@ Configuration Procedure Notes and Constraints --------------------- -- By default, you can create a maximum of 200 firewalls in your cloud account. -- You can associate a firewall with multiple subnets. However, a subnet can only be associated with one firewall at a time. +- By default, each account can have up to 200 firewalls in a region. - A firewall can contain no more than 20 rules in one direction, or performance will deteriorate. -- For optimal performance, import no more than 40 firewall rules at a time. Existing rules will still be available after new rules are imported. Each rule can be imported only once. diff --git a/umn/source/security/firewall/index.rst b/umn/source/access_control/firewall/index.rst similarity index 100% rename from umn/source/security/firewall/index.rst rename to umn/source/access_control/firewall/index.rst diff --git a/umn/source/security/firewall/modifying_a_firewall.rst b/umn/source/access_control/firewall/modifying_a_firewall.rst similarity index 89% rename from umn/source/security/firewall/modifying_a_firewall.rst rename to umn/source/access_control/firewall/modifying_a_firewall.rst index 43bf8fa..e201d2b 100644 --- a/umn/source/security/firewall/modifying_a_firewall.rst +++ b/umn/source/access_control/firewall/modifying_a_firewall.rst @@ -16,15 +16,24 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 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. + 8. Click |image4| on the right of **Description** and edit the firewall description. + 9. Click Y to save the new firewall description. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675413841.png .. |image3| image:: /_static/images/en-us_image_0142359884.png .. |image4| image:: /_static/images/en-us_image_0142359884.png diff --git a/umn/source/security/firewall/modifying_a_firewall_rule.rst b/umn/source/access_control/firewall/modifying_a_firewall_rule.rst similarity index 99% rename from umn/source/security/firewall/modifying_a_firewall_rule.rst rename to umn/source/access_control/firewall/modifying_a_firewall_rule.rst index b9f1b15..a82e257 100644 --- a/umn/source/security/firewall/modifying_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/modifying_a_firewall_rule.rst @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Access Control** > **Firewalls**. 5. Locate the target firewall and click its name to switch to the page showing details of that particular firewall. @@ -84,4 +86,4 @@ Procedure 7. Click **Confirm**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675613957.png diff --git a/umn/source/security/firewall/viewing_a_firewall.rst b/umn/source/access_control/firewall/viewing_a_firewall.rst similarity index 87% rename from umn/source/security/firewall/viewing_a_firewall.rst rename to umn/source/access_control/firewall/viewing_a_firewall.rst index 238258b..eb2ded4 100644 --- a/umn/source/security/firewall/viewing_a_firewall.rst +++ b/umn/source/access_control/firewall/viewing_a_firewall.rst @@ -16,10 +16,16 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 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. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675373917.png diff --git a/umn/source/security/index.rst b/umn/source/access_control/index.rst similarity index 92% rename from umn/source/security/index.rst rename to umn/source/access_control/index.rst index 43617e9..829a69e 100644 --- a/umn/source/security/index.rst +++ b/umn/source/access_control/index.rst @@ -2,8 +2,8 @@ .. _vpc_SecurityGroup_0000: -Security -======== +Access Control +============== - :ref:`Differences Between Security Groups and Firewalls ` - :ref:`Security Group ` diff --git a/umn/source/security/security_group/adding_a_security_group_rule.rst b/umn/source/access_control/security_group/adding_a_security_group_rule.rst similarity index 78% rename from umn/source/security/security_group/adding_a_security_group_rule.rst rename to umn/source/access_control/security_group/adding_a_security_group_rule.rst index f0a590f..f147107 100644 --- a/umn/source/security/security_group/adding_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/adding_a_security_group_rule.rst @@ -8,13 +8,13 @@ Adding a Security Group Rule Scenarios --------- -A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. A security group consists of inbound and outbound rules. +A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules. Like whitelists, security group rules work as follows: - Inbound rules control incoming traffic to instances in the security group. If an inbound request matches the source in an inbound security group rule with **Action** set to **Allow**, the request is allowed. - Unless otherwise specified, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. + By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. - Outbound rules control outgoing traffic from instances in the security group. If the destination of an outbound security group rule with **Action** set to **Allow** is 0.0.0.0/0, all outbound requests are allowed. @@ -27,8 +27,8 @@ If the rules of the security group associated with your instance cannot meet you Security Group Rule Configuration Examples ------------------------------------------ -- The system provides a default security group. For details about the default security group rules, see :ref:`Default Security Groups and Security Group Rules `. If the default security group rules cannot meet your requirements, you can modify them. -- Before configuring security group rules, you need to plan rules for communications among instances in the security group. For more security group rule configuration examples, see :ref:`Security Group Configuration Examples `. +- The system provides a default security group. For details about the default security group rules, see :ref:`Default Security Group `. If the default security group rules cannot meet your requirements, you can modify them. +- Before configuring security group rules, you need to plan access policies for instances in the security group. For details about common security group rule configuration examples, see :ref:`Security Group Configuration Examples `. Procedure --------- @@ -39,11 +39,13 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. -#. Locate the row that contains the target security group, click **Manage Rule** in the **Operation** column. +#. Locate the row that contains the target security group, and click **Manage Rule** in the **Operation** column. The page for configuring security group rules is displayed. @@ -68,9 +70,13 @@ Procedure +=======================+==========================================================================================================================================================================+=======================+ | Type | IPv4 | IPv4 | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Protocol & Port | **Protocol**: The network protocol. Currently, the value can be **All**, **TCP**, **UDP**, **ICMP**, **GRE**, or others. | TCP | + | Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP | + | | | | + | | Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | | **Port**: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535. | 22, or 22-30 | + | | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | 22, or 22-30 | + | | | | + | | Inbound rules control incoming traffic over specific ports to instances in the security group. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Source | Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example: | 0.0.0.0/0 | | | | | @@ -114,9 +120,13 @@ Procedure +=======================+=============================================================================================================================================================================+=======================+ | Type | IPv4 | IPv4 | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Protocol & Port | **Protocol**: The network protocol. Currently, the value can be **All**, **TCP**, **UDP**, **ICMP**, **GRE**, or others. | TCP | + | Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP | + | | | | + | | Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | | **Port**: The port or port range over which the traffic can leave your ECS. The value ranges from 1 to 65535. | 22, or 22-30 | + | | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | 22, or 22-30 | + | | | | + | | Outbound rules control outgoing traffic over specific ports from instances in the security group. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Destination | Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example: | 0.0.0.0/0 | | | | | @@ -138,4 +148,4 @@ Procedure The outbound rule list is displayed. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626734166.png diff --git a/umn/source/security/security_group/adding_instances_to_and_removing_them_from_a_security_group.rst b/umn/source/access_control/security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst similarity index 87% rename from umn/source/security/security_group/adding_instances_to_and_removing_them_from_a_security_group.rst rename to umn/source/access_control/security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst index 5516826..b8e1231 100644 --- a/umn/source/security/security_group/adding_instances_to_and_removing_them_from_a_security_group.rst +++ b/umn/source/access_control/security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst @@ -2,8 +2,8 @@ .. _SecurityGroup_0017: -Adding Instances to and Removing Them from a Security Group -=========================================================== +Adding an Instance to or Removing an Instance from a Security Group +=================================================================== Scenarios --------- @@ -16,24 +16,42 @@ Adding Instances to a Security Group ------------------------------------ #. Log in to the management console. + #. Click |image1| in the upper left corner and select the desired region and project. + #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. + #. On the **Security Groups** page, click **Manage Instance** in the **Operation** column. + #. On the **Servers** tab, click **Add** and add one or more servers to the current security group. + #. On the **Extension NICs** tab, click **Add** and add one or more extension NICs to the current security group. + #. Click **OK**. Removing Instances from a Security Group ---------------------------------------- #. Log in to the management console. + #. Click |image3| in the upper left corner and select the desired region and project. + #. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. + #. On the **Security Groups** page, click **Manage Instance** in the **Operation** column. + #. On the **Servers** tab, locate the target server and click **Remove** in the **Operation** column to remove the server from current security group. + #. On the **Extension NICs** tab, locate the target extension NIC and click **Remove** in the **Operation** column to remove the NIC from the current security group. + #. Click **Yes**. **Removing multiple instances from a security group** @@ -47,6 +65,6 @@ Follow-Up Operations You can delete the security groups that you no longer need. Deleting a security group will also delete all security group rules in the security group. For details, see :ref:`Deleting a Security Group `. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627054058.png .. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001500905066.png +.. |image4| image:: /_static/images/en-us_image_0000001626734162.png diff --git a/umn/source/security/security_group/changing_the_security_group_of_an_ecs.rst b/umn/source/access_control/security_group/changing_the_security_group_of_an_ecs.rst similarity index 100% rename from umn/source/security/security_group/changing_the_security_group_of_an_ecs.rst rename to umn/source/access_control/security_group/changing_the_security_group_of_an_ecs.rst diff --git a/umn/source/security/security_group/cloning_a_security_group.rst b/umn/source/access_control/security_group/cloning_a_security_group.rst similarity index 66% rename from umn/source/security/security_group/cloning_a_security_group.rst rename to umn/source/access_control/security_group/cloning_a_security_group.rst index 66695e7..8ee8853 100644 --- a/umn/source/security/security_group/cloning_a_security_group.rst +++ b/umn/source/access_control/security_group/cloning_a_security_group.rst @@ -14,6 +14,7 @@ You can clone a security group in the following scenarios: - For example, you have security group **sg-A** in region A. If ECSs in region B require the same security group rules as those configured for security group **sg-A**, you can clone security group **sg-A** to region B, freeing you from creating a new security group in region B. - If you need new security group rules, you can clone the original security group as a backup. +- Before you modify security group rules used by a service, you can clone the security group and modify the security group rules in the test environment to ensure that the modified rules work. .. note:: @@ -22,7 +23,12 @@ You can clone a security group in the following scenarios: Notes and Constraints --------------------- -If you clone security group across regions, the system will clone only rules whose source and destination are CIDR blocks or are in the current security group. +- You can clone a security group from the same or a different region. + + - If you want to clone a security group from the same region, you can clone all rules in the security group. + - If you want to clone a security group from a different region, the system will clone only rules whose source and destination are IP addresses and rules whose source and destination is the current security group. + +- Cloning a security group clones its security group rules, but not the instances associated with the security group. Procedure --------- @@ -33,6 +39,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. #. On the **Security Groups** page, locate the row that contains the target security group and choose **More** > **Clone** in the **Operation** column. @@ -48,4 +56,4 @@ Procedure #. Click **OK**. You can then switch to the required region to view the cloned security group in the security group list. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675373901.png diff --git a/umn/source/security/security_group/creating_a_security_group.rst b/umn/source/access_control/security_group/creating_a_security_group.rst similarity index 74% rename from umn/source/security/security_group/creating_a_security_group.rst rename to umn/source/access_control/security_group/creating_a_security_group.rst index 0669ea3..9cf64c3 100644 --- a/umn/source/security/security_group/creating_a_security_group.rst +++ b/umn/source/access_control/security_group/creating_a_security_group.rst @@ -8,12 +8,16 @@ Creating a Security Group Scenarios --------- -A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. A security group consists of inbound and outbound rules. +A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules. + +When creating instances that require security groups, you are advised to allocate instances with different Internet access requirements to different security groups. Notes and Constraints --------------------- -Each ECS must be associated with at least one security group. If you have no security group when creating an ECS, the system automatically creates a default security group (default) for the ECS. For details about the rules in the default security group, see :ref:`Default Security Groups and Security Group Rules `. +If you have not created any security group, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when you create it. + +The default security group name is **default**. For details, see :ref:`Default Security Group `. Procedure --------- @@ -24,6 +28,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. @@ -42,41 +48,41 @@ Procedure .. table:: **Table 1** Parameter description - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | Parameter | Description | Example Value | - +=======================+=======================================================================================================================================================================================================================================================+============================+ - | Name | Mandatory | sg-AB | - | | | | - | | Enter the security group name. | | - | | | | - | | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - | | | | - | | .. 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: | | - | | | | - | | - **Custom**: This template allows you to create security groups with custom security group rules. | | - | | - **General-purpose web server**: 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. | | - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | 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 >). | | - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | Parameter | Description | Example Value | + +=======================+=======================================================================================================================================================================================================================================================================+============================+ + | Name | Mandatory | sg-AB | + | | | | + | | Enter the security group name. | | + | | | | + | | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + | | | | + | | .. 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: | | + | | | | + | | - **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. | | + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | 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**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627054062.png diff --git a/umn/source/security/security_group/default_security_groups_and_security_group_rules.rst b/umn/source/access_control/security_group/default_security_group.rst similarity index 96% rename from umn/source/security/security_group/default_security_groups_and_security_group_rules.rst rename to umn/source/access_control/security_group/default_security_group.rst index 3d7394c..2c21b13 100644 --- a/umn/source/security/security_group/default_security_groups_and_security_group_rules.rst +++ b/umn/source/access_control/security_group/default_security_group.rst @@ -2,8 +2,8 @@ .. _SecurityGroup_0003: -Default Security Groups and Security Group Rules -================================================ +Default Security Group +====================== The system creates a default security group for each account. By default, the default security group rules: diff --git a/umn/source/security/security_group/deleting_a_security_group.rst b/umn/source/access_control/security_group/deleting_a_security_group.rst similarity index 73% rename from umn/source/security/security_group/deleting_a_security_group.rst rename to umn/source/access_control/security_group/deleting_a_security_group.rst index 34f080c..c288840 100644 --- a/umn/source/security/security_group/deleting_a_security_group.rst +++ b/umn/source/access_control/security_group/deleting_a_security_group.rst @@ -8,16 +8,14 @@ Deleting a Security Group Scenarios --------- -This section describes how to delete security groups. +If your security group is no longer required, you can delete it. Notes and Constraints --------------------- - The default security group is named **default** and cannot be deleted. -- A security group cannot be deleted if it is being used by instances, such as cloud servers, containers, and databases. - - If you need to delete such a security group, delete the instances or change the security group used by the instance first. +- If you want to delete a security group that is associated with instances, such as cloud servers, containers, and databases, you need to remove the instances from the security group first. For details, see :ref:`Adding an Instance to or Removing an Instance from a Security Group `. - A security group cannot be deleted if it is used as the source or destination of a rule in another security group. @@ -34,6 +32,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. @@ -45,4 +45,4 @@ Procedure #. Confirm the information and click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626574362.png diff --git a/umn/source/security/security_group/deleting_a_security_group_rule.rst b/umn/source/access_control/security_group/deleting_a_security_group_rule.rst similarity index 93% rename from umn/source/security/security_group/deleting_a_security_group_rule.rst rename to umn/source/access_control/security_group/deleting_a_security_group_rule.rst index c943cb5..c2bf3f7 100644 --- a/umn/source/security/security_group/deleting_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/deleting_a_security_group_rule.rst @@ -24,10 +24,17 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Access Control** > **Security Groups**. + 5. On the **Security Groups** page, click the security group name. + 6. If you do not need a security group rule, locate the row that contains the target rule, and click **Delete**. + 7. Click **Yes** in the displayed dialog box. **Deleting multiple security group rules at once** @@ -35,4 +42,4 @@ Procedure You can also select multiple security group rules and click **Delete** above the security group rule list to delete multiple rules at a time. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675413825.png diff --git a/umn/source/security/security_group/fast-adding_security_group_rules.rst b/umn/source/access_control/security_group/fast-adding_security_group_rules.rst similarity index 83% rename from umn/source/security/security_group/fast-adding_security_group_rules.rst rename to umn/source/access_control/security_group/fast-adding_security_group_rules.rst index 39b58ae..c6aba0f 100644 --- a/umn/source/security/security_group/fast-adding_security_group_rules.rst +++ b/umn/source/access_control/security_group/fast-adding_security_group_rules.rst @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. @@ -41,28 +43,28 @@ Procedure .. table:: **Table 1** Inbound rule parameter description - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Description | Example Value | - +=======================+==========================================================================================================================================================================+=======================+ - | Protocols and Ports | Common protocols and ports are provided for: | SSH (22) | - | | | | - | | - Remote login and ping | | - | | - Web services | | - | | - Databases | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Source | Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example: | 0.0.0.0/0 | - | | | | - | | - xxx.xxx.xxx.xxx/32 (IPv4 address) | | - | | - xxx.xxx.xxx.0/24 (IPv4 address range) | | - | | - 0.0.0.0/0 (all IPv4 addresses) | | - | | - sg-abc (security group) | | - | | | | - | | If the source is a security group, this rule will apply to all instances associated with the selected security group. | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Description | (Optional) Supplementary information about the security group rule. | ``-`` | - | | | | - | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Description | Example Value | + +=======================+==============================================================================================================================================================================+=======================+ + | Protocols and Ports | Common protocols and ports are provided for: | SSH (22) | + | | | | + | | - Remote login and ping | | + | | - Web services | | + | | - Databases | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Source | Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. You can specify: | 0.0.0.0/0 | + | | | | + | | - xxx.xxx.xxx.xxx/32 (IPv4 address) | | + | | - xxx.xxx.xxx.0/24 (IPv4 address range) | | + | | - 0.0.0.0/0 (all IPv4 addresses) | | + | | - sg-abc (security group) | | + | | | | + | | If the source is a security group, this rule will apply to all instances associated with the selected security group. | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | (Optional) Supplementary information about the security group rule. | ``-`` | + | | | | + | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ 8. Click **OK**. @@ -82,30 +84,30 @@ Procedure .. table:: **Table 2** Outbound rule parameter description - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Description | Example Value | - +=======================+=============================================================================================================================================================================+=======================+ - | Protocols and Ports | Common protocols and ports are provided for: | SSH (22) | - | | | | - | | - Remote login and ping | | - | | - Web services | | - | | - Databases | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Destination | Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example: | 0.0.0.0/0 | - | | | | - | | - xxx.xxx.xxx.xxx/32 (IPv4 address) | | - | | - xxx.xxx.xxx.0/24 (IPv4 address range) | | - | | - 0.0.0.0/0 (all IPv4 addresses) | | - | | - sg-abc (security group) | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Description | (Optional) Supplementary information about the security group rule. | ``-`` | - | | | | - | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Description | Example Value | + +=======================+=================================================================================================================================================================================+=======================+ + | Protocols and Ports | Common protocols and ports are provided for: | SSH (22) | + | | | | + | | - Remote login and ping | | + | | - Web services | | + | | - Databases | | + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Destination | Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. You can specify: | 0.0.0.0/0 | + | | | | + | | - xxx.xxx.xxx.xxx/32 (IPv4 address) | | + | | - xxx.xxx.xxx.0/24 (IPv4 address range) | | + | | - 0.0.0.0/0 (all IPv4 addresses) | | + | | - sg-abc (security group) | | + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | (Optional) Supplementary information about the security group rule. | ``-`` | + | | | | + | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ 11. Click **OK**. The outbound rule list is displayed and you can view your added rule. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675373905.png diff --git a/umn/source/security/security_group/importing_and_exporting_security_group_rules.rst b/umn/source/access_control/security_group/importing_and_exporting_security_group_rules.rst similarity index 78% rename from umn/source/security/security_group/importing_and_exporting_security_group_rules.rst rename to umn/source/access_control/security_group/importing_and_exporting_security_group_rules.rst index 9aec169..7ed7858 100644 --- a/umn/source/security/security_group/importing_and_exporting_security_group_rules.rst +++ b/umn/source/access_control/security_group/importing_and_exporting_security_group_rules.rst @@ -8,7 +8,9 @@ Importing and Exporting Security Group Rules Scenarios --------- -- If you want to quickly create or restore security group rules, you can import existing rules to the security group. +You can configure security group rules in an Excel file and import the rules to the security group. You can also export security group rules to an Excel file. You are advised to use this function in the following scenarios: + +- If you want to quickly create or restore a security group rule, you can import your exported security group rule file to the security group. - If you want to back up security group rules locally, you can export the rules to an Excel file. - If you want to quickly apply the rules of one security group to another, or if you want to modify multiple rules of the current security group at once, you can import or export existing rules. @@ -27,6 +29,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. @@ -55,9 +59,15 @@ Procedure | | - **Inbound**: Inbound rules control incoming traffic to instances in the security group. | | | | - **Outbound**: Outbound rules control outgoing traffic from instances in the security group. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ - | Protocol & Port | **Protocol**: The network protocol. Currently, the value can be **All**, **TCP**, **UDP**, **ICMP**, **GRE**, or others. | TCP | + | Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP | + | | | | + | | Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ - | | **Port**: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535. | 22, or 22-30 | + | | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | 22, or 22-30 | + | | | | + | | Inbound rules control incoming traffic over specific ports to instances in the security group. | | + | | | | + | | Outbound rules control outgoing traffic over specific ports from instances in the security group. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ | Source | Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example: | sg-test[96a8a93f-XXX-d7872990c314] | | | | | @@ -77,6 +87,6 @@ Procedure +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675254013.png .. |image3| image:: /_static/images/en-us_image_0142360062.png .. |image4| image:: /_static/images/en-us_image_0142360094.png diff --git a/umn/source/security/security_group/index.rst b/umn/source/access_control/security_group/index.rst similarity index 79% rename from umn/source/security/security_group/index.rst rename to umn/source/access_control/security_group/index.rst index 5a4b40c..3e3e3df 100644 --- a/umn/source/security/security_group/index.rst +++ b/umn/source/access_control/security_group/index.rst @@ -5,20 +5,20 @@ Security Group ============== -- :ref:`Security Group Overview ` -- :ref:`Default Security Groups and Security Group Rules ` +- :ref:`Security Groups and Security Group Rules ` +- :ref:`Default Security Group ` - :ref:`Security Group Configuration Examples ` - :ref:`Creating a Security Group ` -- :ref:`Adding a Security Group Rule ` -- :ref:`Fast-Adding Security Group Rules ` -- :ref:`Replicating a Security Group Rule ` -- :ref:`Modifying a Security Group Rule ` -- :ref:`Deleting a Security Group Rule ` -- :ref:`Importing and Exporting Security Group Rules ` -- :ref:`Deleting a Security Group ` -- :ref:`Adding Instances to and Removing Them from a Security Group ` - :ref:`Cloning a Security Group ` - :ref:`Modifying a Security Group ` +- :ref:`Deleting a Security Group ` +- :ref:`Adding a Security Group Rule ` +- :ref:`Fast-Adding Security Group Rules ` +- :ref:`Modifying a Security Group Rule ` +- :ref:`Replicating a Security Group Rule ` +- :ref:`Importing and Exporting Security Group Rules ` +- :ref:`Deleting a Security Group Rule ` +- :ref:`Adding an Instance to or Removing an Instance from a Security Group ` - :ref:`Viewing the Security Group of an ECS ` - :ref:`Changing the Security Group of an ECS ` @@ -26,19 +26,19 @@ Security Group :maxdepth: 1 :hidden: - security_group_overview - default_security_groups_and_security_group_rules + security_groups_and_security_group_rules + default_security_group security_group_configuration_examples creating_a_security_group - adding_a_security_group_rule - fast-adding_security_group_rules - replicating_a_security_group_rule - modifying_a_security_group_rule - deleting_a_security_group_rule - importing_and_exporting_security_group_rules - deleting_a_security_group - adding_instances_to_and_removing_them_from_a_security_group cloning_a_security_group modifying_a_security_group + deleting_a_security_group + adding_a_security_group_rule + fast-adding_security_group_rules + modifying_a_security_group_rule + replicating_a_security_group_rule + importing_and_exporting_security_group_rules + deleting_a_security_group_rule + adding_an_instance_to_or_removing_an_instance_from_a_security_group viewing_the_security_group_of_an_ecs changing_the_security_group_of_an_ecs diff --git a/umn/source/security/security_group/modifying_a_security_group.rst b/umn/source/access_control/security_group/modifying_a_security_group.rst similarity index 87% rename from umn/source/security/security_group/modifying_a_security_group.rst rename to umn/source/access_control/security_group/modifying_a_security_group.rst index 143b226..10d4e44 100644 --- a/umn/source/security/security_group/modifying_a_security_group.rst +++ b/umn/source/access_control/security_group/modifying_a_security_group.rst @@ -16,28 +16,46 @@ Procedure **Method 1** #. Log in to the management console. + #. Click |image1| in the upper left corner and select the desired region and project. + #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. + #. On the **Security Groups** page, locate the target security group and choose **More** > **Modify** in the **Operation** column. + #. Modify the name and description of the security group as required. + #. Click **OK**. **Method 2** #. Log in to the management console. + #. Click |image3| in the upper left corner and select the desired region and project. + #. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. + #. On the **Security Groups** page, click the security group name. + #. On the displayed page, click |image5| on the right of **Name** and edit the security group name. + #. Click **Y** to save the security group name. + #. Click |image6| on the right of **Description** and edit the security group description. + #. Click **Y** to save the security group description. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626894086.png .. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001500905066.png +.. |image4| image:: /_static/images/en-us_image_0000001675613933.png .. |image5| image:: /_static/images/en-us_image_0239476777.png .. |image6| image:: /_static/images/en-us_image_0239476777.png diff --git a/umn/source/security/security_group/modifying_a_security_group_rule.rst b/umn/source/access_control/security_group/modifying_a_security_group_rule.rst similarity index 88% rename from umn/source/security/security_group/modifying_a_security_group_rule.rst rename to umn/source/access_control/security_group/modifying_a_security_group_rule.rst index 7ecafef..78a8156 100644 --- a/umn/source/security/security_group/modifying_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/modifying_a_security_group_rule.rst @@ -14,12 +14,20 @@ Procedure --------- #. Log in to the management console. + #. Click |image1| in the upper left corner and select the desired region and project. + #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. + #. On the **Security Groups** page, click the security group name. + #. On the displayed page, locate the row that contains the security group rule to be modified, and click **Modify** in the **Operation** column. + #. Modify the rule and click **Confirm**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675613937.png diff --git a/umn/source/security/security_group/replicating_a_security_group_rule.rst b/umn/source/access_control/security_group/replicating_a_security_group_rule.rst similarity index 90% rename from umn/source/security/security_group/replicating_a_security_group_rule.rst rename to umn/source/access_control/security_group/replicating_a_security_group_rule.rst index 7dcc70d..baa8998 100644 --- a/umn/source/security/security_group/replicating_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/replicating_a_security_group_rule.rst @@ -19,6 +19,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. #. On the **Security Groups** page, click the security group name. @@ -30,4 +32,4 @@ Procedure #. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626894090.png diff --git a/umn/source/security/security_group/security_group_configuration_examples.rst b/umn/source/access_control/security_group/security_group_configuration_examples.rst similarity index 100% rename from umn/source/security/security_group/security_group_configuration_examples.rst rename to umn/source/access_control/security_group/security_group_configuration_examples.rst diff --git a/umn/source/access_control/security_group/security_groups_and_security_group_rules.rst b/umn/source/access_control/security_group/security_groups_and_security_group_rules.rst new file mode 100644 index 0000000..a0ea7af --- /dev/null +++ b/umn/source/access_control/security_group/security_groups_and_security_group_rules.rst @@ -0,0 +1,107 @@ +:original_name: en-us_topic_0073379079.html + +.. _en-us_topic_0073379079: + +Security Groups and Security Group Rules +======================================== + +Security Groups +--------------- + +A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection requirements and that are mutually trusted. After a security group is created, you can create various access rules for the security group, these rules will apply to all cloud resources added to this security group. + +If you have not created any security group, the system automatically creates a default security group for you and associates it with the instance (such as an ECS) when you create it. For details about the default security group, see :ref:`Default Security Group `. + +Security groups are stateful. If you send a request from your instance and the outbound traffic is allowed, the response traffic for that request is allowed to flow in regardless of inbound security group rules. Similarly, if inbound traffic is allowed, responses to allowed inbound traffic are allowed to flow out, regardless of outbound rules. + +Security groups use connection tracking to track traffic to and from instances that they contain and security group rules are applied based on the connection status of the traffic to determine whether to allow or deny traffic. + +- If you add, modify, or delete a security group rule, or add or remove an instance to or from a security group, the inbound connection tracking of all instances in the security group will be automatically cleared. The inbound or outbound traffic of the instance will be considered as new connections, which need to match the inbound or outbound security group rules to ensure that the rules take effect immediately and the security of incoming traffic. + +- If there is no inbound or outbound traffic of an instance for a long time, the traffic will be considered as new connections after the connection tracking times out, and the connections need to match the outbound and inbound rules. The timeout period of connection tracking varies according to the protocol. The timeout period of a TCP connection in the established state is 600s, and the timeout period of an ICMP connection is 30s. For other protocols, if packets are received in both inbound and outbound directions, the connection tracking timeout period is 180s. If packets are received only in one direction, the connection tracking timeout period is 30s. For protocols other than TCP, UDP, and ICMP, only the IP address and protocol number are tracked. + +Security Group Rules +-------------------- + +A security group has inbound and outbound rules to control traffic that's allowed to reach or leave the instances associated with the security group. You can specify protocol, port, source/destination for a security group rule. :ref:`Table 1 ` describes key information about a security group rule. + +.. _en-us_topic_0073379079__table1919155115499: + +.. table:: **Table 1** Security group rule information + + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Parameter | Description | + +===================================+=========================================================================================================================================================================================================================================================================================================================================================================================+ + | Protocol | The network protocol used to match traffic in a security group rule. Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Port | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | + | | | + | | - Inbound rules control incoming traffic over specific ports to instances in the security group. | + | | - Outbound rules control outgoing traffic over specific ports from instances in the security group. | + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Source (Inbound) | The source in an inbound rule is used to match the IP address or address range of an external request. The source can be: | + | | | + | | - IP address: | + | | | + | | - Example IPv4 address: 192.168.10.10/32 | + | | - Example IPv4 address range: 192.168.52.0/24 All IPv4 addresses: 0.0.0.0/0 | + | | | + | | - Security group: You can select another security group in the same region under the current account as the source. For example, instance A is in security group A and instance B is in security group B. If security group A has an inbound rule with **Action** set to **Allow** and **Source** set to security group B, access from instance B is allowed to instance A. | + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Destination (Outbound) | The destination in an outbound rule is used to match the IP address or address range of an internal request. The destination can be: | + | | | + | | - IP address: | + | | | + | | - Example IPv4 address: 192.168.10.10/32 | + | | - Example IPv4 address range: 192.168.52.0/24 All IPv4 addresses: 0.0.0.0/0 | + | | | + | | - Security group: You can select another security group in the same region under the current account as the destination. For example, instance A is in security group A and instance B is in security group B. If security group A has an outbound rule with **Action** set to **Allow** and **Destination** set to security group B, access from instance A is allowed to instance B. | + +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +Like whitelists, security group rules work as follows: + +- Inbound rules control incoming traffic to instances in the security group. If an inbound request matches the source in an inbound security group rule with **Action** set to **Allow**, the request is allowed. + + By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. + +- Outbound rules control outgoing traffic from instances in the security group. If the destination of an outbound security group rule with **Action** set to **Allow** is 0.0.0.0/0, all outbound requests are allowed. + + 0.0.0.0/0 represents all IPv4 addresses. + + ::/0 represents all IPv6 addresses. + +:ref:`Table 2 ` shows the inbound and outbound rules in security group sg-AB. + +.. _en-us_topic_0073379079__table102261597217: + +.. table:: **Table 2** Rules in security group sg-AB + + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Direction | Type | Protocol & Port | Source/Destination | Description | + +===========+======+=================+========================+======================================================================================================================================+ + | Inbound | IPv4 | All | Source: sg-AB | This rule allows ECSs in the security group to communicate with each other. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Inbound | IPv4 | TCP: 22 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over SSH port 22 for remotely logging in to Linux ECSs. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Inbound | IPv4 | TCP: 3389 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over RDP port 3389 for remotely logging in to Windows ECSs. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Inbound | IPv4 | TCP: 80 | Source: 10.5.6.30/32 | This rule allows IP address 10.5.6.30 to access ECSs in the security group over port 80. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Outbound | IPv4 | All | Destination: 0.0.0.0/0 | This rule allows access from ECSs in the security group to any IPv4 address over any port. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + +.. important:: + + - After a port is enabled in a security group rule, ensure that the port in the instance is also enabled to ensure normal network communication. + - Generally, instances in the same security group can communicate with each other by default. If instances in the same security group cannot communicate with each other, the possible causes are as follows: + + - The inbound rule for communication between instances in the same security group is deleted. + + - Different VPCs cannot communicate with each other. The instances belong to the same security group but different VPCs. + + You can use :ref:`VPC peering connections ` to connect VPCs in different regions. + +Security Group Constraints +-------------------------- + +- By default, you can add up to 50 security group rules to a security group. diff --git a/umn/source/security/security_group/viewing_the_security_group_of_an_ecs.rst b/umn/source/access_control/security_group/viewing_the_security_group_of_an_ecs.rst similarity index 80% rename from umn/source/security/security_group/viewing_the_security_group_of_an_ecs.rst rename to umn/source/access_control/security_group/viewing_the_security_group_of_an_ecs.rst index 0cc3518..2abb587 100644 --- a/umn/source/security/security_group/viewing_the_security_group_of_an_ecs.rst +++ b/umn/source/access_control/security_group/viewing_the_security_group_of_an_ecs.rst @@ -17,7 +17,7 @@ Procedure #. Click |image1| in the upper left corner and select the desired region and project. -#. Under **Computing**, click **Elastic Cloud Server**. +#. In the upper left corner of the page, click |image2|. In the service list, choose **Computing** > **Elastic Cloud Server**. The ECS list is displayed. @@ -30,3 +30,4 @@ Procedure You can view the security groups associated with the ECS and the inbound and outbound rules. .. |image1| image:: /_static/images/en-us_image_0141273034.png +.. |image2| image:: /_static/images/en-us_image_0000001675413821.png diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index f3c28de..2ca19d8 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -8,11 +8,23 @@ Change History +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Released On | Description | +===================================+====================================================================================================================================================================================================================================================================================================================================+ +| 2023-09-08 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | - Optimized description in :ref:`Step 4: Add a Security Group Rule `. | +| | - Optimized description in :ref:`Creating a Security Group `. | +| | - Optimized the procedure for verifying IAM permissions in :ref:`Creating a User and Granting VPC Permissions `. | ++-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2023-07-18 | This release incorporates the following changes: | | | | | | Updated the following content: | | | | | | Added description about enabling shared SNAT using an API in :ref:`Shared SNAT `. | +| | | +| | Security group | +| | | +| | Firewall | +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2023-06-12 | This release incorporates the following changes: | | | | @@ -43,7 +55,7 @@ Change History | | 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) `. | +| | - Added the step for viewing NIC details to :ref:`Disabling Source/Destination Check for an ECS NIC `. | +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2023-02-15 | This release incorporates the following changes: | | | | @@ -122,7 +134,7 @@ Change History +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2020-05-30 | Added the following content: | | | | -| | Added basic information to :ref:`Security Group Overview ` and :ref:`Firewall Overview `. | +| | Added basic information to :ref:`Security Groups and Security Group Rules ` and :ref:`Firewall Overview `. | | | | | | Modified the following content: | | | | @@ -156,7 +168,7 @@ Change History | | - Optimized figure examples in this document. | | | - Optimized descriptions in :ref:`Firewall Configuration Examples `. | | | - Optimized descriptions in :ref:`Firewall Overview `. | -| | - Changed the position of :ref:`Security `. | +| | - Changed the position of :ref:`Access Control `. | | | - Optimized :ref:`What Is a Quota? ` | | | | | | Deleted the following content: | @@ -174,7 +186,7 @@ Change History +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 2019-12-13 | Added the following content: | | | | -| | - Added restrictions on ports and port ranges in :ref:`Security Group Overview `. | +| | - Added restrictions on ports and port ranges in :ref:`Security Groups and Security Group Rules `. | | | - Added description about IP address groups in :ref:`Importing and Exporting Security Group Rules `. | | | - Added impacts caused by IP address group modification or deletion in "Managing an IP Address Group". | | | | @@ -189,7 +201,7 @@ Change History | | - Optimized figure examples in this document. | | | - Optimized descriptions in :ref:`Firewall Configuration Examples `. | | | - Optimized descriptions in :ref:`Firewall Overview `. | -| | - Changed the position of :ref:`Security `. | +| | - Changed the position of :ref:`Access Control `. | | | | | | Deleted the following content: | | | | 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 03c4ace..6f403cf 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 @@ -22,7 +22,7 @@ Notes and Constraints - 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. +- Only EIPs with no instance bound can be released. If you want to release an EIP with an instance bound, you need to unbind EIP from the instance first. Procedure --------- diff --git a/umn/source/faq/bandwidth/how_do_i_buy_a_shared_bandwidth.rst b/umn/source/faq/bandwidth/how_do_i_buy_a_shared_bandwidth.rst deleted file mode 100644 index 974d645..0000000 --- a/umn/source/faq/bandwidth/how_do_i_buy_a_shared_bandwidth.rst +++ /dev/null @@ -1,15 +0,0 @@ -:original_name: vpc_faq_0035.html - -.. _vpc_faq_0035: - -How Do I Buy a Shared Bandwidth? -================================ - -#. Log in to the management console. -#. Click |image1| in the upper left corner and select the desired region and project. -#. Click |image2| in the upper left corner and choose **Network** > **Elastic IP**. -#. In the navigation pane on the left, choose **Shared Bandwidths**. -#. In the upper right corner, click **Assign Shared Bandwidth**. On the displayed page, configure parameters as prompted to assign a shared bandwidth. - -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png diff --git a/umn/source/faq/bandwidth/index.rst b/umn/source/faq/bandwidth/index.rst index 09f2fb0..b35debe 100644 --- a/umn/source/faq/bandwidth/index.rst +++ b/umn/source/faq/bandwidth/index.rst @@ -8,7 +8,6 @@ Bandwidth - :ref:`What Is the Bandwidth Size Range? ` - :ref:`What Bandwidth Types Are Available? ` - :ref:`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? ` -- :ref:`How Do I Buy a Shared Bandwidth? ` .. toctree:: :maxdepth: 1 @@ -17,4 +16,3 @@ Bandwidth what_is_the_bandwidth_size_range what_bandwidth_types_are_available what_are_the_differences_between_a_dedicated_bandwidth_and_a_shared_bandwidth_can_a_dedicated_bandwidth_be_changed_to_a_shared_bandwidth_or_the_other_way_around - how_do_i_buy_a_shared_bandwidth diff --git a/umn/source/faq/security/how_many_firewalls_can_i_create.rst b/umn/source/faq/security/how_many_firewalls_can_i_create.rst deleted file mode 100644 index ab1055c..0000000 --- a/umn/source/faq/security/how_many_firewalls_can_i_create.rst +++ /dev/null @@ -1,8 +0,0 @@ -:original_name: vpc_faq_0072.html - -.. _vpc_faq_0072: - -How Many Firewalls Can I Create? -================================ - -You can create up to 200 firewalls. It is recommended that you configure no more than 20 inbound or outbound rules for each firewall. If you configure more than 20 inbound or outbound rules for a firewall, forwarding performance will deteriorate. diff --git a/umn/source/faq/security/how_many_security_groups_can_i_create.rst b/umn/source/faq/security/how_many_security_groups_can_i_create.rst deleted file mode 100644 index b84715f..0000000 --- a/umn/source/faq/security/how_many_security_groups_can_i_create.rst +++ /dev/null @@ -1,10 +0,0 @@ -:original_name: vpc_faq_0040.html - -.. _vpc_faq_0040: - -How Many Security Groups Can I Create? -====================================== - -Each account can have up to 100 security groups and 5000 security group rules. - -When you create an ECS, you can select multiple security groups, but it is recommended that you select no more than five. diff --git a/umn/source/faq/security/index.rst b/umn/source/faq/security/index.rst index 787188c..7aaef8a 100644 --- a/umn/source/faq/security/index.rst +++ b/umn/source/faq/security/index.rst @@ -5,10 +5,9 @@ Security ======== +- :ref:`Why Can't I Delete a Security Group? ` - :ref:`Can I Change the Security Group of an ECS? ` -- :ref:`How Many Security Groups Can I Create? ` - :ref:`How Do I Configure a Security Group for Multi-Channel Protocols? ` -- :ref:`How Many Firewalls Can I Create? ` - :ref:`Does a Security Group Rule or a Firewall Rule Immediately Take Effect for Existing Connections After It Is Modified? ` - :ref:`Which Security Group Rule Has Priority When Multiple Security Group Rules Conflict? ` @@ -16,9 +15,8 @@ Security :maxdepth: 1 :hidden: + why_cant_i_delete_a_security_group can_i_change_the_security_group_of_an_ecs - how_many_security_groups_can_i_create how_do_i_configure_a_security_group_for_multi-channel_protocols - how_many_firewalls_can_i_create does_a_security_group_rule_or_a_firewall_rule_immediately_take_effect_for_existing_connections_after_it_is_modified which_security_group_rule_has_priority_when_multiple_security_group_rules_conflict diff --git a/umn/source/faq/security/why_cant_i_delete_a_security_group.rst b/umn/source/faq/security/why_cant_i_delete_a_security_group.rst new file mode 100644 index 0000000..0682f0b --- /dev/null +++ b/umn/source/faq/security/why_cant_i_delete_a_security_group.rst @@ -0,0 +1,16 @@ +:original_name: faq_security_0003.html + +.. _faq_security_0003: + +Why Can't I Delete a Security Group? +==================================== + +- The default security group is named **default** and cannot be deleted. + +- If you want to delete a security group that is associated with instances, such as cloud servers, containers, and databases, you need to remove the instances from the security group first. + +- A security group cannot be deleted if it is used as the source or destination of a rule in another security group. + + You need to delete or modify the rule first and delete the security group. + + For example, if the source of a rule in security group **sg-B** is set to **sg-A**, you need to delete or modify the rule in **sg-B** before deleting **sg-A**. diff --git a/umn/source/faq/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst b/umn/source/faq/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst index 38e7aeb..6d684da 100644 --- a/umn/source/faq/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst +++ b/umn/source/faq/vpcs_and_subnets/can_subnets_communicate_with_each_other.rst @@ -5,7 +5,8 @@ Can Subnets Communicate with Each Other? ======================================== -Subnets in the same VPC can communicate with each other, but subnets in different VPCs cannot communicate with each other by default. However, you can create VPC peering connections to enable subnets in different VPCs to communicate with each other. +- Subnets in the same VPC can communicate with each other by default. +- VPCs are isolated from each other. Subnets from different VPCs cannot communicate with each other. You can use a VPC peering connection to enable communication between VPCs in the same region. .. note:: diff --git a/umn/source/faq/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst b/umn/source/faq/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst index 115d849..067d789 100644 --- a/umn/source/faq/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst +++ b/umn/source/faq/vpcs_and_subnets/what_subnet_cidr_blocks_are_available.rst @@ -5,4 +5,6 @@ What Subnet CIDR Blocks Are Available? ====================================== -A subnet CIDR block must be included in its VPC CIDR block. Supported VPC CIDR blocks are **10.0.0.0/8-24**, **172.16.0.0/12-24**, and **192.168.0.0/16-24**. The allowed block size of a subnet is between the netmask of its VPC CIDR block and the /29 netmask. +A subnet is an IP address range from a VPC. The VPC service supports CIDR blocks 10.0.0.0/8-24, 172.16.0.0/12-24, and 192.168.0.0/16-24. + +Subnets must reside within your VPC, and the subnet masks used to define them can be between the netmask of its VPC CIDR block and /29 netmask. diff --git a/umn/source/faq/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 index 4d32cd9..97a7da5 100644 --- a/umn/source/faq/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 @@ -26,7 +26,7 @@ You can refer to :ref:`Table 1 ` to delete sub +=================================================================================================+============================================================================+============================================================================================================================================================+ | You do not have permission to perform this operation. | Your account does not have permissions to delete subnets. | Contact the account administrator to grant permissions to your account and then delete the subnet. | +-------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Delete custom routes from the associated route table of the subnet and then delete the subnet. | The route table has custom routes with the following as the next hop type: | Delete the custom route from the route table and then delete the subnet. | + | Delete custom routes from the associated route table of the subnet and then delete the subnet. | The route table has custom routes with the following as the next hop type: | Delete the custom routes from the route table and then delete the subnet. | | | | | | | - Server | #. :ref:`Viewing the Route Table Associated with a Subnet ` | | | - Extension NIC | #. :ref:`Deleting a Route ` | @@ -37,7 +37,7 @@ You can refer to :ref:`Table 1 ` to delete sub | | | | | | | :ref:`Releasing a Virtual IP Address ` | +-------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Release any private IP addresses configured in the subnet and then delete the subnet. | The subnet has virtual IP addresses that are not used by any instance. | On the **IP Addresses** tab, view and release these private IP addresses and then delete the subnet. | + | Release any private IP addresses configured in the subnet and then delete the subnet. | The subnet has virtual IP addresses that are not used by any instance. | On the **IP Addresses** tab, release these private IP addresses that are not required and then delete the subnet. | | | | | | | | #. :ref:`Viewing IP Addresses in a Subnet ` | | | | #. In the private IP address list, locate the IP address that is not being used and click **Release** in the **Operation** column. | diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/index.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/index.rst index df485a1..4efe30f 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/index.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/index.rst @@ -11,6 +11,8 @@ Configuring a VPC for ECSs That Access the Internet Using EIPs #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. Click **Create VPC**. #. On the **Create VPC** page, set parameters as prompted. @@ -19,63 +21,63 @@ Configuring a VPC for ECSs That Access the Internet Using EIPs .. table:: **Table 1** VPC parameter descriptions - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Category | Parameter | Description | Example Value | - +=====================================+========================+=========================================================================================================================================================================================================================================================================================================+=====================+ - | Basic Information | Region | Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. | eu-de | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Name | The VPC name. | VPC-001 | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | - | | | | | - | | | The following CIDR blocks are supported: | | - | | | | | - | | | 10.0.0.0/8-24 | | - | | | | | - | | | 172.16.0.0/12-24 | | - | | | | | - | | | 192.168.0.0/16-24 | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | - | | | | | - | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | - | | | | - Value: vpc-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | - | | | | | - | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Name | The subnet name. | Subnet | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | - | | | | | - | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added. | | - | | | | | - | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | - | | | | - Value: subnet-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | - | | | | | - | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Category | Parameter | Description | Example Value | + +=====================================+========================+=============================================================================================================================================================================================================================================================+=====================+ + | Basic Information | Region | Select the region nearest to you to ensure the lowest latency possible. | eu-de | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Name | The VPC name. | VPC-001 | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | + | | | | | + | | | The following CIDR blocks are supported: | | + | | | | | + | | | 10.0.0.0/8-24 | | + | | | | | + | | | 172.16.0.0/12-24 | | + | | | | | + | | | 192.168.0.0/16-24 | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | + | | | | | + | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | + | | | | - Value: vpc-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | + | | | | | + | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Name | The subnet name. | Subnet | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | + | | | | | + | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | + | | | | | + | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | + | | | | - Value: subnet-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | + | | | | | + | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ .. _en-us_topic_0017816228__en-us_topic_0013935842_table248245914136: diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_1_create_a_vpc.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_1_create_a_vpc.rst index 9775e81..e2cda31 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_1_create_a_vpc.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_1_create_a_vpc.rst @@ -21,6 +21,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. Click **Create VPC**. #. On the **Create VPC** page, set parameters as prompted. @@ -29,63 +31,63 @@ Procedure .. table:: **Table 1** VPC parameter descriptions - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Category | Parameter | Description | Example Value | - +=====================================+========================+=========================================================================================================================================================================================================================================================================================================+=====================+ - | Basic Information | Region | Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. | eu-de | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Name | The VPC name. | VPC-001 | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | - | | | | | - | | | The following CIDR blocks are supported: | | - | | | | | - | | | 10.0.0.0/8-24 | | - | | | | | - | | | 172.16.0.0/12-24 | | - | | | | | - | | | 192.168.0.0/16-24 | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | - | | | | | - | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | - | | | | - Value: vpc-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | - | | | | | - | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Name | The subnet name. | Subnet | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | - | | | | | - | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added. | | - | | | | | - | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | - | | | | - Value: subnet-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | - | | | | | - | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Category | Parameter | Description | Example Value | + +=====================================+========================+=============================================================================================================================================================================================================================================================+=====================+ + | Basic Information | Region | Select the region nearest to you to ensure the lowest latency possible. | eu-de | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Name | The VPC name. | VPC-001 | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | + | | | | | + | | | The following CIDR blocks are supported: | | + | | | | | + | | | 10.0.0.0/8-24 | | + | | | | | + | | | 172.16.0.0/12-24 | | + | | | | | + | | | 192.168.0.0/16-24 | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | + | | | | | + | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | + | | | | - Value: vpc-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | + | | | | | + | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Name | The subnet name. | Subnet | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | + | | | | | + | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | + | | | | | + | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | + | | | | - Value: subnet-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | + | | | | | + | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ .. _vpc_qs_0009__en-us_topic_0013935842_table248245914136: diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_2_create_a_subnet_for_the_vpc.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_2_create_a_subnet_for_the_vpc.rst index 8df7335..da22c06 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_2_create_a_subnet_for_the_vpc.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_2_create_a_subnet_for_the_vpc.rst @@ -21,6 +21,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. 5. Click **Create Subnet**. @@ -37,37 +39,37 @@ Procedure .. table:: **Table 1** Parameter descriptions - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Description | Example Value | - +======================================+=============================================================================================================================================================================================================================================+=======================+ - | VPC | The VPC for which you want to create a subnet. | ``-`` | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Name | The subnet name. | Subnet | - | | | | - | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Gateway | The gateway address of the subnet. | 192.168.0.1 | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/DNS Server Address | By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | - | | | | - | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added. | | - | | | | - | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | - | | | - Value: subnet-01 | - | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Description | Supplementary information about the subnet. This parameter is optional. | ``-`` | - | | | | - | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Description | Example Value | + +======================================+=============================================================================================================================================================================================================================================================+=======================+ + | VPC | The VPC for which you want to create a subnet. | ``-`` | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Name | The subnet name. | Subnet | + | | | | + | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Gateway | The gateway address of the subnet. | 192.168.0.1 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/DNS Server Address | By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | + | | | | + | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | + | | | | + | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | + | | | - Value: subnet-01 | + | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Description | Supplementary information about the subnet. This parameter is optional. | ``-`` | + | | | | + | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ .. _vpc_qs_0010__en-us_topic_0013748726_table42131827173915: @@ -111,4 +113,4 @@ When a subnet is created, there are five reserved IP addresses, which cannot be If you configured the default settings under **Advanced Settings** during subnet creation, the reserved IP addresses may be different from the default ones, but there will still be five of them. The specific addresses depend on your subnet settings. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675254021.png diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_4_create_a_security_group.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_4_create_a_security_group.rst index c97b24b..d69e08c 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_4_create_a_security_group.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_4_create_a_security_group.rst @@ -8,7 +8,9 @@ Step 4: Create a Security Group Scenarios --------- -A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. A security group consists of inbound and outbound rules. +A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules. + +When creating instances that require security groups, you are advised to allocate instances with different Internet access requirements to different security groups. Procedure --------- @@ -19,6 +21,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. @@ -37,41 +41,41 @@ Procedure .. table:: **Table 1** Parameter description - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | Parameter | Description | Example Value | - +=======================+=======================================================================================================================================================================================================================================================+============================+ - | Name | Mandatory | sg-AB | - | | | | - | | Enter the security group name. | | - | | | | - | | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - | | | | - | | .. 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: | | - | | | | - | | - **Custom**: This template allows you to create security groups with custom security group rules. | | - | | - **General-purpose web server**: 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. | | - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | 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 >). | | - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | Parameter | Description | Example Value | + +=======================+=======================================================================================================================================================================================================================================================================+============================+ + | Name | Mandatory | sg-AB | + | | | | + | | Enter the security group name. | | + | | | | + | | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + | | | | + | | .. 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: | | + | | | | + | | - **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. | | + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | 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**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627054062.png diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_5_add_a_security_group_rule.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_5_add_a_security_group_rule.rst index d79429a..56e7a12 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_5_add_a_security_group_rule.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_5_add_a_security_group_rule.rst @@ -8,13 +8,13 @@ Step 5: Add a Security Group Rule Scenarios --------- -A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. A security group consists of inbound and outbound rules. +A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules. Like whitelists, security group rules work as follows: - Inbound rules control incoming traffic to instances in the security group. If an inbound request matches the source in an inbound security group rule with **Action** set to **Allow**, the request is allowed. - Unless otherwise specified, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. + By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. - Outbound rules control outgoing traffic from instances in the security group. If the destination of an outbound security group rule with **Action** set to **Allow** is 0.0.0.0/0, all outbound requests are allowed. @@ -33,11 +33,13 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. -#. Locate the row that contains the target security group, click **Manage Rule** in the **Operation** column. +#. Locate the row that contains the target security group, and click **Manage Rule** in the **Operation** column. The page for configuring security group rules is displayed. @@ -62,9 +64,13 @@ Procedure +=======================+==========================================================================================================================================================================+=======================+ | Type | IPv4 | IPv4 | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Protocol & Port | **Protocol**: The network protocol. Currently, the value can be **All**, **TCP**, **UDP**, **ICMP**, **GRE**, or others. | TCP | + | Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP | + | | | | + | | Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | | **Port**: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535. | 22, or 22-30 | + | | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | 22, or 22-30 | + | | | | + | | Inbound rules control incoming traffic over specific ports to instances in the security group. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Source | Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example: | 0.0.0.0/0 | | | | | @@ -108,9 +114,13 @@ Procedure +=======================+=============================================================================================================================================================================+=======================+ | Type | IPv4 | IPv4 | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Protocol & Port | **Protocol**: The network protocol. Currently, the value can be **All**, **TCP**, **UDP**, **ICMP**, **GRE**, or others. | TCP | + | Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP | + | | | | + | | Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | | **Port**: The port or port range over which the traffic can leave your ECS. The value ranges from 1 to 65535. | 22, or 22-30 | + | | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | 22, or 22-30 | + | | | | + | | Outbound rules control outgoing traffic over specific ports from instances in the security group. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Destination | Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example: | 0.0.0.0/0 | | | | | @@ -132,4 +142,4 @@ Procedure The outbound rule list is displayed. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626734166.png diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_1_create_a_vpc.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_1_create_a_vpc.rst index bf2ed7f..c0f7f98 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_1_create_a_vpc.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_1_create_a_vpc.rst @@ -21,6 +21,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. Click **Create VPC**. #. On the **Create VPC** page, set parameters as prompted. @@ -29,63 +31,63 @@ Procedure .. table:: **Table 1** VPC parameter descriptions - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Category | Parameter | Description | Example Value | - +=====================================+========================+=========================================================================================================================================================================================================================================================================================================+=====================+ - | Basic Information | Region | Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. | eu-de | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Name | The VPC name. | VPC-001 | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | - | | | | | - | | | The following CIDR blocks are supported: | | - | | | | | - | | | 10.0.0.0/8-24 | | - | | | | | - | | | 172.16.0.0/12-24 | | - | | | | | - | | | 192.168.0.0/16-24 | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | - | | | | | - | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | - | | | | - Value: vpc-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | - | | | | | - | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Name | The subnet name. | Subnet | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | - | | | | | - | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added. | | - | | | | | - | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | - | | | | - Value: subnet-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | - | | | | | - | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Category | Parameter | Description | Example Value | + +=====================================+========================+=============================================================================================================================================================================================================================================================+=====================+ + | Basic Information | Region | Select the region nearest to you to ensure the lowest latency possible. | eu-de | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Name | The VPC name. | VPC-001 | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | + | | | | | + | | | The following CIDR blocks are supported: | | + | | | | | + | | | 10.0.0.0/8-24 | | + | | | | | + | | | 172.16.0.0/12-24 | | + | | | | | + | | | 192.168.0.0/16-24 | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | + | | | | | + | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | + | | | | - Value: vpc-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | + | | | | | + | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Name | The subnet name. | Subnet | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | + | | | | | + | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | + | | | | | + | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | + | | | | - Value: subnet-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | + | | | | | + | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ .. _vpc_qs_0005__en-us_topic_0013935842_table248245914136: diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_2_create_a_subnet_for_the_vpc.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_2_create_a_subnet_for_the_vpc.rst index 2ae8aa7..686be34 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_2_create_a_subnet_for_the_vpc.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_2_create_a_subnet_for_the_vpc.rst @@ -21,6 +21,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. 5. Click **Create Subnet**. @@ -37,37 +39,37 @@ Procedure .. table:: **Table 1** Parameter descriptions - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Description | Example Value | - +======================================+=============================================================================================================================================================================================================================================+=======================+ - | VPC | The VPC for which you want to create a subnet. | ``-`` | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Name | The subnet name. | Subnet | - | | | | - | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Gateway | The gateway address of the subnet. | 192.168.0.1 | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/DNS Server Address | By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | - | | | | - | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added. | | - | | | | - | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | - | | | - Value: subnet-01 | - | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Description | Supplementary information about the subnet. This parameter is optional. | ``-`` | - | | | | - | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Description | Example Value | + +======================================+=============================================================================================================================================================================================================================================================+=======================+ + | VPC | The VPC for which you want to create a subnet. | ``-`` | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Name | The subnet name. | Subnet | + | | | | + | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Gateway | The gateway address of the subnet. | 192.168.0.1 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/DNS Server Address | By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | + | | | | + | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | + | | | | + | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | + | | | - Value: subnet-01 | + | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Description | Supplementary information about the subnet. This parameter is optional. | ``-`` | + | | | | + | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ .. _vpc_qs_0006__en-us_topic_0013748726_table42131827173915: @@ -111,4 +113,4 @@ When a subnet is created, there are five reserved IP addresses, which cannot be If you configured the default settings under **Advanced Settings** during subnet creation, the reserved IP addresses may be different from the default ones, but there will still be five of them. The specific addresses depend on your subnet settings. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675254021.png diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_3_create_a_security_group.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_3_create_a_security_group.rst index 8c6933f..8f4b0f2 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_3_create_a_security_group.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_3_create_a_security_group.rst @@ -8,7 +8,9 @@ Step 3: Create a Security Group Scenarios --------- -A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. A security group consists of inbound and outbound rules. +A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules. + +When creating instances that require security groups, you are advised to allocate instances with different Internet access requirements to different security groups. Procedure --------- @@ -19,6 +21,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. @@ -37,41 +41,41 @@ Procedure .. table:: **Table 1** Parameter description - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | Parameter | Description | Example Value | - +=======================+=======================================================================================================================================================================================================================================================+============================+ - | Name | Mandatory | sg-AB | - | | | | - | | Enter the security group name. | | - | | | | - | | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - | | | | - | | .. 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: | | - | | | | - | | - **Custom**: This template allows you to create security groups with custom security group rules. | | - | | - **General-purpose web server**: 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. | | - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | 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 >). | | - +-----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | Parameter | Description | Example Value | + +=======================+=======================================================================================================================================================================================================================================================================+============================+ + | Name | Mandatory | sg-AB | + | | | | + | | Enter the security group name. | | + | | | | + | | The security group name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + | | | | + | | .. 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: | | + | | | | + | | - **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. | | + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | 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**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627054062.png diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_4_add_a_security_group_rule.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_4_add_a_security_group_rule.rst index 6ea873d..b2951b9 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_4_add_a_security_group_rule.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/step_4_add_a_security_group_rule.rst @@ -8,13 +8,13 @@ Step 4: Add a Security Group Rule Scenarios --------- -A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. A security group consists of inbound and outbound rules. +A security group is a collection of access control rules to control the traffic that is allowed to reach and leave the cloud resources that it is associated with. The cloud resources can be cloud servers, containers, databases, and more. Cloud resources associated with the same security group have the same security requirements and are mutually trusted within a VPC. A security group consists of inbound and outbound rules. Like whitelists, security group rules work as follows: - Inbound rules control incoming traffic to instances in the security group. If an inbound request matches the source in an inbound security group rule with **Action** set to **Allow**, the request is allowed. - Unless otherwise specified, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. + By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. - Outbound rules control outgoing traffic from instances in the security group. If the destination of an outbound security group rule with **Action** set to **Allow** is 0.0.0.0/0, all outbound requests are allowed. @@ -33,11 +33,13 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Access Control** > **Security Groups**. The security group list is displayed. -#. Locate the row that contains the target security group, click **Manage Rule** in the **Operation** column. +#. Locate the row that contains the target security group, and click **Manage Rule** in the **Operation** column. The page for configuring security group rules is displayed. @@ -62,9 +64,13 @@ Procedure +=======================+==========================================================================================================================================================================+=======================+ | Type | IPv4 | IPv4 | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Protocol & Port | **Protocol**: The network protocol. Currently, the value can be **All**, **TCP**, **UDP**, **ICMP**, **GRE**, or others. | TCP | + | Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP | + | | | | + | | Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | | **Port**: The port or port range over which the traffic can reach your ECS. The value ranges from 1 to 65535. | 22, or 22-30 | + | | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | 22, or 22-30 | + | | | | + | | Inbound rules control incoming traffic over specific ports to instances in the security group. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Source | Source of the security group rule. The value can be an IP address or a security group to allow access from IP addresses or instances in the security group. For example: | 0.0.0.0/0 | | | | | @@ -108,9 +114,13 @@ Procedure +=======================+=============================================================================================================================================================================+=======================+ | Type | IPv4 | IPv4 | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Protocol & Port | **Protocol**: The network protocol. Currently, the value can be **All**, **TCP**, **UDP**, **ICMP**, **GRE**, or others. | TCP | + | Protocol & Port | The network protocol used to match traffic in a security group rule. | TCP | + | | | | + | | Currently, the value can be **All**, **TCP**, **UDP**, or **ICMP**, or others. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | | **Port**: The port or port range over which the traffic can leave your ECS. The value ranges from 1 to 65535. | 22, or 22-30 | + | | Destination port used to match traffic in a security group rule. The value can be from 1 to 65535. | 22, or 22-30 | + | | | | + | | Outbound rules control outgoing traffic over specific ports from instances in the security group. | | +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Destination | Destination of the security group rule. The value can be an IP address or a security group to allow access to IP addresses or instances in the security group. For example: | 0.0.0.0/0 | | | | | @@ -132,4 +142,4 @@ Procedure The outbound rule list is displayed. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626734166.png diff --git a/umn/source/index.rst b/umn/source/index.rst index 25cf7f3..0d67998 100644 --- a/umn/source/index.rst +++ b/umn/source/index.rst @@ -8,7 +8,7 @@ Virtual Private Cloud - User Guide service_overview/index getting_started/index vpc_and_subnet/index - security/index + access_control/index elastic_ip/index shared_bandwidth/index route_tables/index diff --git a/umn/source/monitoring/creating_an_alarm_rule.rst b/umn/source/monitoring/creating_an_alarm_rule.rst index 73c022e..5c86995 100644 --- a/umn/source/monitoring/creating_an_alarm_rule.rst +++ b/umn/source/monitoring/creating_an_alarm_rule.rst @@ -17,7 +17,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. -3. Hover on the upper left corner to display **Service List** and choose **Management & Deployment** > **Cloud Eye**. +3. In the upper left corner of the page, click |image2| to open the service list and choose **Management & Deployment** > **Cloud Eye**. 4. In the left navigation pane on the left, choose **Alarm Management** > **Alarm Rules**. @@ -32,3 +32,4 @@ Procedure For more information about alarm rules, see the *Cloud Eye User Guide*. .. |image1| image:: /_static/images/en-us_image_0141273034.png +.. |image2| image:: /_static/images/en-us_image_0000001675258889.png diff --git a/umn/source/monitoring/viewing_metrics.rst b/umn/source/monitoring/viewing_metrics.rst index e59e05a..e99b41c 100644 --- a/umn/source/monitoring/viewing_metrics.rst +++ b/umn/source/monitoring/viewing_metrics.rst @@ -20,8 +20,7 @@ Procedure (**Elastic IP and Bandwidth** Console) #. Click |image2| in the upper left corner and choose **Network** > **Elastic IP**. #. On the **EIPs** page, search for the EIP, click **More** in the **Operation** column, and click **View Metric** to view the monitoring metric details. #. In the navigation pane on the left, choose **Elastic IP and Bandwidth** > **Shared Bandwidths**. - -6. On the **Shared Bandwidths** page, locate the shared bandwidth, click **More** in the **Operation** column, and click **View Metric** to view the monitoring metric details. +#. On the **Shared Bandwidths** page, locate the shared bandwidth, click **More** in the **Operation** column, and click **View Metric** to view the monitoring metric details. Procedure (**Cloud Eye** Console) --------------------------------- @@ -29,10 +28,11 @@ Procedure (**Cloud Eye** Console) #. Log in to the management console. 2. Click |image3| in the upper left corner and select the desired region and project. -3. Hover on the upper left corner to display **Service List** and choose **Management & Deployment** > **Cloud Eye**. +3. In the upper left corner of the page, click |image4| to open the service list and choose **Management & Deployment** > **Cloud Eye**. 4. Click **Cloud Service Monitoring** on the left of the page, and choose **Elastic IP and Bandwidth**. 5. Locate the row that contains the target bandwidth or EIP and click **View Metric** in the **Operation** column to check the bandwidth or EIP monitoring information. .. |image1| image:: /_static/images/en-us_image_0141273034.png .. |image2| image:: /_static/images/en-us_image_0000001572300492.png .. |image3| image:: /_static/images/en-us_image_0141273034.png +.. |image4| image:: /_static/images/en-us_image_0000001675418673.png diff --git a/umn/source/permissions_management/creating_a_user_and_granting_vpc_permissions.rst b/umn/source/permissions_management/creating_a_user_and_granting_vpc_permissions.rst index 030e0eb..1c79c8c 100644 --- a/umn/source/permissions_management/creating_a_user_and_granting_vpc_permissions.rst +++ b/umn/source/permissions_management/creating_a_user_and_granting_vpc_permissions.rst @@ -7,7 +7,7 @@ Creating a User and Granting VPC Permissions This section describes how to use IAM to implement fine-grained permissions control for your VPC resources. With IAM, you can: -- Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing VPC resources. +- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing VPC resources. - Grant users only the permissions required to perform a given task based on their job responsibilities. - Entrust a cloud account or cloud service to perform efficient O&M on your VPC resources. @@ -18,7 +18,7 @@ If your cloud account meets your permissions requirements, you can skip this sec Prerequisites ------------- -Before granting permissions to user groups, learn about permissions (:ref:`Permissions `) for VPC. +Learn about the permissions (see :ref:`Permissions `) supported by VPC and choose policies or roles according to your requirements. To grant permissions for other services, learn about all `permissions `__ supported by IAM. @@ -40,5 +40,4 @@ Process Flow In the authorized region, perform the following operations: - - Choose **Service List** > **Virtual Private Cloud**. Then click **Create VPC** on the VPC console. If a message appears indicating that you have insufficient permissions to perform the operation, the **VPC ReadOnlyAccess** policy is in effect. - - Choose another service from **Service List**. If a message appears indicating that you have insufficient permissions to access the service, the **VPC ReadOnlyAccess** policy is in effect. + - Choose **Service List** > **Virtual Private Cloud**. Then click **Create VPC** on the VPC console. If a message appears indicating that you have insufficient permissions to perform the operation, the **VPCReadOnlyAccess** policy is in effect. diff --git a/umn/source/route_tables/adding_a_custom_route.rst b/umn/source/route_tables/adding_a_custom_route.rst index 291bf51..138681d 100644 --- a/umn/source/route_tables/adding_a_custom_route.rst +++ b/umn/source/route_tables/adding_a_custom_route.rst @@ -10,11 +10,6 @@ Scenarios Each route table contains a default system route, which indicates that ECSs in a VPC can communicate with each other. You can also add custom routes as required to forward the traffic destined for the destination to the specified next hop. -Notes and Constraints ---------------------- - -A maximum of 200 routes can be added to each route table. - Procedure --------- @@ -24,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. 5. In the route table list, click the name of the route table to which you want to add a route. @@ -69,4 +66,4 @@ Procedure 7. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675255405.png diff --git a/umn/source/route_tables/associating_a_route_table_with_a_subnet.rst b/umn/source/route_tables/associating_a_route_table_with_a_subnet.rst index c661936..7731dc7 100644 --- a/umn/source/route_tables/associating_a_route_table_with_a_subnet.rst +++ b/umn/source/route_tables/associating_a_route_table_with_a_subnet.rst @@ -8,12 +8,19 @@ Associating a Route Table with a Subnet Scenarios --------- -After a route table is associated with a subnet, its routes control the routing for the subnet and apply to all cloud resources in the subnet. +After a subnet is created, the system associates the subnet with the default route table of its VPC. If you want to use specific routes for a subnet, you can associate the subnet with a custom route table. + +The custom route table associated with a subnet affects only the outbound traffic. The default route table determines the inbound traffic. + +.. important:: + + After a route table is associated with a subnet, the routes in the route table control the routing for the subnet and apply to all cloud resources in the subnet. Notes and Constraints --------------------- -A subnet can only be associated with one route table. +- A subnet must have a route table associated and can only be associated with one route table. +- A route table can be associated with multiple subnets. Procedure --------- @@ -24,6 +31,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. 5. In the route table list, locate the row that contains the target route table and click **Associate Subnet** in the **Operation** column. @@ -39,4 +48,4 @@ Procedure 7. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626735570.png diff --git a/umn/source/route_tables/changing_the_route_table_associated_with_a_subnet.rst b/umn/source/route_tables/changing_the_route_table_associated_with_a_subnet.rst index f45845b..dbe8d59 100644 --- a/umn/source/route_tables/changing_the_route_table_associated_with_a_subnet.rst +++ b/umn/source/route_tables/changing_the_route_table_associated_with_a_subnet.rst @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. 5. Click the name of the target route table. @@ -30,4 +32,4 @@ Procedure After the route table for a subnet is changed, routes in the new route table will apply to all cloud resources in the subnet. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626575750.png diff --git a/umn/source/route_tables/creating_a_custom_route_table.rst b/umn/source/route_tables/creating_a_custom_route_table.rst index 2c6970b..bb19964 100644 --- a/umn/source/route_tables/creating_a_custom_route_table.rst +++ b/umn/source/route_tables/creating_a_custom_route_table.rst @@ -8,12 +8,7 @@ Creating a Custom Route Table Scenarios --------- -If your default route table cannot meet your service requirements, you can create a custom route table by following the instructions provided in this section. - -Notes and Constraints ---------------------- - -- Each VPC can have a maximum of 10 route tables, including the default route table. +A VPC automatically comes with a default route table. If your default route table cannot meet your service requirements, you can create a custom route table. Procedure --------- @@ -24,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. 5. In the upper right corner, click **Create Route Table**. On the displayed page, configure parameters as prompted. @@ -65,4 +62,4 @@ Procedure c. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627055454.png diff --git a/umn/source/route_tables/deleting_a_route.rst b/umn/source/route_tables/deleting_a_route.rst index 8bc625f..95d2d57 100644 --- a/umn/source/route_tables/deleting_a_route.rst +++ b/umn/source/route_tables/deleting_a_route.rst @@ -31,6 +31,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. 5. Locate the target route table and click its name. @@ -44,4 +46,4 @@ Procedure 7. Confirm the information and click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675375405.png diff --git a/umn/source/route_tables/deleting_a_route_table.rst b/umn/source/route_tables/deleting_a_route_table.rst index 54060dc..b3ad566 100644 --- a/umn/source/route_tables/deleting_a_route_table.rst +++ b/umn/source/route_tables/deleting_a_route_table.rst @@ -24,17 +24,19 @@ Procedure #. Log in to the management console. -#. Click |image1| in the upper left corner and select the desired region and project. +2. Click |image1| in the upper left corner and select the desired region and project. -#. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. +3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -#. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. + The **Virtual Private Cloud** page is displayed. -#. Locate the row that contains the route table you want to delete and click **Delete** in the **Operation** column. +4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. + +5. Locate the row that contains the route table you want to delete and click **Delete** in the **Operation** column. A confirmation dialog box is displayed. -#. Click **Yes**. +6. Click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675615337.png diff --git a/umn/source/route_tables/exporting_route_table_information.rst b/umn/source/route_tables/exporting_route_table_information.rst index e24001f..bb686e4 100644 --- a/umn/source/route_tables/exporting_route_table_information.rst +++ b/umn/source/route_tables/exporting_route_table_information.rst @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. 5. On the displayed page, click |image3| in the upper right of the route table list. @@ -26,5 +28,5 @@ Procedure The system will automatically export information about all route tables under your account in the current region as an Excel file to a local directory. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626895486.png .. |image3| image:: /_static/images/en-us_image_0214585307.png diff --git a/umn/source/route_tables/modifying_a_route.rst b/umn/source/route_tables/modifying_a_route.rst index 2162ac2..d4b26d1 100644 --- a/umn/source/route_tables/modifying_a_route.rst +++ b/umn/source/route_tables/modifying_a_route.rst @@ -22,10 +22,17 @@ Procedure #. Log in to the management console. 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**. + + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. + 5. In the route table list, click the name of the target route table. + 6. Locate the row that contains the route to be modified and click **Modify** in the **Operation** column. + 7. Modify the route information in the displayed dialog box. .. table:: **Table 1** Parameter descriptions @@ -59,4 +66,4 @@ Procedure 8. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627055450.png diff --git a/umn/source/route_tables/replicating_a_route.rst b/umn/source/route_tables/replicating_a_route.rst index ac3643c..9537378 100644 --- a/umn/source/route_tables/replicating_a_route.rst +++ b/umn/source/route_tables/replicating_a_route.rst @@ -52,19 +52,21 @@ Procedure #. Log in to the management console. -#. Click |image1| in the upper left corner and select the desired region and project. +2. Click |image1| in the upper left corner and select the desired region and project. -#. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. +3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -#. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. + The **Virtual Private Cloud** page is displayed. -#. 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. +4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. -#. Select the target route table that you want to replicate route to and the routes to be replicated as prompted. +5. 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. + +6. Select the target route table that you want to replicate route to and the routes to be replicated as prompted. The listed routes are those that do not exist in the target route table. You can select one or more routes to replicate to the target route table. -#. Click **OK**. +7. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626735566.png diff --git a/umn/source/route_tables/viewing_route_table_information.rst b/umn/source/route_tables/viewing_route_table_information.rst index a44e820..5642fed 100644 --- a/umn/source/route_tables/viewing_route_table_information.rst +++ b/umn/source/route_tables/viewing_route_table_information.rst @@ -23,6 +23,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Route Tables**. 5. Click the name of the target route table. @@ -33,4 +35,4 @@ Procedure b. On the **Associated Subnets** tab page, view the subnets associated with the route table. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675415213.png diff --git a/umn/source/route_tables/viewing_the_route_table_associated_with_a_subnet.rst b/umn/source/route_tables/viewing_the_route_table_associated_with_a_subnet.rst index b8ceb6a..d10d0bf 100644 --- a/umn/source/route_tables/viewing_the_route_table_associated_with_a_subnet.rst +++ b/umn/source/route_tables/viewing_the_route_table_associated_with_a_subnet.rst @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -34,4 +36,4 @@ Procedure The route table details page is displayed. You can further view the route information. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675375297.png diff --git a/umn/source/security/security_group/security_group_overview.rst b/umn/source/security/security_group/security_group_overview.rst deleted file mode 100644 index 2172958..0000000 --- a/umn/source/security/security_group/security_group_overview.rst +++ /dev/null @@ -1,85 +0,0 @@ -:original_name: en-us_topic_0073379079.html - -.. _en-us_topic_0073379079: - -Security Group Overview -======================= - -Security Group --------------- - -A security group is a collection of access control rules for cloud resources, such as cloud servers, containers, and databases, that have the same security protection requirements and that are mutually trusted. After a security group is created, you can create various access rules for the security group, these rules will apply to all cloud resources added to this security group. - -Like whitelists, security group rules work as follows: - -- Inbound rules control incoming traffic to instances in the security group. If an inbound request matches the source in an inbound security group rule with **Action** set to **Allow**, the request is allowed. - - Unless otherwise specified, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. - -- Outbound rules control outgoing traffic from instances in the security group. If the destination of an outbound security group rule with **Action** set to **Allow** is 0.0.0.0/0, all outbound requests are allowed. - - 0.0.0.0/0 represents all IPv4 addresses. - - ::/0 represents all IPv6 addresses. - -:ref:`Table 1 ` shows the inbound and outbound rules in security group sg-AB. - -.. _en-us_topic_0073379079__table102261597217: - -.. table:: **Table 1** Rules in security group sg-AB - - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Direction | Action | Type | Protocol & Port | Source/Destination | Description | - +===========+========+======+=================+===========================+======================================================================================================================================+ - | Inbound | Allow | IPv4 | All | Source: sg-AB | This rule allows ECSs in the security group to communicate with each other. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Inbound | Allow | IPv4 | TCP: 22 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over SSH port 22 for remotely logging in to Linux ECSs. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Inbound | Allow | IPv4 | TCP: 3389 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over RDP port 3389 for remotely logging in to Windows ECSs. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Inbound | Allow | IPv4 | TCP: 80 | Source: 10.5.6.30/32 | This rule allows IP address 10.5.6.30 to access ECSs in the security group over port 80. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Outbound | Allow | IPv4 | All | Destination: 0.0.0.0/0 | This rule allows access from ECSs in the security group to any IPv4 address over any port. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Outbound | Allow | IPv6 | All | Destination: ::/0 | This rule allows access from ECSs in the security group to any IPv6 address over any port. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Outbound | Allow | IPv4 | TCP: 80 | Destination: 10.7.6.51/32 | This rule allows access from ECSs in the security group to IP address 10.7.6.51 over port 80. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - -The system automatically creates a default security group for each account. If the default security group does not meet your requirements, you can :ref:`modify security group rules ` or :ref:`create a custom security group `. - -Security Group Basics ---------------------- - -- You can associate instances, such as servers and extension NICs, with one or more security groups. - - You can also change the security groups that are associated with the instances. By default, when you create an instance, it is associated with the default security group of its VPC unless you specify another security group. - -- You can add security group rules to allow instances in the same security group to communicate with each other. - -- Security groups are stateful. If you send a request from your instance and the outbound traffic is allowed, the response traffic for that request is allowed to flow in regardless of inbound security group rules. Similarly, if inbound traffic is allowed, responses to allowed inbound traffic are allowed to flow out, regardless of outbound rules. - - Security groups use connection tracking to track traffic to and from instances that they contain and security group rules are applied based on the connection status of the traffic to determine whether to allow or deny traffic. If you add, modify, or delete a security group rule, or create or delete an instance in the security group, the connection tracking of all instances in the security group will be automatically cleared. In this case, the inbound or outbound traffic of the instance will be considered as new connections, which need to match the inbound or outbound security group rules to ensure that the rules take effect immediately and the security of incoming traffic. - - In addition, if the inbound or outbound traffic of an instance has no packets for a long time, the traffic will be considered as new connections after the connection tracking times out, and the connections need to match the outbound and inbound rules. The timeout period of connection tracking varies according to the protocol. The timeout period of a TCP connection in the established state is 600s, and the timeout period of an ICMP connection is 30s. For other protocols, if packets are received in both directions, the connection tracking timeout period is 180s. If one or more packets are received in one direction but no packet is received in the other direction, the connection tracking timeout period is 30s. For protocols other than TCP, UDP, and ICMP, only the IP address and protocol number are tracked. - -.. note:: - - If two ECSs are in the same security group but in different VPCs, the ECSs cannot communicate with each other. To enable communications between the ECSs, use a VPC peering connection to connect the two VPCs. - -Security Group Rules --------------------- - -After you create a security group, you can add rules to the security group. A rule applies either to inbound traffic or outbound traffic. After you add cloud resources to the security group, they are protected by the rules of the group. - -Each security group has its default rules. For details, see :ref:`Table 1 `. You can also customize security group rules. For details, see :ref:`Adding a Security Group Rule `. - -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. -- 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. - - Inbound rules: only allow data packets from 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 e4d01a3..a2d3459 100644 --- a/umn/source/service_overview/basic_concepts/route_table.rst +++ b/umn/source/service_overview/basic_concepts/route_table.rst @@ -5,17 +5,6 @@ Route Table =========== -Route Tables ------------- - -A route table contains a set of routes that are used to determine where network traffic from your subnets in a VPC is directed. Each subnet must be associated with a route table. You can associate a subnet with only one route table at a time, but you can associate multiple subnets with the same route table. - - -.. figure:: /_static/images/en-us_image_0000001229959315.png - :alt: **Figure 1** Route Table - - **Figure 1** Route Table - Default Route Table and Custom Route Table ------------------------------------------ @@ -33,7 +22,7 @@ If you do not want to use the default route table, you can now create a custom r Route ----- -A route is configured with the destination, next hop type, and next hop to determine where network traffic is directed. Routes are classified into system routes and custom routes. +You can add routes to default and custom route tables and configure the destination, next hop type, and next hop in the routes to determine where network traffic is directed. Routes are classified into system routes and custom routes. - System routes: These routes are automatically added by the system and cannot be modified or deleted. diff --git a/umn/source/service_overview/basic_concepts/security_group.rst b/umn/source/service_overview/basic_concepts/security_group.rst index 01c9c12..7923e13 100644 --- a/umn/source/service_overview/basic_concepts/security_group.rst +++ b/umn/source/service_overview/basic_concepts/security_group.rst @@ -11,7 +11,7 @@ Like whitelists, security group rules work as follows: - Inbound rules control incoming traffic to instances in the security group. If an inbound request matches the source in an inbound security group rule with **Action** set to **Allow**, the request is allowed. - Unless otherwise specified, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. + By default, you do not need to configure deny rules in the inbound direction because requests that do not match allow rules will be denied. - Outbound rules control outgoing traffic from instances in the security group. If the destination of an outbound security group rule with **Action** set to **Allow** is 0.0.0.0/0, all outbound requests are allowed. @@ -25,20 +25,16 @@ Like whitelists, security group rules work as follows: .. table:: **Table 1** Rules in security group sg-AB - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Direction | Action | Type | Protocol & Port | Source/Destination | Description | - +===========+========+======+=================+===========================+======================================================================================================================================+ - | Inbound | Allow | IPv4 | All | Source: sg-AB | This rule allows ECSs in the security group to communicate with each other. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Inbound | Allow | IPv4 | TCP: 22 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over SSH port 22 for remotely logging in to Linux ECSs. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Inbound | Allow | IPv4 | TCP: 3389 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over RDP port 3389 for remotely logging in to Windows ECSs. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Inbound | Allow | IPv4 | TCP: 80 | Source: 10.5.6.30/32 | This rule allows IP address 10.5.6.30 to access ECSs in the security group over port 80. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Outbound | Allow | IPv4 | All | Destination: 0.0.0.0/0 | This rule allows access from ECSs in the security group to any IPv4 address over any port. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Outbound | Allow | IPv6 | All | Destination: ::/0 | This rule allows access from ECSs in the security group to any IPv6 address over any port. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ - | Outbound | Allow | IPv4 | TCP: 80 | Destination: 10.7.6.51/32 | This rule allows access from ECSs in the security group to IP address 10.7.6.51 over port 80. | - +-----------+--------+------+-----------------+---------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Direction | Type | Protocol & Port | Source/Destination | Description | + +===========+======+=================+========================+======================================================================================================================================+ + | Inbound | IPv4 | All | Source: sg-AB | This rule allows ECSs in the security group to communicate with each other. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Inbound | IPv4 | TCP: 22 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over SSH port 22 for remotely logging in to Linux ECSs. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Inbound | IPv4 | TCP: 3389 | Source: 0.0.0.0/0 | This rule allows all IPv4 addresses to access ECSs in the security group over RDP port 3389 for remotely logging in to Windows ECSs. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Inbound | IPv4 | TCP: 80 | Source: 10.5.6.30/32 | This rule allows IP address 10.5.6.30 to access ECSs in the security group over port 80. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ + | Outbound | IPv4 | All | Destination: 0.0.0.0/0 | This rule allows access from ECSs in the security group to any IPv4 address over any port. | + +-----------+------+-----------------+------------------------+--------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/service_overview/basic_concepts/shared_snat.rst b/umn/source/service_overview/basic_concepts/shared_snat.rst index 55e9fb8..483ed29 100644 --- a/umn/source/service_overview/basic_concepts/shared_snat.rst +++ b/umn/source/service_overview/basic_concepts/shared_snat.rst @@ -20,9 +20,15 @@ The VPC service provides free SNAT function, which allows ECSs to use a limited - To enable shared SNAT on the management console: #. Log in to the management console. - #. On the console homepage, under **Network**, click **Virtual Private Cloud**. + + #. Click |image1| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. On the **Virtual Private Cloud** page, locate the VPC for which shared SNAT is to be enabled, and click **Modify**. + #. In the displayed dialog box, enable **Shared SNAT**. + #. Click **OK**. After being configured for a VPC, shared SNAT takes effect for the whole VPC. If EIPs are bound to ECSs in a VPC for which shared SNAT is configured, Internet traffic is preferentially forwarded using the EIPs. If you want to prevent an ECS from connecting to the Internet, you can configure an outbound rule for the security group associated with the ECS. @@ -57,3 +63,5 @@ To prevent an ECS from connecting to the Internet but allow the ECS to access 19 - A custom route enables ECSs to access the Internet through an SNAT server that has an EIP bound. The ECSs' access requests are routed to the SNAT server based on the route table. - Shared SNAT takes effect for the whole VPC by default, while a custom route takes effect for the VPC or subnet for which routes have been configured. - A custom route has a higher priority than a shared SNAT. + +.. |image1| image:: /_static/images/en-us_image_0000001675619157.png diff --git a/umn/source/service_overview/index.rst b/umn/source/service_overview/index.rst index a09d654..13643f5 100644 --- a/umn/source/service_overview/index.rst +++ b/umn/source/service_overview/index.rst @@ -9,7 +9,6 @@ Service Overview - :ref:`Product Advantages ` - :ref:`Application Scenarios ` - :ref:`VPC Connectivity ` -- :ref:`Notes and Constraints ` - :ref:`VPC and Other Services ` - :ref:`Permissions ` - :ref:`Basic Concepts ` @@ -23,7 +22,6 @@ Service Overview product_advantages application_scenarios vpc_connectivity - notes_and_constraints vpc_and_other_services permissions basic_concepts/index diff --git a/umn/source/service_overview/notes_and_constraints.rst b/umn/source/service_overview/notes_and_constraints.rst deleted file mode 100644 index 2209681..0000000 --- a/umn/source/service_overview/notes_and_constraints.rst +++ /dev/null @@ -1,69 +0,0 @@ -:original_name: overview_0003.html - -.. _overview_0003: - -Notes and Constraints -===================== - -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. -- 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. - - Inbound rules: only allow data packets from the selected security group or only data packets from the peer load balancer. - -Firewall --------- - -- By default, you can create a maximum of 200 firewalls in your cloud account. -- You can associate a firewall with multiple subnets. However, a subnet can only be associated with one firewall at a time. -- A firewall can contain no more than 20 rules in one direction, or performance will deteriorate. -- For optimal performance, import no more than 40 firewall rules at a time. Existing rules will still be available after new rules are imported. Each rule can be imported only once. - -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 VPC endpoint, VPN or Direct Connect connection, the default route table automatically delivers a route that cannot be deleted or modified. - -VPC Peering Connection ----------------------- - -- A VPC peering connection can only connect VPCs in the same region. -- If the local and peer VPCs have overlapping CIDR blocks, the VPC peering connection may not take effect. -- A VPC cannot use EIPs of its peered VPC for Internet access. For example, if VPC A is peered with VPC B that has EIPs, VPC A cannot use EIPs in VPC B to access the Internet. - -VPC Flow Log ------------- - -- Currently, only C3, M3, and S2 ECSs support VPC flow logs. -- By default, you can create a maximum of 10 VPC flow logs. -- By default, a maximum of 400,000 flow log records are supported. - -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. - -EIP ---- - -- Each EIP can only be bound to one cloud resource. -- An EIP that has already been bound to a cloud resource cannot be bound to another resource without first being unbound from the current resource. -- You can only release EIPs that are not bound to any resources. -- The system preferentially assigns EIPs to you from the ones you released, if any. However, if any of these EIPs is already assigned to another user, it cannot be re-assigned to you. -- EIPs cannot be transferred across accounts. - -Bandwidth ---------- - -- A dedicated bandwidth can control how much data can be transferred using a single EIP. -- A shared bandwidth cannot control how much data can be transferred using a single EIP. Data transfer rate on EIPs cannot be customized. -- A shared bandwidth or dedicated bandwidth can only be used by resources owned by the same account. - -.. note:: - - - Inbound bandwidth is the bandwidth consumed when data is transferred from the Internet to the cloud. Outbound bandwidth is the bandwidth consumed when data is transferred from the cloud to the Internet. diff --git a/umn/source/service_overview/permissions.rst b/umn/source/service_overview/permissions.rst index 0025db9..905be36 100644 --- a/umn/source/service_overview/permissions.rst +++ b/umn/source/service_overview/permissions.rst @@ -23,7 +23,7 @@ VPC is a project-level service deployed for specific regions. When you set **Sco You can grant permissions by using roles and policies. - Roles: A coarse-grained authorization strategy provided by IAM to assign permissions based on users' job responsibilities. Only a limited number of service-level roles are available for authorization. When you grant permissions using roles, you also need to attach dependent roles. Roles are not ideal for fine-grained authorization and least privilege access. -- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant users only permission to manage VPCs of a certain type. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by VPC, see `Permissions Policies and Supported Actions `__. +- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access. For example, you can grant VPC users only the permissions for managing a certain type of resources. A majority of fine-grained policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by VPC, see `Permissions Policies and Supported Actions `__. :ref:`Table 1 ` lists all the system-defined permissions for VPC. @@ -34,7 +34,7 @@ You can grant permissions by using roles and policies. +--------------------+-------------------------------------------------------------------------------------------------------------------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------+ | Policy Name | Description | Policy Type | Dependencies | +====================+=========================================================================================================================+=======================+==============================================================================================================================+ - | VPC FullAccess | Full permissions for VPC | System-defined policy | None | + | VPC FullAccess | Full permissions for VPC | System-defined policy | To use the VPC flow log function, users must also have the **LTS ReadOnlyAccess** permission. | +--------------------+-------------------------------------------------------------------------------------------------------------------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------+ | VPC ReadOnlyAccess | Read-only permissions on VPC. | System-defined policy | None | +--------------------+-------------------------------------------------------------------------------------------------------------------------+-----------------------+------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/shared_bandwidth/adding_eips_to_a_shared_bandwidth.rst b/umn/source/shared_bandwidth/adding_eips_to_a_shared_bandwidth.rst index a0e8921..e42c400 100644 --- a/umn/source/shared_bandwidth/adding_eips_to_a_shared_bandwidth.rst +++ b/umn/source/shared_bandwidth/adding_eips_to_a_shared_bandwidth.rst @@ -13,9 +13,7 @@ Add EIPs to a shared bandwidth and the EIPs can then share that bandwidth. You c Notes and Constraints --------------------- -- After an EIP is added to a shared bandwidth, the original bandwidth used by the EIP will become invalid and the EIP will start to use the shared bandwidth. -- The EIP's original dedicated bandwidth will be deleted. -- If it is a standard shared bandwidth, you can add dynamic BGP EIPs and IPv6 NICs to it. If it is a premium shared bandwidth, you can add premium BGP EIPs and IPv6 NICs to it. +- The type of EIPs must be the same as that of the shared bandwidth the EIPs to be added to. - Do not add EIPs of the dedicated load balancer type (**5_gray**) and other types to the same shared bandwidth. Otherwise, the bandwidth limit policy will not take effect. Procedure @@ -29,7 +27,11 @@ Procedure 4. In the navigation pane on the left, choose **Elastic IP and Bandwidth** > **Shared Bandwidths**. -5. In the shared bandwidth list, locate the row that contains the shared bandwidth that you want to add EIPs to. In the **Operation** column, choose **More** > **Add EIP**, and select the EIPs to be added. +5. In the shared bandwidth list, locate the row that contains the shared bandwidth that you want to add EIPs to. In the **Operation** column, choose **Add EIP**, and select the EIPs to be added. + + .. note:: + + - After an EIP is added to a shared bandwidth, the dedicated bandwidth used by the EIP will become invalid and the EIP will start to use the shared bandwidth. The EIP's dedicated bandwidth will be deleted and will no longer be billed. .. figure:: /_static/images/en-us_image_0000001211006359.png diff --git a/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst b/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst index d2eae01..7093b52 100644 --- a/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst +++ b/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst @@ -23,6 +23,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** > **Elastic IP**. + 4. In the navigation pane on the left, choose **Elastic IP and Bandwidth** > **Shared Bandwidths**. 5. In the shared bandwidth list, locate the row that contains the shared bandwidth you want to delete, click **More** in the **Operation** column, and then click **Delete**. 6. In the displayed dialog box, click **Yes**. diff --git a/umn/source/shared_bandwidth/shared_bandwidth_overview.rst b/umn/source/shared_bandwidth/shared_bandwidth_overview.rst index 8be79a2..50704cc 100644 --- a/umn/source/shared_bandwidth/shared_bandwidth_overview.rst +++ b/umn/source/shared_bandwidth/shared_bandwidth_overview.rst @@ -7,6 +7,10 @@ Shared Bandwidth Overview A shared bandwidth can be shared by multiple EIPs and controls the data transfer rate on these EIPs in a centralized manner. All ECSs, BMSs, and load balancers that have EIPs bound in the same region can share a bandwidth. +.. note:: + + - A shared bandwidth cannot control how much data can be transferred using a single EIP. Data transfer rate on EIPs cannot be customized. + When you host a large number of applications on the cloud, if each EIP uses a bandwidth, a lot of bandwidths are required, increasing O&M workload. If all EIPs share the same bandwidth, VPCs and the region-level bandwidth can be managed in a unified manner, simplifying O&M statistics and network operations cost settlement. - Easy to Manage diff --git a/umn/source/virtual_ip_address/assigning_a_virtual_ip_address.rst b/umn/source/virtual_ip_address/assigning_a_virtual_ip_address.rst index b2dde32..7ee8266 100644 --- a/umn/source/virtual_ip_address/assigning_a_virtual_ip_address.rst +++ b/umn/source/virtual_ip_address/assigning_a_virtual_ip_address.rst @@ -14,20 +14,29 @@ Procedure --------- #. Log in to the management console. + #. Click |image1| in the upper left corner and select the desired region and project. + #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. + #. In the subnet list, click the name of the subnet where a virtual IP address is to be assigned. + #. Click the **IP Addresses** tab and click **Assign Virtual IP Address**. + #. Select a virtual IP address assignment mode. - **Automatic**: The system assigns an IP address automatically. - **Manual**: You can specify an IP address. #. Select **Manual** and enter a virtual IP address. + #. Click **OK**. You can then query the assigned virtual IP address in the IP address list. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001554010645.png +.. |image2| image:: /_static/images/en-us_image_0000001626897562.png diff --git a/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip.rst b/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip.rst index 2cf1b8c..a10a09a 100644 --- a/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip.rst +++ b/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip.rst @@ -19,10 +19,18 @@ Procedure --------- #. Log in to the management console. + #. Click |image1| in the upper left corner and select the desired region and project. -#. On the console homepage, under **Network**, click **Elastic IP**. + +#. Click |image2| in the upper left corner and choose **Network** > **Elastic IP**. + + The EIP list page is displayed. + #. Locate the row that contains the EIP to be bound to the virtual IP address, and click **Bind** in the **Operation** column. + #. In the **Bind EIP** dialog box, set **Instance Type** to **Virtual IP address**. + #. In the virtual IP address list, select the virtual IP address to be bound and click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png +.. |image2| image:: /_static/images/en-us_image_0000001626578706.png diff --git a/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip_or_ecs.rst b/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip_or_ecs.rst index 2edbaf5..7d14be5 100644 --- a/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip_or_ecs.rst +++ b/umn/source/virtual_ip_address/binding_a_virtual_ip_address_to_an_eip_or_ecs.rst @@ -10,14 +10,26 @@ Scenarios You can bind a virtual IP address to an EIP so that you can access the ECSs bound with the same virtual IP address from the Internet. These ECSs can work in the active/standby mode to improve fault tolerance. +Notes and Constraints +--------------------- + +- Each virtual IP address can be bound to only one EIP. + Procedure --------- #. Log in to the management console. + #. Click |image1| in the upper left corner and select the desired region and project. + #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. + #. In the subnet list, click the name of the subnet that the virtual IP address belongs to. + #. Click the **IP Addresses** tab. - To bind a virtual IP address to an EIP, locate the row that contains the virtual IP address and click **Bind to EIP** in the **Operation** column. @@ -129,7 +141,7 @@ Procedure In the command output, **IPv4 Address** is the virtual IP address 10.0.0.154, indicating that the virtual IP address of the ECS NIC has been correctly configured. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001553930581.png +.. |image2| image:: /_static/images/en-us_image_0000001626738526.png .. |image3| image:: /_static/images/en-us_image_0000001281210233.png .. |image4| image:: /_static/images/en-us_image_0000001237328110.png .. |image5| image:: /_static/images/en-us_image_0000001237013856.png diff --git a/umn/source/virtual_ip_address/disabling_ip_forwarding_on_the_standby_ecs.rst b/umn/source/virtual_ip_address/disabling_ip_forwarding_on_the_standby_ecs.rst new file mode 100644 index 0000000..bbe194d --- /dev/null +++ b/umn/source/virtual_ip_address/disabling_ip_forwarding_on_the_standby_ecs.rst @@ -0,0 +1,57 @@ +:original_name: vpc_vip_0007.html + +.. _vpc_vip_0007: + +Disabling IP Forwarding on the Standby ECS +========================================== + +Scenarios +--------- + +If a virtual IP address is used in an active/standby scenario, disable IP forwarding on the standby ECS. + +Linux +----- + +#. Log in to the ECS. + +#. Check whether IP forwarding is enabled: + + **cat /proc/sys/net/ipv4/ip_forward** + + In the command output, **1** indicates it is enabled, and **0** indicates it is disabled. The default value is **0**. + + - If **1** is displayed, go to :ref:`3 `. + - If **0** is displayed, no further action is required. + +#. .. _vpc_vip_0007__en-us_topic_0206027322_li97125518364: + + Use either of the following methods to modify the configuration file: + + - Method 1: Use the vi editor to open the **/etc/sysctl.conf** file, change the value of **net.ipv4.ip_forward** to **0**, and enter **:wq** to save the change and exit. + + - Method 2: Use the **sed** command. An example command is as follows: + + **sed -i '/net.ipv4.ip_forward/s/1/0/g' /etc/sysctl.conf** + +#. Make the modification take effect: + + **sysctl -p /etc/sysctl.conf** + +Windows +------- + +#. Log in to the ECS. + +#. Open **Command Prompt** and run the following command: + + **ipconfig/all** + + In the command output, if the value of **IP Routing Enabled** is **No**, the IP forwarding function is disabled. + +#. Press **Windows** and **R** keys together to open the **Run** box, and enter **regedit** to open the **Registry Editor**. + +#. Set the value of **IPEnableRouter** under **HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters** to **0**. + + - If the value is set to **0**, IP forwarding will be disabled. + - If the value is set to **1**, IP forwarding will be enabled. 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 deleted file mode 100644 index d8c4e5a..0000000 --- a/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst +++ /dev/null @@ -1,16 +0,0 @@ -:original_name: vpc_vip_0008.html - -.. _vpc_vip_0008: - -Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) -=========================================================================== - -#. Log in to the management console. -#. Click |image1| in the upper left corner and select the desired region and project. -#. 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/disabling_source_destination_check_for_an_ecs_nic.rst b/umn/source/virtual_ip_address/disabling_source_destination_check_for_an_ecs_nic.rst new file mode 100644 index 0000000..c910801 --- /dev/null +++ b/umn/source/virtual_ip_address/disabling_source_destination_check_for_an_ecs_nic.rst @@ -0,0 +1,25 @@ +:original_name: vpc_vip_0008.html + +.. _vpc_vip_0008: + +Disabling Source/Destination Check for an ECS NIC +================================================= + +Scenarios +--------- + +If a virtual IP address is used in an HA load balancing cluster, you need to disable source/destination check for ECS NICs. + +Procedure +--------- + +#. Log in to the management console. +#. Click |image1| in the upper left corner and select the desired region and project. +#. In the upper left corner of the page, click |image2|. In the service list, choose **Computing** > **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 +.. |image2| image:: /_static/images/en-us_image_0000001681512581.png diff --git a/umn/source/virtual_ip_address/index.rst b/umn/source/virtual_ip_address/index.rst index fb460b4..3622855 100644 --- a/umn/source/virtual_ip_address/index.rst +++ b/umn/source/virtual_ip_address/index.rst @@ -12,7 +12,8 @@ Virtual IP Address - :ref:`Using a VPN to Access a Virtual IP Address ` - :ref:`Using a Direct Connect Connection to Access the Virtual IP Address ` - :ref:`Using a VPC Peering Connection to Access the Virtual IP Address ` -- :ref:`Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) ` +- :ref:`Disabling IP Forwarding on the Standby ECS ` +- :ref:`Disabling Source/Destination Check for an ECS NIC ` - :ref:`Unbinding a Virtual IP Address from an Instance ` - :ref:`Unbinding a Virtual IP Address from an EIP ` - :ref:`Releasing a Virtual IP Address ` @@ -28,7 +29,8 @@ Virtual IP Address using_a_vpn_to_access_a_virtual_ip_address using_a_direct_connect_connection_to_access_the_virtual_ip_address using_a_vpc_peering_connection_to_access_the_virtual_ip_address - disabling_source_and_destination_check_ha_load_balancing_cluster_scenario + disabling_ip_forwarding_on_the_standby_ecs + disabling_source_destination_check_for_an_ecs_nic unbinding_a_virtual_ip_address_from_an_instance unbinding_a_virtual_ip_address_from_an_eip releasing_a_virtual_ip_address diff --git a/umn/source/virtual_ip_address/releasing_a_virtual_ip_address.rst b/umn/source/virtual_ip_address/releasing_a_virtual_ip_address.rst index 34eba0e..3f65990 100644 --- a/umn/source/virtual_ip_address/releasing_a_virtual_ip_address.rst +++ b/umn/source/virtual_ip_address/releasing_a_virtual_ip_address.rst @@ -43,6 +43,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. #. Click the name of the subnet that the virtual IP address belongs to. @@ -54,4 +56,4 @@ Procedure #. Confirm the information and click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001553650753.png +.. |image2| image:: /_static/images/en-us_image_0000001675378241.png diff --git a/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_eip.rst b/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_eip.rst index 5478db5..7b0881d 100644 --- a/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_eip.rst +++ b/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_eip.rst @@ -19,6 +19,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -38,4 +40,4 @@ Procedure #. Confirm the information and click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503170970.png +.. |image2| image:: /_static/images/en-us_image_0000001675258381.png diff --git a/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_instance.rst b/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_instance.rst index dd550d6..44b9790 100644 --- a/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_instance.rst +++ b/umn/source/virtual_ip_address/unbinding_a_virtual_ip_address_from_an_instance.rst @@ -19,6 +19,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -52,4 +54,4 @@ Procedure c. Confirm the information and click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503170974.png +.. |image2| image:: /_static/images/en-us_image_0000001675618277.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 79fff81..ea261d6 100644 --- a/umn/source/virtual_ip_address/virtual_ip_address_overview.rst +++ b/umn/source/virtual_ip_address/virtual_ip_address_overview.rst @@ -64,27 +64,4 @@ Notes and Constraints --------------------- - 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. -- IP forwarding must be disabled on the standby ECS. Perform the following operations to confirm whether the IP forwarding is disabled on the standby ECS: - - #. Log in to standby ECS and run the following command to check whether the IP forwarding is enabled: - - cat /proc/sys/net/ipv4/ip_forward - - In the command output, **1** indicates it is enabled, and **0** indicates it is disabled. The default value is **0**. - - - If the command output is **1**, perform :ref:`2 ` and :ref:`3 ` to disable the IP forwarding. - - If the command output is **0**, no further action is required. - - #. .. _vpc_vip_0001__en-us_topic_0206027322_en-us_topic_0095139658_li1473585332417: - - Use the vi editor to open the **/etc/sysctl.conf** file, change the value of **net.ipv4.ip_forward** to **0**, and enter **:wq** to save the change and exit. You can also use the **sed** command to modify the configuration. A command example is as follows: - - sed -i '/net.ipv4.ip_forward/s/1/0/g' /etc/sysctl.conf - - #. .. _vpc_vip_0001__en-us_topic_0206027322_en-us_topic_0095139658_li88984711254: - - Run the following command to make the change take effect: - - sysctl -p /etc/sysctl.conf - -- Each virtual IP address can be bound to only one EIP. +- If a virtual IP address is used in an active/standby scenario, disable IP forwarding on the standby ECS. For details, see :ref:`Disabling IP Forwarding on the Standby ECS `. diff --git a/umn/source/vpc_and_subnet/subnet/creating_a_subnet_for_the_vpc.rst b/umn/source/vpc_and_subnet/subnet/creating_a_subnet_for_the_vpc.rst index 6a30c9b..0f6214d 100644 --- a/umn/source/vpc_and_subnet/subnet/creating_a_subnet_for_the_vpc.rst +++ b/umn/source/vpc_and_subnet/subnet/creating_a_subnet_for_the_vpc.rst @@ -21,6 +21,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. 5. Click **Create Subnet**. @@ -37,37 +39,37 @@ Procedure .. table:: **Table 1** Parameter descriptions - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Description | Example Value | - +======================================+=============================================================================================================================================================================================================================================+=======================+ - | VPC | The VPC for which you want to create a subnet. | ``-`` | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Name | The subnet name. | Subnet | - | | | | - | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Gateway | The gateway address of the subnet. | 192.168.0.1 | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/DNS Server Address | By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | - | | | | - | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added. | | - | | | | - | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | - | | | - Value: subnet-01 | - | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Advanced Settings/Description | Supplementary information about the subnet. This parameter is optional. | ``-`` | - | | | | - | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Parameter | Description | Example Value | + +======================================+=============================================================================================================================================================================================================================================================+=======================+ + | VPC | The VPC for which you want to create a subnet. | ``-`` | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Name | The subnet name. | Subnet | + | | | | + | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Gateway | The gateway address of the subnet. | 192.168.0.1 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/DNS Server Address | By default, two DNS server addresses are configured. You can change them if necessary. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | + | | | | + | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | + | | | | + | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | + | | | - Value: subnet-01 | + | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Advanced Settings/Description | Supplementary information about the subnet. This parameter is optional. | ``-`` | + | | | | + | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ .. _en-us_topic_0013748726__table42131827173915: @@ -111,4 +113,4 @@ When a subnet is created, there are five reserved IP addresses, which cannot be If you configured the default settings under **Advanced Settings** during subnet creation, the reserved IP addresses may be different from the default ones, but there will still be five of them. The specific addresses depend on your subnet settings. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675254021.png diff --git a/umn/source/vpc_and_subnet/subnet/deleting_a_subnet.rst b/umn/source/vpc_and_subnet/subnet/deleting_a_subnet.rst index 4e7e0c7..8144d2a 100644 --- a/umn/source/vpc_and_subnet/subnet/deleting_a_subnet.rst +++ b/umn/source/vpc_and_subnet/subnet/deleting_a_subnet.rst @@ -8,7 +8,7 @@ Deleting a Subnet Scenarios --------- -This section describes how to delete a subnet. +If your subnet is no longer required, you can delete it: Notes and Constraints --------------------- @@ -26,6 +26,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -41,4 +43,4 @@ Procedure If a VPC cannot be deleted, a message will be displayed on the console. Delete the resources that are in the VPC by referring to :ref:`Why Can't I Delete My VPCs and Subnets? ` .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626574366.png diff --git a/umn/source/vpc_and_subnet/subnet/exporting_subnet_list.rst b/umn/source/vpc_and_subnet/subnet/exporting_subnet_list.rst index 4b99717..edab6d6 100644 --- a/umn/source/vpc_and_subnet/subnet/exporting_subnet_list.rst +++ b/umn/source/vpc_and_subnet/subnet/exporting_subnet_list.rst @@ -19,6 +19,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -28,5 +30,5 @@ Procedure The system will automatically export information about all subnets under your account in the current region as an Excel file to a local directory. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675613941.png .. |image3| image:: /_static/images/en-us_image_0000001221842468.png diff --git a/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst b/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst index 95d92e5..499790b 100644 --- a/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst +++ b/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst @@ -8,7 +8,9 @@ Managing Subnet Tags Scenarios --------- -A subnet tag identifies a subnet. Tags can be added to subnets to facilitate subnet identification and administration. You can add a tag to a subnet when creating the subnet, or you can add a tag to a created subnet on the subnet details page. A maximum of 20 tags can be added to each subnet. +You can add tags to subnets to help you identify and organize them. + +You can add a tag to a subnet when creating the subnet, or you can add a tag to a created subnet on the subnet details page. A maximum of 20 tags can be added to each subnet. A tag consists of a key and value pair. :ref:`Table 1 ` lists the tag key and value requirements. @@ -49,10 +51,16 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. +#. Click **+** to add another tag key and value. + + You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for subnets, the subnets containing all specified tags will be displayed. + #. In the search box above the subnet list, click the search box. a. Click **Tag**. @@ -69,6 +77,8 @@ Procedure #. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -94,6 +104,6 @@ Procedure Locate the row that contains the tag you want to delete, and click **Delete** in the **Operation** column. In the displayed dialog box, click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675373909.png .. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001500905066.png +.. |image4| image:: /_static/images/en-us_image_0000001626894094.png diff --git a/umn/source/vpc_and_subnet/subnet/modifying_a_subnet.rst b/umn/source/vpc_and_subnet/subnet/modifying_a_subnet.rst index 5b64a38..923f7a4 100644 --- a/umn/source/vpc_and_subnet/subnet/modifying_a_subnet.rst +++ b/umn/source/vpc_and_subnet/subnet/modifying_a_subnet.rst @@ -19,7 +19,9 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -4. Locate the row that contains the target VPC and click the number in the **Subnets** column. + The **Virtual Private Cloud** page is displayed. + +4. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -44,7 +46,7 @@ Procedure +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | | | | | - | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, you do not add an NTP server IP address. | | + | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | | | | | | | A maximum of four unique NTP server IP addresses can be configured. Multiple IP addresses must be separated by a comma (,). If you add or change the NTP server addresses of a subnet, you need to renew the DHCP lease for or restart all the ECSs in the subnet to make the change take effect immediately. If the NTP server addresses have been cleared out, restarting the ECSs will not help. You must renew the DHCP lease for all ECSs to make the change take effect immediately. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ @@ -56,5 +58,5 @@ Procedure 7. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626574370.png .. |image3| image:: /_static/images/en-us_image_0000001337710801.png diff --git a/umn/source/vpc_and_subnet/subnet/viewing_and_deleting_resources_in_a_subnet.rst b/umn/source/vpc_and_subnet/subnet/viewing_and_deleting_resources_in_a_subnet.rst index 7194fb1..d9ba90d 100644 --- a/umn/source/vpc_and_subnet/subnet/viewing_and_deleting_resources_in_a_subnet.rst +++ b/umn/source/vpc_and_subnet/subnet/viewing_and_deleting_resources_in_a_subnet.rst @@ -25,6 +25,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -81,5 +83,5 @@ Procedure +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+ .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675413829.png .. |image3| image:: /_static/images/en-us_image_0000001461263993.png diff --git a/umn/source/vpc_and_subnet/subnet/viewing_ip_addresses_in_a_subnet.rst b/umn/source/vpc_and_subnet/subnet/viewing_ip_addresses_in_a_subnet.rst index 562b384..a11a1a0 100644 --- a/umn/source/vpc_and_subnet/subnet/viewing_ip_addresses_in_a_subnet.rst +++ b/umn/source/vpc_and_subnet/subnet/viewing_ip_addresses_in_a_subnet.rst @@ -31,6 +31,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **Subnets**. The **Subnets** page is displayed. @@ -42,7 +44,7 @@ Procedure #. Click the **IP Addresses** tab to view the IP addresses in the subnet. a. In the virtual IP address list, you can view the virtual IP addresses assigned from the subnet. - b. In the private IP address list in the lower part of the page, you can view the private IP addresses used by the subnet (gateway, system interface, and DHCP). + b. In the private IP address list in the lower part of the page, you can view the private IP addresses and the resources that use the IP addresses of the subnet. Follow-up Operations -------------------- @@ -50,4 +52,4 @@ Follow-up Operations If you want to view and delete the resources in a subnet, refer to :ref:`Why Can't I Delete My VPCs and Subnets? ` .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675254017.png diff --git a/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst b/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst index 7511ff8..fe8e312 100644 --- a/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst @@ -21,6 +21,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. Click **Create VPC**. #. On the **Create VPC** page, set parameters as prompted. @@ -29,63 +31,63 @@ Procedure .. table:: **Table 1** VPC parameter descriptions - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Category | Parameter | Description | Example Value | - +=====================================+========================+=========================================================================================================================================================================================================================================================================================================+=====================+ - | Basic Information | Region | Regions are geographic areas that are physically isolated from each other. The networks inside different regions are not connected to each other, so resources cannot be shared across different regions. For lower network latency and faster access to your resources, select the region nearest you. | eu-de | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Name | The VPC name. | VPC-001 | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | - | | | | | - | | | The following CIDR blocks are supported: | | - | | | | | - | | | 10.0.0.0/8-24 | | - | | | | | - | | | 172.16.0.0/12-24 | | - | | | | | - | | | 192.168.0.0/16-24 | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | - | | | | | - | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | - | | | | - Value: vpc-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | - | | | | | - | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Name | The subnet name. | Subnet | - | | | | | - | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | - | | | | | - | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If this parameter is left empty, no IP address of the NTP server is added. | | - | | | | | - | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | - | | | | - Value: subnet-01 | - | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | - | | | | | - | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-------------------------------------+------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Category | Parameter | Description | Example Value | + +=====================================+========================+=============================================================================================================================================================================================================================================================+=====================+ + | Basic Information | Region | Select the region nearest to you to ensure the lowest latency possible. | eu-de | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Name | The VPC name. | VPC-001 | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | IPv4 CIDR Block | The CIDR block of the VPC. The CIDR block of a subnet can be the same as the CIDR block for the VPC (for a single subnet in the VPC) or a subset of the CIDR block for the VPC (for multiple subnets in the VPC). | 192.168.0.0/16 | + | | | | | + | | | The following CIDR blocks are supported: | | + | | | | | + | | | 10.0.0.0/8-24 | | + | | | | | + | | | 172.16.0.0/12-24 | | + | | | | | + | | | 192.168.0.0/16-24 | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information | Enterprise Project | The enterprise project to which the VPC belongs. | default | + | | | | | + | | | An enterprise project facilitates project-level management and grouping of cloud resources and users. The name of the default project is **default**. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Tag | The VPC tag, which consists of a key and value pair. You can add a maximum of 20 tags to each VPC. | - Key: vpc_key1 | + | | | | - Value: vpc-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 2 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Basic Information/Advanced Settings | Description | Supplementary information about the VPC. This parameter is optional. | N/A | + | | | | | + | | | The VPC description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Name | The subnet name. | Subnet | + | | | | | + | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Gateway | The gateway address of the subnet. | 192.168.0.1 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | DNS Server Address | By default, two DNS server addresses are configured. You can change them as required. A maximum of five DNS server addresses can be configured. Multiple IP addresses must be separated using commas (,). | 100.125.x.x | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | NTP Server Address | The IP address of the NTP server. This parameter is optional. | 192.168.2.1 | + | | | | | + | | | You can configure the NTP server IP addresses to be added to the subnet as required. The IP addresses are added in addition to the default NTP server addresses. If you do not specify this parameter, no additional NTP server IP addresses will be added. | | + | | | | | + | | | A maximum of four IP addresses can be configured. Multiple IP addresses must be separated using commas (,). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Tag | The subnet tag, which consists of a key and value pair. You can add a maximum of 20 tags to each subnet. | - Key: subnet_key1 | + | | | | - Value: subnet-01 | + | | | The tag key and value must meet the requirements listed in :ref:`Table 3 `. | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet/Advanced Settings | Description | Supplementary information about the subnet. This parameter is optional. | N/A | + | | | | | + | | | The subnet description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ .. _en-us_topic_0013935842__table248245914136: diff --git a/umn/source/vpc_and_subnet/vpc/deleting_a_vpc.rst b/umn/source/vpc_and_subnet/vpc/deleting_a_vpc.rst index bdc315a..821ac76 100644 --- a/umn/source/vpc_and_subnet/vpc/deleting_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/deleting_a_vpc.rst @@ -26,6 +26,8 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. On the **Virtual Private Cloud** page, locate the row that contains the VPC to be deleted and click **Delete** in the **Operation** column. A confirmation dialog box is displayed. @@ -37,4 +39,4 @@ Procedure If a VPC cannot be deleted, a message will be displayed on the console. Delete the resources that are in the VPC by referring to :ref:`Why Can't I Delete My VPCs and Subnets? ` .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626734174.png diff --git a/umn/source/vpc_and_subnet/vpc/exporting_vpc_list.rst b/umn/source/vpc_and_subnet/vpc/exporting_vpc_list.rst index 350fa18..1e8b543 100644 --- a/umn/source/vpc_and_subnet/vpc/exporting_vpc_list.rst +++ b/umn/source/vpc_and_subnet/vpc/exporting_vpc_list.rst @@ -8,7 +8,9 @@ Exporting VPC List Scenarios --------- -Information about all VPCs under your account can be exported as an Excel file to a local directory. This file records the names, ID, status, IP address ranges of VPCs, and the number of subnets. +Information about all VPCs under your account can be exported as an Excel file to a local directory. + +Such a file records the names, ID, status, CIDR blocks, and the number of subnets of your VPCs. Procedure --------- @@ -19,10 +21,12 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the upper right corner of the VPC list, click |image3|. - The system will automatically export information about all VPCs under your account in the current region. They will be exported in Excel format. + The system will automatically export information about all VPCs under your account in the current region as an Excel file to a local directory. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001626894098.png .. |image3| image:: /_static/images/en-us_image_0233469654.png diff --git a/umn/source/vpc_and_subnet/vpc/managing_vpc_tags.rst b/umn/source/vpc_and_subnet/vpc/managing_vpc_tags.rst index 8573eef..6b373c6 100644 --- a/umn/source/vpc_and_subnet/vpc/managing_vpc_tags.rst +++ b/umn/source/vpc_and_subnet/vpc/managing_vpc_tags.rst @@ -8,7 +8,9 @@ Managing VPC Tags Scenarios --------- -A VPC tag identifies a VPC. Tags can be added to VPCs to facilitate VPC identification and management. You can add a tag to a VPC when creating the VPC, or you can add a tag to a created VPC on the VPC details page. A maximum of 20 tags can be added to each VPC. +You can add tags to VPCs to help you identify and organize them. + +You can add a tag to a VPC when creating the VPC, or you can add a tag to a created VPC on the VPC details page. A maximum of 20 tags can be added to each VPC. A tag consists of a key and value pair. :ref:`Table 1 ` lists the tag key and value requirements. @@ -44,8 +46,13 @@ Procedure **Search for VPCs by tag key and value on the page showing the VPC list.** #. Log in to the management console. + #. Click |image1| in the upper left corner and select the desired region and project. + #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + + The **Virtual Private Cloud** page is displayed. + #. In the search box above the VPC list, click the search box. a. Click **Tag**. @@ -62,6 +69,8 @@ Procedure #. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. On the **Virtual Private Cloud** page, locate the VPC whose tags are to be managed and click the VPC name. The page showing details about the particular VPC is displayed. @@ -85,6 +94,6 @@ Procedure Locate the row that contains the tag you want to delete, and click **Delete** in the **Operation** column. In the displayed dialog box, click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001627052380.png .. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001500905066.png +.. |image4| image:: /_static/images/en-us_image_0000001675373913.png diff --git a/umn/source/vpc_and_subnet/vpc/modifying_a_vpc.rst b/umn/source/vpc_and_subnet/vpc/modifying_a_vpc.rst index ac5b612..21a58f3 100644 --- a/umn/source/vpc_and_subnet/vpc/modifying_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/modifying_a_vpc.rst @@ -8,27 +8,15 @@ Modifying a VPC Scenarios --------- -Change the VPC name and CIDR block. +You can modify the following information about a VPC: -If the VPC CIDR block conflicts with the CIDR block of a VPN created in the VPC, you can modify its CIDR block. +- :ref:`Modifying the Name and Description of a VPC ` +- :ref:`Modifying the CIDR Block of a VPC ` -Notes and Constraints ---------------------- +.. _en-us_topic_0030969462__section495418425354: -- When modifying the VPC CIDR block: - - - The VPC CIDR block to be modified must be in the supported CIDR blocks: 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, and 192.168.0.0 - 192.168.255.255 - - If the VPC has subnets, the VPC CIDR block to be modified must contain all subnet CIDR blocks. - -When modifying the VPC CIDR block: - -- The VPC CIDR block to be modified must be in the supported CIDR blocks: 10.0.0.0 - 10.255.255.255, 172.16.0.0 - 172.31.255.255, and 192.168.0.0 - 192.168.255.255 -- If the VPC has subnets, the VPC CIDR block to be modified must contain all subnet CIDR blocks. - -Procedure ---------- - -**Modifying the VPC CIDR Block** +Modifying the Name and Description of a VPC +------------------------------------------- #. Log in to the management console. @@ -36,34 +24,68 @@ Procedure #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -#. On the **Virtual Private Cloud** page, locate the row that contains the VPC to be modified and click **Edit CIDR Block** in the **Operation** column. + The **Virtual Private Cloud** page is displayed. -#. Set a new CIDR block. +#. Modify the name and description of a VPC using either of the following methods: + - Method 1: - .. figure:: /_static/images/en-us_image_0000001151300782.png - :alt: **Figure 1** Modify CIDR Block + a. In the VPC list, click |image3| on the right of the VPC name. + b. Enter the VPC name and click **OK**. - **Figure 1** Modify CIDR Block + - Method 2: -#. Click **OK**. + a. In the VPC list, click the VPC name with a hyperlink. -**Modifying a VPC** + The **Summary** page is displayed. + + b. Click |image4| on the right of the VPC name or description, enter the information, and click |image5|. + +.. _en-us_topic_0030969462__section696206193617: + +Modifying the CIDR Block of a VPC +--------------------------------- #. Log in to the management console. -#. Click |image3| in the upper left corner and select the desired region and project. -#. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. -#. Modify the basic information about a VPC using either of the following methods: - - In the VPC list, click |image5| on the right of the VPC name to change the VPC name. +#. Click |image6| in the upper left corner and select the desired region and project. - - In the VPC list, click the VPC name. +#. Click |image7| in the upper left corner and choose **Network** > **Virtual Private Cloud**. - On the VPC details page, click |image6| next to the VPC name or description to change the VPC name or description. + The **Virtual Private Cloud** page is displayed. + +4. In the VPC list, locate the row that contains the VPC and click **Edit CIDR Block** in the **Operation** column. + + The **Edit CIDR Block** dialog box is displayed. + +5. Modify the VPC CIDR block as prompted. + + .. important:: + + A VPC CIDR block must be from 10.0.0.0/8-24, 172.16.0.0/12-24, or 192.168.0.0/16-24. + + - If a VPC has no subnets, you can change both its network address and subnet mask. + + + .. figure:: /_static/images/en-us_image_0000001627653972.png + :alt: **Figure 1** Modifying network address and subnet mask + + **Figure 1** Modifying network address and subnet mask + + - If a VPC has subnets, you only can change its subnet mask. + + + .. figure:: /_static/images/en-us_image_0000001627493158.png + :alt: **Figure 2** Modifying subnet mask + + **Figure 2** Modifying subnet mask + +6. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001520717193.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001520717193.png -.. |image5| image:: /_static/images/en-us_image_0000001267230305.png -.. |image6| image:: /_static/images/en-us_image_0000001267350317.png +.. |image2| image:: /_static/images/en-us_image_0000001676063997.png +.. |image3| image:: /_static/images/en-us_image_0000001627174280.png +.. |image4| image:: /_static/images/en-us_image_0000001675813933.png +.. |image5| image:: /_static/images/en-us_image_0000001627334080.png +.. |image6| image:: /_static/images/en-us_image_0141273034.png +.. |image7| image:: /_static/images/en-us_image_0000001627744152.png diff --git a/umn/source/vpc_and_subnet/vpc/obtaining_a_vpc_id.rst b/umn/source/vpc_and_subnet/vpc/obtaining_a_vpc_id.rst index c91f21d..7ca5448 100644 --- a/umn/source/vpc_and_subnet/vpc/obtaining_a_vpc_id.rst +++ b/umn/source/vpc_and_subnet/vpc/obtaining_a_vpc_id.rst @@ -10,7 +10,7 @@ Scenarios This section describes how to view and obtain a VPC ID. -If you want to obtain the ID of the peer VPC when you create a VPC peering connection between two VPCs from different accounts, you can share this section with the owner of the peer account to obtain the VPC ID. +If you want to obtain the ID of the peer VPC when you create a VPC peering connection between two VPCs from different accounts, you can refer to the following procedure. Procedure --------- @@ -21,6 +21,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. On the **Virtual Private Cloud** page, locate the VPC and click its name. The VPC details page is displayed. @@ -30,5 +32,5 @@ Procedure Click |image3| next to ID to copy the VPC ID. .. |image1| image:: /_static/images/en-us_image_0000001515644737.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675613945.png .. |image3| image:: /_static/images/en-us_image_0000001465124712.png diff --git a/umn/source/vpc_and_subnet/vpc/viewing_a_vpc_topology.rst b/umn/source/vpc_and_subnet/vpc/viewing_a_vpc_topology.rst index 5ab4043..71c6ee9 100644 --- a/umn/source/vpc_and_subnet/vpc/viewing_a_vpc_topology.rst +++ b/umn/source/vpc_and_subnet/vpc/viewing_a_vpc_topology.rst @@ -19,6 +19,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the VPC list, click the name of the VPC for which the topology is to be viewed. The VPC details page is displayed. @@ -33,4 +35,4 @@ Procedure - Add an ECS to a subnet, bind an EIP to the ECS, and change the security group of the ECS. .. |image1| image:: /_static/images/en-us_image_0000001221790501.png -.. |image2| image:: /_static/images/en-us_image_0000001500905066.png +.. |image2| image:: /_static/images/en-us_image_0000001675413833.png diff --git a/umn/source/vpc_flow_log/creating_a_vpc_flow_log.rst b/umn/source/vpc_flow_log/creating_a_vpc_flow_log.rst index 710dcbf..67a95c7 100644 --- a/umn/source/vpc_flow_log/creating_a_vpc_flow_log.rst +++ b/umn/source/vpc_flow_log/creating_a_vpc_flow_log.rst @@ -29,6 +29,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **VPC Flow Logs**. 5. In the upper right corner, click **Create VPC Flow Log**. On the displayed page, configure parameters as prompted. @@ -76,4 +78,4 @@ Procedure 6. Click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001553770733.png +.. |image2| image:: /_static/images/en-us_image_0000001675616561.png diff --git a/umn/source/vpc_flow_log/deleting_a_vpc_flow_log.rst b/umn/source/vpc_flow_log/deleting_a_vpc_flow_log.rst index 9742c64..bff6fff 100644 --- a/umn/source/vpc_flow_log/deleting_a_vpc_flow_log.rst +++ b/umn/source/vpc_flow_log/deleting_a_vpc_flow_log.rst @@ -23,6 +23,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **VPC Flow Logs**. 5. Locate the row that contains the VPC flow log to be deleted and click **Delete** in the **Operation** column. @@ -36,4 +38,4 @@ Procedure 6. Click **Yes** in the displayed dialog box. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503330854.png +.. |image2| image:: /_static/images/en-us_image_0000001626736794.png diff --git a/umn/source/vpc_flow_log/enabling_or_disabling_vpc_flow_log.rst b/umn/source/vpc_flow_log/enabling_or_disabling_vpc_flow_log.rst index 112d518..ba414d1 100644 --- a/umn/source/vpc_flow_log/enabling_or_disabling_vpc_flow_log.rst +++ b/umn/source/vpc_flow_log/enabling_or_disabling_vpc_flow_log.rst @@ -19,9 +19,11 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **VPC Flow Logs**. 5. Locate the VPC flow log to be enabled or disabled, and choose **More** > **Enable** or **More** > **Disable** in the **Operation** column. 6. Click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503011070.png +.. |image2| image:: /_static/images/en-us_image_0000001627056686.png diff --git a/umn/source/vpc_flow_log/viewing_a_vpc_flow_log.rst b/umn/source/vpc_flow_log/viewing_a_vpc_flow_log.rst index e677c2d..067e28c 100644 --- a/umn/source/vpc_flow_log/viewing_a_vpc_flow_log.rst +++ b/umn/source/vpc_flow_log/viewing_a_vpc_flow_log.rst @@ -25,6 +25,8 @@ Procedure 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **VPC Flow Logs**. 5. Locate the target VPC flow log and click **View Log Record** in the **Operation** column to view information about the flow log record in LTS. @@ -119,4 +121,4 @@ Procedure You can enter a keyword on the log topic details page on the LTS console to search for flow log records. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503490746.png +.. |image2| image:: /_static/images/en-us_image_0000001675256657.png diff --git a/umn/source/vpc_flow_log/vpc_flow_log_overview.rst b/umn/source/vpc_flow_log/vpc_flow_log_overview.rst index 98dd76b..edb51ce 100644 --- a/umn/source/vpc_flow_log/vpc_flow_log_overview.rst +++ b/umn/source/vpc_flow_log/vpc_flow_log_overview.rst @@ -19,6 +19,5 @@ VPC flow logs must be used together with the Log Tank Service (LTS). Before you Notes and Constraints --------------------- -- Currently, only C3, M3, and S2 ECSs support VPC flow logs. -- By default, you can create a maximum of 10 VPC flow logs. -- By default, a maximum of 400,000 flow log records are supported. +- Currently, C3, M3, and S2 ECSs support VPC flow logs. +- Each account can have up to 10 VPC flow logs in a region. diff --git a/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_a_vpc_in_another_account.rst b/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_a_vpc_in_another_account.rst index 50c0967..852d867 100644 --- a/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_a_vpc_in_another_account.rst +++ b/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_a_vpc_in_another_account.rst @@ -41,7 +41,7 @@ Notes and Constraints Prerequisites ------------- -You have two VPCs in the same region. If you want to create one, see :ref:`Creating a VPC `. +You have two VPCs in the same region, but they are from different accounts. If you want to create one, see :ref:`Creating a VPC `. .. _en-us_topic_0046655038__section14616192294815: @@ -54,6 +54,8 @@ Step 1: Create a VPC Peering Connection 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -125,6 +127,8 @@ After you create a VPC peering connection with a VPC in another account, you nee #. Click |image3| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -262,5 +266,5 @@ After you add routes for the VPC peering connection, verify the communication be - If VPCs connected by a VPC peering connection cannot communicate with each other, refer to :ref:`Why Did Communication Fail Between VPCs That Were Connected by a VPC Peering Connection? `. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503159042.png -.. |image3| image:: /_static/images/en-us_image_0000001503478818.png +.. |image2| image:: /_static/images/en-us_image_0000001675415841.png +.. |image3| image:: /_static/images/en-us_image_0000001626736198.png diff --git a/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_another_vpc_in_your_account.rst b/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_another_vpc_in_your_account.rst index c484625..9ae17a2 100644 --- a/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_another_vpc_in_your_account.rst +++ b/umn/source/vpc_peering_connection/creating_a_vpc_peering_connection_with_another_vpc_in_your_account.rst @@ -34,7 +34,7 @@ Notes and Constraints Prerequisites ------------- -You have two VPCs in the same region. If you want to create one, see :ref:`Creating a VPC `. +You have two VPCs from the same account in the same region. If you want to create one, see :ref:`Creating a VPC `. .. _en-us_topic_0046655037__section143383585438: @@ -47,6 +47,8 @@ Step 1: Create a VPC Peering Connection 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -111,10 +113,6 @@ Step 1: Create a VPC Peering Connection a. If you click **Add Route**, the **Local Routes** page is displayed. Then, go to :ref:`Step 2: Add Routes for the VPC Peering Connection `. b. If you click **Add Later**, the VPC peering connection list is displayed. - .. important:: - - After a VPC peering connection is created, you must add routes to the route tables of the local and peer VPCs. Otherwise, the VPC peering connection does not take effect. - .. _en-us_topic_0046655037__section19655123018712: Step 2: Add Routes for the VPC Peering Connection @@ -220,4 +218,4 @@ After you add routes for the VPC peering connection, verify the communication be - If VPCs connected by a VPC peering connection cannot communicate with each other, refer to :ref:`Why Did Communication Fail Between VPCs That Were Connected by a VPC Peering Connection? `. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503318922.png +.. |image2| image:: /_static/images/en-us_image_0000001627056086.png diff --git a/umn/source/vpc_peering_connection/deleting_a_vpc_peering_connection.rst b/umn/source/vpc_peering_connection/deleting_a_vpc_peering_connection.rst index c56f0d9..325e8ac 100644 --- a/umn/source/vpc_peering_connection/deleting_a_vpc_peering_connection.rst +++ b/umn/source/vpc_peering_connection/deleting_a_vpc_peering_connection.rst @@ -24,7 +24,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. -3. On the console homepage, under **Network**, click **Virtual Private Cloud**. +3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. The **Virtual Private Cloud** page is displayed. @@ -39,3 +39,4 @@ Procedure 6. Click **Yes**. .. |image1| image:: /_static/images/en-us_image_0141273034.png +.. |image2| image:: /_static/images/en-us_image_0000001675416345.png diff --git a/umn/source/vpc_peering_connection/deleting_routes_configured_for_a_vpc_peering_connection.rst b/umn/source/vpc_peering_connection/deleting_routes_configured_for_a_vpc_peering_connection.rst index 4ad2cf0..1957805 100644 --- a/umn/source/vpc_peering_connection/deleting_routes_configured_for_a_vpc_peering_connection.rst +++ b/umn/source/vpc_peering_connection/deleting_routes_configured_for_a_vpc_peering_connection.rst @@ -24,6 +24,8 @@ Deleting Routes of a VPC Peering Connection Between VPCs in the Same Account #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -71,6 +73,8 @@ Only the account owner of a VPC in a VPC peering connection can delete the route b. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + c. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -94,6 +98,6 @@ Only the account owner of a VPC in a VPC peering connection can delete the route #. Log in to the management console using the account of the peer VPC and delete the route of the peer VPC by referring to :ref:`1 `. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503330858.png +.. |image2| image:: /_static/images/en-us_image_0000001626896590.png .. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001553770737.png +.. |image4| image:: /_static/images/en-us_image_0000001675616433.png diff --git a/umn/source/vpc_peering_connection/modifying_a_vpc_peering_connection.rst b/umn/source/vpc_peering_connection/modifying_a_vpc_peering_connection.rst index e6f3d76..0af6278 100644 --- a/umn/source/vpc_peering_connection/modifying_a_vpc_peering_connection.rst +++ b/umn/source/vpc_peering_connection/modifying_a_vpc_peering_connection.rst @@ -19,7 +19,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. -3. On the console homepage, under **Network**, click **Virtual Private Cloud**. +3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. The **Virtual Private Cloud** page is displayed. @@ -34,3 +34,4 @@ Procedure 6. Modify the VPC peering connection information and click **OK**. .. |image1| image:: /_static/images/en-us_image_0141273034.png +.. |image2| image:: /_static/images/en-us_image_0000001626576382.png diff --git a/umn/source/vpc_peering_connection/modifying_routes_configured_for_a_vpc_peering_connection.rst b/umn/source/vpc_peering_connection/modifying_routes_configured_for_a_vpc_peering_connection.rst index 5004df6..13e1ecb 100644 --- a/umn/source/vpc_peering_connection/modifying_routes_configured_for_a_vpc_peering_connection.rst +++ b/umn/source/vpc_peering_connection/modifying_routes_configured_for_a_vpc_peering_connection.rst @@ -26,6 +26,8 @@ Modifying Routes of a VPC Peering Connection Between VPCs in the Same Account #. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + #. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -73,6 +75,8 @@ Only the account owner of a VPC can modify the routes added for the connection. b. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + c. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -96,6 +100,6 @@ Only the account owner of a VPC can modify the routes added for the connection. #. 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 `. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001554010649.png +.. |image2| image:: /_static/images/en-us_image_0000001627056574.png .. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001553650757.png +.. |image4| image:: /_static/images/en-us_image_0000001626736678.png diff --git a/umn/source/vpc_peering_connection/obtaining_the_peer_project_id_of_a_vpc_peering_connection.rst b/umn/source/vpc_peering_connection/obtaining_the_peer_project_id_of_a_vpc_peering_connection.rst index dbcdf54..f73d923 100644 --- a/umn/source/vpc_peering_connection/obtaining_the_peer_project_id_of_a_vpc_peering_connection.rst +++ b/umn/source/vpc_peering_connection/obtaining_the_peer_project_id_of_a_vpc_peering_connection.rst @@ -17,5 +17,5 @@ Procedure The owner of the peer account logs in to the management console. -2. Select **My Credentials** from the username drop-down list. +2. In the upper right corner of the page, select **My Credentials** from the username drop-down list. 3. In the project list, obtain the project ID. diff --git a/umn/source/vpc_peering_connection/viewing_routes_configured_for_a_vpc_peering_connection.rst b/umn/source/vpc_peering_connection/viewing_routes_configured_for_a_vpc_peering_connection.rst index b8fb49f..d122d37 100644 --- a/umn/source/vpc_peering_connection/viewing_routes_configured_for_a_vpc_peering_connection.rst +++ b/umn/source/vpc_peering_connection/viewing_routes_configured_for_a_vpc_peering_connection.rst @@ -26,6 +26,8 @@ Viewing Routes of a VPC Peering Connection Between VPCs in the Same Account 3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + 4. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -54,6 +56,8 @@ Only the account owner of a VPC in a VPC peering connection can view the routes b. Click |image4| in the upper left corner and choose **Network** > **Virtual Private Cloud**. + The **Virtual Private Cloud** page is displayed. + c. In the navigation pane on the left, choose **Virtual Private Cloud** > **VPC Peering Connections**. The VPC peering connection list is displayed. @@ -67,6 +71,6 @@ Only the account owner of a VPC in a VPC peering connection can view the routes #. 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 `. .. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001503011074.png +.. |image2| image:: /_static/images/en-us_image_0000001626576858.png .. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001503490750.png +.. |image4| image:: /_static/images/en-us_image_0000001675256529.png diff --git a/umn/source/vpc_peering_connection/viewing_vpc_peering_connections.rst b/umn/source/vpc_peering_connection/viewing_vpc_peering_connections.rst index 5f7f8cc..fc9f207 100644 --- a/umn/source/vpc_peering_connection/viewing_vpc_peering_connections.rst +++ b/umn/source/vpc_peering_connection/viewing_vpc_peering_connections.rst @@ -19,7 +19,7 @@ Procedure 2. Click |image1| in the upper left corner and select the desired region and project. -3. On the console homepage, under **Network**, click **Virtual Private Cloud**. +3. Click |image2| in the upper left corner and choose **Network** > **Virtual Private Cloud**. The **Virtual Private Cloud** page is displayed. @@ -32,3 +32,4 @@ Procedure On the displayed page, view details about the VPC peering connection. .. |image1| image:: /_static/images/en-us_image_0141273034.png +.. |image2| image:: /_static/images/en-us_image_0000001675256029.png diff --git a/umn/source/vpc_peering_connection/vpc_peering_connection_usage_examples.rst b/umn/source/vpc_peering_connection/vpc_peering_connection_usage_examples.rst index 7ea19dd..aff425b 100644 --- a/umn/source/vpc_peering_connection/vpc_peering_connection_usage_examples.rst +++ b/umn/source/vpc_peering_connection/vpc_peering_connection_usage_examples.rst @@ -5,7 +5,7 @@ VPC Peering Connection Usage Examples ===================================== -A VPC peering connection is a networking connection between two VPCs and enables them to communicate. :ref:`Table 1 ` lists different scenarios of using VPC peering connections. +A VPC peering connection is a networking connection between two VPCs in the same region and enables them to communicate. :ref:`Table 1 ` lists different scenarios of using VPC peering connections. .. _en-us_topic_0046809840__table18339193642913: @@ -191,7 +191,10 @@ As shown in :ref:`Figure 4 `, VPC-A and Peering ECSs in a Central VPC with ECSs in Two Other VPCs --------------------------------------------------------- -As shown in :ref:`Figure 5 `, VPC-B and VPC-C have overlapping CIDR blocks, and their Subnet-B01 and Subnet-BC01 have overlapping CIDR blocks. In this case, the VPC peering connection can connect ECSs in Subnet-B01 and Subnet-A01, and ECSs in Subnet-C01 and Subnet-A01. +As shown in :ref:`Figure 5 `, VPC-B and VPC-C have overlapping CIDR blocks, and their Subnet-B01 and Subnet-C01 have overlapping CIDR blocks. You can only create a VPC peering connection between ECSs. + +- Use VPC peering connection Peering-AB to connect ECSs in Subnet-B01 and Subnet-A01. +- Use VPC peering connection Peering-AC to connect ECSs in Subnet-C01 and Subnet-A01. .. _en-us_topic_0046809840__fig568511518481: