diff --git a/umn/source/_static/images/en-us_image_0000001211006359.png b/umn/source/_static/images/en-us_image_0000001211006359.png deleted file mode 100644 index 66686f7..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001211006359.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001211445065.png b/umn/source/_static/images/en-us_image_0000001211445065.png deleted file mode 100644 index a86f5c5..0000000 Binary files a/umn/source/_static/images/en-us_image_0000001211445065.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0000001454059512.png b/umn/source/_static/images/en-us_image_0000001649841616.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001454059512.png rename to umn/source/_static/images/en-us_image_0000001649841616.png diff --git a/umn/source/_static/images/en-us_image_0000001490118666.png b/umn/source/_static/images/en-us_image_0000001818822962.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001490118666.png rename to umn/source/_static/images/en-us_image_0000001818822962.png diff --git a/umn/source/_static/images/en-us_image_0162332046.png b/umn/source/_static/images/en-us_image_0000001818823006.png similarity index 100% rename from umn/source/_static/images/en-us_image_0162332046.png rename to umn/source/_static/images/en-us_image_0000001818823006.png diff --git a/umn/source/_static/images/en-us_image_0000001678437642.png b/umn/source/_static/images/en-us_image_0000001818823010.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001678437642.png rename to umn/source/_static/images/en-us_image_0000001818823010.png diff --git a/umn/source/_static/images/en-us_image_0000001221790501.png b/umn/source/_static/images/en-us_image_0000001818823030.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001221790501.png rename to umn/source/_static/images/en-us_image_0000001818823030.png diff --git a/umn/source/_static/images/en-us_image_0000001117669274.png b/umn/source/_static/images/en-us_image_0000001818823034.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001117669274.png rename to umn/source/_static/images/en-us_image_0000001818823034.png diff --git a/umn/source/_static/images/en-us_image_0142359884.png b/umn/source/_static/images/en-us_image_0000001818823038.png similarity index 100% rename from umn/source/_static/images/en-us_image_0142359884.png rename to umn/source/_static/images/en-us_image_0000001818823038.png diff --git a/umn/source/_static/images/en-us_image_0209583952.png b/umn/source/_static/images/en-us_image_0000001818823042.png similarity index 100% rename from umn/source/_static/images/en-us_image_0209583952.png rename to umn/source/_static/images/en-us_image_0000001818823042.png diff --git a/umn/source/_static/images/en-us_image_0000001221842468.png b/umn/source/_static/images/en-us_image_0000001818823050.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001221842468.png rename to umn/source/_static/images/en-us_image_0000001818823050.png diff --git a/umn/source/_static/images/en-us_image_0000001520717193.png b/umn/source/_static/images/en-us_image_0000001818823058.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001520717193.png rename to umn/source/_static/images/en-us_image_0000001818823058.png diff --git a/umn/source/_static/images/en-us_image_0211552164.png b/umn/source/_static/images/en-us_image_0000001818823074.png similarity index 100% rename from umn/source/_static/images/en-us_image_0211552164.png rename to umn/source/_static/images/en-us_image_0000001818823074.png diff --git a/umn/source/_static/images/en-us_image_0000001572300492.png b/umn/source/_static/images/en-us_image_0000001818823082.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001572300492.png rename to umn/source/_static/images/en-us_image_0000001818823082.png diff --git a/umn/source/_static/images/en-us_image_0000001208260576.png b/umn/source/_static/images/en-us_image_0000001818823110.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001208260576.png rename to umn/source/_static/images/en-us_image_0000001818823110.png diff --git a/umn/source/_static/images/en-us_image_0000001209442636.png b/umn/source/_static/images/en-us_image_0000001818823118.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001209442636.png rename to umn/source/_static/images/en-us_image_0000001818823118.png diff --git a/umn/source/_static/images/en-us_image_0000001237013856.png b/umn/source/_static/images/en-us_image_0000001818823138.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001237013856.png rename to umn/source/_static/images/en-us_image_0000001818823138.png diff --git a/umn/source/_static/images/en-us_image_0000001179761510.png b/umn/source/_static/images/en-us_image_0000001818823142.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001179761510.png rename to umn/source/_static/images/en-us_image_0000001818823142.png diff --git a/umn/source/_static/images/en-us_image_0000001626574358.png b/umn/source/_static/images/en-us_image_0000001818823162.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626574358.png rename to umn/source/_static/images/en-us_image_0000001818823162.png diff --git a/umn/source/_static/images/en-us_image_0000001626574362.png b/umn/source/_static/images/en-us_image_0000001818823166.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626574362.png rename to umn/source/_static/images/en-us_image_0000001818823166.png diff --git a/umn/source/_static/images/en-us_image_0000001626574366.png b/umn/source/_static/images/en-us_image_0000001818823186.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626574366.png rename to umn/source/_static/images/en-us_image_0000001818823186.png diff --git a/umn/source/_static/images/en-us_image_0000001429281925.png b/umn/source/_static/images/en-us_image_0000001818823194.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001429281925.png rename to umn/source/_static/images/en-us_image_0000001818823194.png diff --git a/umn/source/_static/images/en-us_image_0000001626574370.png b/umn/source/_static/images/en-us_image_0000001818823210.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626574370.png rename to umn/source/_static/images/en-us_image_0000001818823210.png diff --git a/umn/source/_static/images/en-us_image_0214585341.png b/umn/source/_static/images/en-us_image_0000001818823214.png similarity index 100% rename from umn/source/_static/images/en-us_image_0214585341.png rename to umn/source/_static/images/en-us_image_0000001818823214.png diff --git a/umn/source/_static/images/en-us_image_0000001626574374.png b/umn/source/_static/images/en-us_image_0000001818823254.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626574374.png rename to umn/source/_static/images/en-us_image_0000001818823254.png diff --git a/umn/source/_static/images/en-us_image_0000001856562181.png b/umn/source/_static/images/en-us_image_0000001818823258.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001856562181.png rename to umn/source/_static/images/en-us_image_0000001818823258.png diff --git a/umn/source/_static/images/en-us_image_0000001626575750.png b/umn/source/_static/images/en-us_image_0000001818823270.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626575750.png rename to umn/source/_static/images/en-us_image_0000001818823270.png diff --git a/umn/source/_static/images/en-us_image_0214585309.png b/umn/source/_static/images/en-us_image_0000001818823278.png similarity index 100% rename from umn/source/_static/images/en-us_image_0214585309.png rename to umn/source/_static/images/en-us_image_0000001818823278.png diff --git a/umn/source/_static/images/en-us_image_0000001626576382.png b/umn/source/_static/images/en-us_image_0000001818823286.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626576382.png rename to umn/source/_static/images/en-us_image_0000001818823286.png diff --git a/umn/source/_static/images/en-us_image_0000001626576858.png b/umn/source/_static/images/en-us_image_0000001818823302.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626576858.png rename to umn/source/_static/images/en-us_image_0000001818823302.png diff --git a/umn/source/_static/images/en-us_image_0129304042.png b/umn/source/_static/images/en-us_image_0000001818823318.png similarity index 100% rename from umn/source/_static/images/en-us_image_0129304042.png rename to umn/source/_static/images/en-us_image_0000001818823318.png diff --git a/umn/source/_static/images/en-us_image_0000001626578706.png b/umn/source/_static/images/en-us_image_0000001818823338.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626578706.png rename to umn/source/_static/images/en-us_image_0000001818823338.png diff --git a/umn/source/_static/images/en-us_image_0152727234.png b/umn/source/_static/images/en-us_image_0000001818823370.png similarity index 100% rename from umn/source/_static/images/en-us_image_0152727234.png rename to umn/source/_static/images/en-us_image_0000001818823370.png diff --git a/umn/source/_static/images/en-us_image_0274115599.png b/umn/source/_static/images/en-us_image_0000001818823374.png similarity index 100% rename from umn/source/_static/images/en-us_image_0274115599.png rename to umn/source/_static/images/en-us_image_0000001818823374.png diff --git a/umn/source/_static/images/en-us_image_0000001626734158.png b/umn/source/_static/images/en-us_image_0000001818823378.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626734158.png rename to umn/source/_static/images/en-us_image_0000001818823378.png diff --git a/umn/source/_static/images/en-us_image_0152668782.png b/umn/source/_static/images/en-us_image_0000001818823386.png similarity index 100% rename from umn/source/_static/images/en-us_image_0152668782.png rename to umn/source/_static/images/en-us_image_0000001818823386.png diff --git a/umn/source/_static/images/en-us_image_0000001627174280.png b/umn/source/_static/images/en-us_image_0000001818823394.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627174280.png rename to umn/source/_static/images/en-us_image_0000001818823394.png diff --git a/umn/source/_static/images/en-us_image_0000001626734162.png b/umn/source/_static/images/en-us_image_0000001818823402.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626734162.png rename to umn/source/_static/images/en-us_image_0000001818823402.png diff --git a/umn/source/_static/images/en-us_image_0000001626734166.png b/umn/source/_static/images/en-us_image_0000001818823406.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626734166.png rename to umn/source/_static/images/en-us_image_0000001818823406.png diff --git a/umn/source/_static/images/en-us_image_0191588554.png b/umn/source/_static/images/en-us_image_0000001818823446.png similarity index 100% rename from umn/source/_static/images/en-us_image_0191588554.png rename to umn/source/_static/images/en-us_image_0000001818823446.png diff --git a/umn/source/_static/images/en-us_image_0000001626734174.png b/umn/source/_static/images/en-us_image_0000001818823450.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626734174.png rename to umn/source/_static/images/en-us_image_0000001818823450.png diff --git a/umn/source/_static/images/en-us_image_0000001197228903.png b/umn/source/_static/images/en-us_image_0000001818823514.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001197228903.png rename to umn/source/_static/images/en-us_image_0000001818823514.png diff --git a/umn/source/_static/images/en-us_image_0171311823.png b/umn/source/_static/images/en-us_image_0000001818823522.png similarity index 100% rename from umn/source/_static/images/en-us_image_0171311823.png rename to umn/source/_static/images/en-us_image_0000001818823522.png diff --git a/umn/source/_static/images/en-us_image_0000001818823594.png b/umn/source/_static/images/en-us_image_0000001818823594.png new file mode 100644 index 0000000..ebc4d6f Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001818823594.png differ diff --git a/umn/source/_static/images/en-us_image_0000001464757610.png b/umn/source/_static/images/en-us_image_0000001818823598.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001464757610.png rename to umn/source/_static/images/en-us_image_0000001818823598.png diff --git a/umn/source/_static/images/en-us_image_0167839112.png b/umn/source/_static/images/en-us_image_0000001818823602.png similarity index 100% rename from umn/source/_static/images/en-us_image_0167839112.png rename to umn/source/_static/images/en-us_image_0000001818823602.png diff --git a/umn/source/_static/images/en-us_image_0162336264.png b/umn/source/_static/images/en-us_image_0000001818823626.png similarity index 100% rename from umn/source/_static/images/en-us_image_0162336264.png rename to umn/source/_static/images/en-us_image_0000001818823626.png diff --git a/umn/source/_static/images/en-us_image_0000001512701025.png b/umn/source/_static/images/en-us_image_0000001818823678.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001512701025.png rename to umn/source/_static/images/en-us_image_0000001818823678.png diff --git a/umn/source/_static/images/en-us_image_0000001209321492.png b/umn/source/_static/images/en-us_image_0000001818823702.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001209321492.png rename to umn/source/_static/images/en-us_image_0000001818823702.png diff --git a/umn/source/_static/images/en-us_image_0000001626735566.png b/umn/source/_static/images/en-us_image_0000001818823714.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626735566.png rename to umn/source/_static/images/en-us_image_0000001818823714.png diff --git a/umn/source/_static/images/en-us_image_0000001626735570.png b/umn/source/_static/images/en-us_image_0000001818823738.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626735570.png rename to umn/source/_static/images/en-us_image_0000001818823738.png diff --git a/umn/source/_static/images/en-us_image_0162329244.png b/umn/source/_static/images/en-us_image_0000001818823762.png similarity index 100% rename from umn/source/_static/images/en-us_image_0162329244.png rename to umn/source/_static/images/en-us_image_0000001818823762.png diff --git a/umn/source/_static/images/en-us_image_0000001626736198.png b/umn/source/_static/images/en-us_image_0000001818823766.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626736198.png rename to umn/source/_static/images/en-us_image_0000001818823766.png diff --git a/umn/source/_static/images/en-us_image_0000001796404809.png b/umn/source/_static/images/en-us_image_0000001818823770.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001796404809.png rename to umn/source/_static/images/en-us_image_0000001818823770.png diff --git a/umn/source/_static/images/en-us_image_0000001626736678.png b/umn/source/_static/images/en-us_image_0000001818823798.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626736678.png rename to umn/source/_static/images/en-us_image_0000001818823798.png diff --git a/umn/source/_static/images/en-us_image_0000001117669524.png b/umn/source/_static/images/en-us_image_0000001818823830.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001117669524.png rename to umn/source/_static/images/en-us_image_0000001818823830.png diff --git a/umn/source/_static/images/en-us_image_0000001429973081.png b/umn/source/_static/images/en-us_image_0000001818982734.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001429973081.png rename to umn/source/_static/images/en-us_image_0000001818982734.png diff --git a/umn/source/_static/images/en-us_image_0000001570070841.png b/umn/source/_static/images/en-us_image_0000001818982758.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001570070841.png rename to umn/source/_static/images/en-us_image_0000001818982758.png diff --git a/umn/source/_static/images/en-us_image_0000001626736794.png b/umn/source/_static/images/en-us_image_0000001818982762.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626736794.png rename to umn/source/_static/images/en-us_image_0000001818982762.png diff --git a/umn/source/_static/images/en-us_image_0000001461263993.png b/umn/source/_static/images/en-us_image_0000001818982794.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001461263993.png rename to umn/source/_static/images/en-us_image_0000001818982794.png diff --git a/umn/source/_static/images/en-us_image_0000001626738526.png b/umn/source/_static/images/en-us_image_0000001818982798.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626738526.png rename to umn/source/_static/images/en-us_image_0000001818982798.png diff --git a/umn/source/_static/images/en-us_image_0000001626894086.png b/umn/source/_static/images/en-us_image_0000001818982822.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626894086.png rename to umn/source/_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/_static/images/en-us_image_0000001626894090.png b/umn/source/_static/images/en-us_image_0000001818982826.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626894090.png rename to umn/source/_static/images/en-us_image_0000001818982826.png diff --git a/umn/source/_static/images/en-us_image_0000001626894094.png b/umn/source/_static/images/en-us_image_0000001818982830.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626894094.png rename to umn/source/_static/images/en-us_image_0000001818982830.png diff --git a/umn/source/_static/images/en-us_image_0142360094.png b/umn/source/_static/images/en-us_image_0000001818982838.png similarity index 100% rename from umn/source/_static/images/en-us_image_0142360094.png rename to umn/source/_static/images/en-us_image_0000001818982838.png diff --git a/umn/source/_static/images/en-us_image_0000001626894098.png b/umn/source/_static/images/en-us_image_0000001818982846.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626894098.png rename to umn/source/_static/images/en-us_image_0000001818982846.png diff --git a/umn/source/_static/images/en-us_image_0000001626894106.png b/umn/source/_static/images/en-us_image_0000001818982858.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626894106.png rename to umn/source/_static/images/en-us_image_0000001818982858.png diff --git a/umn/source/_static/images/en-us_image_0000001626894110.png b/umn/source/_static/images/en-us_image_0000001818982866.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626894110.png rename to umn/source/_static/images/en-us_image_0000001818982866.png diff --git a/umn/source/_static/images/en-us_image_0000001254335981.png b/umn/source/_static/images/en-us_image_0000001818982898.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001254335981.png rename to umn/source/_static/images/en-us_image_0000001818982898.png diff --git a/umn/source/_static/images/en-us_image_0000001207699446.png b/umn/source/_static/images/en-us_image_0000001818982906.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001207699446.png rename to umn/source/_static/images/en-us_image_0000001818982906.png diff --git a/umn/source/_static/images/en-us_image_0000001626895486.png b/umn/source/_static/images/en-us_image_0000001818982918.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626895486.png rename to umn/source/_static/images/en-us_image_0000001818982918.png diff --git a/umn/source/_static/images/en-us_image_0000001281210233.png b/umn/source/_static/images/en-us_image_0000001818982930.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001281210233.png rename to umn/source/_static/images/en-us_image_0000001818982930.png diff --git a/umn/source/_static/images/en-us_image_0000001225081545.png b/umn/source/_static/images/en-us_image_0000001818982934.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001225081545.png rename to umn/source/_static/images/en-us_image_0000001818982934.png diff --git a/umn/source/_static/images/en-us_image_0000001699135873.png b/umn/source/_static/images/en-us_image_0000001818982946.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001699135873.png rename to umn/source/_static/images/en-us_image_0000001818982946.png diff --git a/umn/source/_static/images/en-us_image_0162335382.png b/umn/source/_static/images/en-us_image_0000001818982962.png similarity index 100% rename from umn/source/_static/images/en-us_image_0162335382.png rename to umn/source/_static/images/en-us_image_0000001818982962.png diff --git a/umn/source/_static/images/en-us_image_0000001626896590.png b/umn/source/_static/images/en-us_image_0000001818982974.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626896590.png rename to umn/source/_static/images/en-us_image_0000001818982974.png diff --git a/umn/source/_static/images/en-us_image_0000001512591549.png b/umn/source/_static/images/en-us_image_0000001818983018.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001512591549.png rename to umn/source/_static/images/en-us_image_0000001818983018.png diff --git a/umn/source/_static/images/en-us_image_0000001626897562.png b/umn/source/_static/images/en-us_image_0000001818983026.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001626897562.png rename to umn/source/_static/images/en-us_image_0000001818983026.png diff --git a/umn/source/_static/images/en-us_image_0000001856641285.png b/umn/source/_static/images/en-us_image_0000001818983038.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001856641285.png rename to umn/source/_static/images/en-us_image_0000001818983038.png diff --git a/umn/source/_static/images/en-us_image_0000001627052380.png b/umn/source/_static/images/en-us_image_0000001818983042.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627052380.png rename to umn/source/_static/images/en-us_image_0000001818983042.png diff --git a/umn/source/_static/images/en-us_image_0000001515644737.png b/umn/source/_static/images/en-us_image_0000001818983054.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001515644737.png rename to umn/source/_static/images/en-us_image_0000001818983054.png diff --git a/umn/source/_static/images/en-us_image_0214585308.png b/umn/source/_static/images/en-us_image_0000001818983066.png similarity index 100% rename from umn/source/_static/images/en-us_image_0214585308.png rename to umn/source/_static/images/en-us_image_0000001818983066.png diff --git a/umn/source/_static/images/en-us_image_0000001627054054.png b/umn/source/_static/images/en-us_image_0000001818983162.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627054054.png rename to umn/source/_static/images/en-us_image_0000001818983162.png diff --git a/umn/source/_static/images/en-us_image_0118499140.png b/umn/source/_static/images/en-us_image_0000001818983170.png similarity index 100% rename from umn/source/_static/images/en-us_image_0118499140.png rename to umn/source/_static/images/en-us_image_0000001818983170.png diff --git a/umn/source/_static/images/en-us_image_0000001627054058.png b/umn/source/_static/images/en-us_image_0000001818983174.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627054058.png rename to umn/source/_static/images/en-us_image_0000001818983174.png diff --git a/umn/source/_static/images/en-us_image_0000001627653972.png b/umn/source/_static/images/en-us_image_0000001818983182.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627653972.png rename to umn/source/_static/images/en-us_image_0000001818983182.png diff --git a/umn/source/_static/images/en-us_image_0000001627334080.png b/umn/source/_static/images/en-us_image_0000001818983186.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627334080.png rename to umn/source/_static/images/en-us_image_0000001818983186.png diff --git a/umn/source/_static/images/en-us_image_0000001627054062.png b/umn/source/_static/images/en-us_image_0000001818983190.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627054062.png rename to umn/source/_static/images/en-us_image_0000001818983190.png diff --git a/umn/source/_static/images/en-us_image_0000001465124712.png b/umn/source/_static/images/en-us_image_0000001818983194.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001465124712.png rename to umn/source/_static/images/en-us_image_0000001818983194.png diff --git a/umn/source/_static/images/en-us_image_0000001627054074.png b/umn/source/_static/images/en-us_image_0000001818983198.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627054074.png rename to umn/source/_static/images/en-us_image_0000001818983198.png diff --git a/umn/source/_static/images/en-us_image_0209577986.png b/umn/source/_static/images/en-us_image_0000001818983218.png similarity index 100% rename from umn/source/_static/images/en-us_image_0209577986.png rename to umn/source/_static/images/en-us_image_0000001818983218.png diff --git a/umn/source/_static/images/en-us_image_0191594527.png b/umn/source/_static/images/en-us_image_0000001818983242.png similarity index 100% rename from umn/source/_static/images/en-us_image_0191594527.png rename to umn/source/_static/images/en-us_image_0000001818983242.png diff --git a/umn/source/_static/images/en-us_image_0000001627054082.png b/umn/source/_static/images/en-us_image_0000001818983298.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627054082.png rename to umn/source/_static/images/en-us_image_0000001818983298.png diff --git a/umn/source/_static/images/en-us_image_0000001627055450.png b/umn/source/_static/images/en-us_image_0000001818983374.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627055450.png rename to umn/source/_static/images/en-us_image_0000001818983374.png diff --git a/umn/source/_static/images/en-us_image_0000001818983398.png b/umn/source/_static/images/en-us_image_0000001818983398.png new file mode 100644 index 0000000..f3053c0 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001818983398.png differ diff --git a/umn/source/_static/images/en-us_image_0000001627055454.png b/umn/source/_static/images/en-us_image_0000001818983406.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627055454.png rename to umn/source/_static/images/en-us_image_0000001818983406.png diff --git a/umn/source/_static/images/en-us_image_0000001627056086.png b/umn/source/_static/images/en-us_image_0000001818983414.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627056086.png rename to umn/source/_static/images/en-us_image_0000001818983414.png diff --git a/umn/source/_static/images/en-us_image_0000001627056574.png b/umn/source/_static/images/en-us_image_0000001818983426.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627056574.png rename to umn/source/_static/images/en-us_image_0000001818983426.png diff --git a/umn/source/_static/images/en-us_image_0000001209777270.png b/umn/source/_static/images/en-us_image_0000001818983474.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001209777270.png rename to umn/source/_static/images/en-us_image_0000001818983474.png diff --git a/umn/source/_static/images/en-us_image_0000001627056686.png b/umn/source/_static/images/en-us_image_0000001818983486.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627056686.png rename to umn/source/_static/images/en-us_image_0000001818983486.png diff --git a/umn/source/_static/images/en-us_image_0000001627744152.png b/umn/source/_static/images/en-us_image_0000001818983494.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627744152.png rename to umn/source/_static/images/en-us_image_0000001818983494.png diff --git a/umn/source/_static/images/en-us_image_0000001646961692.png b/umn/source/_static/images/en-us_image_0000001818983506.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001646961692.png rename to umn/source/_static/images/en-us_image_0000001818983506.png diff --git a/umn/source/_static/images/en-us_image_0000001675254013.png b/umn/source/_static/images/en-us_image_0000001818983610.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675254013.png rename to umn/source/_static/images/en-us_image_0000001818983610.png diff --git a/umn/source/_static/images/en-us_image_0000001832479012.png b/umn/source/_static/images/en-us_image_0000001832479012.png new file mode 100644 index 0000000..2fb3fb2 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001832479012.png differ diff --git a/umn/source/_static/images/en-us_image_0000001602035305.png b/umn/source/_static/images/en-us_image_0000001865582513.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001602035305.png rename to umn/source/_static/images/en-us_image_0000001865582513.png diff --git a/umn/source/_static/images/en-us_image_0000001163949251.png b/umn/source/_static/images/en-us_image_0000001865582577.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001163949251.png rename to umn/source/_static/images/en-us_image_0000001865582577.png diff --git a/umn/source/_static/images/en-us_image_0000001675254017.png b/umn/source/_static/images/en-us_image_0000001865582585.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675254017.png rename to umn/source/_static/images/en-us_image_0000001865582585.png diff --git a/umn/source/_static/images/en-us_image_0000001675254021.png b/umn/source/_static/images/en-us_image_0000001865582593.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675254021.png rename to umn/source/_static/images/en-us_image_0000001865582593.png diff --git a/umn/source/_static/images/en-us_image_0211560998.png b/umn/source/_static/images/en-us_image_0000001865582617.png similarity index 100% rename from umn/source/_static/images/en-us_image_0211560998.png rename to umn/source/_static/images/en-us_image_0000001865582617.png diff --git a/umn/source/_static/images/en-us_image_0284993717.png b/umn/source/_static/images/en-us_image_0000001865582629.png similarity index 100% rename from umn/source/_static/images/en-us_image_0284993717.png rename to umn/source/_static/images/en-us_image_0000001865582629.png diff --git a/umn/source/_static/images/en-us_image_0000001675254033.png b/umn/source/_static/images/en-us_image_0000001865582633.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675254033.png rename to umn/source/_static/images/en-us_image_0000001865582633.png diff --git a/umn/source/_static/images/en-us_image_0000001675255405.png b/umn/source/_static/images/en-us_image_0000001865582665.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675255405.png rename to umn/source/_static/images/en-us_image_0000001865582665.png diff --git a/umn/source/_static/images/en-us_image_0000001675256029.png b/umn/source/_static/images/en-us_image_0000001865582673.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675256029.png rename to umn/source/_static/images/en-us_image_0000001865582673.png diff --git a/umn/source/_static/images/en-us_image_0000001237328110.png b/umn/source/_static/images/en-us_image_0000001865582677.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001237328110.png rename to umn/source/_static/images/en-us_image_0000001865582677.png diff --git a/umn/source/_static/images/en-us_image_0000001675256529.png b/umn/source/_static/images/en-us_image_0000001865582681.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675256529.png rename to umn/source/_static/images/en-us_image_0000001865582681.png diff --git a/umn/source/_static/images/en-us_image_0000001675256657.png b/umn/source/_static/images/en-us_image_0000001865582701.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675256657.png rename to umn/source/_static/images/en-us_image_0000001865582701.png diff --git a/umn/source/_static/images/en-us_image_0000001675258381.png b/umn/source/_static/images/en-us_image_0000001865582721.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675258381.png rename to umn/source/_static/images/en-us_image_0000001865582721.png diff --git a/umn/source/_static/images/en-us_image_0000001675258889.png b/umn/source/_static/images/en-us_image_0000001865582729.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675258889.png rename to umn/source/_static/images/en-us_image_0000001865582729.png diff --git a/umn/source/_static/images/en-us_image_0000001675373901.png b/umn/source/_static/images/en-us_image_0000001865582809.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675373901.png rename to umn/source/_static/images/en-us_image_0000001865582809.png diff --git a/umn/source/_static/images/en-us_image_0000001675373905.png b/umn/source/_static/images/en-us_image_0000001865582817.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675373905.png rename to umn/source/_static/images/en-us_image_0000001865582817.png diff --git a/umn/source/_static/images/en-us_image_0000001675373909.png b/umn/source/_static/images/en-us_image_0000001865582825.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675373909.png rename to umn/source/_static/images/en-us_image_0000001865582825.png diff --git a/umn/source/_static/images/en-us_image_0000001675373913.png b/umn/source/_static/images/en-us_image_0000001865582893.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675373913.png rename to umn/source/_static/images/en-us_image_0000001865582893.png diff --git a/umn/source/_static/images/en-us_image_0191544038.png b/umn/source/_static/images/en-us_image_0000001865582905.png similarity index 100% rename from umn/source/_static/images/en-us_image_0191544038.png rename to umn/source/_static/images/en-us_image_0000001865582905.png diff --git a/umn/source/_static/images/en-us_image_0000001675373917.png b/umn/source/_static/images/en-us_image_0000001865582933.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675373917.png rename to umn/source/_static/images/en-us_image_0000001865582933.png diff --git a/umn/source/_static/images/en-us_image_0093507575.png b/umn/source/_static/images/en-us_image_0000001865582937.png similarity index 100% rename from umn/source/_static/images/en-us_image_0093507575.png rename to umn/source/_static/images/en-us_image_0000001865582937.png diff --git a/umn/source/_static/images/en-us_image_0285048674.png b/umn/source/_static/images/en-us_image_0000001865582941.png similarity index 100% rename from umn/source/_static/images/en-us_image_0285048674.png rename to umn/source/_static/images/en-us_image_0000001865582941.png diff --git a/umn/source/_static/images/en-us_image_0000001675375297.png b/umn/source/_static/images/en-us_image_0000001865582981.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675375297.png rename to umn/source/_static/images/en-us_image_0000001865582981.png diff --git a/umn/source/_static/images/en-us_image_0000001675375405.png b/umn/source/_static/images/en-us_image_0000001865582989.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675375405.png rename to umn/source/_static/images/en-us_image_0000001865582989.png diff --git a/umn/source/_static/images/en-us_image_0000001675378241.png b/umn/source/_static/images/en-us_image_0000001865583133.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675378241.png rename to umn/source/_static/images/en-us_image_0000001865583133.png diff --git a/umn/source/_static/images/en-us_image_0000001865583153.png b/umn/source/_static/images/en-us_image_0000001865583153.png new file mode 100644 index 0000000..53878c8 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001865583153.png differ diff --git a/umn/source/_static/images/en-us_image_0000001675413821.png b/umn/source/_static/images/en-us_image_0000001865583165.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675413821.png rename to umn/source/_static/images/en-us_image_0000001865583165.png diff --git a/umn/source/_static/images/en-us_image_0000001675413825.png b/umn/source/_static/images/en-us_image_0000001865583185.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675413825.png rename to umn/source/_static/images/en-us_image_0000001865583185.png diff --git a/umn/source/_static/images/en-us_image_0000001462622484.png b/umn/source/_static/images/en-us_image_0000001865583217.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001462622484.png rename to umn/source/_static/images/en-us_image_0000001865583217.png diff --git a/umn/source/_static/images/en-us_image_0000001675413829.png b/umn/source/_static/images/en-us_image_0000001865583245.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675413829.png rename to umn/source/_static/images/en-us_image_0000001865583245.png diff --git a/umn/source/_static/images/en-us_image_0157880395.png b/umn/source/_static/images/en-us_image_0000001865583253.png similarity index 100% rename from umn/source/_static/images/en-us_image_0157880395.png rename to umn/source/_static/images/en-us_image_0000001865583253.png diff --git a/umn/source/_static/images/en-us_image_0000001865583269.png b/umn/source/_static/images/en-us_image_0000001865583269.png new file mode 100644 index 0000000..f1f960f Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001865583269.png differ diff --git a/umn/source/_static/images/en-us_image_0000001675413833.png b/umn/source/_static/images/en-us_image_0000001865583297.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675413833.png rename to umn/source/_static/images/en-us_image_0000001865583297.png diff --git a/umn/source/_static/images/en-us_image_0000001337710801.png b/umn/source/_static/images/en-us_image_0000001865583301.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001337710801.png rename to umn/source/_static/images/en-us_image_0000001865583301.png diff --git a/umn/source/_static/images/en-us_image_0000001675413841.png b/umn/source/_static/images/en-us_image_0000001865662721.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675413841.png rename to umn/source/_static/images/en-us_image_0000001865662721.png diff --git a/umn/source/_static/images/en-us_image_0141273034.png b/umn/source/_static/images/en-us_image_0000001865662737.png similarity index 100% rename from umn/source/_static/images/en-us_image_0141273034.png rename to umn/source/_static/images/en-us_image_0000001865662737.png diff --git a/umn/source/_static/images/en-us_image_0000001675413845.png b/umn/source/_static/images/en-us_image_0000001865662745.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675413845.png rename to umn/source/_static/images/en-us_image_0000001865662745.png diff --git a/umn/source/_static/images/en-us_image_0118499144.png b/umn/source/_static/images/en-us_image_0000001865662749.png similarity index 100% rename from umn/source/_static/images/en-us_image_0118499144.png rename to umn/source/_static/images/en-us_image_0000001865662749.png diff --git a/umn/source/_static/images/en-us_image_0162733894.png b/umn/source/_static/images/en-us_image_0000001865662753.png similarity index 100% rename from umn/source/_static/images/en-us_image_0162733894.png rename to umn/source/_static/images/en-us_image_0000001865662753.png diff --git a/umn/source/_static/images/en-us_image_0000001865662757.jpg b/umn/source/_static/images/en-us_image_0000001865662757.jpg new file mode 100644 index 0000000..ad56842 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001865662757.jpg differ diff --git a/umn/source/_static/images/en-us_image_0000001166028070.png b/umn/source/_static/images/en-us_image_0000001865662761.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001166028070.png rename to umn/source/_static/images/en-us_image_0000001865662761.png diff --git a/umn/source/_static/images/en-us_image_0000001675415213.png b/umn/source/_static/images/en-us_image_0000001865662765.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675415213.png rename to umn/source/_static/images/en-us_image_0000001865662765.png diff --git a/umn/source/_static/images/en-us_image_0000001675415841.png b/umn/source/_static/images/en-us_image_0000001865662773.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675415841.png rename to umn/source/_static/images/en-us_image_0000001865662773.png diff --git a/umn/source/_static/images/en-us_image_0284920908.png b/umn/source/_static/images/en-us_image_0000001865662817.png similarity index 100% rename from umn/source/_static/images/en-us_image_0284920908.png rename to umn/source/_static/images/en-us_image_0000001865662817.png diff --git a/umn/source/_static/images/en-us_image_0000001230120807.png b/umn/source/_static/images/en-us_image_0000001865662829.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001230120807.png rename to umn/source/_static/images/en-us_image_0000001865662829.png diff --git a/umn/source/_static/images/en-us_image_0000001521533677.png b/umn/source/_static/images/en-us_image_0000001865662833.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001521533677.png rename to umn/source/_static/images/en-us_image_0000001865662833.png diff --git a/umn/source/_static/images/en-us_image_0000001207827554.png b/umn/source/_static/images/en-us_image_0000001865662841.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001207827554.png rename to umn/source/_static/images/en-us_image_0000001865662841.png diff --git a/umn/source/_static/images/en-us_image_0000001197426329.png b/umn/source/_static/images/en-us_image_0000001865662885.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001197426329.png rename to umn/source/_static/images/en-us_image_0000001865662885.png diff --git a/umn/source/_static/images/en-us_image_0000001675416345.png b/umn/source/_static/images/en-us_image_0000001865662901.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675416345.png rename to umn/source/_static/images/en-us_image_0000001865662901.png diff --git a/umn/source/_static/images/en-us_image_0000001650535960.png b/umn/source/_static/images/en-us_image_0000001865662949.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001650535960.png rename to umn/source/_static/images/en-us_image_0000001865662949.png diff --git a/umn/source/_static/images/en-us_image_0000001540846821.png b/umn/source/_static/images/en-us_image_0000001865662969.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001540846821.png rename to umn/source/_static/images/en-us_image_0000001865662969.png diff --git a/umn/source/_static/images/en-us_image_0000001675418673.png b/umn/source/_static/images/en-us_image_0000001865662989.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675418673.png rename to umn/source/_static/images/en-us_image_0000001865662989.png diff --git a/umn/source/_static/images/en-us_image_0000001675613937.png b/umn/source/_static/images/en-us_image_0000001865663001.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675613937.png rename to umn/source/_static/images/en-us_image_0000001865663001.png diff --git a/umn/source/_static/images/en-us_image_0000001865663033.png b/umn/source/_static/images/en-us_image_0000001865663033.png new file mode 100644 index 0000000..ce84b5c Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001865663033.png differ diff --git a/umn/source/_static/images/en-us_image_0000001675613941.png b/umn/source/_static/images/en-us_image_0000001865663057.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675613941.png rename to umn/source/_static/images/en-us_image_0000001865663057.png diff --git a/umn/source/_static/images/en-us_image_0000001675613945.png b/umn/source/_static/images/en-us_image_0000001865663089.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675613945.png rename to umn/source/_static/images/en-us_image_0000001865663089.png diff --git a/umn/source/_static/images/en-us_image_0275513364.png b/umn/source/_static/images/en-us_image_0000001865663101.png similarity index 100% rename from umn/source/_static/images/en-us_image_0275513364.png rename to umn/source/_static/images/en-us_image_0000001865663101.png diff --git a/umn/source/_static/images/en-us_image_0000001675613953.png b/umn/source/_static/images/en-us_image_0000001865663109.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675613953.png rename to umn/source/_static/images/en-us_image_0000001865663109.png diff --git a/umn/source/_static/images/en-us_image_0152667656.png b/umn/source/_static/images/en-us_image_0000001865663121.png similarity index 100% rename from umn/source/_static/images/en-us_image_0152667656.png rename to umn/source/_static/images/en-us_image_0000001865663121.png diff --git a/umn/source/_static/images/en-us_image_0000001675613957.png b/umn/source/_static/images/en-us_image_0000001865663129.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675613957.png rename to umn/source/_static/images/en-us_image_0000001865663129.png diff --git a/umn/source/_static/images/en-us_image_0000001675813933.png b/umn/source/_static/images/en-us_image_0000001865663133.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675813933.png rename to umn/source/_static/images/en-us_image_0000001865663133.png diff --git a/umn/source/_static/images/en-us_image_0000001627493158.png b/umn/source/_static/images/en-us_image_0000001865663137.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001627493158.png rename to umn/source/_static/images/en-us_image_0000001865663137.png diff --git a/umn/source/_static/images/en-us_image_0000001675615337.png b/umn/source/_static/images/en-us_image_0000001865663157.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675615337.png rename to umn/source/_static/images/en-us_image_0000001865663157.png diff --git a/umn/source/_static/images/en-us_image_0191577030.png b/umn/source/_static/images/en-us_image_0000001865663181.png similarity index 100% rename from umn/source/_static/images/en-us_image_0191577030.png rename to umn/source/_static/images/en-us_image_0000001865663181.png diff --git a/umn/source/_static/images/en-us_image_0209606948.png b/umn/source/_static/images/en-us_image_0000001865663209.png similarity index 100% rename from umn/source/_static/images/en-us_image_0209606948.png rename to umn/source/_static/images/en-us_image_0000001865663209.png diff --git a/umn/source/_static/images/en-us_image_0000001675616433.png b/umn/source/_static/images/en-us_image_0000001865663213.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675616433.png rename to umn/source/_static/images/en-us_image_0000001865663213.png diff --git a/umn/source/_static/images/en-us_image_0000001512876289.png b/umn/source/_static/images/en-us_image_0000001865663449.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001512876289.png rename to umn/source/_static/images/en-us_image_0000001865663449.png diff --git a/umn/source/_static/images/en-us_image_0167840073.png b/umn/source/_static/images/en-us_image_0000001865663453.png similarity index 100% rename from umn/source/_static/images/en-us_image_0167840073.png rename to umn/source/_static/images/en-us_image_0000001865663453.png diff --git a/umn/source/_static/images/en-us_image_0000001675616561.png b/umn/source/_static/images/en-us_image_0000001865663457.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675616561.png rename to umn/source/_static/images/en-us_image_0000001865663457.png diff --git a/umn/source/_static/images/en-us_image_0000001675618277.png b/umn/source/_static/images/en-us_image_0000001865663461.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675618277.png rename to umn/source/_static/images/en-us_image_0000001865663461.png diff --git a/umn/source/_static/images/en-us_image_0000001675619157.png b/umn/source/_static/images/en-us_image_0000001865663473.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001675619157.png rename to umn/source/_static/images/en-us_image_0000001865663473.png diff --git a/umn/source/_static/images/en-us_image_0000001676063997.png b/umn/source/_static/images/en-us_image_0000001865663509.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001676063997.png rename to umn/source/_static/images/en-us_image_0000001865663509.png diff --git a/umn/source/_static/images/en-us_image_0000001681512581.png b/umn/source/_static/images/en-us_image_0000001865663521.png similarity index 100% rename from umn/source/_static/images/en-us_image_0000001681512581.png rename to umn/source/_static/images/en-us_image_0000001865663521.png diff --git a/umn/source/_static/images/en-us_image_0240332622.png b/umn/source/_static/images/en-us_image_0000001865663537.png similarity index 100% rename from umn/source/_static/images/en-us_image_0240332622.png rename to umn/source/_static/images/en-us_image_0000001865663537.png diff --git a/umn/source/_static/images/en-us_image_0000001879005797.png b/umn/source/_static/images/en-us_image_0000001879005797.png new file mode 100644 index 0000000..f620327 Binary files /dev/null and b/umn/source/_static/images/en-us_image_0000001879005797.png differ diff --git a/umn/source/_static/images/en-us_image_0142360062.png b/umn/source/_static/images/en-us_image_0142360062.png deleted file mode 100644 index f5a39cd..0000000 Binary files a/umn/source/_static/images/en-us_image_0142360062.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0162391155.png b/umn/source/_static/images/en-us_image_0162391155.png deleted file mode 100644 index 8dc4f6f..0000000 Binary files a/umn/source/_static/images/en-us_image_0162391155.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0214585307.png b/umn/source/_static/images/en-us_image_0214585307.png deleted file mode 100644 index f5a39cd..0000000 Binary files a/umn/source/_static/images/en-us_image_0214585307.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0233469196.png b/umn/source/_static/images/en-us_image_0233469196.png deleted file mode 100644 index a844ced..0000000 Binary files a/umn/source/_static/images/en-us_image_0233469196.png and /dev/null differ diff --git a/umn/source/_static/images/en-us_image_0233469654.png b/umn/source/_static/images/en-us_image_0233469654.png deleted file mode 100644 index f5a39cd..0000000 Binary files a/umn/source/_static/images/en-us_image_0233469654.png and /dev/null differ diff --git a/umn/source/access_control/differences_between_security_groups_and_firewalls.rst b/umn/source/access_control/differences_between_security_groups_and_firewalls.rst index 07bb377..de9a514 100644 --- a/umn/source/access_control/differences_between_security_groups_and_firewalls.rst +++ b/umn/source/access_control/differences_between_security_groups_and_firewalls.rst @@ -14,7 +14,7 @@ For details, see :ref:`Figure 1 `. .. _en-us_topic_0052003963__fig9582182315479: -.. figure:: /_static/images/en-us_image_0000001699135873.png +.. figure:: /_static/images/en-us_image_0000001818982946.png :alt: **Figure 1** Security groups and firewalls **Figure 1** Security groups and firewalls diff --git a/umn/source/access_control/firewall/firewall_overview.rst b/umn/source/access_control/firewall/firewall_overview.rst index 369179a..e925870 100644 --- a/umn/source/access_control/firewall/firewall_overview.rst +++ b/umn/source/access_control/firewall/firewall_overview.rst @@ -11,7 +11,7 @@ A firewall is an optional layer of security for your subnets. After you associat .. _acl_0001__fig9582182315479: -.. figure:: /_static/images/en-us_image_0000001699135873.png +.. figure:: /_static/images/en-us_image_0000001818982946.png :alt: **Figure 1** Security groups and firewalls **Figure 1** Security groups and firewalls @@ -103,7 +103,7 @@ Configuration Procedure .. _acl_0001__fig1643183218163: -.. figure:: /_static/images/en-us_image_0162335382.png +.. figure:: /_static/images/en-us_image_0000001818982962.png :alt: **Figure 2** firewall configuration procedure **Figure 2** firewall configuration procedure diff --git a/umn/source/access_control/firewall/management_firewall_rules/adding_a_firewall_rule.rst b/umn/source/access_control/firewall/management_firewall_rules/adding_a_firewall_rule.rst index 4f0127b..ffb0801 100644 --- a/umn/source/access_control/firewall/management_firewall_rules/adding_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/management_firewall_rules/adding_a_firewall_rule.rst @@ -36,7 +36,7 @@ Procedure - Locate the row that contains the firewall rule and click **Replicate** in the **Operation** column to replicate an existing rule. - .. figure:: /_static/images/en-us_image_0274115599.png + .. figure:: /_static/images/en-us_image_0000001818823374.png :alt: **Figure 1** Add Inbound Rule **Figure 1** Add Inbound Rule @@ -85,5 +85,5 @@ Procedure 7. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001627054054.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983162.png diff --git a/umn/source/access_control/firewall/management_firewall_rules/changing_the_sequence_of_a_firewall_rule.rst b/umn/source/access_control/firewall/management_firewall_rules/changing_the_sequence_of_a_firewall_rule.rst index f56ccf5..4511c34 100644 --- a/umn/source/access_control/firewall/management_firewall_rules/changing_the_sequence_of_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/management_firewall_rules/changing_the_sequence_of_a_firewall_rule.rst @@ -33,5 +33,5 @@ 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_0000001626894110.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582933.png diff --git a/umn/source/access_control/firewall/management_firewall_rules/deleting_a_firewall_rule.rst b/umn/source/access_control/firewall/management_firewall_rules/deleting_a_firewall_rule.rst index 278b692..93cf3f9 100644 --- a/umn/source/access_control/firewall/management_firewall_rules/deleting_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/management_firewall_rules/deleting_a_firewall_rule.rst @@ -33,5 +33,5 @@ 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_0000001627054082.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823162.png diff --git a/umn/source/access_control/firewall/management_firewall_rules/enabling_or_disabling_a_firewall_rule.rst b/umn/source/access_control/firewall/management_firewall_rules/enabling_or_disabling_a_firewall_rule.rst index 6d66828..7be2761 100644 --- a/umn/source/access_control/firewall/management_firewall_rules/enabling_or_disabling_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/management_firewall_rules/enabling_or_disabling_a_firewall_rule.rst @@ -31,5 +31,5 @@ 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_0000001675254033.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823738.png diff --git a/umn/source/access_control/firewall/management_firewall_rules/modifying_a_firewall_rule.rst b/umn/source/access_control/firewall/management_firewall_rules/modifying_a_firewall_rule.rst index 7f0c707..cfa8eb2 100644 --- a/umn/source/access_control/firewall/management_firewall_rules/modifying_a_firewall_rule.rst +++ b/umn/source/access_control/firewall/management_firewall_rules/modifying_a_firewall_rule.rst @@ -28,7 +28,7 @@ Procedure 6. On the **Inbound Rules** or **Outbound Rules** tab, locate the row that contains the target rule and click **Modify** in the **Operation** column. In the displayed dialog box, configure parameters as prompted. :ref:`Table 1 ` lists the parameters to be configured. - .. figure:: /_static/images/en-us_image_0285048674.png + .. figure:: /_static/images/en-us_image_0000001865582941.png :alt: **Figure 1** Modify Rule **Figure 1** Modify Rule @@ -37,47 +37,47 @@ Procedure .. table:: **Table 1** Parameter descriptions - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Parameter | Description | Example Value | - +========================+========================================================================================================================================================================================+=======================+ - | Type | The firewall type. This parameter is mandatory. You can select a value from the drop-down list. Currently, only **IPv4** and **IPv6** are supported. | IPv4 | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Action | The action in the firewall. This parameter is mandatory. You can select a value from the drop-down list. Currently, the value can be **Allow** or **Deny**. | Allow | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Protocol | The protocol supported by the firewall. This parameter is mandatory. You can select a protocol from the drop-down list. | TCP | - | | | | - | | You can select **TCP**, **UDP**, **ICMP**, or **All**. | | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Source | The source from which the traffic is allowed. The source can be an IP address or IP address range. | 0.0.0.0/0 | - | | | | - | | - IP address: | | - | | | | - | | - Single IP address: 192.168.10.10/32 | | - | | - All IP addresses: 0.0.0.0/0 | | - | | - IP address range: 192.168.1.0/24 | | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Source Port Range | The source port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, **1-100**. | 22, or 22-30 | - | | | | - | | You must specify this parameter if **TCP** or **UDP** is selected for **Protocol**. | | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Destination | The destination to which the traffic is allowed. The destination can be an IP address or IP address range. | 0.0.0.0/0 | - | | | | - | | - IP address: | | - | | | | - | | - Single IP address: 192.168.10.10/32 | | - | | - All IP addresses: 0.0.0.0/0 | | - | | - IP address range: 192.168.1.0/24 | | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Destination Port Range | The destination port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, **1-100**. | 22, or 22-30 | - | | | | - | | You must specify this parameter if **TCP** or **UDP** is selected for **Protocol**. | | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Description | Supplementary information about the firewall rule. This parameter is optional. | N/A | - | | | | - | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Item | Description | Example Value | + +============================+========================================================================================================================================================================================+=======================+ + | Type | Specifies the firewall type. This parameter is mandatory. You can select a value from the drop-down list. Currently, only **IPv4** and **IPv6** are supported. | IPv4 | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Action | Specifies the firewall policy. This parameter is mandatory. You can select a value from the drop-down list. Currently, the value can be **Allow** or **Deny**. | Allow | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Protocol | Specifies the protocol supported by the firewall. This parameter is mandatory. You can select a value from the drop-down list. | TCP | + | | | | + | | You can select **TCP**, **UDP**, **ICMP**, or **All**. | | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Source | The source from which the traffic is allowed. The source can be an IP address or IP address range. | 0.0.0.0/0 | + | | | | + | | - IP address: | | + | | | | + | | - Single IP address: 192.168.10.10/32 | | + | | - All IP addresses: 0.0.0.0/0 | | + | | - IP address range: 192.168.1.0/24 | | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Source Port Range | The source port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, **1-100**. | 22, or 22-30 | + | | | | + | | You must specify this parameter if **TCP** or **UDP** is selected for **Protocol**. | | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Destination | The destination to which the traffic is allowed. The destination can be an IP address or IP address range. | 0.0.0.0/0 | + | | | | + | | - IP address: | | + | | | | + | | - Single IP address: 192.168.10.10/32 | | + | | - All IP addresses: 0.0.0.0/0 | | + | | - IP address range: 192.168.1.0/24 | | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | **Destination Port Range** | The destination port number or port number range. The value ranges from 1 to 65535. For a port number range, enter two port numbers connected by a hyphen (-). For example, **1-100**. | 22, or 22-30 | + | | | | + | | You must specify this parameter if **TCP** or **UDP** is selected for **Protocol**. | | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | Provides supplementary information about the firewall network ACL rule. This parameter is optional. | ``-`` | + | | | | + | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ 7. Click **Confirm**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675613957.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823406.png diff --git a/umn/source/access_control/firewall/managing_firewalls/creating_a_firewall.rst b/umn/source/access_control/firewall/managing_firewalls/creating_a_firewall.rst index 32fdb05..408e08a 100644 --- a/umn/source/access_control/firewall/managing_firewalls/creating_a_firewall.rst +++ b/umn/source/access_control/firewall/managing_firewalls/creating_a_firewall.rst @@ -30,7 +30,7 @@ Procedure 6. On the **Create Firewall** page, configure parameters as prompted. - .. figure:: /_static/images/en-us_image_0129304042.png + .. figure:: /_static/images/en-us_image_0000001818823318.png :alt: **Figure 1** Create Firewall **Figure 1** Create Firewall @@ -51,5 +51,5 @@ Procedure 7. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626574358.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663057.png diff --git a/umn/source/access_control/firewall/managing_firewalls/deleting_a_firewall.rst b/umn/source/access_control/firewall/managing_firewalls/deleting_a_firewall.rst index 057b698..05bc8cd 100644 --- a/umn/source/access_control/firewall/managing_firewalls/deleting_a_firewall.rst +++ b/umn/source/access_control/firewall/managing_firewalls/deleting_a_firewall.rst @@ -31,5 +31,5 @@ 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_0000001675613953.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982830.png diff --git a/umn/source/access_control/firewall/managing_firewalls/enabling_or_disabling_a_firewall.rst b/umn/source/access_control/firewall/managing_firewalls/enabling_or_disabling_a_firewall.rst index 60c71ff..4475948 100644 --- a/umn/source/access_control/firewall/managing_firewalls/enabling_or_disabling_a_firewall.rst +++ b/umn/source/access_control/firewall/managing_firewalls/enabling_or_disabling_a_firewall.rst @@ -29,5 +29,5 @@ 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_0000001626894106.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823714.png diff --git a/umn/source/access_control/firewall/managing_firewalls/modifying_a_firewall.rst b/umn/source/access_control/firewall/managing_firewalls/modifying_a_firewall.rst index e201d2b..62144fe 100644 --- a/umn/source/access_control/firewall/managing_firewalls/modifying_a_firewall.rst +++ b/umn/source/access_control/firewall/managing_firewalls/modifying_a_firewall.rst @@ -33,7 +33,7 @@ Procedure 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_0000001675413841.png -.. |image3| image:: /_static/images/en-us_image_0142359884.png -.. |image4| image:: /_static/images/en-us_image_0142359884.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983494.png +.. |image3| image:: /_static/images/en-us_image_0000001865583253.png +.. |image4| image:: /_static/images/en-us_image_0000001865583253.png diff --git a/umn/source/access_control/firewall/managing_firewalls/viewing_a_firewall.rst b/umn/source/access_control/firewall/managing_firewalls/viewing_a_firewall.rst index eb2ded4..cc23223 100644 --- a/umn/source/access_control/firewall/managing_firewalls/viewing_a_firewall.rst +++ b/umn/source/access_control/firewall/managing_firewalls/viewing_a_firewall.rst @@ -27,5 +27,5 @@ Procedure 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_0000001675373917.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865662773.png diff --git a/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/associating_subnets_with_a_firewall.rst b/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/associating_subnets_with_a_firewall.rst index b6cd722..4faccce 100644 --- a/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/associating_subnets_with_a_firewall.rst +++ b/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/associating_subnets_with_a_firewall.rst @@ -41,5 +41,5 @@ Procedure A subnet with a firewall 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_0000001626734158.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823450.png diff --git a/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/disassociating_subnets_from_a_firewall.rst b/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/disassociating_subnets_from_a_firewall.rst index b850868..baa0ab5 100644 --- a/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/disassociating_subnets_from_a_firewall.rst +++ b/umn/source/access_control/firewall/managing_subnets_associated_with_a_firewall/disassociating_subnets_from_a_firewall.rst @@ -35,5 +35,5 @@ Procedure Select multiple subnets and click **Disassociate** above the subnet list to disassociate the subnets from the firewall at a time. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675413845.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818822962.png diff --git a/umn/source/access_control/security_group/default_security_group_and_its_rules.rst b/umn/source/access_control/security_group/default_security_group_and_its_rules.rst index 3a210c8..805837a 100644 --- a/umn/source/access_control/security_group/default_security_group_and_its_rules.rst +++ b/umn/source/access_control/security_group/default_security_group_and_its_rules.rst @@ -11,7 +11,7 @@ If you have not created any security groups yet, the system automatically create - Outbound rules allow all outbound traffic and response traffic to the outbound requests. -.. figure:: /_static/images/en-us_image_0000001230120807.png +.. figure:: /_static/images/en-us_image_0000001865662829.png :alt: **Figure 1** Default security group **Figure 1** Default security group diff --git a/umn/source/access_control/security_group/managing_a_security_group/cloning_a_security_group.rst b/umn/source/access_control/security_group/managing_a_security_group/cloning_a_security_group.rst index 6d6690a..327dddd 100644 --- a/umn/source/access_control/security_group/managing_a_security_group/cloning_a_security_group.rst +++ b/umn/source/access_control/security_group/managing_a_security_group/cloning_a_security_group.rst @@ -46,7 +46,7 @@ Procedure #. Select the region and name of the new security group as prompted. - .. figure:: /_static/images/en-us_image_0000001602035305.png + .. figure:: /_static/images/en-us_image_0000001865582513.png :alt: **Figure 1** Clone Security Group **Figure 1** Clone Security Group @@ -55,5 +55,5 @@ Procedure 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_0000001675373901.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982762.png diff --git a/umn/source/access_control/security_group/managing_a_security_group/creating_a_security_group.rst b/umn/source/access_control/security_group/managing_a_security_group/creating_a_security_group.rst index 6395801..159865a 100644 --- a/umn/source/access_control/security_group/managing_a_security_group/creating_a_security_group.rst +++ b/umn/source/access_control/security_group/managing_a_security_group/creating_a_security_group.rst @@ -14,61 +14,6 @@ If your instances have different Internet access requirements, you can allocate Each ECS must be associated with at least one security group. If you do not have a security group when creating an ECS, the system provides a default security group. -Security Group Templates ------------------------- - -The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. :ref:`Table 1 ` describes the security group templates. - -.. _en-us_topic_0013748715__table117828131111: - -.. table:: **Table 1** Security group templates - - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Template | Direction | Protocol/Port/Type | Source/Destination | Description | Application Scenario | - +============================+===========+==========================+====================+===================================================================================================================================+============================================================================================================================================================================================================================+ - | General-purpose web server | Inbound | TCP: 22 (IPv4) | 0.0.0.0/0 | Allows all IPv4 addresses to access ECSs in the security group over port 22 (SSH) for remotely logging in to Linux ECSs. | - Remotely log in to ECSs. | - | | | | | | - Use the ping command to test ECS connectivity. | - | | | | | | - ECSs functioning as web servers provide website access services. | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | | TCP: 3389 (IPv4) | 0.0.0.0/0 | Allows all IPv4 addresses to access ECSs in the security group over port 3389 (RDP) for remotely logging in to Windows ECSs. | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | | TCP: 80 (IPv4) | 0.0.0.0/0 | Allows all IPv4 addresses to access ECSs in the security group over port 80 (HTTP) for visiting websites. | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | | TCP: 443 (IPv4) | 0.0.0.0/0 | Allows all IPv4 addresses to access ECSs in the security group over port 443 (HTTPS) for visiting websites. | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | | ICMP: All (IPv4) | 0.0.0.0/0 | Allows all IPv4 addresses to access ECSs in the security group over any port for using the ping command to test ECS connectivity. | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | | All (IPv4) | sg-xxx | Allows ECSs in the security group to communicate with each other. | | - | | | | | | | - | | | All (IPv6) | | | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Outbound | All (IPv4) | 0.0.0.0/0 | Allows access from ECSs in the security group to any IP address over any port. | | - | | | | | | | - | | | All (IPv6) | | | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | All ports open | Inbound | All (IPv4) | sg-xxx | Allows ECSs in the security group to communicate with each other. | Opening all ECS ports in a security group poses security risks. | - | | | | | | | - | | | All (IPv6) | | | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | | All (IPv4) | 0.0.0.0/0 | Allows all IP addresses to access ECSs in the security group over any port. | | - | | | | | | | - | | | All (IPv6) | | | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Outbound | All (IPv4) | 0.0.0.0/0 | Allows access from ECSs in the security group to any IP address over any port. | | - | | | | | | | - | | | All (IPv6) | | | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Fast-add rule | Inbound | All (IPv4) | sg-xxx | Allows ECSs in the security group to communicate with each other. | You can select protocols and ports that the inbound rule will apply to. | - | | | | | | | - | | | All (IPv6) | | | If you do not select any protocols and ports, no protocols and ports will be opened. After the security group is created, add required rules by referring to :ref:`Adding a Security Group Rule `. | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | | Custom port and protocol | 0.0.0.0/0 | Allows all IP addresses to access ECSs in a security group over specified ports (TCP or ICMP) for different purposes. | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | | Outbound | All (IPv4) | 0.0.0.0/0 | Allows access from ECSs in the security group to any IP address over any port. | | - | | | | | | | - | | | All (IPv6) | ::/0 | | | - +----------------------------+-----------+--------------------------+--------------------+-----------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - Notes and Constraints --------------------- @@ -98,52 +43,48 @@ Procedure #. Configure the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001197426329.png + .. figure:: /_static/images/en-us_image_0000001865662885.png :alt: **Figure 1** Create Security Group **Figure 1** Create Security Group - .. table:: **Table 2** Parameter description + .. 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 | - | | | | - | | The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. | | - | | | | - | | :ref:`Table 1 ` describes the security group templates. | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | Description | Optional | N/A | - | | | | - | | Supplementary information about the security group. This parameter is optional. | | - | | | | - | | The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | 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**. -Related Operations ------------------- - -- After a security group is created, if its rules cannot meet your service requirements, you can add new rules to the security group or modify original rules. For details, see :ref:`Adding a Security Group Rule `. -- Each ECS must be associated with at least one security group. You can add an ECS to multiple security groups based on service requirements. For details, see :ref:`Adding an Instance to or Removing an Instance from a Security Group `. - -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001627054062.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582681.png diff --git a/umn/source/access_control/security_group/managing_a_security_group/deleting_a_security_group.rst b/umn/source/access_control/security_group/managing_a_security_group/deleting_a_security_group.rst index c288840..8a2f5ff 100644 --- a/umn/source/access_control/security_group/managing_a_security_group/deleting_a_security_group.rst +++ b/umn/source/access_control/security_group/managing_a_security_group/deleting_a_security_group.rst @@ -44,5 +44,5 @@ Procedure #. Confirm the information and click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626574362.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982846.png diff --git a/umn/source/access_control/security_group/managing_a_security_group/modifying_a_security_group.rst b/umn/source/access_control/security_group/managing_a_security_group/modifying_a_security_group.rst index 5a6798e..d638c34 100644 --- a/umn/source/access_control/security_group/managing_a_security_group/modifying_a_security_group.rst +++ b/umn/source/access_control/security_group/managing_a_security_group/modifying_a_security_group.rst @@ -33,5 +33,5 @@ Procedure #. Click **OK** to save the modification. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626894086.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982918.png diff --git a/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst b/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst index e24950e..b5638f1 100644 --- a/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst +++ b/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/adding_an_instance_to_or_removing_an_instance_from_a_security_group.rst @@ -78,7 +78,7 @@ 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_0000001627054058.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001626734162.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982974.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001865582721.png diff --git a/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/changing_the_security_group_of_an_ecs.rst b/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/changing_the_security_group_of_an_ecs.rst index 4467f82..3552b46 100644 --- a/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/changing_the_security_group_of_an_ecs.rst +++ b/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/changing_the_security_group_of_an_ecs.rst @@ -17,28 +17,29 @@ Procedure #. Click |image1| in the upper left corner and select your region and project. -#. Under **Computing**, click **Elastic Cloud Server**. +#. Click |image2| and choose **Computing** > **Elastic Cloud Server**. -#. In the ECS list, locate the row that contains the target ECS. Click **More** in the **Operation** column and select **Manage Network** > **Change Security Group**. +#. In the ECS list, choose **More** > **Manage Network** > **Change Security Group** in the **Operation** column. The **Change Security Group** dialog box is displayed. - .. figure:: /_static/images/en-us_image_0162733894.png - :alt: **Figure 1** Change Security Group + .. figure:: /_static/images/en-us_image_0000001865662753.png + :alt: **Figure 1** Changing a security group - **Figure 1** Change Security Group + **Figure 1** Changing a security group #. Select the target NIC and security groups. - You can select multiple security groups. In such a case, the rules of all the selected security groups will be aggregated to apply on the ECS. + You can select multiple security groups. In such a case, the access rules of all the selected security groups apply to the ECS. To create a security group, click **Create Security Group**. .. note:: - Using multiple security groups may deteriorate ECS network performance. You are suggested to select no more than five security groups. + Using multiple security groups may deteriorate ECS network performance. We recommend that you associate no more than five security groups with each ECS. #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0093507575.png +.. |image1| image:: /_static/images/en-us_image_0000001818823030.png +.. |image2| image:: /_static/images/en-us_image_0000001865662757.jpg diff --git a/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/viewing_the_security_group_of_an_ecs.rst b/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/viewing_the_security_group_of_an_ecs.rst index 2abb587..7a4af4d 100644 --- a/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/viewing_the_security_group_of_an_ecs.rst +++ b/umn/source/access_control/security_group/managing_instances_associated_with_a_security_group/viewing_the_security_group_of_an_ecs.rst @@ -29,5 +29,5 @@ 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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982866.png diff --git a/umn/source/access_control/security_group/managing_security_group_rules/adding_a_security_group_rule.rst b/umn/source/access_control/security_group/managing_security_group_rules/adding_a_security_group_rule.rst index aa03d49..678c639 100644 --- a/umn/source/access_control/security_group/managing_security_group_rules/adding_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/managing_security_group_rules/adding_a_security_group_rule.rst @@ -64,7 +64,7 @@ Procedure You can click **+** to add more inbound rules. - .. figure:: /_static/images/en-us_image_0284920908.png + .. figure:: /_static/images/en-us_image_0000001865662817.png :alt: **Figure 1** Add Inbound Rule **Figure 1** Add Inbound Rule @@ -94,7 +94,6 @@ Procedure | | - IP address range: 192.168.1.0/24 | | | | | | | | - **Security group**: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. 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. | | - | | - **IP address group**: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | | | | | | | If the source is a security group, this rule will apply to all instances associated with the selected security group. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ @@ -116,7 +115,7 @@ Procedure You can click **+** to add more outbound rules. - .. figure:: /_static/images/en-us_image_0284993717.png + .. figure:: /_static/images/en-us_image_0000001865582629.png :alt: **Figure 2** Add Outbound Rule **Figure 2** Add Outbound Rule @@ -146,7 +145,6 @@ Procedure | | - IP address range: 192.168.1.0/24 | | | | | | | | - **Security group**: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. 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. | | - | | - IP address group: A collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Description | Supplementary information about the security group rule. This parameter is optional. | N/A | | | | | @@ -157,5 +155,5 @@ Procedure The outbound rule list is displayed. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626734166.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823082.png diff --git a/umn/source/access_control/security_group/managing_security_group_rules/allowing_common_ports_with_a_few_clicks.rst b/umn/source/access_control/security_group/managing_security_group_rules/allowing_common_ports_with_a_few_clicks.rst index 729c0da..4739b20 100644 --- a/umn/source/access_control/security_group/managing_security_group_rules/allowing_common_ports_with_a_few_clicks.rst +++ b/umn/source/access_control/security_group/managing_security_group_rules/allowing_common_ports_with_a_few_clicks.rst @@ -67,5 +67,5 @@ Procedure After the operation is complete, you can view the added rules in the security group rule list. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001646961692.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823186.png diff --git a/umn/source/access_control/security_group/managing_security_group_rules/deleting_a_security_group_rule.rst b/umn/source/access_control/security_group/managing_security_group_rules/deleting_a_security_group_rule.rst index 251fdfd..82e7710 100644 --- a/umn/source/access_control/security_group/managing_security_group_rules/deleting_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/managing_security_group_rules/deleting_a_security_group_rule.rst @@ -48,5 +48,5 @@ Procedure 8. Click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675413825.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582633.png diff --git a/umn/source/access_control/security_group/managing_security_group_rules/fast-adding_security_group_rules.rst b/umn/source/access_control/security_group/managing_security_group_rules/fast-adding_security_group_rules.rst index a35e38c..728565d 100644 --- a/umn/source/access_control/security_group/managing_security_group_rules/fast-adding_security_group_rules.rst +++ b/umn/source/access_control/security_group/managing_security_group_rules/fast-adding_security_group_rules.rst @@ -36,7 +36,7 @@ Procedure 7. Configure required parameters. - .. figure:: /_static/images/en-us_image_0211552164.png + .. figure:: /_static/images/en-us_image_0000001818823074.png :alt: **Figure 1** Fast-Add Inbound Rule **Figure 1** Fast-Add Inbound Rule @@ -83,7 +83,7 @@ Procedure 10. Configure required parameters. - .. figure:: /_static/images/en-us_image_0211560998.png + .. figure:: /_static/images/en-us_image_0000001865582617.png :alt: **Figure 2** Fast-Add Outbound Rule **Figure 2** Fast-Add Outbound Rule @@ -121,5 +121,5 @@ Procedure 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_0000001675373905.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982858.png diff --git a/umn/source/access_control/security_group/managing_security_group_rules/importing_and_exporting_security_group_rules.rst b/umn/source/access_control/security_group/managing_security_group_rules/importing_and_exporting_security_group_rules.rst index 2630185..473c545 100644 --- a/umn/source/access_control/security_group/managing_security_group_rules/importing_and_exporting_security_group_rules.rst +++ b/umn/source/access_control/security_group/managing_security_group_rules/importing_and_exporting_security_group_rules.rst @@ -79,16 +79,16 @@ Procedure | | - IP address range: 192.168.1.0/24 | | | | | | | | - **Security group**: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. 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. | | - | | - **IP address group**: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | + | | - **IP address group**: The source is an IP address group. An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ | 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: | sg-test[96a8a93f-XXX-d7872990c314] | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ - | Description | Supplementary information about the security group rule. This parameter is optional. | ``-`` | + | Description | (Optional) Supplementary information about the security group rule. | ``-`` | | | | | - | | The security group rule description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + | | The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0141273034.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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582585.png +.. |image3| image:: /_static/images/en-us_image_0000001818823050.png +.. |image4| image:: /_static/images/en-us_image_0000001818982838.png diff --git a/umn/source/access_control/security_group/managing_security_group_rules/modifying_a_security_group_rule.rst b/umn/source/access_control/security_group/managing_security_group_rules/modifying_a_security_group_rule.rst index ffc6be5..f8a1c07 100644 --- a/umn/source/access_control/security_group/managing_security_group_rules/modifying_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/managing_security_group_rules/modifying_a_security_group_rule.rst @@ -37,5 +37,5 @@ Procedure #. Modify the security group rule information as prompted and click **Confirm**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675613937.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983190.png diff --git a/umn/source/access_control/security_group/managing_security_group_rules/replicating_a_security_group_rule.rst b/umn/source/access_control/security_group/managing_security_group_rules/replicating_a_security_group_rule.rst index 4559c3a..0ff6344 100644 --- a/umn/source/access_control/security_group/managing_security_group_rules/replicating_a_security_group_rule.rst +++ b/umn/source/access_control/security_group/managing_security_group_rules/replicating_a_security_group_rule.rst @@ -35,5 +35,5 @@ Procedure #. Modify the security group rule information as prompted and click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626894090.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865583245.png diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index 543c54a..5ab1a9b 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -5,700 +5,708 @@ Change History ============== -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| Released On | Description | -+===================================+====================================================================================================================================================================================================================================================================================================================================+ -| 2024-02-29 | This release incorporates the following changes: | -| | | -| | Deleted parameter **Destination Address** in :ref:`Creating a Custom Route Table `, :ref:`Adding a Custom Route `, and :ref:`Modifying a Route `. | -| | | -| | Deleted the descriptions about IP address groups in :ref:`Adding a Firewall Rule ` and :ref:`Modifying a Firewall Rule `. | -| | | -| | Modified the subnet description in :ref:`Subnet `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2024-02-18 | This release incorporates the following changes: | -| | | -| | Added :ref:`What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2024-02-02 | This release incorporates the following changes: | -| | | -| | Modified figures in :ref:`Creating a Custom Route Table ` and :ref:`Adding a Custom Route `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2024-01-16 | This release incorporates the following changes: | -| | | -| | Modified the figure for creating a subnet in :ref:`Creating a Subnet for the VPC `, :ref:`Step 2: Create a Subnet for the VPC `, and :ref:`Step 2: Create a Subnet for the VPC `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2024-01-02 | This release incorporates the following changes: | -| | | -| | Modified the parameter descriptions in sections :ref:`Adding a Security Group Rule ` and :ref:`Adding a Firewall Rule `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-12-19 | This release incorporates the following changes: | -| | | -| | - Added screenshots in :ref:`How Do I Configure a Security Group for Multi-Channel Protocols? ` | -| | - Modified the table in :ref:`Why Can't I Delete My VPCs and Subnets? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-12-18 | This release incorporates the following changes: | -| | | -| | Added IPv6-related content. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-12-12 | This release incorporates the following changes: | -| | | -| | Added descriptions about security group and IP address group as source or destination in :ref:`Adding a Security Group Rule `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-11-30 | This release incorporates the following changes: | -| | | -| | Added descriptions about IP address groups as source and destination in :ref:`Adding a Firewall Rule `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-11-14 | This release incorporates the following changes: | -| | | -| | Added the following content: | -| | | -| | Added description about allowing common ports with a few clicks in :ref:`Allowing Common Ports with A Few Clicks `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-10-10 | This release incorporates the following changes: | -| | | -| | - Added the figure for configuring route tables in :ref:`Route Table `. | -| | - Modified :ref:`Step 4: Add a Security Group Rule `. | -| | | -| | - Changed the location of parameter **Type**. | -| | - Added protocol **GRE**. | -| | | -| | - Modified :ref:`Step 5: Add a Security Group Rule ` and :ref:`Adding a Security Group Rule `. | -| | | -| | - Added description that each ECS must be associated with at least one security group. | -| | - Modified description about port. | -| | - Changed the location of parameter **Type**. | -| | - Added protocol **GRE**. | -| | | -| | - Added the function of adding multiple tags for search in :ref:`Managing VPC Tags `. | -| | - Added figures and modified steps in :ref:`Viewing and Deleting Resources in a Subnet `. | -| | - Modified :ref:`Security Groups and Security Group Rules `. | -| | | -| | - Added protocol **GRE** and deleted content about **Action**. | -| | - Modified description about security group sg-AB. | -| | - Added description about security group configuration. | -| | - Added support for IPv6. | -| | | -| | - Changed the section name in :ref:`Default Security Group and Its Rules `. | -| | - Optimized description in :ref:`Creating a Security Group `. | -| | - Modified the figure and added parameter **Type** in :ref:`Fast-Adding Security Group Rules `. | -| | - Modified notes and constraints in :ref:`Importing and Exporting Security Group Rules `. | -| | - Added description about the maximum number of security groups that can be created in :ref:`Creating a Firewall `. | -| | - Modified figures and parameter settings in :ref:`Adding a Firewall Rule `. | -| | - Added the route table quota in notes and constraints in :ref:`Creating a Custom Route Table `. | -| | - Added constraints on the maximum number of routes that can be added to a route table in :ref:`Adding a Custom Route `. | -| | - Modified :ref:`Creating a VPC Peering Connection with Another VPC in Your Account `. | -| | | -| | - Added description that you need to add routes to the route tables of the local and peer VPCs after creating a VPC peering connection. | -| | - Added parameter **Description** for creating a VPC peering connection. | -| | | -| | - Added parameter **Description** for creating a VPC peering connection in :ref:`Creating a VPC Peering Connection with a VPC in Another Account `. | -| | | -| | - Added description about the maximum number of flow log records that can be recorded in :ref:`VPC Flow Log Overview `. | -| | - Modified the section name and scenarios in :ref:`Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) `. | -| | - Modified the verification procedure in :ref:`Creating a User and Granting VPC Permissions `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 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 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: | -| | | -| | Updated the following content: | -| | | -| | Added description about viewing monitoring metrics in :ref:`Viewing Metrics `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-05-26 | This release incorporates the following changes: | -| | | -| | Added the following content: | -| | | -| | Added information about cloning a security group in :ref:`Cloning a Security Group `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-05-17 | This release incorporates the following changes: | -| | | -| | Updated the following content: | -| | | -| | Modified the procedure for viewing monitoring metrics in :ref:`Viewing Metrics `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-04-28 | This release incorporates the following changes: | -| | | -| | Updated the following content: | -| | | -| | Modified the links of sections "Binding an EIP" and "Unbinding an EIP" in :ref:`Assigning an EIP and Binding It to an ECS ` and :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-04-20 | This release incorporates the following changes: | -| | | -| | Updated the following content: | -| | | -| | - Added description that BMS user-defined network is available only in eu-de. | -| | - Added the step for viewing NIC details to :ref:`Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-02-15 | This release incorporates the following changes: | -| | | -| | Updated the following content: | -| | | -| | Modified links in :ref:`What Is Virtual Private Cloud? ` and :ref:`Can I Bind an EIP to Multiple ECSs? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2023-01-10 | This release incorporates the following changes: | -| | | -| | Updated the following content: | -| | | -| | Modified steps in :ref:`Subnet ` and :ref:`Elastic IP `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-12-12 | This release incorporates the following changes: | -| | | -| | Updated the following content: | -| | | -| | Added description that EIPs of the Dedicated Load Balancer (5_gray) type cannot be created in :ref:`Step 3: Assign an EIP and Bind It to an ECS `, :ref:`Assigning an EIP and Binding It to an ECS `, and :ref:`Can I Bind an EIP to Multiple ECSs? `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-11-15 | This release incorporates the following changes: | -| | | -| | Added support for binding and unbinding EIPs of the Dedicated Load Balancer (5_gray) type using APIs in :ref:`Step 3: Assign an EIP and Bind It to an ECS `, :ref:`Assigning an EIP and Binding It to an ECS `, and :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-10-20 | Modified the following content: | -| | | -| | Modified the bandwidth range in :ref:`What Is the Bandwidth Size Range? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-09-07 | Added the following content: | -| | | -| | - Added description about binding EIPs of the dedicated load balancer **(5_gray)** type to load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Added description about binding EIPs of the dedicated load balancer **(5_gray)** type to load balancers in :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-06-25 | Added the following content: | -| | | -| | - Modified constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Modified constraints on EIP binding to load balancers in :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2022-02-15 | Added the following content: | -| | | -| | - Added constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Added description about the default reverse domain name of an EIP in \ :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Added constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS ` and :ref:`Adding EIPs to a Shared Bandwidth `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2021-08-25 | Modified the following content: | -| | | -| | Deleted content about IP address groups. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2021-06-18 | Modified the following content: | -| | | -| | Updated screenshots and deleted the **Bandwidth Type** parameter in :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2021-05-10 | Added the following content: | -| | | -| | Added constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2021-05-08 | Added the following content: | -| | | -| | - Added description about the default reverse domain name of an EIP in :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Added description about modifying a dedicated bandwidth or shared bandwidth in :ref:`Modifying an EIP Bandwidth `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2021-03-16 | Added the following FAQ: | -| | | -| | - :ref:`What Bandwidth Types Are Available? ` | -| | - :ref:`What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-12-16 | This release incorporates the following changes: | -| | | -| | - Deleted the restriction on the number of ECS NICs for SNAT in :ref:`Are There Any Restrictions on Using a Route Table? ` | -| | - Added the procedure for binding a virtual IP address to an ECS in :ref:`Binding a Virtual IP Address to an EIP or ECS `. | -| | - Added description about enabling ports 465 and 587 for Mail BGP EIPs in :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Modified or added content in **Notes and Constraints**. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-07-28 | Modified the following content: | -| | | -| | Changed the maximum number of tags that can be added to 20 in :ref:`Managing VPC Tags ` and :ref:`Managing Subnet Tags `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-05-30 | Added the following content: | -| | | -| | Added basic information to :ref:`Security Groups and Security Group Rules ` and :ref:`Firewall Overview `. | -| | | -| | Modified the following content: | -| | | -| | - Added rules in :ref:`Firewall Configuration Examples `. | -| | - Modified :ref:`Does a Modified Security Group Rule or a Firewall Rule Take Effect Immediately for Existing Connections? ` | -| | - Modified :ref:`Why Can't I Delete My VPCs and Subnets? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-02-25 | Added the following content: | -| | | -| | - Added :ref:`Shared Bandwidth `. | -| | | -| | Modified the following content: | -| | | -| | - Modified steps in :ref:`Elastic IP `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-02-12 | Added the following content: | -| | | -| | Added description that VPC flow logs support S2 ECSs in :ref:`VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-01-08 | Added the following content: | -| | | -| | - Added function and namespace description and optimized information in tables in :ref:`Supported Metrics `. | -| | - Added :ref:`Region and AZ `. | -| | - Added the example of allowing external access to a specified port in :ref:`Security Group Configuration Examples `. | -| | | -| | Modified the following content: | -| | | -| | - Added **Subnet** and **VPC** as the type of resources whose traffic is to be logged in :ref:`VPC Flow Log `. | -| | | -| | - Updated screenshots in :ref:`Adding a Security Group Rule ` and :ref:`Fast-Adding Security Group Rules `. | -| | - Optimized figure examples in this document. | -| | - Optimized descriptions in :ref:`Firewall Configuration Examples `. | -| | - Optimized descriptions in :ref:`Firewall Overview `. | -| | - Changed the position of :ref:`Access Control `. | -| | - Optimized :ref:`What Is a Quota? ` | -| | | -| | Deleted the following content: | -| | | -| | - Deleted section "Deleting a VPN". | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2020-03-06 | Modified the following content: | -| | | -| | - Modified the steps in :ref:`Assigning an EIP and Binding It to an ECS `, :ref:`Elastic IP `, and :ref:`Shared Bandwidth `. | -| | - Updated screenshots in :ref:`Modifying a Shared Bandwidth `. | -| | - Updated screenshots and parameter description in :ref:`Creating a Subnet for the VPC `. | -| | - Modified steps in :ref:`Assigning a Virtual IP Address `, :ref:`Binding a Virtual IP Address to an EIP or ECS `, and :ref:`Releasing a Virtual IP Address `. | -| | - Updated screenshots in :ref:`VPC Peering Connection `. | -| | - Modified description in :ref:`How Many Routes Can a Route Table Contain? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-12-13 | Added the following content: | -| | | -| | - 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". | -| | | -| | Modified the following content: | -| | | -| | - Modified description and value examples of the port and source in :ref:`Step 4: Add a Security Group Rule ` and :ref:`Adding a Security Group Rule `. | -| | - Optimized note description in :ref:`Importing and Exporting Security Group Rules `. | -| | - Changed firewall to firewalls in :ref:`Creating a Firewall `. | -| | - Optimized description about the scenario in :ref:`Changing the Sequence of a Firewall Rule `. | -| | - Optimized description about the scenario in :ref:`Creating an Alarm Rule `. | -| | - Updated screenshots in :ref:`Adding a Security Group Rule ` and :ref:`Fast-Adding Security Group Rules `. | -| | - Optimized figure examples in this document. | -| | - Optimized descriptions in :ref:`Firewall Configuration Examples `. | -| | - Optimized descriptions in :ref:`Firewall Overview `. | -| | - Changed the position of :ref:`Access Control `. | -| | | -| | Deleted the following content: | -| | | -| | - Deleted section "Deleting a VPN". | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-11-29 | Added the following content: | -| | | -| | - Added section "IP Address Group". | -| | - Added port format and IP address group when configuring security group rules in :ref:`Adding a Security Group Rule `. | -| | - Added function and namespace description and optimized information in tables in :ref:`Supported Metrics `. | -| | - Added :ref:`Region and AZ `. | -| | | -| | Modified the following content: | -| | | -| | Optimized :ref:`What Is a Quota? ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-11-05 | Modified the following content: | -| | | -| | Added **Subnet** and **VPC** as the type of resources whose traffic is to be logged in :ref:`VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-08-30 | Added the following content: | -| | | -| | - Added the example of allowing external access to a specified port in :ref:`Security Group Configuration Examples `. | -| | - Added description that EIP type cannot be changed in :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-08-23 | Modified the following content: | -| | | -| | Optimized description about **NTP Server Address** in :ref:`Modifying a Subnet `. | -| | | -| | Added the following content: | -| | | -| | Added descriptions about route types in :ref:`Route Table `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-08-16 | Added the following content: | -| | | -| | Added :ref:`Exporting Route Table Information `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-08-09 | Added the following content: | -| | | -| | - Added parameters **Type** and **Bandwidth Type** to :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Added description about how to replicate multiple routes in :ref:`Replicating a Route `. | -| | - Added the description about **Next Hop Type** in :ref:`Adding a Custom Route `. | -| | | -| | Modified the following content: | -| | | -| | - Modified description about **NTP Server Address** in :ref:`Modifying a Subnet `. | -| | - Modified description about replication in the "Default Route Table and Custom Route Table" part in :ref:`Route Tables and Routes `. | -| | - Modified descriptions about system routes and custom routes in :ref:`Route Tables and Routes `. | -| | - Modified description about usage restrictions in :ref:`Route Tables and Routes `. | -| | | -| | Deleted the following content: | -| | | -| | - Deleted parameter **Enterprise Project** from the document. | -| | - Deleted the Cloud Connect service from the "Default Route Table and Custom Route Table" part in :ref:`Route Tables and Routes `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-08-02 | Added the following content based on the RM-584 requirements: | -| | | -| | - Added subnet parameter description in :ref:`Modifying a Subnet `. | -| | | -| | Modified the following content based on the RM-584 requirements: | -| | | -| | - Added prerequisites in :ref:`Releasing a Virtual IP Address `. | -| | - Optimized description about scenarios and prerequisites in :ref:`Deleting a Subnet `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-07-22 | Added the following content: | -| | | -| | Added :ref:`Enabling or Disabling VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-06-04 | Optimized the description in the following sections: | -| | | -| | - :ref:`What Is an EIP? ` | -| | - :ref:`Step 2: Create a Subnet for the VPC ` | -| | - :ref:`Creating a Subnet for the VPC ` | -| | - :ref:`Route Table ` | -| | - :ref:`Virtual IP Address ` | -| | - :ref:`Virtual IP Address Overview ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-05-31 | Modified the following sections related to subnets and route tables based on the RM-584 requirements: | -| | | -| | - :ref:`Route Table ` | -| | - :ref:`Modifying a VPC ` | -| | - :ref:`Creating a Subnet for the VPC ` | -| | - :ref:`Modifying a Subnet ` | -| | - :ref:`Managing Subnet Tags ` | -| | - :ref:`Creating a VPC Peering Connection with Another VPC in Your Account ` | -| | - :ref:`Creating a VPC Peering Connection with a VPC in Another Account ` | -| | - :ref:`Viewing Routes Configured for a VPC Peering Connection ` | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-05-29 | Added the following content: | -| | | -| | - Added a note in :ref:`Deleting a VPC Flow Log `. | -| | - Added a note about changing the NTP server address in :ref:`Modifying a Subnet `. | -| | | -| | Modified the following content: | -| | | -| | - Modified description about **NTP Server Address** in :ref:`Creating a VPC `, :ref:`Creating a Subnet for the VPC `, and :ref:`Modifying a Subnet `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-05-24 | Modified the following content: | -| | | -| | - Deleted description about DHCP in :ref:`What Is Virtual Private Cloud? `. | -| | - Modified description about **NTP Server Address** in :ref:`Creating a VPC `, :ref:`Creating a Subnet for the VPC `, and :ref:`Modifying a Subnet `. | -| | - Optimized :ref:`Elastic IP `. | -| | - Updated the description and screenshot in :ref:`Creating a VPC Peering Connection with Another VPC in Your Account ` and :ref:`Creating a VPC Peering Connection with a VPC in Another Account ` based on the latest management console page. | -| | - Updated sections :ref:`VPC Flow Log Overview ` and :ref:`Creating a VPC Flow Log `. | -| | | -| | Added the following content: | -| | | -| | - Added description about **Advanced Settings** and updated screenshots in :ref:`Creating a VPC ` and :ref:`Creating a Subnet for the VPC `. | -| | - Added "Obtaining the Peer VPC ID" in :ref:`Creating a VPC Peering Connection with a VPC in Another Account `. | -| | - Added two precautions in :ref:`Virtual IP Address Overview `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-04-28 | Modified the following content: | -| | | -| | - Modified the incorrect word spelling in :ref:`Viewing a VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-04-25 | Added the following content: | -| | | -| | - Added a note in :ref:`Creating a VPC Flow Log `. | -| | - Added the description about no VPC flow log records in :ref:`Viewing a VPC Flow Log `. | -| | - Added :ref:`Security Group Configuration Examples `. The security group configuration examples are integrated into one section and the original independent sections are deleted. | -| | | -| | Modified the following content: | -| | | -| | - Modified description information about **Enterprise Project**. | -| | - Optimized :ref:`Service Overview ` and added the product advantage description to :ref:`What Is Virtual Private Cloud? ` | -| | - Modified the description about how to switch to the **EIPs** page in :ref:`Elastic IP `. | -| | - Modified the description about how to switch to the **Shared Bandwidths** page in :ref:`Shared Bandwidth `. | -| | | -| | Deleted the following content: | -| | | -| | - Deleted "What Is a Security Group?", "Which Protocols Does a Security Group Support?", "What Are the Functions of the Default Security Group Rule?", and "How Can I Configure Security Group Rules?" in :ref:`FAQ `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-04-17 | Accepted in OTC-4.0/Agile-04.2019. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-04-12 | Modified the following content: | -| | | -| | - Modified the description for **DNS Server Address** in :ref:`Creating a VPC `, :ref:`Creating a Subnet for the VPC `, and :ref:`Modifying a Subnet `. | -| | | -| | Added the following content: | -| | | -| | - Added the note about **Resource** in :ref:`Creating a VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-04-10 | Modified the following content: | -| | | -| | - Added the description about **log-status** in :ref:`Viewing a VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-03-30 | Added the following content: | -| | | -| | - Added the **Enterprise Project** parameter in :ref:`Creating a VPC `, :ref:`Creating a Security Group `, and :ref:`Assigning an EIP and Binding It to an ECS `. | -| | - Added :ref:`Shared Bandwidth `. | -| | | -| | Deleted the following content: | -| | | -| | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts `. | -| | - Deleted the FAQs related to VPN in :ref:`FAQ `. | -| | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started `. | -| | | -| | Modified the following content: | -| | | -| | - Updated console screenshots. | -| | - Optimized the description in section "Security Group Configuration Examples". | -| | - Added the support for S2 ECSs in :ref:`VPC Flow Log Overview `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-03-18 | Modified the following content: | -| | | -| | - Modified the example description in :ref:`Viewing a VPC Flow Log `. | -| | - Modified steps in :ref:`Creating a VPC Flow Log `. | -| | | -| | Added the following content: | -| | | -| | - Added use restrictions in :ref:`VPC Flow Log Overview `. | -| | - Updated the console screenshots in :ref:`Deleting a VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-03-01 | Added the following content: | -| | | -| | - Added :ref:`Document Usage Instructions `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-02-27 | Added the following content: | -| | | -| | - Added screenshots and examples in :ref:`Viewing a VPC Flow Log `. | -| | | -| | Modified the following content: | -| | | -| | - Modified description about the scenario in :ref:`Deleting a VPC Flow Log `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-02-25 | Added the following content: | -| | | -| | - Added :ref:`VPC Flow Log `. | -| | | -| | Deleted the following content: | -| | | -| | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts `. | -| | - Deleted the FAQs related to VPN in :ref:`FAQ `. | -| | | -| | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started `. | -| | | -| | Modified the following content: | -| | | -| | - Optimized :ref:`Service Overview ` and added the product advantage description to :ref:`What Is Virtual Private Cloud? ` | -| | - Added :ref:`Security Group Configuration Examples `. The security group configuration examples are integrated into one section and the original independent sections are deleted. | -| | - Modified the description about how to switch to the **EIPs** page in :ref:`Elastic IP `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-02-23 | Added the following content: | -| | | -| | - Added the description about batch subnet creation in :ref:`VPC and Subnet `. | -| | - Added precautions about disabling a firewall in :ref:`Enabling or Disabling a Firewall `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-02-22 | Added the following content: | -| | | -| | Added the **Assign EIP** screenshot in :ref:`Assigning an EIP and Binding It to an ECS `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-02-15 | Added the following content: | -| | | -| | - Added the Anti-DDoS service restriction in :ref:`How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? ` | -| | | -| | Added :ref:`Modifying a Security Group `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-02-11 | Deleted the following content: | -| | | -| | - Deleted the console screenshot from :ref:`Assigning an EIP and Binding It to an ECS `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-01-31 | Accepted in OTC-4.0. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2019-01-30 | Modified the following content: | -| | | -| | - Modified the table listing the parameters for creating a VPC in :ref:`VPC and Subnet `. | -| | - Modified the table listing the parameters for modifying a security group rule in :ref:`Adding a Security Group Rule `. | -| | - Added the link to the default security group rule introduction in :ref:`Adding a Security Group Rule `. | -| | - Modified the format of the exported file to Excel in :ref:`Exporting VPC List ` and :ref:`Importing and Exporting Security Group Rules `. | -| | - Changed the number of characters allowed for the **Description** field to **255** in :ref:`Creating a Firewall `. | -| | - Modified steps in :ref:`Managing EIP Tags `. | -| | - Added the **Monitoring Period** column to the table listing metrics in :ref:`Supported Metrics `. | -| | - Changed the maximum bandwidth size allowed to 1000 Mbit/s in :ref:`What Is the Bandwidth Size Range? ` | -| | - Modified the table listing subnet parameters in :ref:`Modifying a Subnet `. | -| | - Updated the security group description in :ref:`Security Group `. | -| | - Updated the VPC peering connection description in :ref:`VPC Peering Connection `. | -| | - Updated firewall description in :ref:`Firewall `. | -| | - Updated console screenshots in :ref:`Adding a Firewall Rule `. | -| | - Updated console screenshots in :ref:`Modifying a Firewall Rule `. | -| | | -| | Added the following content: | -| | | -| | - Added :ref:`Security Group Configuration Examples `. | -| | - Added :ref:`Modifying an EIP Bandwidth `. | -| | - Added description about disassociating and releasing multiple EIPs at a time in :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | -| | | -| | Deleted the following content: | -| | | -| | - Deleted description about the **Reject** action from :ref:`Adding a Firewall Rule `. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-12-30 | Modified the following content: | -| | | -| | - Modified description about how to switch to the security group and firewall pages based on the changes made on the management console. | -| | | -| | Added the following content: | -| | | -| | - Added section **Firewall** **Overview**. | -| | - Added section **Firewall** **Configuration Examples**. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-11-30 | Added the following content: | -| | | -| | - Added parameter **NTP Server Address** to the description about how to create a subnet. | -| | | -| | Modified the following content: | -| | | -| | - Updated the document based on changes made to the firewall console pages. | -| | | -| | - Added description about how to delete multiple firewall rules at a time and how to disassociate multiple subnets from a firewall at a time. | -| | - Changed parameter **Any** to **All**. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-09-18 | Accepted in OTC-3.2/AGile-09.2018. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-09-06 | Modified the following content: | -| | | -| | - Modified the content and changed some screenshots in the document based on the latest management console. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-08-30 | This release incorporates the following change: | -| | | -| | - Added section "Adding Instances to and Removing Them from a Security Group". | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-07-30 | This release incorporates the following changes: | -| | | -| | - Modified sections related to security groups: | -| | | -| | - Added section "Replicating a Security Group Rule". | -| | - Added section "Modifying a Security Group Rule". | -| | - Modified section "Deleting a Security Group Rule" and added description about how to delete multiple security group rules at a time. | -| | - Added section "Importing and Exporting Security Group Rules". | -| | | -| | - Modified the VPN sections: | -| | | -| | - Modified the step for switching to the VPN console. | -| | - Deleted sections related to VPNs. An independent VPN user guide will be provided. | -| | - Deleted section "VPN Best Practice". | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-06-30 | This release incorporates the following changes: | -| | | -| | - Optimized sections under "Service Overview." | -| | - Optimized sections under "Security Group". | -| | | -| | - Optimized section "Security Group Overview". | -| | | -| | - Optimized section "Default Security Groups and Security Group Rules". | -| | - Optimized section "Creating a Security Group". | -| | - Optimized section "Adding a Security Group Rule". | -| | - Optimized section "Fast-Adding Security Group Rules". | -| | - Added security group configuration examples. | -| | - Added section "Viewing the Security Group of an ECS". | -| | - Added section "Changing the Security Group of an ECS". | -| | | -| | - Categorized FAQs. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-06-11 | This release incorporates the following changes: | -| | | -| | - Added section "Monitoring". | -| | - Modified tag description. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-05-23 | Accepted in OTC 3.1. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-04-28 | This release incorporates the following changes: | -| | | -| | - Added description about VPN tagging. | -| | - Added the IPv6 address description. | -| | - Added section "Exporting VPC Information". | -| | - Modified the bandwidth range. | -| | - Modified the VPN modification screenshots. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-03-30 | This release incorporates the following changes: | -| | | -| | Deleted the IPv6 address description. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-02-28 | This release incorporates the following changes: | -| | | -| | Added the description that the security group description can contain a maximum of 128 characters. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2018-01-30 | This release incorporates the following changes: | -| | | -| | - Added description about the function of unbinding and releasing EIPs in batches. | -| | - Added description about the function that the negotiation mode of the IKE policy in the VPN can be configured. | -| | - Added the description that the security group description can contain a maximum of 64 characters. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-11-30 | This release incorporates the following changes: | -| | | -| | - Updated screenshots and steps based on the latest management console. | -| | - Added description to indicate that subnets can be created without specifying the AZ. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-10-30 | This release incorporates the following changes: | -| | | -| | - Added description about the fast security group rule adding function. | -| | - Added ECS security group configuration examples. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-09-30 | This release incorporates the following changes: | -| | | -| | - Added description to indicate that the peer project ID needs to be configured when a tenant creates a VPC peering connection with the VPC of another tenant. | -| | - Modified description in sections "Adding a Security Group Rule" and "Deleting a Security Group Rule" based on changes made to the network console. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-08-30 | This release incorporates the following changes: | -| | | -| | - Added section "Managing Subnet Tags". | -| | - Added description about the VPC, subnet, and EIP tags. | -| | - Added section "Security Group Overview". | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-07-30 | This release incorporates the following changes: | -| | | -| | - Added description about how to enable shared SNAT on the management console. | -| | - Added section "Managing VPC Tags". | -| | - Added section "Managing EIP Tags". | -| | - Changed the number of routes allowed in a route table by default to **100**. | -| | - Updated procedures in sections "VPC and Subnet" and "Custom Route" based on changes made to the network console. | -| | - Added description about the multi-project feature. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-06-30 | This release incorporates the following change: | -| | | -| | - Added description about the virtual IP address feature. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-05-30 | This release incorporates the following change: | -| | | -| | - Added FAQ **How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?** | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-04-28 | This release incorporates the following change: | -| | | -| | - Added description about how to add DNS server addresses during subnet information modification. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-03-30 | This release incorporates the following change: | -| | | -| | - Added description about the firewall function. | -| | - Added description about the shared SNAT function. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-02-28 | This release incorporates the following change: | -| | | -| | - Deleted description about the button for disabling the DHCP function. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-02-24 | This release incorporates the following change: | -| | | -| | - Added description about the VPC peering function. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2017-01-12 | This release incorporates the following change: | -| | | -| | - Added description about the custom route table function. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2016-10-19 | This release incorporates the following change: | -| | | -| | - Updated the Help Center URL of the VPN service. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2016-07-15 | This release incorporates the following changes: | -| | | -| | - Modified the VPN authentication algorithm. | -| | - Optimized the traffic metering function. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| 2016-03-14 | This issue is the first official release. | -+-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| Released On | Description | ++===================================+=================================================================================================================================================================================================================================================================================================================================================+ +| 2024-03-27 | This release incorporates the following changes: | +| | | +| | - Changed **VPCReadOnlyAccess** and **VPCFullAccess** into **VPC ReadOnlyAccess** and **VPC FullAccess**. | +| | - Modified the subnet description in :ref:`Subnet `. | +| | - Deleted parameter **Fast-add rule** in :ref:`Creating a Security Group `. | +| | - Added the description indicating that if the secondary IPv4 CIDR block function is available in a region, the CIDR block of a VPC in this region cannot be modified through the console in :ref:`Modifying a VPC ` and :ref:`Adding a Secondary IPv4 CIDR Block to a VPC `. | +| | - Added the procedure for exporting the list of shared bandwidths in :ref:`Exporting Shared Bandwidths `. | +| | - Modified the operation procedure and figures in :ref:`Adding EIPs to a Shared Bandwidth ` and :ref:`Removing EIPs from a Shared Bandwidth `. | +| | - Modified the procedure for exporting the resource list in :ref:`Exporting VPC List `, :ref:`Exporting Subnet List `, :ref:`Importing and Exporting Security Group Rules `, :ref:`Exporting EIP Information `, and :ref:`Exporting Route Table Information `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2024-02-29 | This release incorporates the following changes: | +| | | +| | - Deleted parameter **Destination Address** in :ref:`Creating a Custom Route Table `, :ref:`Adding a Custom Route `, and :ref:`Modifying a Route `. | +| | - Deleted the descriptions about IP address groups in :ref:`Adding a Firewall Rule ` and :ref:`Modifying a Firewall Rule `. | +| | - Modified the subnet description in :ref:`Subnet `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2024-02-18 | This release incorporates the following changes: | +| | | +| | Added :ref:`What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2024-02-02 | This release incorporates the following changes: | +| | | +| | Modified figures in :ref:`Creating a Custom Route Table ` and :ref:`Adding a Custom Route `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2024-01-16 | This release incorporates the following changes: | +| | | +| | Modified the figure for creating a subnet in :ref:`Creating a Subnet for the VPC `, :ref:`Step 2: Create a Subnet for the VPC `, and :ref:`Step 2: Create a Subnet for the VPC `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2024-01-02 | This release incorporates the following changes: | +| | | +| | Modified the parameter descriptions in sections :ref:`Adding a Security Group Rule ` and :ref:`Adding a Firewall Rule `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-12-19 | This release incorporates the following changes: | +| | | +| | - Added screenshots in :ref:`How Do I Configure a Security Group for Multi-Channel Protocols? ` | +| | - Modified the table in :ref:`Why Can't I Delete My VPCs and Subnets? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-12-18 | This release incorporates the following changes: | +| | | +| | Added IPv6-related content. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-12-12 | This release incorporates the following changes: | +| | | +| | Added descriptions about security group and IP address group as source or destination in :ref:`Adding a Security Group Rule `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-11-30 | This release incorporates the following changes: | +| | | +| | Added descriptions about IP address groups as source and destination in :ref:`Adding a Firewall Rule `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-11-14 | This release incorporates the following changes: | +| | | +| | Added the following content: | +| | | +| | Added description about allowing common ports with a few clicks in :ref:`Allowing Common Ports with A Few Clicks `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-10-10 | This release incorporates the following changes: | +| | | +| | - Added the figure for configuring route tables in :ref:`Route Table `. | +| | - Modified :ref:`Step 4: Add a Security Group Rule `. | +| | | +| | - Changed the location of parameter **Type**. | +| | - Added protocol **GRE**. | +| | | +| | - Modified :ref:`Step 5: Add a Security Group Rule ` and :ref:`Adding a Security Group Rule `. | +| | | +| | - Added description that each ECS must be associated with at least one security group. | +| | - Modified description about port. | +| | - Changed the location of parameter **Type**. | +| | - Added protocol **GRE**. | +| | | +| | - Added the function of adding multiple tags for search in :ref:`Managing VPC Tags `. | +| | - Added figures and modified steps in :ref:`Viewing and Deleting Resources in a Subnet `. | +| | - Modified :ref:`Security Groups and Security Group Rules `. | +| | | +| | - Added protocol **GRE** and deleted content about **Action**. | +| | - Modified description about security group sg-AB. | +| | - Added description about security group configuration. | +| | - Added support for IPv6. | +| | | +| | - Changed the section name in :ref:`Default Security Group and Its Rules `. | +| | - Optimized description in :ref:`Creating a Security Group `. | +| | - Modified the figure and added parameter **Type** in :ref:`Fast-Adding Security Group Rules `. | +| | - Modified notes and constraints in :ref:`Importing and Exporting Security Group Rules `. | +| | - Added description about the maximum number of security groups that can be created in :ref:`Creating a Firewall `. | +| | - Modified figures and parameter settings in :ref:`Adding a Firewall Rule `. | +| | - Added the route table quota in notes and constraints in :ref:`Creating a Custom Route Table `. | +| | - Added constraints on the maximum number of routes that can be added to a route table in :ref:`Adding a Custom Route `. | +| | - Modified :ref:`Creating a VPC Peering Connection with Another VPC in Your Account `. | +| | | +| | - Added description that you need to add routes to the route tables of the local and peer VPCs after creating a VPC peering connection. | +| | - Added parameter **Description** for creating a VPC peering connection. | +| | | +| | - Added parameter **Description** for creating a VPC peering connection in :ref:`Creating a VPC Peering Connection with a VPC in Another Account `. | +| | | +| | - Added description about the maximum number of flow log records that can be recorded in :ref:`VPC Flow Log Overview `. | +| | - Modified the section name and scenarios in :ref:`Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) `. | +| | - Modified the verification procedure in :ref:`Creating a User and Granting VPC Permissions `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 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 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: | +| | | +| | Updated the following content: | +| | | +| | Added description about viewing monitoring metrics in :ref:`Viewing Metrics `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-05-26 | This release incorporates the following changes: | +| | | +| | Added the following content: | +| | | +| | Added information about cloning a security group in :ref:`Cloning a Security Group `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-05-17 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | Modified the procedure for viewing monitoring metrics in :ref:`Viewing Metrics `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-04-28 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | Modified the links of sections "Binding an EIP" and "Unbinding an EIP" in :ref:`Assigning an EIP and Binding It to an ECS ` and :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-04-20 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | - Added description that BMS user-defined network is available only in eu-de. | +| | - Added the step for viewing NIC details to :ref:`Disabling Source and Destination Check (HA Load Balancing Cluster Scenario) `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-02-15 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | Modified links in :ref:`What Is Virtual Private Cloud? ` and :ref:`Can I Bind an EIP to Multiple ECSs? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2023-01-10 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | Modified steps in :ref:`Subnet ` and :ref:`Elastic IP `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-12-12 | This release incorporates the following changes: | +| | | +| | Updated the following content: | +| | | +| | Added description that EIPs of the Dedicated Load Balancer (5_gray) type cannot be created in :ref:`Step 3: Assign an EIP and Bind It to an ECS `, :ref:`Assigning an EIP and Binding It to an ECS `, and :ref:`Can I Bind an EIP to Multiple ECSs? `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-11-15 | This release incorporates the following changes: | +| | | +| | Added support for binding and unbinding EIPs of the Dedicated Load Balancer (5_gray) type using APIs in :ref:`Step 3: Assign an EIP and Bind It to an ECS `, :ref:`Assigning an EIP and Binding It to an ECS `, and :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-10-20 | Modified the following content: | +| | | +| | Modified the bandwidth range in :ref:`What Is the Bandwidth Size Range? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-09-07 | Added the following content: | +| | | +| | - Added description about binding EIPs of the dedicated load balancer **(5_gray)** type to load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Added description about binding EIPs of the dedicated load balancer **(5_gray)** type to load balancers in :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-06-25 | Added the following content: | +| | | +| | - Modified constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Modified constraints on EIP binding to load balancers in :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2022-02-15 | Added the following content: | +| | | +| | - Added constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Added description about the default reverse domain name of an EIP in \ :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Added constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS ` and :ref:`Adding EIPs to a Shared Bandwidth `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-08-25 | Modified the following content: | +| | | +| | Deleted content about IP address groups. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-06-18 | Modified the following content: | +| | | +| | Updated screenshots and deleted the **Bandwidth Type** parameter in :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-05-10 | Added the following content: | +| | | +| | Added constraints on EIPs dedicated for dedicated load balancers in :ref:`Assigning an EIP and Binding It to an ECS `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-05-08 | Added the following content: | +| | | +| | - Added description about the default reverse domain name of an EIP in :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Added description about modifying a dedicated bandwidth or shared bandwidth in :ref:`Modifying an EIP Bandwidth `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2021-03-16 | Added the following FAQ: | +| | | +| | - :ref:`What Bandwidth Types Are Available? ` | +| | - :ref:`What Are the Differences Between a Dedicated Bandwidth and a Shared Bandwidth? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-12-16 | This release incorporates the following changes: | +| | | +| | - Deleted the restriction on the number of ECS NICs for SNAT in :ref:`Are There Any Restrictions on Using a Route Table? ` | +| | - Added the procedure for binding a virtual IP address to an ECS in :ref:`Binding a Virtual IP Address to an EIP or ECS `. | +| | - Added description about enabling ports 465 and 587 for Mail BGP EIPs in :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Modified or added content in **Notes and Constraints**. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-07-28 | Modified the following content: | +| | | +| | Changed the maximum number of tags that can be added to 20 in :ref:`Managing VPC Tags ` and :ref:`Managing Subnet Tags `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-05-30 | Added the following content: | +| | | +| | Added basic information to :ref:`Security Groups and Security Group Rules ` and :ref:`Firewall Overview `. | +| | | +| | Modified the following content: | +| | | +| | - Added rules in :ref:`Firewall Configuration Examples `. | +| | - Modified :ref:`Does a Modified Security Group Rule or a Firewall Rule Take Effect Immediately for Existing Connections? ` | +| | - Modified :ref:`Why Can't I Delete My VPCs and Subnets? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-02-25 | Added the following content: | +| | | +| | - Added :ref:`Shared Bandwidth `. | +| | | +| | Modified the following content: | +| | | +| | - Modified steps in :ref:`Elastic IP `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-02-12 | Added the following content: | +| | | +| | Added description that VPC flow logs support S2 ECSs in :ref:`VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-01-08 | Added the following content: | +| | | +| | - Added function and namespace description and optimized information in tables in :ref:`Supported Metrics `. | +| | - Added :ref:`Region and AZ `. | +| | - Added the example of allowing external access to a specified port in :ref:`Security Group Configuration Examples `. | +| | | +| | Modified the following content: | +| | | +| | - Added **Subnet** and **VPC** as the type of resources whose traffic is to be logged in :ref:`VPC Flow Log `. | +| | | +| | - Updated screenshots in :ref:`Adding a Security Group Rule ` and :ref:`Fast-Adding Security Group Rules `. | +| | - Optimized figure examples in this document. | +| | - Optimized descriptions in :ref:`Firewall Configuration Examples `. | +| | - Optimized descriptions in :ref:`Firewall Overview `. | +| | - Changed the position of :ref:`Access Control `. | +| | - Optimized :ref:`What Is a Quota? ` | +| | | +| | Deleted the following content: | +| | | +| | - Deleted section "Deleting a VPN". | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2020-03-06 | Modified the following content: | +| | | +| | - Modified the steps in :ref:`Assigning an EIP and Binding It to an ECS `, :ref:`Elastic IP `, and :ref:`Shared Bandwidth `. | +| | - Updated screenshots in :ref:`Modifying a Shared Bandwidth `. | +| | - Updated screenshots and parameter description in :ref:`Creating a Subnet for the VPC `. | +| | - Modified steps in :ref:`Assigning a Virtual IP Address `, :ref:`Binding a Virtual IP Address to an EIP or ECS `, and :ref:`Releasing a Virtual IP Address `. | +| | - Updated screenshots in :ref:`VPC Peering Connection `. | +| | - Modified description in :ref:`How Many Routes Can a Route Table Contain? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-12-13 | Added the following content: | +| | | +| | - 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". | +| | | +| | Modified the following content: | +| | | +| | - Modified description and value examples of the port and source in :ref:`Step 4: Add a Security Group Rule ` and :ref:`Adding a Security Group Rule `. | +| | - Optimized note description in :ref:`Importing and Exporting Security Group Rules `. | +| | - Changed firewall to firewalls in :ref:`Creating a Firewall `. | +| | - Optimized description about the scenario in :ref:`Changing the Sequence of a Firewall Rule `. | +| | - Optimized description about the scenario in :ref:`Creating an Alarm Rule `. | +| | - Updated screenshots in :ref:`Adding a Security Group Rule ` and :ref:`Fast-Adding Security Group Rules `. | +| | - Optimized figure examples in this document. | +| | - Optimized descriptions in :ref:`Firewall Configuration Examples `. | +| | - Optimized descriptions in :ref:`Firewall Overview `. | +| | - Changed the position of :ref:`Access Control `. | +| | | +| | Deleted the following content: | +| | | +| | - Deleted section "Deleting a VPN". | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-11-29 | Added the following content: | +| | | +| | - Added section "IP Address Group". | +| | - Added port format and IP address group when configuring security group rules in :ref:`Adding a Security Group Rule `. | +| | - Added function and namespace description and optimized information in tables in :ref:`Supported Metrics `. | +| | - Added :ref:`Region and AZ `. | +| | | +| | Modified the following content: | +| | | +| | Optimized :ref:`What Is a Quota? ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-11-05 | Modified the following content: | +| | | +| | Added **Subnet** and **VPC** as the type of resources whose traffic is to be logged in :ref:`VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-08-30 | Added the following content: | +| | | +| | - Added the example of allowing external access to a specified port in :ref:`Security Group Configuration Examples `. | +| | - Added description that EIP type cannot be changed in :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-08-23 | Modified the following content: | +| | | +| | Optimized description about **NTP Server Address** in :ref:`Modifying a Subnet `. | +| | | +| | Added the following content: | +| | | +| | Added descriptions about route types in :ref:`Route Table `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-08-16 | Added the following content: | +| | | +| | Added :ref:`Exporting Route Table Information `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-08-09 | Added the following content: | +| | | +| | - Added parameters **Type** and **Bandwidth Type** to :ref:`Step 3: Assign an EIP and Bind It to an ECS ` and :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Added description about how to replicate multiple routes in :ref:`Replicating a Route `. | +| | - Added the description about **Next Hop Type** in :ref:`Adding a Custom Route `. | +| | | +| | Modified the following content: | +| | | +| | - Modified description about **NTP Server Address** in :ref:`Modifying a Subnet `. | +| | - Modified description about replication in the "Default Route Table and Custom Route Table" part in :ref:`Route Tables and Routes `. | +| | - Modified descriptions about system routes and custom routes in :ref:`Route Tables and Routes `. | +| | - Modified description about usage restrictions in :ref:`Route Tables and Routes `. | +| | | +| | Deleted the following content: | +| | | +| | - Deleted parameter **Enterprise Project** from the document. | +| | - Deleted the Cloud Connect service from the "Default Route Table and Custom Route Table" part in :ref:`Route Tables and Routes `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-08-02 | Added the following content based on the RM-584 requirements: | +| | | +| | - Added subnet parameter description in :ref:`Modifying a Subnet `. | +| | | +| | Modified the following content based on the RM-584 requirements: | +| | | +| | - Added prerequisites in :ref:`Releasing a Virtual IP Address `. | +| | - Optimized description about scenarios and prerequisites in :ref:`Deleting a Subnet `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-07-22 | Added the following content: | +| | | +| | Added :ref:`Enabling or Disabling VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-06-04 | Optimized the description in the following sections: | +| | | +| | - :ref:`What Is an EIP? ` | +| | - :ref:`Step 2: Create a Subnet for the VPC ` | +| | - :ref:`Creating a Subnet for the VPC ` | +| | - :ref:`Route Table ` | +| | - :ref:`Virtual IP Address ` | +| | - :ref:`Virtual IP Address Overview ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-05-31 | Modified the following sections related to subnets and route tables based on the RM-584 requirements: | +| | | +| | - :ref:`Route Table ` | +| | - :ref:`Modifying a VPC ` | +| | - :ref:`Creating a Subnet for the VPC ` | +| | - :ref:`Modifying a Subnet ` | +| | - :ref:`Managing Subnet Tags ` | +| | - :ref:`Creating a VPC Peering Connection with Another VPC in Your Account ` | +| | - :ref:`Creating a VPC Peering Connection with a VPC in Another Account ` | +| | - :ref:`Viewing Routes Configured for a VPC Peering Connection ` | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-05-29 | Added the following content: | +| | | +| | - Added a note in :ref:`Deleting a VPC Flow Log `. | +| | - Added a note about changing the NTP server address in :ref:`Modifying a Subnet `. | +| | | +| | Modified the following content: | +| | | +| | - Modified description about **NTP Server Address** in :ref:`Creating a VPC `, :ref:`Creating a Subnet for the VPC `, and :ref:`Modifying a Subnet `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-05-24 | Modified the following content: | +| | | +| | - Deleted description about DHCP in :ref:`What Is Virtual Private Cloud? `. | +| | - Modified description about **NTP Server Address** in :ref:`Creating a VPC `, :ref:`Creating a Subnet for the VPC `, and :ref:`Modifying a Subnet `. | +| | - Optimized :ref:`Elastic IP `. | +| | - Updated the description and screenshot in :ref:`Creating a VPC Peering Connection with Another VPC in Your Account ` and :ref:`Creating a VPC Peering Connection with a VPC in Another Account ` based on the latest management console page. | +| | - Updated sections :ref:`VPC Flow Log Overview ` and :ref:`Creating a VPC Flow Log `. | +| | | +| | Added the following content: | +| | | +| | - Added description about **Advanced Settings** and updated screenshots in :ref:`Creating a VPC ` and :ref:`Creating a Subnet for the VPC `. | +| | - Added "Obtaining the Peer VPC ID" in :ref:`Creating a VPC Peering Connection with a VPC in Another Account `. | +| | - Added two precautions in :ref:`Virtual IP Address Overview `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-04-28 | Modified the following content: | +| | | +| | - Modified the incorrect word spelling in :ref:`Viewing a VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-04-25 | Added the following content: | +| | | +| | - Added a note in :ref:`Creating a VPC Flow Log `. | +| | - Added the description about no VPC flow log records in :ref:`Viewing a VPC Flow Log `. | +| | - Added :ref:`Security Group Configuration Examples `. The security group configuration examples are integrated into one section and the original independent sections are deleted. | +| | | +| | Modified the following content: | +| | | +| | - Modified description information about **Enterprise Project**. | +| | - Optimized :ref:`Service Overview ` and added the product advantage description to :ref:`What Is Virtual Private Cloud? ` | +| | - Modified the description about how to switch to the **EIPs** page in :ref:`Elastic IP `. | +| | - Modified the description about how to switch to the **Shared Bandwidths** page in :ref:`Shared Bandwidth `. | +| | | +| | Deleted the following content: | +| | | +| | - Deleted "What Is a Security Group?", "Which Protocols Does a Security Group Support?", "What Are the Functions of the Default Security Group Rule?", and "How Can I Configure Security Group Rules?" in :ref:`FAQ `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-04-17 | Accepted in OTC-4.0/Agile-04.2019. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-04-12 | Modified the following content: | +| | | +| | - Modified the description for **DNS Server Address** in :ref:`Creating a VPC `, :ref:`Creating a Subnet for the VPC `, and :ref:`Modifying a Subnet `. | +| | | +| | Added the following content: | +| | | +| | - Added the note about **Resource** in :ref:`Creating a VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-04-10 | Modified the following content: | +| | | +| | - Added the description about **log-status** in :ref:`Viewing a VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-03-30 | Added the following content: | +| | | +| | - Added the **Enterprise Project** parameter in :ref:`Creating a VPC `, :ref:`Creating a Security Group `, and :ref:`Assigning an EIP and Binding It to an ECS `. | +| | - Added :ref:`Shared Bandwidth `. | +| | | +| | Deleted the following content: | +| | | +| | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts `. | +| | - Deleted the FAQs related to VPN in :ref:`FAQ `. | +| | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started `. | +| | | +| | Modified the following content: | +| | | +| | - Updated console screenshots. | +| | - Optimized the description in section "Security Group Configuration Examples". | +| | - Added the support for S2 ECSs in :ref:`VPC Flow Log Overview `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-03-18 | Modified the following content: | +| | | +| | - Modified the example description in :ref:`Viewing a VPC Flow Log `. | +| | - Modified steps in :ref:`Creating a VPC Flow Log `. | +| | | +| | Added the following content: | +| | | +| | - Added use restrictions in :ref:`VPC Flow Log Overview `. | +| | - Updated the console screenshots in :ref:`Deleting a VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-03-01 | Added the following content: | +| | | +| | - Added :ref:`Document Usage Instructions `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-02-27 | Added the following content: | +| | | +| | - Added screenshots and examples in :ref:`Viewing a VPC Flow Log `. | +| | | +| | Modified the following content: | +| | | +| | - Modified description about the scenario in :ref:`Deleting a VPC Flow Log `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-02-25 | Added the following content: | +| | | +| | - Added :ref:`VPC Flow Log `. | +| | | +| | Deleted the following content: | +| | | +| | - Deleted the concepts of VPN, IPsec VPN, remote gateway, remote subnet, region, and project in :ref:`Basic Concepts `. | +| | - Deleted the FAQs related to VPN in :ref:`FAQ `. | +| | | +| | - Deleted the content related to "Configuring a VPC for ECSs That Access the Internet Through a VPN" in :ref:`Getting Started `. | +| | | +| | Modified the following content: | +| | | +| | - Optimized :ref:`Service Overview ` and added the product advantage description to :ref:`What Is Virtual Private Cloud? ` | +| | - Added :ref:`Security Group Configuration Examples `. The security group configuration examples are integrated into one section and the original independent sections are deleted. | +| | - Modified the description about how to switch to the **EIPs** page in :ref:`Elastic IP `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-02-23 | Added the following content: | +| | | +| | - Added the description about batch subnet creation in :ref:`VPC and Subnet `. | +| | - Added precautions about disabling a firewall in :ref:`Enabling or Disabling a Firewall `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-02-22 | Added the following content: | +| | | +| | Added the **Assign EIP** screenshot in :ref:`Assigning an EIP and Binding It to an ECS `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-02-15 | Added the following content: | +| | | +| | - Added the Anti-DDoS service restriction in :ref:`How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC? ` | +| | | +| | Added :ref:`Modifying a Security Group `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-02-11 | Deleted the following content: | +| | | +| | - Deleted the console screenshot from :ref:`Assigning an EIP and Binding It to an ECS `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-01-31 | Accepted in OTC-4.0. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2019-01-30 | Modified the following content: | +| | | +| | - Modified the table listing the parameters for creating a VPC in :ref:`VPC and Subnet `. | +| | - Modified the table listing the parameters for modifying a security group rule in :ref:`Adding a Security Group Rule `. | +| | - Added the link to the default security group rule introduction in :ref:`Adding a Security Group Rule `. | +| | - Modified the format of the exported file to Excel in :ref:`Exporting VPC List ` and :ref:`Importing and Exporting Security Group Rules `. | +| | - Changed the number of characters allowed for the **Description** field to **255** in :ref:`Creating a Firewall `. | +| | - Modified steps in :ref:`Managing EIP Tags `. | +| | - Added the **Monitoring Period** column to the table listing metrics in :ref:`Supported Metrics `. | +| | - Changed the maximum bandwidth size allowed to 1000 Mbit/s in :ref:`What Is the Bandwidth Size Range? ` | +| | - Modified the table listing subnet parameters in :ref:`Modifying a Subnet `. | +| | - Updated the security group description in :ref:`Security Group `. | +| | - Updated the VPC peering connection description in :ref:`VPC Peering Connection `. | +| | - Updated firewall description in :ref:`Firewall `. | +| | - Updated console screenshots in :ref:`Adding a Firewall Rule `. | +| | - Updated console screenshots in :ref:`Modifying a Firewall Rule `. | +| | | +| | Added the following content: | +| | | +| | - Added :ref:`Security Group Configuration Examples `. | +| | - Added :ref:`Modifying an EIP Bandwidth `. | +| | - Added description about disassociating and releasing multiple EIPs at a time in :ref:`Unbinding an EIP from an ECS and Releasing the EIP `. | +| | | +| | Deleted the following content: | +| | | +| | - Deleted description about the **Reject** action from :ref:`Adding a Firewall Rule `. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-12-30 | Modified the following content: | +| | | +| | - Modified description about how to switch to the security group and firewall pages based on the changes made on the management console. | +| | | +| | Added the following content: | +| | | +| | - Added section **Firewall** **Overview**. | +| | - Added section **Firewall** **Configuration Examples**. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-11-30 | Added the following content: | +| | | +| | - Added parameter **NTP Server Address** to the description about how to create a subnet. | +| | | +| | Modified the following content: | +| | | +| | - Updated the document based on changes made to the firewall console pages. | +| | | +| | - Added description about how to delete multiple firewall rules at a time and how to disassociate multiple subnets from a firewall at a time. | +| | - Changed parameter **Any** to **All**. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-09-18 | Accepted in OTC-3.2/AGile-09.2018. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-09-06 | Modified the following content: | +| | | +| | - Modified the content and changed some screenshots in the document based on the latest management console. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-08-30 | This release incorporates the following change: | +| | | +| | - Added section "Adding Instances to and Removing Them from a Security Group". | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-07-30 | This release incorporates the following changes: | +| | | +| | - Modified sections related to security groups: | +| | | +| | - Added section "Replicating a Security Group Rule". | +| | - Added section "Modifying a Security Group Rule". | +| | - Modified section "Deleting a Security Group Rule" and added description about how to delete multiple security group rules at a time. | +| | - Added section "Importing and Exporting Security Group Rules". | +| | | +| | - Modified the VPN sections: | +| | | +| | - Modified the step for switching to the VPN console. | +| | - Deleted sections related to VPNs. An independent VPN user guide will be provided. | +| | - Deleted section "VPN Best Practice". | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-06-30 | This release incorporates the following changes: | +| | | +| | - Optimized sections under "Service Overview." | +| | - Optimized sections under "Security Group". | +| | | +| | - Optimized section "Security Group Overview". | +| | | +| | - Optimized section "Default Security Groups and Security Group Rules". | +| | - Optimized section "Creating a Security Group". | +| | - Optimized section "Adding a Security Group Rule". | +| | - Optimized section "Fast-Adding Security Group Rules". | +| | - Added security group configuration examples. | +| | - Added section "Viewing the Security Group of an ECS". | +| | - Added section "Changing the Security Group of an ECS". | +| | | +| | - Categorized FAQs. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-06-11 | This release incorporates the following changes: | +| | | +| | - Added section "Monitoring". | +| | - Modified tag description. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-05-23 | Accepted in OTC 3.1. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-04-28 | This release incorporates the following changes: | +| | | +| | - Added description about VPN tagging. | +| | - Added the IPv6 address description. | +| | - Added section "Exporting VPC Information". | +| | - Modified the bandwidth range. | +| | - Modified the VPN modification screenshots. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-03-30 | This release incorporates the following changes: | +| | | +| | Deleted the IPv6 address description. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-02-28 | This release incorporates the following changes: | +| | | +| | Added the description that the security group description can contain a maximum of 128 characters. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2018-01-30 | This release incorporates the following changes: | +| | | +| | - Added description about the function of unbinding and releasing EIPs in batches. | +| | - Added description about the function that the negotiation mode of the IKE policy in the VPN can be configured. | +| | - Added the description that the security group description can contain a maximum of 64 characters. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-11-30 | This release incorporates the following changes: | +| | | +| | - Updated screenshots and steps based on the latest management console. | +| | - Added description to indicate that subnets can be created without specifying the AZ. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-10-30 | This release incorporates the following changes: | +| | | +| | - Added description about the fast security group rule adding function. | +| | - Added ECS security group configuration examples. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-09-30 | This release incorporates the following changes: | +| | | +| | - Added description to indicate that the peer project ID needs to be configured when a tenant creates a VPC peering connection with the VPC of another tenant. | +| | - Modified description in sections "Adding a Security Group Rule" and "Deleting a Security Group Rule" based on changes made to the network console. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-08-30 | This release incorporates the following changes: | +| | | +| | - Added section "Managing Subnet Tags". | +| | - Added description about the VPC, subnet, and EIP tags. | +| | - Added section "Security Group Overview". | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-07-30 | This release incorporates the following changes: | +| | | +| | - Added description about how to enable shared SNAT on the management console. | +| | - Added section "Managing VPC Tags". | +| | - Added section "Managing EIP Tags". | +| | - Changed the number of routes allowed in a route table by default to **100**. | +| | - Updated procedures in sections "VPC and Subnet" and "Custom Route" based on changes made to the network console. | +| | - Added description about the multi-project feature. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-06-30 | This release incorporates the following change: | +| | | +| | - Added description about the virtual IP address feature. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-05-30 | This release incorporates the following change: | +| | | +| | - Added FAQ **How Does an IPv6 Client on the Internet Access the ECS That Has an EIP Bound in a VPC?** | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-04-28 | This release incorporates the following change: | +| | | +| | - Added description about how to add DNS server addresses during subnet information modification. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-03-30 | This release incorporates the following change: | +| | | +| | - Added description about the firewall function. | +| | - Added description about the shared SNAT function. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-02-28 | This release incorporates the following change: | +| | | +| | - Deleted description about the button for disabling the DHCP function. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-02-24 | This release incorporates the following change: | +| | | +| | - Added description about the VPC peering function. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2017-01-12 | This release incorporates the following change: | +| | | +| | - Added description about the custom route table function. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2016-10-19 | This release incorporates the following change: | +| | | +| | - Updated the Help Center URL of the VPN service. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2016-07-15 | This release incorporates the following changes: | +| | | +| | - Modified the VPN authentication algorithm. | +| | - Optimized the traffic metering function. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +| 2016-03-14 | This issue is the first official release. | ++-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst b/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst index 1ff3f9e..a5f3f15 100644 --- a/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst +++ b/umn/source/elastic_ip/assigning_an_eip_and_binding_it_to_an_ecs.rst @@ -38,7 +38,7 @@ Assigning an EIP #. Set the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001117669274.png + .. figure:: /_static/images/en-us_image_0000001818823034.png :alt: **Figure 1** Assign EIP **Figure 1** Assign EIP @@ -85,8 +85,8 @@ Assigning an EIP | Parameter | Requirement | Example Value | +=======================+=====================================================================+=======================+ | Key | - Cannot be left blank. | Ipv4_key1 | - | | - Must be unique for each EIP. | | - | | - Can contain a maximum of 36 characters. | | + | | - The key value must be unique for the same EIP. | | + | | - Can contain up to 36 characters. | | | | - Can contain only the following character types: | | | | | | | | - Uppercase letters | | @@ -94,7 +94,7 @@ Assigning an EIP | | - Digits | | | | - Special characters, including hyphens (-) and underscores (_) | | +-----------------------+---------------------------------------------------------------------+-----------------------+ - | Value | - Can contain a maximum of 43 characters. | 3005eip | + | Value | - Can contain up to 43 characters. | 3005eip | | | - Can contain only the following character types: | | | | | | | | - Uppercase letters | | @@ -115,7 +115,7 @@ Binding an EIP #. Select the instance that you want to bind the EIP to. - .. figure:: /_static/images/en-us_image_0000001166028070.png + .. figure:: /_static/images/en-us_image_0000001865662761.png :alt: **Figure 2** Bind EIP **Figure 2** Bind EIP @@ -135,5 +135,5 @@ You can use any of the following commands to obtain the domain name of an EIP: - nslookup [-qt=ptr] *EIP* - dig -x *EIP* -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/elastic_ip/exporting_eip_information.rst b/umn/source/elastic_ip/exporting_eip_information.rst index 0c4d6a1..4507b17 100644 --- a/umn/source/elastic_ip/exporting_eip_information.rst +++ b/umn/source/elastic_ip/exporting_eip_information.rst @@ -17,12 +17,11 @@ Procedure #. 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**. +#. Click |image2| in the upper left corner, and choose **Network** > **Elastic IP**. -#. On the displayed page, click |image3| in the upper right corner of the EIP list. +#. On the EIP list page, select one or more EIPs and click **Export** in the upper left corner. - The system will automatically export all EIPs in the current region of your account to an Excel file and download the file to a local directory. + The system will automatically export all EIPs to an Excel file and download the file to a local directory. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png -.. |image3| image:: /_static/images/en-us_image_0233469196.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001649841616.png diff --git a/umn/source/elastic_ip/managing_eip_tags.rst b/umn/source/elastic_ip/managing_eip_tags.rst index e62d3a3..dfff434 100644 --- a/umn/source/elastic_ip/managing_eip_tags.rst +++ b/umn/source/elastic_ip/managing_eip_tags.rst @@ -47,23 +47,21 @@ Procedure #. 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**. +#. Click |image2| in the upper left corner, and choose **Network** > **Elastic IP**. -#. Click the search box above the EIP list. +#. In the search box above the EIP list, click anywhere in the box to set filters. -#. Select the tag key and value of the EIP. + Click the tag key and then the value as required. The system filters resources based on the tag you select. - You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for EIPs, the system will display only the EIPs that contain all of the tags you specified. + Click anywhere in the search box to add the next tag key and value. -#. Click **OK**. - - The system displays the EIPs you are looking for based on the entered tag keys and values. + You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for EIPs, the system will display only the EIPs that match all of the tags you specified. **Adding, deleting, editing, and viewing tags on the Tags tab of an EIP** #. 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** > **Elastic IP**. +#. Click |image4| in the upper left corner, and choose **Network** > **Elastic IP**. #. On the displayed page, locate the EIP whose tags you want to manage, and click the EIP name. #. On the page showing EIP details, click the **Tags** tab and perform desired operations on tags. @@ -85,7 +83,7 @@ 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_0000001454059512.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/elastic_ip/modifying_an_eip_bandwidth.rst b/umn/source/elastic_ip/modifying_an_eip_bandwidth.rst index 25bd660..89c6bca 100644 --- a/umn/source/elastic_ip/modifying_an_eip_bandwidth.rst +++ b/umn/source/elastic_ip/modifying_an_eip_bandwidth.rst @@ -21,7 +21,7 @@ Procedure #. 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**. +#. Click |image2| in the upper left corner, and choose **Network** > **Elastic IP**. #. Locate the row that contains the target EIP in the EIP list, click **More** in the **Operation** column, and select **Modify Bandwidth**. @@ -31,5 +31,5 @@ Procedure #. Click **Submit**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png 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 2db8bb8..9603ddd 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 @@ -31,7 +31,7 @@ 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** > **Elastic IP**. +#. Click |image2| in the upper left corner, and choose **Network** > **Elastic IP**. #. On the displayed page, locate the row that contains the EIP, and click **Unbind**. #. Click **Yes** in the displayed dialog box. @@ -39,7 +39,7 @@ Procedure #. 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** > **Elastic IP**. +#. Click |image4| in the upper left corner, and choose **Network** > **Elastic IP**. #. On the displayed page, locate the row that contains the target EIP, click **More** and then **Release** in the **Operation** column. #. Click **Yes** in the displayed dialog box. @@ -47,7 +47,7 @@ Procedure #. Log in to the management console. #. Click |image5| in the upper left corner and select the desired region and project. -#. Click |image6| in the upper left corner and choose **Network** > **Elastic IP**. +#. Click |image6| in the upper left corner, and choose **Network** > **Elastic IP**. #. On the displayed page, select the EIPs to be unbound. #. Click the **Unbind** button located above the EIP list. #. Click **Yes** in the displayed dialog box. @@ -56,16 +56,16 @@ Procedure #. Log in to the management console. #. Click |image7| in the upper left corner and select the desired region and project. -#. Click |image8| in the upper left corner and choose **Network** > **Elastic IP**. +#. Click |image8| in the upper left corner, and choose **Network** > **Elastic IP**. #. On the displayed page, select the EIPs to be released. #. Click the **Release** button located above the EIP list. #. Click **Yes** in the displayed dialog box. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001454059512.png -.. |image5| image:: /_static/images/en-us_image_0141273034.png -.. |image6| image:: /_static/images/en-us_image_0000001454059512.png -.. |image7| image:: /_static/images/en-us_image_0141273034.png -.. |image8| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001818982822.png +.. |image5| image:: /_static/images/en-us_image_0000001818982734.png +.. |image6| image:: /_static/images/en-us_image_0000001818982822.png +.. |image7| image:: /_static/images/en-us_image_0000001818982734.png +.. |image8| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/faq/bandwidth/what_is_the_bandwidth_size_range.rst b/umn/source/faq/bandwidth/what_is_the_bandwidth_size_range.rst index 08d0a33..6419576 100644 --- a/umn/source/faq/bandwidth/what_is_the_bandwidth_size_range.rst +++ b/umn/source/faq/bandwidth/what_is_the_bandwidth_size_range.rst @@ -5,4 +5,4 @@ What Is the Bandwidth Size Range? ================================= -The bandwidth range is from 5 Mbit/s to 1000 Mbit/s. +The bandwidth range is from 5Mbit/s to 1000Mbit/s. diff --git a/umn/source/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst b/umn/source/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst index 31d064f..aee70fa 100644 --- a/umn/source/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst +++ b/umn/source/faq/connectivity/how_does_an_ipv6_client_on_the_internet_access_the_ecs_that_has_an_eip_bound_in_a_vpc.rst @@ -13,7 +13,7 @@ After users who use IPv6 clients bind an IPv6 EIP to an ECS, the data flow is sh .. _vpc_faq_0076__fig1038524023539: -.. figure:: /_static/images/en-us_image_0118499144.png +.. figure:: /_static/images/en-us_image_0000001865662749.png :alt: **Figure 1** IPv6 data flow **Figure 1** IPv6 data flow diff --git a/umn/source/faq/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst b/umn/source/faq/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst index 10a3a59..852eaff 100644 --- a/umn/source/faq/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst +++ b/umn/source/faq/connectivity/why_are_internet_or_internal_domain_names_in_the_cloud_inaccessible_through_domain_names_when_my_ecs_has_multiple_nics.rst @@ -5,7 +5,7 @@ Why Are Internet or Internal Domain Names in the Cloud Inaccessible Through Domain Names When My ECS Has Multiple NICs? ======================================================================================================================= -When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access the Internet or domain names in the cloud. +When an ECS has more than one NIC, if different DNS server addresses are configured for the subnets used by the NICs, the ECS cannot access public websites or internal domain names in the cloud. You can resolve this issue by configuring the same DNS server address for the subnets used by the same ECS. You can perform the following steps to modify DNS server addresses of subnets in a VPC: diff --git a/umn/source/faq/eips/can_i_bind_an_eip_to_multiple_ecss.rst b/umn/source/faq/eips/can_i_bind_an_eip_to_multiple_ecss.rst index 41f8b40..0a9e35c 100644 --- a/umn/source/faq/eips/can_i_bind_an_eip_to_multiple_ecss.rst +++ b/umn/source/faq/eips/can_i_bind_an_eip_to_multiple_ecss.rst @@ -7,4 +7,4 @@ Can I Bind an EIP to Multiple ECSs? Each EIP can be bound to only one ECS at a time. -Multiple ECSs cannot share the same EIP. An ECS and its bound EIP must be in the same region. If you want multiple ECSs in the same VPC to share an EIP, you have to use a NAT gateway. For more information, see `NAT Gateway User Guide `__. +Multiple ECSs cannot share the same EIP. An ECS and its EIP must be in the same region. To enable ECSs across AZs in a VPC to share an EIP, you can use a NAT gateway by referring to `NAT Gateway User Guide `__. diff --git a/umn/source/faq/eips/index.rst b/umn/source/faq/eips/index.rst index ac920b3..6b55408 100644 --- a/umn/source/faq/eips/index.rst +++ b/umn/source/faq/eips/index.rst @@ -10,7 +10,7 @@ EIPs - :ref:`How Do I Access an ECS with an EIP Bound from the Internet? ` - :ref:`Can I Bind an EIP to a Cloud Resource in Another Region? ` - :ref:`Can I Change the Region of My EIP? ` -- :ref:`What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs? ` +- :ref:`What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs? ` .. toctree:: :maxdepth: 1 diff --git a/umn/source/faq/eips/what_are_the_differences_between_5_bgp_5_mailbgp_and_5_gray_eips.rst b/umn/source/faq/eips/what_are_the_differences_between_5_bgp_5_mailbgp_and_5_gray_eips.rst index 24671b7..d47b340 100644 --- a/umn/source/faq/eips/what_are_the_differences_between_5_bgp_5_mailbgp_and_5_gray_eips.rst +++ b/umn/source/faq/eips/what_are_the_differences_between_5_bgp_5_mailbgp_and_5_gray_eips.rst @@ -1,13 +1,13 @@ -:original_name: en-us_topic_0000001799161498.html +:original_name: en-us_topic_0000001818822858.html -.. _en-us_topic_0000001799161498: +.. _en-us_topic_0000001818822858: What Are the Differences Between 5_bgp, 5_mailbgp, and 5_gray EIPs? =================================================================== -:ref:`Table 1 ` lists the differences between **5_bgp**, **5_mailbgp**, and **5_gray** EIPs. +:ref:`Table 1 ` lists the differences between **5_bgp**, **5_mailbgp**, and **5_gray** EIPs. -.. _en-us_topic_0000001799161498__en-us_topic_0000001797977244_faq_bandwidth_0008_table1031220574471: +.. _en-us_topic_0000001818822858__en-us_topic_0000001797977244_en-us_topic_0205159731_table1031220574471: .. table:: **Table 1** Differences between **5_bgp**, **5_mailbgp**, and **5_gray** EIPs diff --git a/umn/source/faq/eips/what_is_an_eip.rst b/umn/source/faq/eips/what_is_an_eip.rst index 2951d37..5a9470d 100644 --- a/umn/source/faq/eips/what_is_an_eip.rst +++ b/umn/source/faq/eips/what_is_an_eip.rst @@ -10,7 +10,7 @@ The Elastic IP (EIP) service enables your cloud resources to communicate with th Each EIP can be used by only one cloud resource at a time. -.. figure:: /_static/images/en-us_image_0209583952.png +.. figure:: /_static/images/en-us_image_0000001818823042.png :alt: **Figure 1** Accessing the Internet using an EIP **Figure 1** Accessing the Internet using an EIP diff --git a/umn/source/faq/general_questions/what_is_a_quota.rst b/umn/source/faq/general_questions/what_is_a_quota.rst index def4c97..df5d337 100644 --- a/umn/source/faq/general_questions/what_is_a_quota.rst +++ b/umn/source/faq/general_questions/what_is_a_quota.rst @@ -22,30 +22,30 @@ How Do I View My Quotas? #. In the upper right corner of the page, click |image2|. - The **Service Quota** page is displayed. + The **Quotas** page is displayed. -#. View the used and total quota of each type of resources on the displayed page. +#. On the **Quotas** page, view the used and total quotas of each type of resources. - If a quota cannot meet service requirements, apply for a higher quota. + If a quota cannot meet your needs, apply for a higher quota by performing the following operations. -How Do I Apply for a Higher Quota? ----------------------------------- +How Do I Increase My Quota? +--------------------------- -The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email. +The system does not support online quota adjustment. To adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email. Before dialing the hotline number or sending an email, make sure that the following information has been obtained: -- Domain name, project name, and project ID, which can be obtained by performing the following operations: +- Domain name, project name, and project ID - Log in to the management console using the cloud account, click the username in the upper right corner, select **My Credentials** from the drop-down list, and obtain the domain name, project name, and project ID on the **My Credentials** page. + To obtain the preceding information, log in to the management console, click the username in the upper-right corner, and choose **My Credentials** from the drop-down list. - Quota information, which includes: - - Service name + - Service Name - Quota type - Required quota `Learn how to obtain the service hotline and email address. `__ -.. |image1| image:: /_static/images/en-us_image_0275513364.png -.. |image2| image:: /_static/images/en-us_image_0152727234.png +.. |image1| image:: /_static/images/en-us_image_0000001865663101.png +.. |image2| image:: /_static/images/en-us_image_0000001818823370.png diff --git a/umn/source/faq/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst b/umn/source/faq/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst index 48dd160..7ada68a 100644 --- a/umn/source/faq/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst +++ b/umn/source/faq/security/how_do_i_configure_a_security_group_for_multi-channel_protocols.rst @@ -18,7 +18,7 @@ You can configure port 69 and configure data channel ports used by TFTP for the The following figure provides an example of the security group rule configuration if the ports used by data channels range from 60001 to 60100. -.. figure:: /_static/images/en-us_image_0000001796404809.png +.. figure:: /_static/images/en-us_image_0000001818823770.png :alt: **Figure 1** Security group rules **Figure 1** Security group rules diff --git a/umn/source/faq/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst b/umn/source/faq/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst index 1f323f6..8ce4980 100644 --- a/umn/source/faq/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst +++ b/umn/source/faq/vpc_peering_connections/can_a_vpc_peering_connection_connect_vpcs_in_different_regions.rst @@ -7,16 +7,16 @@ Can a VPC Peering Connection Connect VPCs in Different Regions? A VPC peering connection only can connect VPCs in the same region. -:ref:`Figure 1 ` shows an application scenario of VPC peering connections. +:ref:`Figure 1 ` shows an application scenario of VPC peering connections. - There are two VPCs (VPC-A and VPC-B) in region A that are not connected. - Service servers (ECS-A01 and ECS-A02) are in VPC-A, and database servers (RDS-B01 and RDS-B02) are in VPC-B. The service servers and database servers cannot communicate with each other. - You need to create a VPC peering connection (peering-AB) between VPC-A and VPC-B so the service servers and database servers can communicate with each other. -.. _faq_connection_0001__en-us_topic_0046655036_fig4721642193711: +.. _faq_connection_0001__en-us_topic_0118498905_fig4721642193711: -.. figure:: /_static/images/en-us_image_0000001512591549.png +.. figure:: /_static/images/en-us_image_0000001818983018.png :alt: **Figure 1** VPC peering connection network diagram **Figure 1** VPC peering connection network diagram diff --git a/umn/source/faq/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst b/umn/source/faq/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst index fe39666..e12d8e1 100644 --- a/umn/source/faq/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst +++ b/umn/source/faq/vpc_peering_connections/why_did_communication_fail_between_vpcs_that_were_connected_by_a_vpc_peering_connection.rst @@ -68,14 +68,14 @@ If the CIDR blocks of VPCs connected by a VPC peering connection overlap, the co .. _vpc_faq_0069__fig465519155457: -.. figure:: /_static/images/en-us_image_0000001254335981.png +.. figure:: /_static/images/en-us_image_0000001818982898.png :alt: **Figure 1** Networking diagram (IPv4) **Figure 1** Networking diagram (IPv4) .. _vpc_faq_0069__fig098452131910: -.. figure:: /_static/images/en-us_image_0000001209777270.png +.. figure:: /_static/images/en-us_image_0000001818983474.png :alt: **Figure 2** Networking diagram (IPv4) **Figure 2** Networking diagram (IPv4) @@ -84,7 +84,7 @@ If CIDR blocks of VPCs overlap and some of their subnets overlap, you can create .. _vpc_faq_0069__fig920231311415: -.. figure:: /_static/images/en-us_image_0000001209321492.png +.. figure:: /_static/images/en-us_image_0000001818823702.png :alt: **Figure 3** Networking diagram (IPv4) **Figure 3** Networking diagram (IPv4) @@ -106,7 +106,7 @@ If CIDR blocks of VPCs overlap and some of their subnets overlap, you can create Incorrect Route Configuration for Local and Peer VPCs ----------------------------------------------------- -Check the routes in the route tables of the local and peer VPCs by referring to :ref:`Viewing Routes Configured for a VPC Peering Connection `. :ref:`Table 4 ` lists the items that you need to check. +:ref:`Viewing Routes Configured for a VPC Peering Connection `. :ref:`Table 4 ` lists the items that you need to check. .. _vpc_faq_0069__table513212558272: @@ -119,7 +119,7 @@ Check the routes in the route tables of the local and peer VPCs by referring to | | | | | - :ref:`Creating a VPC Peering Connection with Another VPC in Your Account ` | +------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Check the destinations of routes added to the route tables of the local and peer VPCs. | If the route destination is incorrect, change it by referring to :ref:`Modifying Routes Configured for a VPC Peering Connection `. | + | Check the destinations of routes added to the route tables of the local and peer VPCs. | If the route destination is incorrect, modify it by referring to :ref:`Modifying Routes Configured for a VPC Peering Connection `. | | | | | - In the route table of the local VPC, check whether the route destination is the CIDR block, subnet CIDR block, or related private IP address of the peer VPC. | | | - In the route table of the peer VPC, check whether the route destination is the CIDR block, subnet CIDR block, or related private IP address of the local VPC. | | @@ -134,10 +134,10 @@ Check the routes in the route tables of the local and peer VPCs by referring to Incorrect Network Configuration ------------------------------- -#. Check whether security group rules of the ECSs that need to communicate allow inbound traffic from each other by referring to :ref:`Viewing the Security Group of an ECS `. +#. Check whether the security group rules of the ECSs that need to communicate with each other are correctly configured. For details, see :ref:`Viewing the Security Group of an ECS `. - If the ECSs are associated with the same security group, you do not need to check their rules. - - If the ECSs are associated with different security groups, add an inbound rule to allow access from each other by referring to :ref:`Security Group Configuration Examples `. + - If the ECSs are in different security groups, you need to add inbound rules to allow access from the peer security group. For details, see :ref:`Security Group Configuration Examples `. #. Check whether the firewall of the ECS NIC blocks traffic. @@ -172,14 +172,11 @@ ECS Network Failure ------------------- #. Log in to the ECS. - #. Check whether the ECS NIC has an IP address assigned. - Linux ECS: Use the **ifconfig** or **ip address** command to view the IP address of the NIC. - Windows ECS: In the search box, enter **cmd** and press **Enter**. In the displayed command prompt, run the **ipconfig** command. - If the ECS NIC has no IP address assigned, see - #. Check whether the subnet gateway of the ECS can be pinged. a. In the ECS list, click the ECS name. diff --git a/umn/source/faq/vpcs_and_subnets/what_is_virtual_private_cloud.rst b/umn/source/faq/vpcs_and_subnets/what_is_virtual_private_cloud.rst index ce92b9f..3ac800d 100644 --- a/umn/source/faq/vpcs_and_subnets/what_is_virtual_private_cloud.rst +++ b/umn/source/faq/vpcs_and_subnets/what_is_virtual_private_cloud.rst @@ -5,12 +5,12 @@ What Is Virtual Private Cloud? ============================== -The Virtual Private Cloud (VPC) service enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security and simplifying network deployment. You can configure and manage the virtual networks as required. +Virtual Private Cloud (VPC) enables you to provision logically isolated virtual networks for Elastic Cloud Servers (ECSs), improving cloud resource security and simplifying network deployment. You can configure and manage the virtual networks as required. -Within your own VPC, you can create security groups and VPNs, configure IP address ranges, specify bandwidth sizes, manage the networks in the VPC, and make changes to these networks as needed, quickly and securely. You can also define rules to control communications between ECSs in the same security group or in different security groups. +Within your own VPC, you can create security groups and VPNs, configure IP address ranges, specify bandwidth sizes, manage the networks in the VPC, and make changes to these networks as needed, quickly and securely. You can also customize the ECS access rules within a security group and between security groups to enhance ECS security. -.. figure:: /_static/images/en-us_image_0209606948.png +.. figure:: /_static/images/en-us_image_0000001865663209.png :alt: **Figure 1** VPC components **Figure 1** VPC components 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 1f20d28..cb54a1b 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 @@ -46,7 +46,7 @@ Configuring a VPC for ECSs That Access the Internet Using EIPs +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ | 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 `. | | + | | | 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 | | | | | | @@ -76,14 +76,14 @@ Configuring a VPC for ECSs That Access the Internet Using EIPs +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ | 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 `. | | + | | | 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: + .. _en-us_topic_0017816228__en-us_topic_0118498861_table248245914136: .. table:: **Table 2** VPC tag key and value requirements @@ -109,7 +109,7 @@ Configuring a VPC for ECSs That Access the Internet Using EIPs | | - Special characters, including hyphens (-) and underscores (_) | | +-----------------------+------------------------------------------------------------------------+-----------------------+ - .. _en-us_topic_0017816228__en-us_topic_0013935842_table6536185812515: + .. _en-us_topic_0017816228__en-us_topic_0118498861_table6536185812515: .. table:: **Table 3** Subnet tag key and value requirements @@ -144,8 +144,8 @@ Configuring a VPC for ECSs That Access the Internet Using EIPs - :ref:`Step 4: Create a Security Group ` - :ref:`Step 5: Add a Security Group Rule ` -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001520717193.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663089.png .. toctree:: :maxdepth: 1 diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/overview.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/overview.rst index e6c2375..95aa148 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/overview.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/overview.rst @@ -9,7 +9,7 @@ If your ECSs need to access the Internet (for example, the ECSs functioning as t .. _vpc_qs_0022__fe457c1ec47c84d6fa3b87210d5b284eb: -.. figure:: /_static/images/en-us_image_0162332046.png +.. figure:: /_static/images/en-us_image_0000001818823006.png :alt: **Figure 1** Configuring the network **Figure 1** Configuring the network 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 99efccf..e142bcd 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 @@ -147,5 +147,5 @@ Procedure #. Click **Create Now**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001520717193.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663089.png 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 8fa113d..c107e74 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 @@ -32,7 +32,7 @@ Procedure 6. Set the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001197228903.png + .. figure:: /_static/images/en-us_image_0000001818823514.png :alt: **Figure 1** Create Subnet **Figure 1** Create Subnet @@ -70,14 +70,14 @@ Procedure +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | 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 `. | | + | | 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: + .. _vpc_qs_0010__en-us_topic_0013748726_table6536185812515: .. table:: **Table 2** Subnet tag key and value requirements @@ -118,5 +118,5 @@ 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_0000001675254021.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983298.png diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_3_assign_an_eip_and_bind_it_to_an_ecs.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_3_assign_an_eip_and_bind_it_to_an_ecs.rst index b78cd70..e7e7eed 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_3_assign_an_eip_and_bind_it_to_an_ecs.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_access_the_internet_using_eips/step_3_assign_an_eip_and_bind_it_to_an_ecs.rst @@ -38,7 +38,7 @@ Assigning an EIP #. Set the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001117669274.png + .. figure:: /_static/images/en-us_image_0000001818823034.png :alt: **Figure 1** Assign EIP **Figure 1** Assign EIP @@ -85,8 +85,8 @@ Assigning an EIP | Parameter | Requirement | Example Value | +=======================+=====================================================================+=======================+ | Key | - Cannot be left blank. | Ipv4_key1 | - | | - Must be unique for each EIP. | | - | | - Can contain a maximum of 36 characters. | | + | | - The key value must be unique for the same EIP. | | + | | - Can contain up to 36 characters. | | | | - Can contain only the following character types: | | | | | | | | - Uppercase letters | | @@ -94,7 +94,7 @@ Assigning an EIP | | - Digits | | | | - Special characters, including hyphens (-) and underscores (_) | | +-----------------------+---------------------------------------------------------------------+-----------------------+ - | Value | - Can contain a maximum of 43 characters. | 3005eip | + | Value | - Can contain up to 43 characters. | 3005eip | | | - Can contain only the following character types: | | | | | | | | - Uppercase letters | | @@ -115,7 +115,7 @@ Binding an EIP #. Select the instance that you want to bind the EIP to. - .. figure:: /_static/images/en-us_image_0000001166028070.png + .. figure:: /_static/images/en-us_image_0000001865662761.png :alt: **Figure 2** Bind EIP **Figure 2** Bind EIP @@ -135,5 +135,5 @@ You can use any of the following commands to obtain the domain name of an EIP: - nslookup [-qt=ptr] *EIP* - dig -x *EIP* -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.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 b488893..5a1df78 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 @@ -36,46 +36,48 @@ Procedure #. Configure the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001197426329.png + .. figure:: /_static/images/en-us_image_0000001865662885.png :alt: **Figure 1** Create Security Group **Figure 1** Create Security Group .. 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 | - | | | | - | | The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. | | - | | | | - | | :ref:`Table 1 ` describes the security group templates. | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | Description | Optional | N/A | - | | | | - | | Supplementary information about the security group. This parameter is optional. | | - | | | | - | | The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | 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_0000001627054062.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582681.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 94054e3..8d1886e 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 @@ -58,7 +58,7 @@ Procedure You can click **+** to add more inbound rules. - .. figure:: /_static/images/en-us_image_0284920908.png + .. figure:: /_static/images/en-us_image_0000001865662817.png :alt: **Figure 1** Add Inbound Rule **Figure 1** Add Inbound Rule @@ -88,7 +88,6 @@ Procedure | | - IP address range: 192.168.1.0/24 | | | | | | | | - **Security group**: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. 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. | | - | | - **IP address group**: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | | | | | | | If the source is a security group, this rule will apply to all instances associated with the selected security group. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ @@ -110,7 +109,7 @@ Procedure You can click **+** to add more outbound rules. - .. figure:: /_static/images/en-us_image_0284993717.png + .. figure:: /_static/images/en-us_image_0000001865582629.png :alt: **Figure 2** Add Outbound Rule **Figure 2** Add Outbound Rule @@ -140,7 +139,6 @@ Procedure | | - IP address range: 192.168.1.0/24 | | | | | | | | - **Security group**: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. 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. | | - | | - IP address group: A collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Description | Supplementary information about the security group rule. This parameter is optional. | N/A | | | | | @@ -151,5 +149,5 @@ Procedure The outbound rule list is displayed. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626734166.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823082.png diff --git a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/overview.rst b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/overview.rst index 8bd2e53..645fcb7 100644 --- a/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/overview.rst +++ b/umn/source/getting_started/configuring_a_vpc_for_ecss_that_do_not_require_internet_access/overview.rst @@ -9,7 +9,7 @@ If your ECSs do not require Internet access or need to access the Internet using .. _vpc_qs_0004__fd87108563a6848bba1a0f0295fef3515: -.. figure:: /_static/images/en-us_image_0162329244.png +.. figure:: /_static/images/en-us_image_0000001818823762.png :alt: **Figure 1** Configuring the network **Figure 1** Configuring the network 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 697dc5e..5c75313 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 @@ -147,5 +147,5 @@ Procedure #. Click **Create Now**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001520717193.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663089.png 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 565979a..d599bf4 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 @@ -32,7 +32,7 @@ Procedure 6. Set the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001197228903.png + .. figure:: /_static/images/en-us_image_0000001818823514.png :alt: **Figure 1** Create Subnet **Figure 1** Create Subnet @@ -70,14 +70,14 @@ Procedure +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | 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 `. | | + | | 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: + .. _vpc_qs_0006__en-us_topic_0013748726_table6536185812515: .. table:: **Table 2** Subnet tag key and value requirements @@ -118,5 +118,5 @@ 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_0000001675254021.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983298.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 ec9b39f..f60cb13 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 @@ -36,46 +36,48 @@ Procedure #. Configure the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001197426329.png + .. figure:: /_static/images/en-us_image_0000001865662885.png :alt: **Figure 1** Create Security Group **Figure 1** Create Security Group .. 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 | - | | | | - | | The system provides several security group templates for you to create a security group. A security group template has preconfigured inbound and outbound rules. You can select a template based on your service requirements. | | - | | | | - | | :ref:`Table 1 ` describes the security group templates. | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ - | Description | Optional | N/A | - | | | | - | | Supplementary information about the security group. This parameter is optional. | | - | | | | - | | The security group description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------+ + | 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_0000001627054062.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582681.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 8ced623..1e544a0 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 @@ -58,7 +58,7 @@ Procedure You can click **+** to add more inbound rules. - .. figure:: /_static/images/en-us_image_0284920908.png + .. figure:: /_static/images/en-us_image_0000001865662817.png :alt: **Figure 1** Add Inbound Rule **Figure 1** Add Inbound Rule @@ -88,7 +88,6 @@ Procedure | | - IP address range: 192.168.1.0/24 | | | | | | | | - **Security group**: The source is from another security group. You can select a security group in the same region under the current account from the drop-down list. 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. | | - | | - **IP address group**: An IP address group is a collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | | | | | | | If the source is a security group, this rule will apply to all instances associated with the selected security group. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ @@ -110,7 +109,7 @@ Procedure You can click **+** to add more outbound rules. - .. figure:: /_static/images/en-us_image_0284993717.png + .. figure:: /_static/images/en-us_image_0000001865582629.png :alt: **Figure 2** Add Outbound Rule **Figure 2** Add Outbound Rule @@ -140,7 +139,6 @@ Procedure | | - IP address range: 192.168.1.0/24 | | | | | | | | - **Security group**: The destination is from another security group. You can select a security group in the same region under the current account from the drop-down list. 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. | | - | | - IP address group: A collection of one or more IP addresses. You can select an available IP address group from the drop-down list. An IP address group can help you manage IP address ranges and IP addresses with same security requirements in a more simple way. | | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Description | Supplementary information about the security group rule. This parameter is optional. | N/A | | | | | @@ -151,5 +149,5 @@ Procedure The outbound rule list is displayed. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626734166.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823082.png diff --git a/umn/source/glossary.rst b/umn/source/glossary.rst index 9133640..2f075c6 100644 --- a/umn/source/glossary.rst +++ b/umn/source/glossary.rst @@ -2,7 +2,7 @@ .. _vpc_faq_0106: -Glossary -======== +**Glossary** +============ -For details about the terms involved in this document, see `Glossary `__. +For details about the glossaries in this document, see `Glossary `__. diff --git a/umn/source/monitoring/creating_an_alarm_rule.rst b/umn/source/monitoring/creating_an_alarm_rule.rst index 5c86995..89a4d13 100644 --- a/umn/source/monitoring/creating_an_alarm_rule.rst +++ b/umn/source/monitoring/creating_an_alarm_rule.rst @@ -29,7 +29,7 @@ Procedure .. note:: - For more information about alarm rules, see the *Cloud Eye User Guide*. + For more information about alarm rules, see `Cloud Eye User Guide `__. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675258889.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663473.png diff --git a/umn/source/monitoring/viewing_metrics.rst b/umn/source/monitoring/viewing_metrics.rst index e99b41c..ded9a8b 100644 --- a/umn/source/monitoring/viewing_metrics.rst +++ b/umn/source/monitoring/viewing_metrics.rst @@ -18,7 +18,7 @@ Procedure (**Elastic IP and Bandwidth** Console) #. 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**. -#. On the **EIPs** page, search for the EIP, click **More** in the **Operation** column, and click **View Metric** to view the monitoring metric details. +#. On the **EIPs** page, locate the target EIP and click **View Metric** in the **Monitoring** column to view the monitoring metrics. #. In the navigation pane on the left, choose **Elastic IP and Bandwidth** > **Shared Bandwidths**. #. 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. @@ -32,7 +32,7 @@ Procedure (**Cloud Eye** Console) 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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663457.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001865663461.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 25e9972..dca39b4 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 @@ -18,7 +18,7 @@ If your cloud account meets your permissions requirements, you can skip this sec Prerequisites ------------- -Learn about the permissions (see :ref:`Permissions `) supported by VPC and choose policies or roles according to your requirements. +Before granting permissions to user groups, learn about permissions (:ref:`Permissions `) for VPC. To grant permissions for other services, learn about all `permissions `__ supported by IAM. @@ -27,7 +27,7 @@ Process Flow .. _permission_0003__fig1447123814172: -.. figure:: /_static/images/en-us_image_0171311823.png +.. figure:: /_static/images/en-us_image_0000001818823522.png :alt: **Figure 1** Process for granting VPC permissions **Figure 1** Process for granting VPC permissions @@ -40,5 +40,5 @@ 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 **VPCReadOnlyAccess** 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 **VPCReadOnlyAccess** 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 **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. diff --git a/umn/source/route_tables/configuring_an_snat_server.rst b/umn/source/route_tables/configuring_an_snat_server.rst index 622ef19..a88d6d3 100644 --- a/umn/source/route_tables/configuring_an_snat_server.rst +++ b/umn/source/route_tables/configuring_an_snat_server.rst @@ -93,7 +93,7 @@ Procedure **iptables -t nat -A POSTROUTING -o eth0 -s subnet -j SNAT --to nat-instance-ip** - .. figure:: /_static/images/en-us_image_0214585308.png + .. figure:: /_static/images/en-us_image_0000001818983066.png :alt: **Figure 1** Configuring SNAT **Figure 1** Configuring SNAT @@ -122,7 +122,7 @@ Procedure .. _vpc_route_0004__en-us_topic_0212076959_fig8358771201535: - .. figure:: /_static/images/en-us_image_0214585309.png + .. figure:: /_static/images/en-us_image_0000001818823278.png :alt: **Figure 2** Verifying configuration **Figure 2** Verifying configuration @@ -133,5 +133,5 @@ Procedure After these operations are complete, if the network communication still fails, check your security group and firewall configuration to see whether required traffic is allowed. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001490118666.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582817.png diff --git a/umn/source/route_tables/managing_route_tables/associating_a_route_table_with_a_subnet.rst b/umn/source/route_tables/managing_route_tables/associating_a_route_table_with_a_subnet.rst index 7731dc7..577202a 100644 --- a/umn/source/route_tables/managing_route_tables/associating_a_route_table_with_a_subnet.rst +++ b/umn/source/route_tables/managing_route_tables/associating_a_route_table_with_a_subnet.rst @@ -40,12 +40,12 @@ Procedure 6. Select the subnet to be associated. - .. figure:: /_static/images/en-us_image_0000001540846821.png + .. figure:: /_static/images/en-us_image_0000001865662969.png :alt: **Figure 1** Associate Subnet **Figure 1** Associate Subnet 7. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626735570.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983026.png diff --git a/umn/source/route_tables/managing_route_tables/changing_the_route_table_associated_with_a_subnet.rst b/umn/source/route_tables/managing_route_tables/changing_the_route_table_associated_with_a_subnet.rst index dbe8d59..bb9c056 100644 --- a/umn/source/route_tables/managing_route_tables/changing_the_route_table_associated_with_a_subnet.rst +++ b/umn/source/route_tables/managing_route_tables/changing_the_route_table_associated_with_a_subnet.rst @@ -31,5 +31,5 @@ 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_0000001626575750.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823210.png diff --git a/umn/source/route_tables/managing_route_tables/creating_a_custom_route_table.rst b/umn/source/route_tables/managing_route_tables/creating_a_custom_route_table.rst index c60f0b1..a467fdd 100644 --- a/umn/source/route_tables/managing_route_tables/creating_a_custom_route_table.rst +++ b/umn/source/route_tables/managing_route_tables/creating_a_custom_route_table.rst @@ -31,7 +31,7 @@ Procedure 5. In the upper right corner, click **Create Route Table**. On the displayed page, configure parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001856641285.png + .. figure:: /_static/images/en-us_image_0000001818983038.png :alt: **Figure 1** Create Route Table **Figure 1** Create Route Table @@ -66,5 +66,5 @@ Procedure b. Click **Associate Subnet** and select the target subnets to be associated. c. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001627055454.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823254.png diff --git a/umn/source/route_tables/managing_route_tables/deleting_a_route_table.rst b/umn/source/route_tables/managing_route_tables/deleting_a_route_table.rst index fde7885..81b8c28 100644 --- a/umn/source/route_tables/managing_route_tables/deleting_a_route_table.rst +++ b/umn/source/route_tables/managing_route_tables/deleting_a_route_table.rst @@ -36,5 +36,5 @@ Procedure 6. Click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675615337.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983042.png diff --git a/umn/source/route_tables/managing_route_tables/exporting_route_table_information.rst b/umn/source/route_tables/managing_route_tables/exporting_route_table_information.rst index bb686e4..7ab2d11 100644 --- a/umn/source/route_tables/managing_route_tables/exporting_route_table_information.rst +++ b/umn/source/route_tables/managing_route_tables/exporting_route_table_information.rst @@ -23,10 +23,9 @@ Procedure 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. +5. In the route table list, select one or more route tables you want to export and click **Export** in the upper left corner. - 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. + The system will automatically export information about all of your route tables as an Excel file to a local directory. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626895486.png -.. |image3| image:: /_static/images/en-us_image_0214585307.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582809.png diff --git a/umn/source/route_tables/managing_route_tables/viewing_route_table_information.rst b/umn/source/route_tables/managing_route_tables/viewing_route_table_information.rst index 5642fed..287b79d 100644 --- a/umn/source/route_tables/managing_route_tables/viewing_route_table_information.rst +++ b/umn/source/route_tables/managing_route_tables/viewing_route_table_information.rst @@ -34,5 +34,5 @@ Procedure a. On the **Summary** tab page, view the basic information and routes of the route table. 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_0000001675415213.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582825.png diff --git a/umn/source/route_tables/managing_route_tables/viewing_the_route_table_associated_with_a_subnet.rst b/umn/source/route_tables/managing_route_tables/viewing_the_route_table_associated_with_a_subnet.rst index d10d0bf..0769822 100644 --- a/umn/source/route_tables/managing_route_tables/viewing_the_route_table_associated_with_a_subnet.rst +++ b/umn/source/route_tables/managing_route_tables/viewing_the_route_table_associated_with_a_subnet.rst @@ -35,5 +35,5 @@ 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_0000001675375297.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582701.png diff --git a/umn/source/route_tables/managing_routes/adding_a_custom_route.rst b/umn/source/route_tables/managing_routes/adding_a_custom_route.rst index 386c0f0..63d8f33 100644 --- a/umn/source/route_tables/managing_routes/adding_a_custom_route.rst +++ b/umn/source/route_tables/managing_routes/adding_a_custom_route.rst @@ -35,7 +35,7 @@ Procedure You can click **+** to add more routes. - .. figure:: /_static/images/en-us_image_0000001856562181.png + .. figure:: /_static/images/en-us_image_0000001818823258.png :alt: **Figure 1** Add Route **Figure 1** Add Route @@ -70,5 +70,5 @@ Procedure 7. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675255405.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865662989.png diff --git a/umn/source/route_tables/managing_routes/deleting_a_route.rst b/umn/source/route_tables/managing_routes/deleting_a_route.rst index 95d2d57..3a93828 100644 --- a/umn/source/route_tables/managing_routes/deleting_a_route.rst +++ b/umn/source/route_tables/managing_routes/deleting_a_route.rst @@ -45,5 +45,5 @@ Procedure 7. Confirm the information and click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675375405.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823286.png diff --git a/umn/source/route_tables/managing_routes/modifying_a_route.rst b/umn/source/route_tables/managing_routes/modifying_a_route.rst index 6d3aa4a..2100ef8 100644 --- a/umn/source/route_tables/managing_routes/modifying_a_route.rst +++ b/umn/source/route_tables/managing_routes/modifying_a_route.rst @@ -37,33 +37,33 @@ Procedure .. table:: **Table 1** Parameter descriptions - +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ - | Parameter | Description | Example Value | - +=======================+======================================================================================================================================================================+========================+ - | Destination | Mandatory | IPv4: 192.168.0.0/16 | - | | | | - | | Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation. | | - | | | | - | | The destination of each route in a route table must be unique. The destination cannot overlap with any subnet in the VPC. | | - +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ - | Next Hop Type | Mandatory | VPC peering connection | - | | | | - | | Set the type of the next hop. | | - | | | | - | | .. note:: | | - | | | | - | | When you add or modify a custom route in a default route table, the next hop type of the route cannot be set to **VPN connection** or **Direct Connect gateway**. | | - +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ - | Next Hop | Mandatory | peer-AB | - | | | | - | | Set the next hop. The resources in the drop-down list box are displayed based on the selected next hop type. | | - +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ - | Description | Optional | ``-`` | - | | | | - | | Enter the description of the route in the text box as required. | | - +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------+ + +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Item | Description | Example Value | + +=======================+======================================================================================================================================================================+=======================+ + | Destination | Mandatory | Pv4: 192.168.0.0/16 | + | | | | + | | Enter the destination of the route. You can enter a single IP address or an IP address range in CIDR notation. | | + | | | | + | | The destination of each route must be unique. The destination cannot overlap with any subnet CIDR block in the VPC. | | + +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Next Hop Type | Mandatory | VPC peering | + | | | | + | | Set the type of the next hop. | | + | | | | + | | .. note:: | | + | | | | + | | When you add or modify a custom route in a default route table, the next hop type of the route cannot be set to **VPN connection** or **Direct Connect gateway**. | | + +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Next Hop | Mandatory | peer-AB | + | | | | + | | Set the next hop. The resources in the drop-down list box are displayed based on the selected next hop type. | | + +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | Description | Optional | ``-`` | + | | | | + | | Enter the description of the route in the text box as required. | | + +-----------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ 8. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001627055450.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823338.png diff --git a/umn/source/route_tables/managing_routes/replicating_a_route.rst b/umn/source/route_tables/managing_routes/replicating_a_route.rst index 9537378..0434d91 100644 --- a/umn/source/route_tables/managing_routes/replicating_a_route.rst +++ b/umn/source/route_tables/managing_routes/replicating_a_route.rst @@ -13,11 +13,11 @@ This section describes how to replicate routes among all route tables of a VPC. Notes and Constraints --------------------- -:ref:`Table 1 ` shows whether routes of different types can be replicated to default or custom route tables. +:ref:`Table 1 ` shows whether routes of different types can be replicated to default or custom route tables. For example, if the next hop type of a route is a server, this route can be replicated to both default or custom route tables. If the next hop type of a route is a Direct Connect gateway, the route cannot be replicated to the default route table, but can be replicated to a custom route table. -.. _vpc_route01_0013__route_0001_table1727714140542: +.. _vpc_route01_0013__en-us_topic_0121831807_table1727714140542: .. table:: **Table 1** Route replication @@ -68,5 +68,5 @@ Procedure 7. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626735566.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823270.png diff --git a/umn/source/route_tables/route_tables_and_routes.rst b/umn/source/route_tables/route_tables_and_routes.rst index e5e826f..a797aae 100644 --- a/umn/source/route_tables/route_tables_and_routes.rst +++ b/umn/source/route_tables/route_tables_and_routes.rst @@ -11,7 +11,7 @@ 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. A subnet can only be associated with one route table, but you can associate multiple subnets with the same route table. -.. figure:: /_static/images/en-us_image_0000001650535960.png +.. figure:: /_static/images/en-us_image_0000001865662949.png :alt: **Figure 1** Route tables **Figure 1** Route tables @@ -49,11 +49,11 @@ You can add routes to default and custom route tables and configure the destinat - Custom routes: These are routes that you can add, modify, and delete. The destination of a custom route cannot overlap with that of a system route. - You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. :ref:`Table 1 ` lists the supported types of next hops. + You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. :ref:`Table 1 ` lists the supported types of next hops. You cannot add two routes with the same destination to a VPC route table even if their next hop types are different. The route priority depends on the destination. According to the longest match routing rule, the destination with a higher matching degree is preferentially selected for packet forwarding. - .. _vpc_route01_0001__en-us_topic_0038263963_route_0001_table1727714140542: + .. _vpc_route01_0001__en-us_topic_0118498988_en-us_topic_0121831807_table1727714140542: .. table:: **Table 1** Next hop type @@ -95,7 +95,7 @@ Custom Route Table Configuration Process .. _vpc_route01_0001__en-us_topic_0212076956_fig16862186152219: -.. figure:: /_static/images/en-us_image_0214585341.png +.. figure:: /_static/images/en-us_image_0000001818823214.png :alt: **Figure 2** Route table configuration process **Figure 2** Route table configuration process diff --git a/umn/source/service_overview/basic_concepts/elastic_ip.rst b/umn/source/service_overview/basic_concepts/elastic_ip.rst index a7635e0..ca1722e 100644 --- a/umn/source/service_overview/basic_concepts/elastic_ip.rst +++ b/umn/source/service_overview/basic_concepts/elastic_ip.rst @@ -10,7 +10,7 @@ The Elastic IP (EIP) service enables your cloud resources to communicate with th Each EIP can be used by only one cloud resource at a time. -.. figure:: /_static/images/en-us_image_0209583952.png +.. figure:: /_static/images/en-us_image_0000001818823042.png :alt: **Figure 1** Accessing the Internet using an EIP **Figure 1** Accessing the Internet using an EIP diff --git a/umn/source/service_overview/basic_concepts/firewall.rst b/umn/source/service_overview/basic_concepts/firewall.rst index 7580aca..487970c 100644 --- a/umn/source/service_overview/basic_concepts/firewall.rst +++ b/umn/source/service_overview/basic_concepts/firewall.rst @@ -6,3 +6,11 @@ Firewall ======== A firewall is an optional layer of security for your subnets. After you associate one or more subnets with a firewall, you can control traffic in and out of the subnets. + + +.. figure:: /_static/images/en-us_image_0000001818982946.png + :alt: **Figure 1** Security groups and firewalls + + **Figure 1** Security groups and firewalls + +Similar to security groups, firewalls control access to subnets and add an additional layer of defense to your subnets. Security groups only have the "allow" rules, but firewalls have both "allow" and "deny" rules. You can use firewalls together with security groups to implement comprehensive and fine-grained access control. diff --git a/umn/source/service_overview/basic_concepts/index.rst b/umn/source/service_overview/basic_concepts/index.rst index 48b47af..429a336 100644 --- a/umn/source/service_overview/basic_concepts/index.rst +++ b/umn/source/service_overview/basic_concepts/index.rst @@ -14,7 +14,6 @@ Basic Concepts - :ref:`VPC Peering Connection ` - :ref:`Firewall ` - :ref:`Virtual IP Address ` -- :ref:`Region and AZ ` .. toctree:: :maxdepth: 1 @@ -29,4 +28,3 @@ Basic Concepts vpc_peering_connection firewall virtual_ip_address - region_and_az diff --git a/umn/source/service_overview/basic_concepts/route_table.rst b/umn/source/service_overview/basic_concepts/route_table.rst index 244736b..b04e658 100644 --- a/umn/source/service_overview/basic_concepts/route_table.rst +++ b/umn/source/service_overview/basic_concepts/route_table.rst @@ -11,7 +11,7 @@ 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. A subnet can only be associated with one route table, but you can associate multiple subnets with the same route table. -.. figure:: /_static/images/en-us_image_0000001650535960.png +.. figure:: /_static/images/en-us_image_0000001865662949.png :alt: **Figure 1** Route tables **Figure 1** Route tables @@ -28,7 +28,7 @@ A route table contains a set of routes that are used to determine where network Route ----- -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. +You can add routes to default and custom route tables and configure the destination type 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. @@ -49,11 +49,11 @@ You can add routes to default and custom route tables and configure the destinat - Custom routes: These are routes that you can add, modify, and delete. The destination of a custom route cannot overlap with that of a system route. - You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. :ref:`Table 1 ` lists the supported types of next hops. + You can add a custom route and configure the destination, next hop type, and next hop in the route to determine where network traffic is directed. :ref:`Table 1 ` lists the supported types of next hops. You cannot add two routes with the same destination to a VPC route table even if their next hop types are different. The route priority depends on the destination. According to the longest match routing rule, the destination with a higher matching degree is preferentially selected for packet forwarding. - .. _en-us_topic_0038263963__route_0001_table1727714140542: + .. _en-us_topic_0038263963__en-us_topic_0121831807_table1727714140542: .. table:: **Table 1** Next hop type @@ -86,4 +86,4 @@ You can add routes to default and custom route tables and configure the destinat If you specify the destination when creating a resource, a system route is delivered. If you do not specify a destination when creating a resource, a custom route that can be modified or deleted is delivered. - For example, when you create a NAT gateway, the system automatically delivers a custom route without a specific destination (0.0.0.0/0 is used by default). In this case, you can change the destination. However, when you create a VPN connection or Direct Connect gateway, you need to specify the remote subnet, that is, the destination of a route. In this case, the system delivers this system route. Do not modify the route destination on the **Route Tables** page. If you do, the destination will be inconsistent with the configured remote subnet. To modify the route destination, go to the specific resource page and modify the remote subnet, then the route destination will be changed accordingly. + For example, when you create a NAT gateway, the system automatically delivers a custom route without a specific destination (0.0.0.0/0 is used by default). In this case, you can change the destination. However, when you create a VPN connection or Direct Connect gateway, you need to specify the remote subnet, that is, the destination of a route. In this case, the system delivers a system route. Do not modify the route destination on the **Route Tables** page. If you do, the destination will be inconsistent with the configured remote subnet. To modify the route destination, go to the specific resource page and modify the remote subnet, then the route destination will be changed accordingly. diff --git a/umn/source/service_overview/basic_concepts/security_group.rst b/umn/source/service_overview/basic_concepts/security_group.rst index 218837d..8a23e5c 100644 --- a/umn/source/service_overview/basic_concepts/security_group.rst +++ b/umn/source/service_overview/basic_concepts/security_group.rst @@ -23,9 +23,9 @@ Like whitelists, security group rules work as follows: ::/0 represents all IPv6 addresses. -:ref:`Table 1 ` uses custom security group sg-AB as an example to describe its inbound and outbound rules in detail. +:ref:`Table 1 ` uses custom security group sg-AB as an example to describe its inbound and outbound rules in detail. -.. _vpc_concepts_0005__en-us_topic_0073379079_table102261597217: +.. _vpc_concepts_0005__en-us_topic_0118534002_table102261597217: .. table:: **Table 1** Rules in security group sg-AB diff --git a/umn/source/service_overview/basic_concepts/shared_snat.rst b/umn/source/service_overview/basic_concepts/shared_snat.rst index 483ed29..7e5f4d3 100644 --- a/umn/source/service_overview/basic_concepts/shared_snat.rst +++ b/umn/source/service_overview/basic_concepts/shared_snat.rst @@ -11,25 +11,12 @@ The VPC service provides free SNAT function, which allows ECSs to use a limited .. _vpc_concepts_0010__f04fc5d5739d142e5b38d73f3746f6cad: -.. figure:: /_static/images/en-us_image_0118499140.png +.. figure:: /_static/images/en-us_image_0000001818983170.png :alt: **Figure 1** SNAT function **Figure 1** SNAT function - To enable shared SNAT using the API, refer to `Updating a Router `__ and set **enable_snat** to **true**. -- To enable shared SNAT on the management console: - - #. Log in to the management console. - - #. 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. @@ -42,7 +29,7 @@ To prevent an ECS from connecting to the Internet but allow the ECS to access 19 After this rule is deleted, ECSs associated with this security group are not allowed to access any network, including the internal networks in the VPC of the ECSs. - .. figure:: /_static/images/en-us_image_0152667656.png + .. figure:: /_static/images/en-us_image_0000001865663121.png :alt: **Figure 2** Deleting the default outbound rule from the security group **Figure 2** Deleting the default outbound rule from the security group @@ -52,7 +39,7 @@ To prevent an ECS from connecting to the Internet but allow the ECS to access 19 The following shows the added outbound rule that allows the ECS to access the 192.168.10.0/24 CIDR block. - .. figure:: /_static/images/en-us_image_0152668782.png + .. figure:: /_static/images/en-us_image_0000001818823386.png :alt: **Figure 3** Adding an outbound rule for the security group **Figure 3** Adding an outbound rule for the security group @@ -63,5 +50,3 @@ 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/basic_concepts/subnet.rst b/umn/source/service_overview/basic_concepts/subnet.rst index e162903..46e2521 100644 --- a/umn/source/service_overview/basic_concepts/subnet.rst +++ b/umn/source/service_overview/basic_concepts/subnet.rst @@ -7,6 +7,8 @@ Subnet A subnet is a unique CIDR block with a range of IP addresses in a VPC. All resources in a VPC must be deployed on subnets. +- By default, all instances in different subnets of the same VPC can communicate with each other. If you have a VPC with two subnets in it, they can communicate with each other by default. + - After a subnet is created, its CIDR block cannot be modified. Subnets in the same VPC cannot overlap. A subnet mask can be between the netmask of its VPC CIDR block and /29 netmask. If a VPC CIDR block is 10.0.0.0/16, its subnet mask can be between 16 and 29. diff --git a/umn/source/service_overview/basic_concepts/virtual_ip_address.rst b/umn/source/service_overview/basic_concepts/virtual_ip_address.rst index 3df9627..0476058 100644 --- a/umn/source/service_overview/basic_concepts/virtual_ip_address.rst +++ b/umn/source/service_overview/basic_concepts/virtual_ip_address.rst @@ -5,9 +5,9 @@ Virtual IP Address ================== -A virtual IP address can be shared among multiple ECSs. An ECS can have both private and virtual IP addresses, and you can access the ECS through either IP address. A virtual IP address has the same network access capabilities as a private IP address, including layer 2 and layer 3 communication in VPCs, access between VPCs using VPC peering connections, as well as access through EIPs, VPN connections, and Direct Connect connections. +A virtual IP address can be shared among multiple ECSs. An ECS can have a private and a virtual IP address, which allows your users to access the ECS through either IP address. You can use either IP address to enable layer 2 and layer 3 communications in a VPC, access a different VPC using peering connections, and access cloud servers through EIPs, Direct Connect connections, and VPN connections. -You can bind ECSs deployed in active/standby mode with the same virtual IP address, and then bind an EIP to the virtual IP address. Virtual IP addresses can work together with Keepalived to ensure high availability and disaster recovery. If the active ECS is faulty, the standby ECS automatically takes over services from the active one. +You can bind a virtual IP address to ECSs deployed in the active/standby pair, and then bind an EIP to the virtual IP address. Virtual IP addresses can work together with Keepalived to ensure high availability and disaster recovery. If the active ECS is faulty, the standby ECS automatically takes over services from the active one. Networking ---------- @@ -16,7 +16,7 @@ Virtual IP addresses are used for high availability and can work together with K - **Networking mode 1**: HA - If you want to improve service availability and avoid single points of failure, you can deploy ECSs in the active/standby mode or deploy one active ECS and multiple standby ECSs. In this arrangement, the ECSs all use the same virtual IP address. If the active ECS becomes faulty, a standby ECS takes over services from the active ECS and services continue uninterrupted. + To improve service availability and eliminate single points of failure, you can deploy ECSs in the active/standby pair or deploy one active ECS and multiple standby ECSs. And then, you can bind the same virtual IP address to these ECSs. If the active ECS becomes faulty, a standby ECS takes over services from the active ECS and services continue uninterrupted. .. figure:: /_static/images/en-us_image_0209608153.png @@ -24,8 +24,8 @@ Virtual IP addresses are used for high availability and can work together with K **Figure 1** Networking diagram of the HA mode - - In this configuration, a single virtual IP address is bound to two ECSs in the same subnet. - - Keepalived is then used to configure the two ECSs to work in the active/standby mode. Follow industry standards for configuring Keepalived. The details are not included here. + - As shown in the above figure, bind a virtual IP address to two ECSs in the same subnet. + - Configure Keepalived for the two ECSs to work in the active/standby pair. Follow industry standards for configuring Keepalived. The details are not included here. - **Networking mode 2**: HA load balancing cluster @@ -38,7 +38,7 @@ Virtual IP addresses are used for high availability and can work together with K **Figure 2** HA load balancing cluster - Bind a single virtual IP address to two ECSs. - - Configure the two ECSs as LVS nodes working as direct routers and use Keepalived to configure the nodes in the active/standby mode. The two ECSs will evenly forward requests to different backend servers. + - Configure the two ECSs as LVS nodes working as direct routers and use Keepalived to configure the nodes in the active/standby pair. The two ECSs will evenly forward requests to different backend servers. - Configure two more ECSs as backend servers. - Disable the source/destination check for the two backend servers. @@ -53,4 +53,4 @@ Application Scenarios - Using a VPN, Direct Connect, or VPC peering connection to access a virtual IP address - To ensure high availability and access to the Internet, use a VPN for security and Direct Connect for a stable connection. The VPC peering connection is needed so that the VPCs in the same region can communicate with each other. + To ensure high availability and access to the Internet, use VPN for security and Direct Connect for stable connectivity. The VPC peering connection is needed so that the VPCs in the same region can communicate with each other. diff --git a/umn/source/service_overview/basic_concepts/vpc_peering_connection.rst b/umn/source/service_overview/basic_concepts/vpc_peering_connection.rst index 6abc9dc..035926a 100644 --- a/umn/source/service_overview/basic_concepts/vpc_peering_connection.rst +++ b/umn/source/service_overview/basic_concepts/vpc_peering_connection.rst @@ -18,7 +18,7 @@ A VPC peering connection is a networking connection that connects two VPCs for t .. _vpc_concepts_0011__en-us_topic_0046655036_fig4721642193711: -.. figure:: /_static/images/en-us_image_0000001512591549.png +.. figure:: /_static/images/en-us_image_0000001818983018.png :alt: **Figure 1** VPC peering connection network diagram **Figure 1** VPC peering connection network diagram diff --git a/umn/source/service_overview/document_usage_instructions.rst b/umn/source/service_overview/document_usage_instructions.rst index dbf573e..8993d76 100644 --- a/umn/source/service_overview/document_usage_instructions.rst +++ b/umn/source/service_overview/document_usage_instructions.rst @@ -10,4 +10,4 @@ Instructions for using this document are as follows: - To facilitate your operations, the management console may provide more than one way for you to perform a task or an operation. This document describes only the main way. - You can click |image1| next to some parameter values to quickly edit the values. This document does not describe this function. -.. |image1| image:: /_static/images/en-us_image_0157880395.png +.. |image1| image:: /_static/images/en-us_image_0000001818823038.png diff --git a/umn/source/service_overview/index.rst b/umn/source/service_overview/index.rst index 13643f5..f3d439a 100644 --- a/umn/source/service_overview/index.rst +++ b/umn/source/service_overview/index.rst @@ -12,6 +12,7 @@ Service Overview - :ref:`VPC and Other Services ` - :ref:`Permissions ` - :ref:`Basic Concepts ` +- :ref:`Region and AZ ` - :ref:`Document Usage Instructions ` .. toctree:: @@ -25,4 +26,5 @@ Service Overview vpc_and_other_services permissions basic_concepts/index + region_and_az document_usage_instructions diff --git a/umn/source/service_overview/permissions.rst b/umn/source/service_overview/permissions.rst index 50d1a89..632ddad 100644 --- a/umn/source/service_overview/permissions.rst +++ b/umn/source/service_overview/permissions.rst @@ -18,7 +18,7 @@ VPC Permissions New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned. -VPC is a project-level service deployed for specific regions. When you set **Scope** to **Region-specific projects** and select the specified projects in the specified regions , the users only have permissions for VPCs in the selected projects. If you set **Scope** to **All resources**, users have permissions for VPCs in all region-specific projects. When accessing VPCs, the users need to switch to the authorized region. +VPC is a project-level service deployed for specific regions. When you set **Scope** to **Region-specific projects** and select the specified projects in the specified regions, the users only have permissions for VPCs in the selected projects. If you set **Scope** to **All resources**, users have permissions for VPCs in all region-specific projects. When accessing VPCs, the users need to switch to the authorized region. You can grant permissions by using roles and policies. @@ -49,89 +49,89 @@ You can grant permissions by using roles and policies. .. table:: **Table 2** Common operations supported by system-defined permissions - +--------------------------------------------+-------------------+-------------------+----------------+ - | Operation | VPCReadOnlyAccess | VPC Administrator | VPC FullAccess | - +============================================+===================+===================+================+ - | Creating a VPC | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a VPC | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a VPC | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Viewing VPC information | Y | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Creating a subnet | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Viewing subnet information | Y | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a subnet | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a subnet | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Creating a security group | x | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Viewing security group information | Y | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a security group | x | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a security group | x | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Adding a security group rule | x | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Viewing a security group rule | Y | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a security group rule | x | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a security group rule | x | x | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Creating a firewall | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Viewing a firewall | Y | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a firewall | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a firewall | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Adding a firewall rule | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a firewall rule | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a firewall rule | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Creating a VPC peering connection | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a VPC peering connection | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a VPC peering connection | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Querying a VPC peering connection | Y | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Accepting a VPC peering connection request | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Rejecting a VPC peering connection request | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Creating a route table | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a route table | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a route table | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Associating a route table with a subnet | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Adding a route | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Modifying a route | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a route | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Creating a VPC flow log | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Viewing a VPC flow log | Y | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Enabling or disabling a VPC flow log | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ - | Deleting a VPC flow log | x | Y | Y | - +--------------------------------------------+-------------------+-------------------+----------------+ + +--------------------------------------------+--------------------+-------------------+----------------+ + | Operation | VPC ReadOnlyAccess | VPC Administrator | VPC FullAccess | + +============================================+====================+===================+================+ + | Creating a VPC | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a VPC | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a VPC | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Viewing VPC information | Y | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Creating a subnet | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Viewing subnet information | Y | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a subnet | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a subnet | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Creating a security group | x | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Viewing security group information | Y | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a security group | x | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a security group | x | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Adding a security group rule | x | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Viewing a security group rule | Y | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a security group rule | x | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a security group rule | x | x | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Creating a firewall | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Viewing a firewall | Y | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a firewall | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a firewall | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Adding a firewall rule | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a firewall rule | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a firewall rule | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Creating a VPC peering connection | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a VPC peering connection | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a VPC peering connection | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Querying a VPC peering connection | Y | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Accepting a VPC peering connection request | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Rejecting a VPC peering connection request | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Creating a route table | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a route table | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a route table | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Associating a route table with a subnet | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Adding a route | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Modifying a route | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a route | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Creating a VPC flow log | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Viewing a VPC flow log | Y | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Enabling or disabling a VPC flow log | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ + | Deleting a VPC flow log | x | Y | Y | + +--------------------------------------------+--------------------+-------------------+----------------+ Helpful Links ------------- diff --git a/umn/source/service_overview/product_advantages.rst b/umn/source/service_overview/product_advantages.rst index 81e58c8..8c87f86 100644 --- a/umn/source/service_overview/product_advantages.rst +++ b/umn/source/service_overview/product_advantages.rst @@ -16,7 +16,7 @@ Secure and Reliable VPCs are logically isolated through tunneling technologies. By default, different VPCs cannot communicate with each other. You can use firewalls to protect subnets and use security groups to protect ECSs. They add additional layers of security to your VPCs, so your network is secure. -.. figure:: /_static/images/en-us_image_0209577986.png +.. figure:: /_static/images/en-us_image_0000001818983218.png :alt: **Figure 1** Secure and Reliable **Figure 1** Secure and Reliable @@ -44,15 +44,15 @@ Advantage Comparison .. table:: **Table 1** Comparison between a VPC and a traditional IDC - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Item | VPC | Traditional IDC | - +=======================+=================================================================================================================================================================================================================+===============================================================================================================================================================================================================================================+ - | Deployment cycle | - You do not need to perform complex engineering deployment, including engineering planning and cabling. | You need to set up networks and perform tests. The entire process takes a long time and requires professional technical support. | - | | - You can determine your networks, subnets, and routes on based on service requirements. | | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Total cost | provides flexible billing modes for network services. You can select whichever one best fits your business needs. There are no upfront costs and network O&M costs, reducing the total cost of ownership (TCO). | You need to invest heavily in equipment rooms, power supply, construction, and hardware materials. You also need professional O&M teams to ensure network security. Asset management costs increase with any change in business requirements. | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Flexibility | provides a variety of network services for you to choose from. If you need more network resources (for instance, if you need more bandwidth), you can expand resources on the fly. | You have to strictly comply with the network plan to complete the service deployment. If there are changes in your service requirements, it is difficult to dynamically adjust the network. | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ - | Security | VPCs are logically isolated from each other. You can use security features such as firewalls and security groups, and even security services like Advanced Anti-DDoS (AAD) to protect your cloud resources. | The network is insecure and difficult to maintain. You need professional technical personnel to ensure network security. | - +-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Item | VPC | Traditional IDC | + +=======================+===========================================================================================================================================================================================================================+===============================================================================================================================================================================================================================================+ + | Deployment cycle | - You do not need to perform complex engineering deployment, including engineering planning and cabling. | You need to set up networks and perform tests. The entire process takes a long time and requires professional technical support. | + | | - You can determine your networks, subnets, and routes on the cloud based on service requirements. | | + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Total cost | The cloud provides flexible billing modes for network services. You can select whichever one best fits your business needs. There are no upfront costs and network O&M costs, reducing the total cost of ownership (TCO). | You need to invest heavily in equipment rooms, power supply, construction, and hardware materials. You also need professional O&M teams to ensure network security. Asset management costs increase with any change in business requirements. | + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Flexibility | The cloud provides a variety of network services for you to choose from. If you need more network resources (for instance, if you need more bandwidth), you can expand resources on the fly. | You have to strictly comply with the network plan to complete the service deployment. If there are changes in your service requirements, it is difficult to dynamically adjust the network. | + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ + | Security | VPCs are logically isolated from each other. You can use security features such as firewalls and security groups, and even security services like Advanced Anti-DDoS (AAD) to protect your cloud resources. | The network is insecure and difficult to maintain. You need professional technical personnel to ensure network security. | + +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ diff --git a/umn/source/service_overview/basic_concepts/region_and_az.rst b/umn/source/service_overview/region_and_az.rst similarity index 100% rename from umn/source/service_overview/basic_concepts/region_and_az.rst rename to umn/source/service_overview/region_and_az.rst diff --git a/umn/source/service_overview/what_is_virtual_private_cloud.rst b/umn/source/service_overview/what_is_virtual_private_cloud.rst index b8a313c..45e55a8 100644 --- a/umn/source/service_overview/what_is_virtual_private_cloud.rst +++ b/umn/source/service_overview/what_is_virtual_private_cloud.rst @@ -13,7 +13,7 @@ The Virtual Private Cloud (VPC) service enables you to provision logically isola Within your own VPC, you can create security groups and VPNs, configure IP address ranges, specify bandwidth sizes, manage the networks in the VPC, and make changes to these networks as needed, quickly and securely. You can also define rules to control communications between ECSs in the same security group or in different security groups. -.. figure:: /_static/images/en-us_image_0209606948.png +.. figure:: /_static/images/en-us_image_0000001865663209.png :alt: **Figure 1** VPC components **Figure 1** VPC components 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 e42c400..5361a29 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 @@ -23,23 +23,19 @@ 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**. +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 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. +5. In the shared bandwidth list, locate the target shared bandwidth that you want to add EIPs to. In the **Operation** column, choose **Add Public IP Address**, and select the EIPs or IPv6 addresses to be added. - .. figure:: /_static/images/en-us_image_0000001211006359.png - :alt: **Figure 1** Add EIP + .. figure:: /_static/images/en-us_image_0000001832479012.png + :alt: **Figure 1** Adding EIPs or IPv6 addresses - **Figure 1** Add EIP + **Figure 1** Adding EIPs or IPv6 addresses 6. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/shared_bandwidth/assigning_a_shared_bandwidth.rst b/umn/source/shared_bandwidth/assigning_a_shared_bandwidth.rst index 444ee65..7203533 100644 --- a/umn/source/shared_bandwidth/assigning_a_shared_bandwidth.rst +++ b/umn/source/shared_bandwidth/assigning_a_shared_bandwidth.rst @@ -17,14 +17,14 @@ Procedure #. 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**. +#. Click |image2| in the upper left corner, and choose **Network** > **Elastic IP**. #. In the navigation pane on the left, choose **Elastic IP and Bandwidth** > **Shared Bandwidths**. #. In the upper right corner, click **Assign Shared Bandwidth**. On the displayed page, configure parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001163949251.png + .. figure:: /_static/images/en-us_image_0000001865582577.png :alt: **Figure 1** Assigning Shared Bandwidth **Figure 1** Assigning Shared Bandwidth @@ -47,5 +47,5 @@ Procedure #. Click **Assign Now**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst b/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst index 0ddff4a..5a1b7f1 100644 --- a/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst +++ b/umn/source/shared_bandwidth/deleting_a_shared_bandwidth.rst @@ -22,11 +22,11 @@ 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**. +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 **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/shared_bandwidth/exporting_shared_bandwidths.rst b/umn/source/shared_bandwidth/exporting_shared_bandwidths.rst new file mode 100644 index 0000000..4b03c0c --- /dev/null +++ b/umn/source/shared_bandwidth/exporting_shared_bandwidths.rst @@ -0,0 +1,21 @@ +:original_name: vpc010010.html + +.. _vpc010010: + +Exporting Shared Bandwidths +=========================== + +#. 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** > **Elastic IP**. + +4. In the navigation pane on the left, choose **Elastic IP and Bandwidth** > **Shared Bandwidths**. + +5. On the shared bandwidth list page, select one or more shared bandwidths and click **Export** in the upper left corner. + + The system will automatically export information about all of your shared bandwidths as an Excel file to a local directory. + +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/shared_bandwidth/index.rst b/umn/source/shared_bandwidth/index.rst index 0fd79c8..705c190 100644 --- a/umn/source/shared_bandwidth/index.rst +++ b/umn/source/shared_bandwidth/index.rst @@ -11,6 +11,7 @@ Shared Bandwidth - :ref:`Removing EIPs from a Shared Bandwidth ` - :ref:`Modifying a Shared Bandwidth ` - :ref:`Deleting a Shared Bandwidth ` +- :ref:`Exporting Shared Bandwidths ` .. toctree:: :maxdepth: 1 @@ -22,3 +23,4 @@ Shared Bandwidth removing_eips_from_a_shared_bandwidth modifying_a_shared_bandwidth deleting_a_shared_bandwidth + exporting_shared_bandwidths diff --git a/umn/source/shared_bandwidth/modifying_a_shared_bandwidth.rst b/umn/source/shared_bandwidth/modifying_a_shared_bandwidth.rst index 4f9d738..d50f660 100644 --- a/umn/source/shared_bandwidth/modifying_a_shared_bandwidth.rst +++ b/umn/source/shared_bandwidth/modifying_a_shared_bandwidth.rst @@ -17,14 +17,14 @@ 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**. +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 modify, click **Modify Bandwidth** in the **Operation** column, and modify the bandwidth settings. - .. figure:: /_static/images/en-us_image_0000001117669524.png + .. figure:: /_static/images/en-us_image_0000001818823830.png :alt: **Figure 1** Modify Bandwidth **Figure 1** Modify Bandwidth @@ -33,5 +33,5 @@ Procedure 7. Click **Submit**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818982822.png diff --git a/umn/source/shared_bandwidth/removing_eips_from_a_shared_bandwidth.rst b/umn/source/shared_bandwidth/removing_eips_from_a_shared_bandwidth.rst index 3f473b1..19942da 100644 --- a/umn/source/shared_bandwidth/removing_eips_from_a_shared_bandwidth.rst +++ b/umn/source/shared_bandwidth/removing_eips_from_a_shared_bandwidth.rst @@ -17,19 +17,19 @@ 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**. +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 bandwidth from which EIPs are to be removed, choose **More** > **Remove EIP** in the **Operation** column, and select the EIPs to be removed in the displayed dialog box. +5. In the shared bandwidth list, locate the target bandwidth from which you want to remove EIPs, choose **More** > **Remove Public IP Address** in the **Operation** column, and select the EIPs or IPv6 addresses to be removed in the displayed dialog box. - .. figure:: /_static/images/en-us_image_0000001211445065.png - :alt: **Figure 1** Remove EIP + .. figure:: /_static/images/en-us_image_0000001879005797.png + :alt: **Figure 1** Removing EIPs or IPv6 addresses - **Figure 1** Remove EIP + **Figure 1** Removing EIPs or IPv6 addresses 6. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001454059512.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001649841616.png 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 c3ea821..1925871 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 @@ -43,5 +43,5 @@ Procedure 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_0000001626897562.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663157.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 a10a09a..ea899c8 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 @@ -32,5 +32,5 @@ Procedure #. 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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582665.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 9de7a7a..a37459a 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 @@ -138,7 +138,7 @@ The following OSs are used as examples here. For other OSs, see the help documen **Linux (Ubuntu 22.04 server 64bit is used as an example.)** -If an ECS runs Ubuntu 22 or Ubuntu 20, perform the following operations: +For Ubuntu 22 or Ubuntu 20 ECSs, perform the following operations: #. Obtain the NIC that the virtual IP address is to be bound: @@ -251,7 +251,7 @@ If an ECS runs Ubuntu 22 or Ubuntu 20, perform the following operations: #. Select **Use the following IP address** and set **IP address** to the private IP address of the ECS, for example, 10.0.0.101. - .. figure:: /_static/images/en-us_image_0000001179761510.png + .. figure:: /_static/images/en-us_image_0000001818823142.png :alt: **Figure 1** Configuring private IP address **Figure 1** Configuring private IP address @@ -263,7 +263,7 @@ If an ECS runs Ubuntu 22 or Ubuntu 20, perform the following operations: Add the virtual IP address, for example, 10.0.0.154. - .. figure:: /_static/images/en-us_image_0000001225081545.png + .. figure:: /_static/images/en-us_image_0000001818982934.png :alt: **Figure 2** Configuring virtual IP address **Figure 2** Configuring virtual IP address @@ -276,8 +276,8 @@ If an ECS runs Ubuntu 22 or Ubuntu 20, perform the following operations: 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_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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582673.png +.. |image3| image:: /_static/images/en-us_image_0000001818982930.png +.. |image4| image:: /_static/images/en-us_image_0000001865582677.png +.. |image5| image:: /_static/images/en-us_image_0000001818823138.png diff --git a/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst b/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst index 6b1756c..026839d 100644 --- a/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst +++ b/umn/source/virtual_ip_address/disabling_source_and_destination_check_ha_load_balancing_cluster_scenario.rst @@ -21,5 +21,5 @@ Procedure #. 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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983486.png 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 9e91d76..8e7a1d0 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 @@ -55,5 +55,5 @@ Procedure #. Confirm the information and click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675378241.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983414.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 7b0881d..9ee811a 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 @@ -39,5 +39,5 @@ Procedure #. Confirm the information and click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675258381.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823302.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 44b9790..a59c636 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 @@ -34,7 +34,7 @@ Procedure The virtual IP address list is displayed. - .. figure:: /_static/images/en-us_image_0000001570070841.png + .. figure:: /_static/images/en-us_image_0000001818982758.png :alt: **Figure 1** Virtual IP addresses **Figure 1** Virtual IP addresses @@ -53,5 +53,5 @@ Procedure c. Confirm the information and click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675618277.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865662721.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 ea261d6..8bd296b 100644 --- a/umn/source/virtual_ip_address/virtual_ip_address_overview.rst +++ b/umn/source/virtual_ip_address/virtual_ip_address_overview.rst @@ -24,7 +24,7 @@ Virtual IP addresses are used for high availability and can work together with K If you want to improve service availability and avoid single points of failure, you can deploy ECSs in the active/standby mode or deploy one active ECS and multiple standby ECSs. In this arrangement, the ECSs all use the same virtual IP address. If the active ECS becomes faulty, a standby ECS takes over services from the active ECS and services continue uninterrupted. - .. figure:: /_static/images/en-us_image_0209608153.png + .. figure:: /_static/images/en-us_image_0000001865663033.png :alt: **Figure 1** Networking diagram of the HA mode **Figure 1** Networking diagram of the HA mode @@ -37,7 +37,7 @@ Virtual IP addresses are used for high availability and can work together with K If you want to build a high-availability load balancing cluster, use Keepalived and configure LVS nodes as direct routers. - .. figure:: /_static/images/en-us_image_0240332622.png + .. figure:: /_static/images/en-us_image_0000001865663537.png :alt: **Figure 2** HA load balancing cluster **Figure 2** HA load balancing cluster 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 f987ce2..c72b29e 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 @@ -32,7 +32,7 @@ Procedure 6. Set the parameters as prompted. - .. figure:: /_static/images/en-us_image_0000001197228903.png + .. figure:: /_static/images/en-us_image_0000001818823514.png :alt: **Figure 1** Create Subnet **Figure 1** Create Subnet @@ -70,14 +70,14 @@ Procedure +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | 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 `. | | + | | 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: + .. _en-us_topic_0013748726__table6536185812515: .. table:: **Table 2** Subnet tag key and value requirements @@ -118,5 +118,5 @@ 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_0000001675254021.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983298.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 56af1cd..c1c8a6d 100644 --- a/umn/source/vpc_and_subnet/subnet/deleting_a_subnet.rst +++ b/umn/source/vpc_and_subnet/subnet/deleting_a_subnet.rst @@ -40,7 +40,7 @@ Procedure .. important:: - 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? ` + If a subnet cannot be deleted, a message will be displayed on the console. Delete the resources that are in the subnet 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_0000001626574366.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663521.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 edab6d6..85d310a 100644 --- a/umn/source/vpc_and_subnet/subnet/exporting_subnet_list.rst +++ b/umn/source/vpc_and_subnet/subnet/exporting_subnet_list.rst @@ -25,10 +25,9 @@ Procedure The **Subnets** page is displayed. -#. In the upper right corner of the subnet list, click |image3|. +#. In the subnet list, select one or more subnets you want to export and click **Export** in the upper left corner. - The system will automatically export information about all subnets under your account in the current region as an Excel file to a local directory. + The system will automatically export information about all of your subnets as an Excel file to a local directory. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675613941.png -.. |image3| image:: /_static/images/en-us_image_0000001221842468.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865583297.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 b793d0f..9d0e665 100644 --- a/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst +++ b/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst @@ -99,7 +99,7 @@ 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_0000001675373909.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001626894094.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983406.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001865583165.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 923f7a4..16fb423 100644 --- a/umn/source/vpc_and_subnet/subnet/modifying_a_subnet.rst +++ b/umn/source/vpc_and_subnet/subnet/modifying_a_subnet.rst @@ -57,6 +57,6 @@ Procedure 7. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626574370.png -.. |image3| image:: /_static/images/en-us_image_0000001337710801.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823766.png +.. |image3| image:: /_static/images/en-us_image_0000001865583301.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 059ca5a..f327f39 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 @@ -41,7 +41,7 @@ Procedure b. In the **Networking Components** area on the right of the page, view the NAT gateway, route table, and subnet. - .. figure:: /_static/images/en-us_image_0000001678437642.png + .. figure:: /_static/images/en-us_image_0000001818823010.png :alt: **Figure 1** Viewing resources in a subnet **Figure 1** Viewing resources in a subnet @@ -88,6 +88,6 @@ Procedure | | c. Locate the row that contains the NAT gateway and click **Delete** in the **Operation** column. | +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+ -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675413829.png -.. |image3| image:: /_static/images/en-us_image_0000001461263993.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865662745.png +.. |image3| image:: /_static/images/en-us_image_0000001818982794.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 2707ded..b58ba75 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 @@ -49,7 +49,7 @@ Procedure 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? ` +If you want to view and delete the resources in the 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_0000001675254017.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983610.png diff --git a/umn/source/vpc_and_subnet/vpc/adding_a_secondary_ipv4_cidr_block_to_a_vpc.rst b/umn/source/vpc_and_subnet/vpc/adding_a_secondary_ipv4_cidr_block_to_a_vpc.rst index 19abf2a..7189aa8 100644 --- a/umn/source/vpc_and_subnet/vpc/adding_a_secondary_ipv4_cidr_block_to_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/adding_a_secondary_ipv4_cidr_block_to_a_vpc.rst @@ -8,7 +8,11 @@ Adding a Secondary IPv4 CIDR Block to a VPC Scenarios --------- -When you create a VPC, you specify a primary IPv4 CIDR block for the VPC, which cannot be changed. To extend the IP address range of your VPC, you can add a secondary CIDR block to the VPC. +When you create a VPC, you specify a primary IPv4 CIDR block for the VPC, which cannot be changed. To extend the IP address range of your VPC, you can add a secondary CIDR block to the VPC. Five secondary CIDR blocks can be added. + +.. note:: + + If the :ref:`secondary IPv4 CIDR block ` function is available in a region, the CIDR block of a VPC in this region cannot be modified through the console. You can call an API to modify VPC CIDR block by referring to `Updating VPC Information `__. Notes and Constraints --------------------- @@ -30,6 +34,10 @@ Notes and Constraints +-----------------------------------+-----------------------------------+ | Type | CIDR Block (Not Supported) | +===================================+===================================+ + | Reserved private CIDR blocks | - 172.31.0.0/16 | + | | - 192.168.0.0/16 | + | | - In-use primary CIDR blocks | + +-----------------------------------+-----------------------------------+ | Reserved system CIDR blocks | - 100.64.0.0/10 | | | - 214.0.0.0/7 | | | - 198.18.0.0/15 | @@ -52,7 +60,7 @@ Procedure The **Virtual Private Cloud** page is displayed. -#. In the VPC list, locate the row that contains the VPC and click **Edit CIDR Block** in the **Operation** column. +#. In the VPC list, locate the target VPC and click **Edit CIDR Block** in the **Operation** column. The **Edit CIDR Block** dialog box is displayed. @@ -60,5 +68,5 @@ Procedure #. Enter the secondary CIDR block and click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001429281925.png -.. |image2| image:: /_static/images/en-us_image_0000001626574374.png +.. |image1| image:: /_static/images/en-us_image_0000001818983054.png +.. |image2| image:: /_static/images/en-us_image_0000001865663001.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 4d11f6e..c59a6bf 100644 --- a/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst @@ -147,5 +147,5 @@ Procedure #. Click **Create Now**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001520717193.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663089.png diff --git a/umn/source/vpc_and_subnet/vpc/deleting_a_secondary_ipv4_cidr_block_from_a_vpc.rst b/umn/source/vpc_and_subnet/vpc/deleting_a_secondary_ipv4_cidr_block_from_a_vpc.rst index b57fb24..044cb34 100644 --- a/umn/source/vpc_and_subnet/vpc/deleting_a_secondary_ipv4_cidr_block_from_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/deleting_a_secondary_ipv4_cidr_block_from_a_vpc.rst @@ -24,7 +24,7 @@ Procedure The **Virtual Private Cloud** page is displayed. -#. In the VPC list, locate the row that contains the VPC and click **Edit CIDR Block** in the **Operation** column. +#. In the VPC list, locate the target VPC and click **Edit CIDR Block** in the **Operation** column. The **Edit CIDR Block** dialog box is displayed. @@ -32,5 +32,5 @@ Procedure #. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0000001429973081.png -.. |image2| image:: /_static/images/en-us_image_0000001627054074.png +.. |image1| image:: /_static/images/en-us_image_0000001818823194.png +.. |image2| image:: /_static/images/en-us_image_0000001865582729.png 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 821ac76..911e026 100644 --- a/umn/source/vpc_and_subnet/vpc/deleting_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/deleting_a_vpc.rst @@ -38,5 +38,5 @@ 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_0000001626734174.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663509.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 5371b5a..27d87ec 100644 --- a/umn/source/vpc_and_subnet/vpc/exporting_vpc_list.rst +++ b/umn/source/vpc_and_subnet/vpc/exporting_vpc_list.rst @@ -23,10 +23,9 @@ Procedure The **Virtual Private Cloud** page is displayed. -#. In the upper right corner of the VPC list, click |image3|. +#. In the VPC list, select one or more VPCs you want to export and click **Export** in the upper left corner. - The system will automatically export information about all VPCs under your account in the current region as an Excel file to a local directory. + The system will automatically export information about all of your VPCs as an Excel file to a local directory. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626894098.png -.. |image3| image:: /_static/images/en-us_image_0233469654.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823378.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 7cc5f02..57878c4 100644 --- a/umn/source/vpc_and_subnet/vpc/managing_vpc_tags.rst +++ b/umn/source/vpc_and_subnet/vpc/managing_vpc_tags.rst @@ -93,7 +93,7 @@ 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_0000001627052380.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001675373913.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865583185.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001818983426.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 21a58f3..c7bb338 100644 --- a/umn/source/vpc_and_subnet/vpc/modifying_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/modifying_a_vpc.rst @@ -13,6 +13,10 @@ You can modify the following information about a VPC: - :ref:`Modifying the Name and Description of a VPC ` - :ref:`Modifying the CIDR Block of a VPC ` + .. note:: + + If the :ref:`secondary IPv4 CIDR block ` function is available in a region, the CIDR block of a VPC in this region cannot be modified through the console. You can call an API to modify VPC CIDR block by referring to `Updating VPC Information `__. + .. _en-us_topic_0030969462__section495418425354: Modifying the Name and Description of a VPC @@ -67,7 +71,7 @@ Modifying the CIDR Block of a VPC - If a VPC has no subnets, you can change both its network address and subnet mask. - .. figure:: /_static/images/en-us_image_0000001627653972.png + .. figure:: /_static/images/en-us_image_0000001818983182.png :alt: **Figure 1** Modifying network address and subnet mask **Figure 1** Modifying network address and subnet mask @@ -75,17 +79,17 @@ Modifying the CIDR Block of a VPC - If a VPC has subnets, you only can change its subnet mask. - .. figure:: /_static/images/en-us_image_0000001627493158.png + .. figure:: /_static/images/en-us_image_0000001865663137.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_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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823402.png +.. |image3| image:: /_static/images/en-us_image_0000001818823394.png +.. |image4| image:: /_static/images/en-us_image_0000001865663133.png +.. |image5| image:: /_static/images/en-us_image_0000001818983186.png +.. |image6| image:: /_static/images/en-us_image_0000001818982734.png +.. |image7| image:: /_static/images/en-us_image_0000001865663129.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 7e22276..bf5e683 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 @@ -31,6 +31,6 @@ 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_0000001675613945.png -.. |image3| image:: /_static/images/en-us_image_0000001465124712.png +.. |image1| image:: /_static/images/en-us_image_0000001865582937.png +.. |image2| image:: /_static/images/en-us_image_0000001818983198.png +.. |image3| image:: /_static/images/en-us_image_0000001818983194.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 71c6ee9..7f82e76 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 @@ -34,5 +34,5 @@ Procedure - Modify or delete a subnet. - 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_0000001675413833.png +.. |image1| image:: /_static/images/en-us_image_0000001865662737.png +.. |image2| image:: /_static/images/en-us_image_0000001818982798.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 0597445..47b12f9 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 @@ -36,7 +36,7 @@ Procedure 5. In the upper right corner, click **Create VPC Flow Log**. On the displayed page, configure parameters as prompted. - .. figure:: /_static/images/en-us_image_0191544038.png + .. figure:: /_static/images/en-us_image_0000001865582905.png :alt: **Figure 1** Create VPC Flow Log **Figure 1** Create VPC Flow Log @@ -77,5 +77,5 @@ Procedure 6. Click **OK**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675616561.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663109.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 bff6fff..0754920 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 @@ -30,12 +30,12 @@ Procedure 5. Locate the row that contains the VPC flow log to be deleted and click **Delete** in the **Operation** column. - .. figure:: /_static/images/en-us_image_0191594527.png + .. figure:: /_static/images/en-us_image_0000001818983242.png :alt: **Figure 1** Deleting a VPC flow log **Figure 1** Deleting a VPC flow log 6. Click **Yes** in the displayed dialog box. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001626736794.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582989.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 1a80a56..e9bb638 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 @@ -31,5 +31,5 @@ Procedure 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_0000001627056686.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983174.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 067e28c..1408e89 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 @@ -32,13 +32,13 @@ Procedure 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. - .. figure:: /_static/images/en-us_image_0191577030.png + .. figure:: /_static/images/en-us_image_0000001865663181.png :alt: **Figure 1** Viewing a log record **Figure 1** Viewing a log record - .. figure:: /_static/images/en-us_image_0191588554.png + .. figure:: /_static/images/en-us_image_0000001818823446.png :alt: **Figure 2** Flow log record **Figure 2** Flow log record @@ -120,5 +120,5 @@ 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_0000001675256657.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582981.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 1945087..aea77c5 100644 --- a/umn/source/vpc_flow_log/vpc_flow_log_overview.rst +++ b/umn/source/vpc_flow_log/vpc_flow_log_overview.rst @@ -14,7 +14,7 @@ VPC flow logs must be used together with the Log Tank Service (LTS). Before you .. _flowlog_0002__fig1535115691415: -.. figure:: /_static/images/en-us_image_0162336264.png +.. figure:: /_static/images/en-us_image_0000001818823626.png :alt: **Figure 1** Configuring VPC flow logs **Figure 1** Configuring VPC flow logs 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 d127300..dbfd0ca 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 @@ -18,12 +18,12 @@ Procedure: :ref:`Step 2: Peer Account Accepts the VPC Peering Connection Request ` -:ref:`Step 3: Add Routes for the VPC Peering Connection ` +:ref:`Step 3: Add Routes for the VPC Peering Connection ` :ref:`Step 4: Verify Network Connectivity ` -.. figure:: /_static/images/en-us_image_0000001464757610.png +.. figure:: /_static/images/en-us_image_0000001818823598.png :alt: **Figure 1** Networking diagram of a VPC peering connection between VPCs in different accounts **Figure 1** Networking diagram of a VPC peering connection between VPCs in different accounts @@ -72,7 +72,7 @@ Step 1: Create a VPC Peering Connection For details, see :ref:`Table 1 `. - .. figure:: /_static/images/en-us_image_0167840073.png + .. figure:: /_static/images/en-us_image_0000001818823602.png :alt: **Figure 2** Create VPC Peering Connection **Figure 2** Create VPC Peering Connection @@ -140,21 +140,21 @@ After you create a VPC peering connection with a VPC in another account, you nee The VPC peering connection list is displayed. -#. In the VPC peering connection list, locate the VPC peering connection request to be accepted. +#. In the upper part of the VPC peering connection list, locate the VPC peering connection request to be accepted. - .. figure:: /_static/images/en-us_image_0162391155.png - :alt: **Figure 3** VPC peering connection list + .. figure:: /_static/images/en-us_image_0000001865583153.png + :alt: **Figure 3** Accept Request - **Figure 3** VPC peering connection list + **Figure 3** Accept Request #. Locate the row that contains the target VPC peering connection and click **Accept Request** in the **Operation** column. After the status of the VPC peering connection changes to **Accepted**, the VPC peering connection is created. -#. Go to :ref:`Step 3: Add Routes for the VPC Peering Connection `. +#. Go to :ref:`Step 3: Add Routes for the VPC Peering Connection `. -.. _en-us_topic_0046655038__section519111175712: +.. _en-us_topic_0046655038__section2675929184617: Step 3: Add Routes for the VPC Peering Connection ------------------------------------------------- @@ -167,69 +167,95 @@ Both accounts need to add a route to the route table of their VPC. In this examp a. In the VPC peering connection list of the local account, click the name of the target VPC peering connection. - The **Basic Information** tab of the VPC peering connection is displayed. + The page showing the VPC peering connection details is displayed. - b. On the **Local Routes** tab of the VPC peering connection, click the **Route Tables** hyperlink. + b. In the lower part of the VPC peering connection details page, click **Add Route**. - The **Summary** tab of the default route table for the local VPC is displayed. + The **Add Route** dialog box is displayed. - c. Click **Add Route**. - :ref:`Table 2 ` describes the route parameters. + .. figure:: /_static/images/en-us_image_0000001818983398.png + :alt: **Figure 4** Add Route - .. _en-us_topic_0046655038__en-us_topic_0046655037_table97163496270: + **Figure 4** Add Route + + c. Add routes to the route tables as prompted. + + :ref:`Table 2 ` describes the parameters. + + .. _en-us_topic_0046655038__table124160361764: .. table:: **Table 2** Parameter description - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Parameter | Description | Example Value | - +=======================+========================================================================================================================================================+=================================+ - | Destination | The peer VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see :ref:`VPC Peering Connection Usage Examples `. | VPC-B CIDR block: 172.17.0.0/16 | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop Type | The next hop type. Select **VPC peering connection**. | VPC peering connection | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop | The next hop address. Select the name of the current VPC peering connection. | peering-AB | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Description | Supplementary information about the route. This parameter is optional. | ``-`` | - | | | | - | | The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Parameter | Description | Example Value | + +=======================+==============================================================================================================================================================================================================================================================================================================+=================================+ + | VPC | The default value is the VPC connected by the VPC peering connection in the current account. You do not need to select a VPC. | VPC-A | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Route Table | Select the route table of the VPC. The route will be added to this route table. | rtb-VPC-A (Default route table) | + | | | | + | | Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. | | + | | | | + | | - If there is only the default route table in the drop-down list, select the default route table. | | + | | - If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection. | | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Destination | An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see :ref:`VPC Peering Connection Usage Examples `. | VPC-B CIDR block: 172.17.0.0/16 | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Next Hop | The default value is the current VPC peering connection. You do not need to specify this parameter. | peering-AB | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Description | Supplementary information about the route. This parameter is optional. | Route from VPC-A to VPC-B | + | | | | + | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ d. Click **OK**. - You can view the route in the route list. + You can view the routes in the route list. #. Add routes to the route table of the peer VPC: a. In the VPC peering connection list of the peer account, click the name of the target VPC peering connection. - The **Basic Information** tab of the VPC peering connection is displayed. + The page showing the VPC peering connection details is displayed. - b. On the **Local Routes** tab of the VPC peering connection, click the **Route Tables** hyperlink. + b. In the lower part of the VPC peering connection details page, click **Add Route**. - The **Summary** tab of the default route table for the peer VPC is displayed. + The **Add Route** dialog box is displayed. - c. Click **Add Route**. - :ref:`Table 3 ` describes the route parameters. + .. figure:: /_static/images/en-us_image_0000001818823594.png + :alt: **Figure 5** Add Route - .. _en-us_topic_0046655038__en-us_topic_0046655037_table13697163914393: + **Figure 5** Add Route + + c. Add routes to the route table as prompted. + + :ref:`Table 3 ` describes the parameters. + + .. _en-us_topic_0046655038__table563312179168: .. table:: **Table 3** Parameter description - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Parameter | Description | Example Value | - +=======================+=========================================================================================================================================================+=================================+ - | Destination | The local VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see :ref:`VPC Peering Connection Usage Examples `. | VPC-A CIDR block: 172.16.0.0/16 | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop Type | The next hop type. Select **VPC peering connection**. | VPC peering connection | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop | The next hop address. Select the name of the current VPC peering connection. | peering-AB | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Description | Supplementary information about the route. This parameter is optional. | ``-`` | - | | | | - | | The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Parameter | Description | Example Value | + +=======================+==============================================================================================================================================================================================================================================================================================================+=================================+ + | VPC | The default value is the VPC connected by the VPC peering connection in the current account. You do not need to select a VPC. | VPC-B | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Route Table | Select the route table of the VPC. The route will be added to this route table. | rtb-VPC-B (Default route table) | + | | | | + | | Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. | | + | | | | + | | - If there is only the default route table in the drop-down list, select the default route table. | | + | | - If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection. | | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Destination | An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see :ref:`VPC Peering Connection Usage Examples `. | VPC-A CIDR block: 172.16.0.0/16 | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Next Hop | The default value is the current VPC peering connection. You do not need to specify this parameter. | peering-AB | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Description | Supplementary information about the route. This parameter is optional. | Route from VPC-B to VPC-A. | + | | | | + | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ d. Click **OK**. @@ -248,7 +274,7 @@ After you add routes for the VPC peering connection, verify the communication be **ping** *IP address of RDS-B01* - Example command: + Run the following commands: **ping 172.17.0.21** @@ -270,6 +296,6 @@ After you add routes for the VPC peering connection, verify the communication be - In this example, ECS-A01 and RDS-B01 are in the same security group. If the instances in different security groups, you need to add inbound rules to allow access from the peer security group. For details, see :ref:`Enabling ECSs In Different Security Groups to Communicate Through an Internal Network `. - 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_0000001675415841.png -.. |image3| image:: /_static/images/en-us_image_0000001626736198.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865583133.png +.. |image3| image:: /_static/images/en-us_image_0000001818983374.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 b5edd78..1ff697e 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 @@ -16,12 +16,12 @@ Procedure: :ref:`Step 1: Create a VPC Peering Connection ` -:ref:`Step 2: Add Routes for the VPC Peering Connection ` +:ref:`Step 2: Add Routes for the VPC Peering Connection ` :ref:`Step 3: Verify Network Connectivity ` -.. figure:: /_static/images/en-us_image_0000001512876289.png +.. figure:: /_static/images/en-us_image_0000001865663449.png :alt: **Figure 1** Networking diagram of a VPC peering connection between VPCs in the same account **Figure 1** Networking diagram of a VPC peering connection between VPCs in the same account @@ -65,7 +65,7 @@ Step 1: Create a VPC Peering Connection For details, see :ref:`Table 1 `. - .. figure:: /_static/images/en-us_image_0167839112.png + .. figure:: /_static/images/en-us_image_0000001865663453.png :alt: **Figure 2** Create VPC Peering Connection **Figure 2** Create VPC Peering Connection @@ -115,81 +115,76 @@ Step 1: Create a VPC Peering Connection A dialog box for adding routes is displayed. -8. Click **Add Route** or **Add Later**. +8. In the displayed dialog box, click **Add Now**. On the displayed page about the VPC peering connection details, go to :ref:`Step 2: Add Routes for the VPC Peering Connection ` to add a route. - 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. - -.. _en-us_topic_0046655037__section19655123018712: +.. _en-us_topic_0046655037__section1241619362061: Step 2: Add Routes for the VPC Peering Connection ------------------------------------------------- -To enable communications between VPCs connected by a VPC peering connection, you need to add forward and return routes to the route tables of the VPCs. For details, see :ref:`VPC Peering Connection Usage Examples `. +#. In the lower part of the VPC peering connection details page, click **Add Route**. -#. Add routes to the route table of the local VPC: + The **Add Route** dialog box is displayed. - a. On the **Local Routes** tab of the VPC peering connection, click the **Route Tables** hyperlink. - The **Summary** tab of the default route table for the local VPC is displayed. + .. figure:: /_static/images/en-us_image_0000001865583269.png + :alt: **Figure 3** Add Route - b. Click **Add Route**. + **Figure 3** Add Route - :ref:`Table 2 ` describes the route parameters. +#. Add routes to the route tables as prompted. - .. _en-us_topic_0046655037__table97163496270: + :ref:`Table 2 ` describes the parameters. - .. table:: **Table 2** Parameter description + .. _en-us_topic_0046655037__table124160361764: - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Parameter | Description | Example Value | - +=======================+========================================================================================================================================================+=================================+ - | Destination | The peer VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see :ref:`VPC Peering Connection Usage Examples `. | VPC-B CIDR block: 172.17.0.0/16 | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop Type | The next hop type. Select **VPC peering connection**. | VPC peering connection | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop | The next hop address. Select the name of the current VPC peering connection. | peering-AB | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Description | Supplementary information about the route. This parameter is optional. | ``-`` | - | | | | - | | The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + .. table:: **Table 2** Parameter description - c. Click **OK**. + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Parameter | Description | Example Value | + +===============================+==============================================================================================================================================================================================================================================================================================================+=================================+ + | VPC | Select a VPC that is connected by the VPC peering connection. | VPC-A | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Route Table | Select the route table of the VPC. The route will be added to this route table. | rtb-VPC-A (Default route table) | + | | | | + | | Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. | | + | | | | + | | - If there is only the default route table in the drop-down list, select the default route table. | | + | | - If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection. | | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Destination | An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see :ref:`VPC Peering Connection Usage Examples `. | VPC-B CIDR block: 172.17.0.0/16 | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Next Hop | The default value is the current VPC peering connection. You do not need to specify this parameter. | peering-AB | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Description | Supplementary information about the route. This parameter is optional. | Route from VPC-A to VPC-B | + | | | | + | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Add a route for the other VPC | If you select this option, you can also add a route for the other VPC connected by the VPC peering connection. | Selected | + | | | | + | | To enable communications between VPCs connected by a VPC peering connection, you need to add both forward and return routes to the route tables of the VPCs. For details, see :ref:`VPC Peering Connection Usage Examples `. | | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | VPC | By default, the system selects the other VPC connected by the VPC peering connection. You do not need to specify this parameter. | VPC-B | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Route Table | Select the route table of the VPC. The route will be added to this route table. | rtb-VPC-B (Default route table) | + | | | | + | | Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. | | + | | | | + | | - If there is only the default route table in the drop-down list, select the default route table. | | + | | - If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection. | | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Destination | An IP address or address range in the other VPC connected by the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address. For details about the route configuration example, see :ref:`VPC Peering Connection Usage Examples `. | VPC-A CIDR block: 172.16.0.0/16 | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Next Hop | The default value is the current VPC peering connection. You do not need to specify this parameter. | peering-AB | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ + | Description | Supplementary information about the route. This parameter is optional. | Route from VPC-B to VPC-A. | + | | | | + | | The description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | + +-------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - You can view the route in the route list. +#. Click **OK**. -2. Add routes to the route table of the peer VPC: - - a. On the **Peer Routes** tab of the VPC peering connection, click the **Route Tables** hyperlink. - - The **Summary** tab of the default route table for the peer VPC is displayed. - - b. Click **Add Route**. - - :ref:`Table 3 ` describes the route parameters. - - .. _en-us_topic_0046655037__table13697163914393: - - .. table:: **Table 3** Parameter description - - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Parameter | Description | Example Value | - +=======================+=========================================================================================================================================================+=================================+ - | Destination | The local VPC CIDR block, subnet CIDR block, or ECS IP address. For details, see :ref:`VPC Peering Connection Usage Examples `. | VPC-A CIDR block: 172.16.0.0/16 | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop Type | The next hop type. Select **VPC peering connection**. | VPC peering connection | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Next Hop | The next hop address. Select the name of the current VPC peering connection. | peering-AB | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - | Description | Supplementary information about the route. This parameter is optional. | ``-`` | - | | | | - | | The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >). | | - +-----------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------+ - - c. Click **OK**. - - You can view the route in the route list. + You can view the routes in the route list. .. _en-us_topic_0046655037__section026312306414: @@ -226,5 +221,5 @@ After you add routes for the VPC peering connection, verify the communication be - In this example, ECS-A01 and RDS-B01 are in the same security group. If the instances in different security groups, you need to add inbound rules to allow access from the peer security group. For details, see :ref:`Enabling ECSs In Different Security Groups to Communicate Through an Internal Network `. - 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_0000001627056086.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818983506.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 325e8ac..9dded8a 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 @@ -38,5 +38,5 @@ Procedure 6. Click **Yes**. -.. |image1| image:: /_static/images/en-us_image_0141273034.png -.. |image2| image:: /_static/images/en-us_image_0000001675416345.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823798.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 1957805..0f7ad0c 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 @@ -97,7 +97,7 @@ 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_0000001626896590.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001675616433.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001818823058.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001865582593.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 0af6278..159d7d8 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 @@ -33,5 +33,5 @@ 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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865582893.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 13e1ecb..183da5d 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 @@ -99,7 +99,7 @@ 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_0000001627056574.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001626736678.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865662901.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001818823166.png 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 d122d37..d8a02d3 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 @@ -70,7 +70,7 @@ 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_0000001626576858.png -.. |image3| image:: /_static/images/en-us_image_0141273034.png -.. |image4| image:: /_static/images/en-us_image_0000001675256529.png +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865662765.png +.. |image3| image:: /_static/images/en-us_image_0000001818982734.png +.. |image4| image:: /_static/images/en-us_image_0000001818982826.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 fc9f207..8b2258d 100644 --- a/umn/source/vpc_peering_connection/viewing_vpc_peering_connections.rst +++ b/umn/source/vpc_peering_connection/viewing_vpc_peering_connections.rst @@ -31,5 +31,5 @@ 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 +.. |image1| image:: /_static/images/en-us_image_0000001818982734.png +.. |image2| image:: /_static/images/en-us_image_0000001865663213.png diff --git a/umn/source/vpc_peering_connection/vpc_peering_connection_overview.rst b/umn/source/vpc_peering_connection/vpc_peering_connection_overview.rst index dd832e5..dd738fe 100644 --- a/umn/source/vpc_peering_connection/vpc_peering_connection_overview.rst +++ b/umn/source/vpc_peering_connection/vpc_peering_connection_overview.rst @@ -21,7 +21,7 @@ A VPC peering connection is a networking connection that connects two VPCs for t .. _en-us_topic_0046655036__fig4721642193711: -.. figure:: /_static/images/en-us_image_0000001512591549.png +.. figure:: /_static/images/en-us_image_0000001818983018.png :alt: **Figure 1** VPC peering connection network diagram **Figure 1** VPC peering connection network diagram @@ -37,7 +37,7 @@ A VPC peering connection can only connect VPCs in the same region. .. _en-us_topic_0046655036__en-us_topic_0000001154868962_fig10285152624918: - .. figure:: /_static/images/en-us_image_0000001512701025.png + .. figure:: /_static/images/en-us_image_0000001818823678.png :alt: **Figure 2** Process of creating a VPC peering connection between VPCs in the same account **Figure 2** Process of creating a VPC peering connection between VPCs in the same account @@ -50,7 +50,7 @@ A VPC peering connection can only connect VPCs in the same region. .. _en-us_topic_0046655036__fig16137161191713: - .. figure:: /_static/images/en-us_image_0000001462622484.png + .. figure:: /_static/images/en-us_image_0000001865583217.png :alt: **Figure 3** Process of creating a VPC peering connection between VPCs in different accounts **Figure 3** Process of creating a VPC peering connection between VPCs in different accounts 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 aff425b..ec2280b 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 @@ -37,7 +37,7 @@ Peering Two or More VPCs .. _en-us_topic_0046809840__fig465519155457: - .. figure:: /_static/images/en-us_image_0000001207827554.png + .. figure:: /_static/images/en-us_image_0000001865662841.png :alt: **Figure 1** Networking diagram (IPv4) **Figure 1** Networking diagram (IPv4) @@ -64,7 +64,7 @@ Peering Two or More VPCs .. _en-us_topic_0046809840__fig2032313286441: - .. figure:: /_static/images/en-us_image_0000001207699446.png + .. figure:: /_static/images/en-us_image_0000001818982906.png :alt: **Figure 2** Networking diagram (IPv4) **Figure 2** Networking diagram (IPv4) @@ -106,7 +106,7 @@ Peering One Central VPC with Multiple VPCs .. _en-us_topic_0046809840__fig724664185: -.. figure:: /_static/images/en-us_image_0000001208260576.png +.. figure:: /_static/images/en-us_image_0000001818823110.png :alt: **Figure 3** Networking diagram (IPv4) **Figure 3** Networking diagram (IPv4) @@ -163,7 +163,7 @@ As shown in :ref:`Figure 4 `, VPC-A and .. _en-us_topic_0046809840__fig06955277200: -.. figure:: /_static/images/en-us_image_0000001521533677.png +.. figure:: /_static/images/en-us_image_0000001865662833.png :alt: **Figure 4** Networking diagram (IPv4) **Figure 4** Networking diagram (IPv4) @@ -198,7 +198,7 @@ As shown in :ref:`Figure 5 `, VPC-B and .. _en-us_topic_0046809840__fig568511518481: -.. figure:: /_static/images/en-us_image_0000001209442636.png +.. figure:: /_static/images/en-us_image_0000001818823118.png :alt: **Figure 5** Networking diagram (IPv4) **Figure 5** Networking diagram (IPv4) @@ -237,7 +237,7 @@ If VPCs with the same CIDR block also include subnets that overlap, VPC peering In the rtb-VPC-A route table, the custom route for routing traffic from VPC-A to VPC-B and the local route have overlapping destinations. The local route has a higher priority and traffic will be forwarded within VPC-A and cannot reach VPC-B. -.. figure:: /_static/images/en-us_image_0000001254335981.png +.. figure:: /_static/images/en-us_image_0000001818982898.png :alt: **Figure 6** Networking diagram (IPv4) **Figure 6** Networking diagram (IPv4)