From 1035a9f1b7c3ca4aa1e0bf466146122de1db3102 Mon Sep 17 00:00:00 2001 From: OpenTelekomCloud Proposal Bot Date: Tue, 19 Dec 2023 11:39:01 +0000 Subject: [PATCH] Update content --- .../images/en-us_image_0000001796404809.png | Bin 0 -> 23749 bytes ...ing_and_exporting_security_group_rules.rst | 5 + umn/source/change_history.rst | 10 ++ ...rity_group_for_multi-channel_protocols.rst | 6 ++ .../why_cant_i_delete_my_vpcs_and_subnets.rst | 72 ++++++------- .../index.rst | 6 +- .../step_1_create_a_vpc.rst | 6 +- .../step_2_create_a_subnet_for_the_vpc.rst | 6 +- .../step_1_create_a_vpc.rst | 6 +- .../step_2_create_a_subnet_for_the_vpc.rst | 6 +- .../configuring_an_snat_server.rst | 2 +- .../route_tables/route_tables_and_routes.rst | 6 ++ .../basic_concepts/route_table.rst | 6 ++ .../assigning_a_virtual_ip_address.rst | 5 + umn/source/vpc_and_subnet/index.rst | 2 + .../ipv4_and_ipv6_dual-stack_network.rst | 101 ++++++++++++++++++ .../subnet/creating_a_subnet_for_the_vpc.rst | 6 +- .../subnet/managing_subnet_tags.rst | 8 +- .../vpc_and_subnet/vpc/creating_a_vpc.rst | 6 +- .../vpc_flow_log/creating_a_vpc_flow_log.rst | 2 +- .../vpc_flow_log/vpc_flow_log_overview.rst | 7 +- 21 files changed, 222 insertions(+), 52 deletions(-) create mode 100644 umn/source/_static/images/en-us_image_0000001796404809.png create mode 100644 umn/source/vpc_and_subnet/ipv4_and_ipv6_dual-stack_network.rst diff --git a/umn/source/_static/images/en-us_image_0000001796404809.png b/umn/source/_static/images/en-us_image_0000001796404809.png new file mode 100644 index 0000000000000000000000000000000000000000..3bd705bb1279cd4d15bff49f0dff7ecbc93e64fb GIT binary patch literal 23749 zcmdSAWmFtd+btL@gy8NH+})jE!QI{6X;S4Kii-OKQ- z%TrljYqRI+y-u&Gqp1f73SG_2@XQ|G&A8gb2UGfHQ;o?qTgah|^1-{}{P+TgCKiN2 z3x)B6ED;Sl_zMPKc(z-tLhRJ0qiP6&PQA%cYPZsY8uvr4Z->|hID1M6ocm&wq4N}8 z;1!sWqgSRaVcC5CRzMqB;MF3VMIMQo`mwOE5kedJkk;SdUv_kUw9saRC8>gSp=qNg zan-8|T|m1TCTqqVSwK6PJX;dJ6H*K-q0)((GNcdbmQ7czfIbK>hXA=hDSb>ESmT%F6HRqcGeClgC5a#eVDc{u+zE&Df2i4TZ){T5%T$t5WtTxfSeKWf5UPm3e)do|Xpcpgyc(u;81*;SqNzgG zz_PSR1XlAb+*!#|w^0E&n*lR)fYP%4O1Odc=g$R&HA#ty->s}@-rn9sR&#SnA|oTi zBO|FnUPZHRe+8??_VE>#l$p=j)`U^nA3h*na8T=Qp`q>E3Ir( z1A9YO%d=SF=?Q3CO(wKXXeGcPuaM$1t6j0lsrpelUs`goOpHLrT$7p_>zD&ZCuOu^ zB1=t8LC3%-Kmc$=@Y9x*mSPg(mfip)Rg#DFJM&J9%K5XLr~K3L@lB2Y#N~E>3r+Q1 zKJmkvnxo-!=|h$l;IQb)tydz25jSHzMR9xgfkJlG(8mgFoGp1pI)Z!7hu?rYTMn`9(6_0%kRIrNKa4#?g779aWyjEjj#l<-oi2TW0HD;tbfZ}zS8pCCy zQw|CMEXrTbr+-#{D08ljnSit-*8tgiSc4s!tI2s8XBGnn?!%LQlz5rMys}#{(7-J9 zmW8b2_QqoNuzxqq+F67JPJdtrg-9e07N*zBch`4d^8dFPzOJmT$N~Z=&r?6+;boeh z9g52bgv^$=-E^_%$W-4ZEk#ccY4^uRNA6b4ls;0Bp)~l%qCD$UDr=L7>gT1W=Al5Xg21(l z{7ucDrqa7i&>Ih?j(_5U->BH>GY_XVG&^fjg1q3}em2)%o=HCrihJG*sj)bwLf+j# z{z)mbYE@{{^rrKRzv*!wcW}+{3x|U5VXL|cu~XGbPYV=oULSTM?11DaC2cgv-s`8) zi?@5Jd&9{#GttTpmt>2)&VMYV0qQ3gcV*WC{^1E$(1TU&adX^nr&gWsuLB?-V2{rp z8xF68iZ&?!=8@F44Wvurzk{&Pb?^2D!a@_svipY&5Hp%eH-J~f)Z0)1F9+P2a<$cE zyVcLEYnd4vhbKHa5_Pd8846jLWG;TKug)=T=_b((6Z|rzp|Hskxnsa5098k*5sV5F ze&+4*dA#R8OH+EwD9uT7C!$fb(lex_A+DO4Yw5kQr7m7|kdxyZ5u@R=c8JU`Ip-X* z2bsKLMwUCwRj;KyH$Q*2B2MPlR3a_ivZv2#Z@iB}{fU8g@dsAo3Va+$Pxii(FLDjW zjZOHo3z>_ZB!RFdDFZm*%!&YwFhZz4)BD)@pI-epyh>Wk(=zFMq+7xH?jW7VLcH@8tp~NwayAl8Lnpx0$l&X{^u1Y0HNzbe zTV3tnB+9NeQq7bnkks4 znPHam0%u5jE$!WQ!41IqB8*q(E7%!nq{Gz+e@O3l1@s1249=HR-&3{sj2aD{5DeDD z#cR(2HR33@AHgEm>Gc;3Qx(~|H@+m^@&+F0dN@Kufg%Nf%2jOe@RSfk^P&pIQDkl~ zTr;!DUJU4CR>4e?`J19Fy!1-T#g8vK$8=4yG!1o(Ib-LVvR~F?8a#3E>MYLRB zw9JGmbCl3^ikg%luG&=-+SH1#G>ri;N)dN+sVg!%d=CIjCwnK>%->BUDc!)AjueJh zAs6ejE&!8qpW&wnek=1CmZU^-l6ug-1iZZJrT?OPVG*vNIUB1P|@ zKmnH^ty7ci|2%=Z?6HhJ7dH=nga3H$%e7lL-aT&JzxW$jx1{#E7RKNlYlkOvQ8w}P zi_d;H=F0U(#}rMm+aqJ8kvEeg%puw5k`*fA_k4^I(h23mC<0Msa{Jso`p3WwcR|JP zzVNx_3wEig(WLa(LBVmu17elqm;JlUsti;`Xy^-*Bx~1%L4GDgS&pq5re^mK``)Pam z7w)~4o{wB3VZo+sxOXarB>u1h-US`ha6%T<#TCinvNHv)b@wG=G--m-nW@(~mP_Ch zb}+iIKvjbU+4r(&pfam3bdHMaGo>%aTUjVHXLbz^Bv(L*i-~7kN z^o?Kbdd_m@40=t8AM={i{+*0P$_KENYr-hR#cSpeYlyv?bbeROV4uV%q&W4xh$s40 z=$wiScp;+SaoCk`ak<{s`8MA0s^RtyI7MykctIP6*(q&?T?ZCOo?IBYti0X_EvH1j zR7^1dCYLYRo;%7w{o+wB3Y8j@`N9tpqS?1jb>qZoDN5Iug=TZ6(hpU)U1wbrMO6Uo z0iSeJ<2Kxf@aqVFS*wzIvY%!hmCJ#Lcv^@}v39f+9MkwhLTdMI&k3t#O-gm;oFQY< z6RhjIk)HO0Mg9e}0X+@aXj7GVSW11$c6#R%h7yn=FGsjYvw2p7WOOnucl#=g zWH+jxht5eAq?Hu8hWIg`{L&{RS>9+a+{)Y4K!CQ8w_x)|5$Juy8?mtpb%px6uYviK zfqHU5J0Y^va_>?}@FAAVBolp*I?_yNrGT@t=kexbe1UUwPKm8*@~e5C&)(&>mG{M3 zzkZF1Q_Z)x^?+1*zrb;*uP`XaaE7VF8#YAp_>wP7QlLu) zs1-*T^6q{mcHhxTRUUqPEK|Vw`3QYtnaDVyPkoO-GW(<*N*4w;``7) zGrY#*?B*fYS1yV$rK>QjyEgUe%}qrG!%suU{KuYCmp@%-Q$#q)gkL=kKTgRKGFAE$ z+;C~K2Sv-lflrrNe)aV6_7=Vxp`;yJWoxmxPtN=3JGK=v!Z!U&qkI8Ro9xZMap;Ge z6aDwmPBv8nTD&V*zYunO;nU-e$MO0ZQsTq=OcU>k8{F7X5mOnzd)mS&3Oa>V@z!W* zk@o&Zv}zZ;d45Bg#xvT0PD(~aw%IfXJ8-V=m*zJrhbq!%TRNR!Q=*}A`o71M8}P`+ zO&n36yfHHWHJo(iccKADUHmT}pJj%r@|t%-SL(vdpJ)`hFT8A}5qalNa#Bxp1*Biu6KSqNSeWv76uR4R3hxw=r zV;tdo166xQs^>?PfTw9AZ|`oVZH+m&0seYs;@N1Dcfe)~QRG7Av0Bau{+h-pU#?Ym z`xP_Y)@c4&rj5u2;{r{iaihK@26G8YC3{?vsGB`L8_F}I@@QA%0BoLn6+`XdQr+rf z#x=?NV7)=wKkLqypfZ%O7HID4m8|31`_>YUB9cMhwJq2sL_IFKs0#k%i^m7S?(Ipa zE0ut|!`;J|BDM02&&i_+d@R?#79cP)j}!}gOfJI{ZQ#q;+$dX=i(GYSu^Tzr`z-&@ z_T~}9u2)|eQ$j9_CFcc>zR}4LZH2?05CeMKsKnMS>*}_eq0!zD1~~qblV;6Cbni$5 zpGDrhZmI2gNIAVZqk|A`+rdwFYuH;u>ig5k?ijzy=j;k}Ghc$3Y<--ALNF%Is?jX+ zTxzvUPy}#twG+|_u$1k3hJU|~L>I#rVI}Lng)+(>TjY1b=TXeO$*sRgfn#Wm=V@;dTBtu<2 zg5LSZIpMq6N7Qc*fy8G=hJ@rH?)AvqpE)KD!xj|s_|@l| zE<+aZc%*0N@9=1MPbW9-)NP#^)*5i+5;W##0php_h+V3(fi9SJ9?s+3H7H)MK-6?~ zsod6F(;wi{^50aw?|Qn!`8ivH5U%DhzOz%^)LD@H;=Jovjcs>k_hWd>nU012MR-m? z!hXfz^FXy@Jv6u7xyWlV##ZWD&R??{pI(By1+cWXB{(YYMfITT`Ad&3SpLr<=UsU$ zyabi``?JegPuHp>(U+x65_K2+uC%;ug#9-H!+(XE9SzDP10_8l8PduA2j5aS%NsAm z)B{i#_Rt=aki!km)WO3p9&tXw1mffOZEj)+o&00}fjCJ211zwm{8=XQ7p+iyLGIB6 zeN=YC&wLA>R4jJ8Re_gbNP8#HSka+jqL02*+ty_l>5_HBYPon)2{Pft0CVn;W+TYYc{MppO>UFoOYFT_Ycz)AzOPNp2rE_$+3{c$MPXw zF44VXY>u$B4kCi&(l^si0b_+q!d!zwuv$Mvu}VEPVG3d;Z5PWwz6=t>6tr|}gMVxYa%H%;cl4*ctXem%*TP6=vF*}9Dgdc0Q^ z`hGn;>M@tEICZ)A2|3nl+7ul=wZnu-se(ZWKd(7Ka%fMKe1% zd~}++Lb|GX7U?}9q82|C#q;MbFposz8X_|UO&SE zIhv;Ksf|v&lLW`0*nBw2e14UJ*vPnxUv`_Pkc8egvX%SHC2x|4VQlm;<4XC-jyqg6 zpm$)3A&JL53Y5wU?tW`J&-)eaMYZAZPMYENk+ksOEKkUF^9;K#)D=vYD0_uE#m!7d zJ1sK%_P$l#0d8EzR*H_oj0K0`ygVD%fIx?byP{Xite6)4>;X>Zs(_U@bH}6G0}V0S z!b4cmbL|ZqVE2uCs5fO75yO2E7k#_^w~^p0kKvOwDY~raw9sH)v z6#WW(p|DwJhJB@T-IDBGNnw5e?8jN?z8sIs1B$rIDL6tt3?q^2H=FT;+1xvOT@#5P z)$RE;WRo-TQz>rUmoey8iG)K_<@DhLej7Bh@xD>mi(=-RXIOLXu*{ z#0NFUbR}^C!wJcuGHUW4H&As+p`-4v_hlDifp~ zkw0ATu;#|JY0riV1N}l{a7Vee<^6LfQwe6fkW%Ucw`yw2wMH~o({J5Q)sJ6k@_aG- z{{R#8T-(*v*S`*Y?_$3lNb=B4XL3d_ch^lq*!+ zZd^lq6UUWdAaOt~ty6PDE#UL<^^-~PMI)vCPm1CBHC$+Zi1+$Q;Dd-1{qX{>b6BQa8_Itl+$-9;ey=rppzH}a%LL(-pkYyOPQ3<@rE{gHi8K=LFP(_V*MB z>tiohH|)r#h3=?1upvp{;6^?o7Dp{W%q-REx-f(>MJ*?}xOz33e-Hp_{g^DRRDA0g z*tr}Br92<-2)3^$H9n6-%^!XZ#}2TQhS_oKJ0`TT&e>=$tujP7&b7qTJ{>%>9cg^f z<iP4mc9X&3+Lwjm)oN0PoNPk|A)m;-pm8?22~?Opm{7C(8U0 zX5iM8z)!BYT5CHXrS+1UY{!*ez(X8U_L#Ht<~0HmYEy z#=CJ=#OwXcY=HjGQ9*^id-1qgVkLkFO2uYaHqnpuO=5$(bMlo6{6l?GEdzft-{Ima zDvT67;na+tZ6pp<#bxrAFQ);$ha%&$CqFDmC?+EcBtKk&Y62!aE;tE>rUV2u*Dw41 zYtT#1dnxJ8w%vPcc<+g5^zHeG(&be)a*l79Wyxdfr$#?<#A(ag_I$X=@4OZM$FWU9 zsocm9uz+@_j*H_`V)y*AqKaY_STriI(MWx+9|Z5ShM!VODpzT|Z#_ZV?p5xuPZo5! zH(vW~rJQp2O6sXf*UJ}L&Wvr2?%qBs^JhvzWI$>3F|{eP#~0Ae;jUSp(_mPN@x#E$ zxSn90Zn+QKD8u=h_v6eAd!TO`9DG4aXjks(R=@q@#)VYg8jnZp@Y9`>@Lop_1W3s# zY>Tg8{@nRd#IJ0dqM-!u;|3QBo|7iL__|{-uKk*fVK{84bVecD1_}rZzEO~sp7L&q znxCifsz0w-N_lvE97tB3uw(dkRxWb6N1A)!0`R|lbb7K*V;R|RC*1Z$4nJ0rh(i6c3DX;fseYZ7 zUs#P-&(QT950ag8)~~FHin)Gbrj}Z6&z+M;UDQ#;8nnrQR74GtHl2m4@bAIWO()JV zvRl5dbnlO+a;-Kv!fI<`;yQR80Uw-k3bs5X8pl&$ul={VqS)MywqqQ_p;7Oq(Q;Cu ztA9>`JhQ3m8lvjzapbv82ZbOYi?w35oEzzTg;D*z#7|49?{2*SePj`pXOEt3t=;|P zd-*3~;my{lFK521R%6#$kL?$O|CTclc@WETO7hAK@v02eJU6{f8WlB|^Q(R9SUHC& z+TE|KzWx`TX-;_DC44+J3fw7In1nT7Qdluk+Uxz@`R-Y)>SYh5*?ojLC%2%eQ$&5b z{CzX0F#E)&DfQ93EUjdTzJ~ja)2aLY+8V#988&5<18wlalbhfs_TG~Go-VJyM|e!+ zPP+Q=n4YHq0}b(KovLt4pzoQ`c(r`nA9mog3vOx5urMf+Wny=3CZRvVm41{1x>iR} z(~-oe5@D8+r+U*Ui8#8Sy2|az~9{hJVy9*znQsnSU=k?FUlj>{AVohJ{J@s`XpWq(a7tL&q zfVeei9WLDFcL?<7a!SOkc0bife>|3Sx#<`yT+$d9F2=U)`0JJH#dS_M&q(3aWDcOiR;JxO`>o_zJFivV z)+TCFWdL~V%=|Y)viSmQr*oy`29@|;#Kod$25KTeXtVN zV^~WFx*Z)cDxrgNnWZl&;O(EZgix9d4pwqZ-dgKy?5usZJv1s7z_pT1?o=>_t2U{B zMM!JdzS1g>DG#xNMNycqv6*pD(;OZ7O^Hr91Pv9ScNm@OzyE1H*}80OY&>x_R*uE9 z5pZE<_~=690pSwmSTm^jOTeCh8BLu2qmV^B20-n}zCJMXf>lnulO-kS(dvW#&9$ZDaiL0ble102A-lBTq-4l8I8=z}9dnsZc)s_!6q$suyv`+*(iUdLG zIHC%5%S62v$2WIq(`Jz8WR~`uU``FM@5tG?xEqI@9 zY;7F9|Bm^~LSt?o_?>G*C@k{@W6h?Fe#f#F-lOChFLQM#Ksd9&gLq$3rIP_dj^dZo zQ=RXyosJ{V@HFX*CtRcHWHN{=RoiIkHpOZx^d0Z&HSNn zM*ibtvV3ZJl%tuDC_0F*3R&oGWrT<($+~Plo^b=;l>EVbo=a?U<9ElN7~ zcCH^iSyWaZ{9Iz0IX{&*Kc6Ejw7Oh2-*EKHTcB=i91Vs7a~vg`y8VwPj)Y%OPE(M! z7D!ZHo^fPkq>-NVJ3#rh4yaE5_3PL0?tq-vpWkz87$OTe4|d+nX(qVZByxp*HMQXn zg?>IfA~d#kjHxOVpb=DZK0P!!by#@0oz}X?&(N-2d&k4wjj~Rbw2`=yW`G#&bhYJI zCs@~Y6I2}PA-uzrLM!X&6%t?lSfaW49LHGS6dw(Q-_Noe<(sAR6)08^CU?OPY&917 z(A9v0wg412m5`t`G&IcS2OLZL9*pDv{P~lLD01iFKcsjMgcMhFP{HV>$ys*jLS&GW zV;rAg+l|c*+peZ7e$<-V;?nxz!HlDElnk}wVb>NT4AsMciICwD2NzB z9Kvx!Bnnot{~w7W4!5?@#KrsnD|!&o{a;VH?okJ#NI>Kh|2?jHj*pMg{-*&^OMJ}A z)8oR5q5bzD@uDRA`jhO-e-DEH|26tT1}<5}-@4oZW!6r1#Z6T)%^uhWLT^YY$Z7$Es}DvhMQ`YzrVtK`GQ2rN*f)1f>2~>o?xUYC#NNnh)pX0 ze_!@Ce)-8j0V4buKzAMbErcU=NQh@@Z5y1@#Kqm=uxw!y8Id6T{QOy)STH!y99oA8 z+5HxoobRgFR1?NDFi->l03@fTs;a88Q)p^v%&e^NJ^!BtmmgE+nMl!*cxf}UvWZT} z;Cji4+j1ESb4%+BkM35q*Jo7GV%`pXXDn4}HF2^FPRReJ88(TLsx8_TO)acEt}Ch@ z)?Z)GUQkfb>T^fGy}iw`(`2{Q3OGsqCGkI7+=?k~z?n?B6*!L~r^a!=OnPuzOzW7^ zGR^Tv;0hVAn3RS##HWO7&lJs8>%OP2PQ5_vk0krUk1V|@XnB5K!rYv4aBvU_2`Sp~ z%>@Y=84`M?VhDNujf~)L(EpF!^qGHF(V*VG=*D$3L%b)xqT=r$(74z-d>5Eo)Bpbc zkdCNQft8al$kQH*NeG60;}*&o;(`GHuHN2W4jhzWJR%}W3JP&d47mS2=$!mm*&RQF zWi#8p+BGrjM_r)Yzll*YA*PtdMt64Cs4~a1lEBL7%x>M;??NjzBr@x} zV)7;&LhR9AAdU(sHdGebfKGz`#&MS3N+0-q_A(=I2InQ)vV?E8;qKw!f1C5s~-8jh=`P zq!?(W7C{GzoI98tv<}A-9C#p*go-PXR!9g}Vc}}%FCz+Swy?;O>Jcr&^9(2gw;Id@ zb=v;NKBc&PG5#@(Hb1Hq;O30ODiZ4Kny!SY7bSj^f2Kl+e~!A<=6enT3If&XD)Q_# z(1y6Dh_6pni^HOvKNbPy8zW;RVfm9f=fn8=gIR4>b0)OvE;#}s^0uo4kMum(} zj`cMu2NU`_^fZJvzmyXhZ*?wD2GHsV(nF(iO4h(#g=|}G#Xt#`>e?cQYMeFO`i6w} zqC!FSFZzA*a3zL(G5@&X!}m31p2xPUqLleLw(`4ol4srWe~RSCz-#{A{9nVC$_1Sl z<+#CN{J?)Q;d`#(*DWY<|nS`UPsb2iN0pF9-Wrh74M*(TxIH;Kuq*%r!ly zKVSrSgqlW(*4XlvmWU||yUm_s3&>vK@y;*u$E_$>re==(M?V>B*n9p&9+S z(Y`-&fGFy4rEexGb(#|QBP)3D>MzVGb((ZR3%Q?NYjP}luB0?;bc>VqdXHmDmR|-` zrkA;9wmg;+@jZTSJfEbvR&ebv+Bg0^GR3f{5^6EZ(daWV6T@;85VlyW!;{rJcYO}< zL_X>ruAKpmx8I#;xA;)WrPU0MKasZ_`_gm(GCm&ddMjrK^2kYg(b~WP>ADG%QQKX?@g+3nv z6$e2p5_F{j8(f+70!(q3eiZ=)*^qGLtaOX@YuEc9Mt|4l01h|%rY=fFYjGpOJ&x3= z#}!R}WeN!(gkxP=t$-!WBdfs5Bl(0XMs`EQH9T}%DzWRdj(c(V-4%Vp;K4aT^>O7J zl#A{;8d}dHcq>CrLP9Fqmuec(YL08%H;_&{cXMdf{MrKB#0}o>``uk(czDyyux5Udg5F{1d^qyZXI3D>M8{YB zH#oO^!en)YJIW^9qWo5tP-4rWOGy|ZeiY86B#JS$*zt^C5lmi94yVueM zoUk>mY7#S(lw1dF?wt$=hEK9(Y!+{&@D3}f_UAQ)U(G3+!PN;RuV+rbNQR}J)&iSu zc=4HLq0oQ92XE(ozQ!a+=yH$v8}GcsF>0ODYRN0qA97m(9Et6b{Z}mdv%fkaT}|@E zKqKzWohQx4lJ6JnXLKK~(8iy-{O8BZhU!hfizJM`@v>@j5K>n(q8k|WY*$M~e!U){ zb;8eZC}>P#!sesY@2KRvmvzT@(kT4qFmzbTsC$&AOISNB5ZfnJHRjN-ut#M`GcFRe zyza9)OcR8ZFMBgQvWO%kPE)+&bJ0-eL>3W{0-2tc6yoS>;9BW6#z#4&1fmZ5KUyR@;R>jmwNoD=;31;0l7)pNk_ z#&CSGyVs5ol6i;-1$c@2Wq69zeRCZZO=?eYV2IfsxR>;MO!>CyO%Ydvj}Y!uYn*}U zLQ$F_>Yu_vgH*a;biIM%R3A7_wi6%ulNHy)VdJNqwXlPkQR_AeJ;rxlz-pe|?e-|FXz!4O;B8v% z#^p<3XEI$H=?BB<0JwRc*)$a)Gf}1s!zOIJLC25N^ce*SqlU5=P2{o zHCOAD6Lq9=*)7&C3}hfiV0(67mIag;&mg~|WHfkB&}-Hh_8)Vd%rpp#Sz99KB*hY! zRM7t1l_uiFGL*kChHq*i=e4jJ7+R=EF~eT6A9xHxoqzDbg2=%t=5PuC`Qr z^H&NbJTI-H4-22WKV@e#O*^qDMm}ymyGH<4Z?`XDz{okN5~|B0VV`S3g4UBP9=mx~^DF9)<{o@W)UlV#_feem-dd6Hk!A8uzvzRaz@W z9;;^-ti*Qda5TIG*PBD~U~9wi+|;r&za9tjK`fL?eg}Puo2Hyj=N0Y9Ss`I5>++1K ziYzQTk81fb-Ue?W%82bQR_7f}XPjC*WT0MP!`o~M4~U&or75vyo$|*Q70D_J(8nSn5!<{~SOR9SjSA7*vzy1d14IToK8cEB8rYOR`|7?^ z1Bo1+BAkA(hj$COtUFZ8_Y=q>@(~w#W3Xr;7N-bIAbID2ONO3d+(M+@lI}UblxM^)Cu@a(S@sUBf@NE9G5J zrMh4l9H96$p!Z}x^tf$bn^=>&jHW8=f5tYgqHxV8m&&9a7o){H(o!#jBJz7n{(kV!E~yJkbmUCnhOq#yplrTkCQ z<}=posYk7C6Q85lmAQEd24Iq;3)^nm^UI#*jl5*Ftm!1lkknLYL){an{KpCH$LB82 zlp^P+Ju#0A0+Z$oyl?nTWsR0~(Q}FaM&3GDX9d2?8=U+AX}7W@1o1LG;Gl)Q@R!T* z{eCJ?(l*EaVd+nkqQ&^+QO;JHva4YxQ_}(~($AvZ{eZ!Tydle}P7i!W>hw4>A5Qpk zt>^QPuPMkI1MPPnSpx=Iis-beD{|@njkYYW4(7mEyu(P^0dGIdhyo@_Ma ze1{ROIHb%^*NKvN(URbls_XKtO7}>Y);%Q=FHcOx0p4F+@{v)`YYD23XCVU>WDqep zW43$&3Q2j_Y_8TD;gM^u1#82?F}+cIV|)4H)Wb~*#=5hMCKBlT6ak+LZc`GX#Ul(* zw{UrKW7^vRP37LO#GxgF6r zRE2PyNOKGEAvI4Oe$7JZz?rK5njSa0$t?~G^FzKDqgJ`}=Zcz!hXyU3y#TvRG%2HpII$-A4{Wbd>!_@@<*0I1Pv z{$WqWi8irkrNR{PA$nT%gH*ZCb!IOFZP>BK#`5Tu!wt^FcTEY5D}a~k{*!uynxR}jL*%Ycb|UHb+&%s2Tz zR@gDnj1JCFm&|-!cYHnGU->!(vuoF{iSzs%!tErE8j+L3rTKh>)7Nb*>F<*z zwjCd_YdT-}#>P=x4s5@Ad$)w&dCs|GEN14A0XviOfxOw#G0W%989(XN0KmeB{1$6$ zc)wX2#<;(hQNkrOrnFhE+a2WNzwYuJ1{9voTd?5sTU=>6{2{U;*MtsAV@%Kls5j%0 zy%;BR6e8VSwChO!xbNs}u;%*g7(4)?FQ5cdci*o)9#{QN55=0D5gAal!c7$HQ@O_aY=nUmP<54n$aW} zLr8McZWBo4HyB3YPI6oMO+3c!LZ;jCldy=5BM8O^;)Qx-<__!pxgxUpPXFer(KX&K zC3>x9DiAXAWmIn9p(qmvBF!RgPiV{b3pPzC;XdL#i)gyRQ8wH`bhAIRf z>Ot>b9%DY|1+((FNp?*`c@;|4G=~R-`8IkhJsHg;fsBz)wPhvZ9>Ye@~+B zT;i%TyRo$*!WQoe$+@48loZ4hRWSZ{dE7NBRohwc2LU#1(0JTPfNRzzRH({u*t6+UVCI!%)3M-o^l7 zQf8jsqh*^;f4@r=!NxZSL!;IVm|?}86m^+WA9Mt<$%4d6xZDbD`UYH$0wmzGn z&}KA>T&RORwsUe`c1O%QeQo7Bx;{t4UOHW_bH$8JbG5FDG@WX`J8TP8VLjUX_f1wj zTBk!I4s$6|CFQqis}Gl@)ec?WJPSd=WuH{Hf&I`^GQHyk?h#731Dw_u1iW&QA$dl- zQaT@z8&Ck;Ta;vDY$*txeFLZnN{;6j2Db=mGa82syq-;C#&aU$%2bBsUTG6ui_TBV(ZG!(aPw@%4O`kI`42}>w zy-^PB*UOh;lybqTRdDVwn}hotZU5UwvJZp9#L4HmMlJ)+Vq&vhfg8RAu6BoHF%4vy zb3*SA4!!ClTes&-TBH`MlQafik^Qggf&M7@FFf_m5M&U*$R(ykC9|n{Sj9!{F8j8q zM=~YT5L3x{^-a9k9?zDF;gFWOnOVO^_4s5Gx|;Xw@4rK|x>cC8uN&U^M9cLF4k)r8 zm(qrhMB*vLp6xECRPJRc3{p zS)Q)E|70m5#t8%loK#z_KG>R@BUq(5!LA{rvs0&cfowutPekGi-1kVEHF?<8KP7{PZz?Uv47g5PU z1ypYTYy2!FtBnP6E{;KGacb~=^}YZVS!kMd;8bXN+ji_zX3BE5YxjZQ#^cE<#C+~e2h%p_jZ)?@|WPMPurM?sCEoYj%UGvBs&O}RibB6x1ULGEE? zSHh;TrlhU*(BEr0t(l;rT|=x5sJg9Fa^Zjz($`&5%*?Rl>Gbo#mW!U)-rwZ9)Nli0 zvm2Y+ci#7ujUF7@+rzVbEM^3Yq8CND4&+`ZH-Z(O83$_^Pn=LLWqFgQyNrH!$fu6h zMkb^MrCe!qS?`1ELUm=I`IFJk`*u7<`sidj)<2zTAP}v*LK%_BPP0YQf9ZP*Rt;0n zHoHSb3Xdt5*7*p5*%51gjSpHjkSR!`5;!L(LuuYecYS4j$tI`O(sCiDfSS34{NGB& z@MBa4o>BgkmpDi6jq?HfzENFOGg~P@gJZ)JFaEHqBe>;_Szi7OVbbw?d&vXOf1uS+ z=pAPUgjhT6reT;Gal%KR1_71d6BIYizH4Pwz@pAdzr+L-(yQ}K|6e5ss;Z#DzsZnF z`!SAfzSIv{|8cK)Y57>~kNdTBiydA;PgS&CSSoF=nW_3=ER>7ap4btt!{X)0ccIC> zXr$7&4(I|Om!MWP%}RrA;)n3r2rJ<`o}}}Zuo%Kymo{D52T>s&p^25|L4ulr2>4di z^6M{+Yen7%CfdQX6nJIdM!n$)J(n@lS2zO(J<5bIN$0RDYx!mLGp+^hwJ1?QRcoTg;&}0^GJZ@dLg4PLfSlAFUFf_Z8}gPb3?^oHIWq1JcS>+17SGv>LbV{4>a>3{r# zWy(X>Dk4NWLs7e(4-S&`pgC#pd{v4#)`X2ht)BPFbGraK`l}tek|&A@B@AVEnn|vX zJOY|{&fh$*)AiGy6BLFBb?it)9j92&o=k`U8zKIWhd+5BPK){T;Tf;!KoMf1Y#av| z!y~KNc#BB#XwL{7#<4ErJ?@?DAYbb&D6KDs+0JgNkSJmmN4zurTLPE~n5fV=ET>@l zi%rNOUKuB)GCxbvBDw+oPkMm=HT-K;#AKymOK6RVe_G6NO6spn$rPe21Xv!!-;R98&Uf z3Y7Pwe6i;XR!_rGtjSlc$gld&w(FRZ5Sn@(!4JEh905s;PL zc6q4@mm2&(_zF0p=;;2D4UMJVF)Y?S_(5xAhMC`~p##FJDtL?!PnG->>8PG;Byt+f zpAzqQL(OOY+yrYsc%T-vlZ;)jk6Mvd|2^KbP`zd-XP%&bZlnTre=uq0OS;<}B;O~T zG^Kjy+4sNCDqN4+(N09r9BvV8K6z2#MoC>%pbMUno7P!_}{efS}b5gIjP2~iuEtK^Q70)L`WA!R`#sJL{S|F45BnZ&& z7K(2h)q8yh)^_)}HoxxO#4$w;_-AL7{mn>=i*;Sj&V`KnX49&$=U#WX|CSRMqt*9Y zUgbln#8O=d{V1kle$OT0c+Gr_qdLbg;43xFL~8vwWA;}AjZ0BXo!(e`y=MGj?X&!e zZ<+NW&eM9sD8szAVeQFi#}QFEOu=x4G7Uxu)w!DX>&AmC>Sv)2@v9O_<2;U54=e5j zfUa{?^IEzzhSIY-PHyn@O2s-*MM0;WV6;HUrJk#I&x^7cnP1f#ziHVS=!UFi3_XVvurxyM{TT1ZwY!y&k=B!28|f4g*jr)5-c zK1i@wsWVvbBm$n39Gh+tk}{te82FnI^oTUobIWYRs5M$m>~eRE&G>fD&}{(Zj6Clx z;!$kWTfIAFuI4HW?XLlTPIzrU;8=)_c0Q}b|K9k8UJdBq$%#Pin^2fAXs8L+N) z1|zRUv$C&_lmN2Wc%5U@3l6TrHc*?eF?SuNCSwSf8~b4?`p@k3JK!ivKP8T?4dDjk z+m7r4!GW74Qah%#X{_}Y4Wq}p)j+8nkhlE#KV!Qi#&(s+7U4-d}Zk`h>|w|zpfXEvV(-b~1oqTv(#sh~{k zA3Aw*+_yxUsA5&_yITcV@`momeJJ1`=2JbehaoLBxZi0aO)yTcHOJoR+4H(qS({2| zL9&;`?OxrVJUzW~SOU;z z`(XD?o3y&ClXpiZ1F}pvVM*_{+n~##4$bmI zS|f>vlWg!$is-)4^UULi+!3yj>V8*Jf~zal=QDPTJ-s@p&6@pJh{qu2JT+*)Ivjgu zN48>zo5hpmLf&j!)Wc^+dj?RX+>BjJ&paJk0Dq;kP${o(P{LrO{$bv5{f`SzPG{1u$_QZ>C{3CaRBj(FW17aL8f93sO-JFM0Q(L>n4}u~c zDbhiz1e7AZqX-jw-oic&7+6AQK4%F@x*tCRn9m6|Vt=c5)cAv$~pxLlsc&Q>) z=y!T2m$jbF$d_znuZ7G6%?$O(H*@ULMH$>@tg_wvq^<8-ENgT}v#KOy8saL#v_|i%BGA!btkv21 zL~45aFL`WH4h-(;gd)q{v!SKoiKI&o2}|vgx_$AD+p8gYP8FS*6k&?xNe=AyiS8&$ zs5_4b#jHJnCfoCiunK6dd?Vd}X9OR;aa69Ej_gpAnj;qy-f@kd9ErU_y;H@TqQL)Y zlS$Icg^1OAt>Ea11##2+=@u&~nb+`yom@!eF6!VAkHyj@HR8f8Y?9RTiLS-hr6H`t z$i5z>`^!ZLwl@`XGHSyX851*#9_B3TADDW|=qzVE(R?^AlSucz^8K(^`BjZ6W$1N> zA;ZCYnA*9$Ui>i)`%YqE1K&+`>q>?yB6P&d>#Lmle7%jIfjE%b(;!tF!3wj`a-r{a zd^AJ?`1P+-J%dL>6Fym(wg;F<>PHWLDTB!FEmk3Y*VI&Lw18CtI}2giKqY7HC6aq} zNyhI!2V_5YAOA-Kaf<;=(}M`VHVn?>a^u1rR`Yu_I(065Fz~_`-|dKIl0)h|oA*XY zu@s0U)l@;yw~AC#_~}Nq)vE3>{s8ZMQ-FXqepOqF-00-p)(X$RxvBY}H%x^33>nw? zt)c2TQIE^qs?1OB9TTYVOx9oqMb$Gg#n`XzAku_0`KjMvYii~PFB>;U zxuWXwg2qy+OXjTex&7gV0TEH7va?$D7Uq_i>W4B4Ti-m0A){PIIcM=(^PvJedx( z+~U!3it3b)cCJ&i*8M*8R|^3^Xs370P2EM2LV~);hl(U(^V{12{|4dn_vhM;d!NVs z0eMFM;$pw=a%f0MPk%p)q@=G)Oi6tc^RCwWA4wEAzFJ8R(z{c`N7UK|u zPsBGgqhM_!QKvPoiPF^2n30YwN%Qr9Ph$=OKosDsa(HwU9v;pJ0)?-vtT2>ch;PMq z*4FZ?sFD4Vco3UM1NX8TW2`PJ3L6{K%m~i#TSuG_)1{l;$KV=h8{CQh|tA%toZ|-{{K*;w`^oXp+YlDG=e1jhyo6N#uq7DwX zlG~@##xQqoubtEC+ic9xbp3r{2C$+!CS41r=pb{%LLuNI^Uv3>ibaPMZ0%^1!F1-g z^qk63_(OdB?OoQ?gQ~RjUld&W=ffA5m!wow3bL}nNEGS6^}GBwFL!9CzZ`VU)&G%zXUZpxkMY3t zVSgk^f&FAx?O zHPqHtR{RX}4Auq)bW>APsY4*fee~nvWVYip-p88d2 z2o+V5pE=Uc?yYajE5vJtY9D>Mu9X+}iG4o*m%=k=|8TW0HCtF*yk9w6QdL`<0t5oF zu(ED?171JBH7KV?2raSnY(z zSd$wpNoOYOSOWYqCnqNkE^cbIgK)@&cZ1y=lc3<6-)>63I_L7>)O;#FSC(X0cq}W| zdfxX6ptjqPj$O70($0O!-4B6*5~ru34x+n=#N*eg&9!${q=k0O9Mhev5nYoX@{;+A zt|`nAf*)_gUA-syMGl)bU3ZA}w-f zzH_qEi8V?ZYGWI#km_*Wdvf1&CL0|N%paW0>8@{~zi@5dsc=&i5o1`!rP+v+weH#j zlJT`AJ%r+6)pdC7o8vB}4Rv$Nx#bv~Qn%@Yh3Bh(pKRA2EGn84*tTd4x^laHa&r5x6`g_818;kTa)+r7G1~8E3I?y#}gZAM4%g&x#%p@yc^qiJXZ0 z8vb-)A30m8Q!^T5Fai5kH)Pn?@sok)%vs5sw9oP~K6kr%Z^?n#rTY-jk7W;e!pwnoPk=9@T8vMnWI*q#9wy3gzWh6=qPs%*J z)68iL=9+%wWfRuzu}S^VcmK{{B|vlDB<$qXFeYJUwIa2n>4l&82HrhAC@M&Z1wc;# z2=x8vh*r0Wj9}lRcplo<;p@o`xVlWAs}A|6k{+U4`xe7o1qTb z$;i`()aWe>J9K)ATM1-nZB2I8Hfos9k(IwLp&m5)>N0{^#LT}T?(8%cbL{_(wF2Qch;jC-YwFDpUa@WIN9QKPt}_fNfv9>oTIjaDsNwxi{02^ByLQ6$)CjF1lT4hE!rmo&gxJZUb!IDhY?? zv;s@#KsO9~FX%3z(~yz~=c!_>LJ`R+{;elRd$mcmLmJzthOgHnDu63j;;>V8;Ngmz z_)a;GAkW&@CQ2tXj50;H0z@t)B&Lk7-;{3fd)Dx?zIHc^EPs)}EX`BHUhB`bC$UdIT-!V4y5)cxv zKN`5)t3KFp#ZB{4&!>lu=hg`at*9*s=+=wS7v?hA5Eq@;b-En=fX%Z zcfFFX59}bWHbsYIvxV~5Kj4u!6i)ze2=+# zp$*)AB9tFgG^ut>7>nCN3rb!@zrVM?OK<2~NqaUN`wIMJJZD6?bL;`}r5Jm!f?18v zUs*rRKk*4hpyuSBdy<48eZ@_F^hpuj%VkKFl`|RaxuH7P#WdEoeA2oL;~i`0m^!0w zDA6nQ1LtDBJfH_CnR560VcY{t1McgG?br+-#q4)4fs+YN@8%=+;h!q0r9zl=o3w_o zusXu_)Fs~&54|55I)}jz3Q2n93X%o8e*Eo5mjsOmS?`Q1R{MQ*Ov!d0h+6x9<;d&;K;{ZPnEFyc^qO|k(R~ZTl&qwF`gyr)Wy-%4K_F!Gc z=y3nZ;*t)>80_1$agT@Fr`^vM@9k1_oKIfiw^ier7s9wBW8|H$6!GQ25OG^)oF6n% zz12Sa?8o~O}atp(0ZF_hKwqgYkAL}E+W3}=t8@Hh}3WEw#ohg+V z5|+!Et#DkTA3kYE-cBrcQ2SW4J}=H)8Yt{Dlpn!83tkv=dZ3U?Hs)V*j)qqRw>bEW zeXJfmKBdWnx~HPwYV}^i0XZzEvGAs8;7!G77ulHQfDI{P27sh~H7dgs^OhVDuhU&B z)Mg{Mk>lG04uEFc-WrhRep`sDdLM|HlWJK|-X+3i67XHYE~#N;L0jc`p0%w0n5|A9 zCooTlObIYpYd#&Fi$e}`uk%1xsT9A_Z;mV|$P{3gLVV-zo;v3JY0tujwgxPDbi8;i zcgT4GSaVLIwxQmM^I1yUrYcStOyWGNAbFo%ZFpoVs-!7=axwDCJ_O>uk|FEiML}o4 zp%}?GWxk4#Lb4lGHU#GOqrFXj4DKcn>L&gWZ5Cw*^_ZY?oV{0*@V z@I_ig@F7<-KXa@>!diabx%}q<}GpM-C`55{=ahWPLb6VBF6WB0N z8tuA;ry+Jkdq3*LlXQU|a}vInk2UaFPgJ0Zzjm0j{ur)DIhDB6u#m?dp{ppJJ^=^| zPNK2CycwF95VZ4>rU_+j$VP2rSB*{GcPyW)mYY8v4+&!j@tFB%IA3LfnQNi>jN@!hu-$c(^R9`n#vX$%J zT%2!(U7{eo7g1h~Q^ELFvvxkGjGg0Gt1?u*isJIZJ(xKl&?5?sr*-kq$9uZ3_=Mpz z&4T_bZ%wRZ87|esuwgHFwGI)5z2A%1rJIy~(k1LS&>gfL+r+Ld#McsZIjDLw3n4u2 zhTe)oe0}KA*JDH-$-mc8@cLg8o5??=+|m){I$~AqGcamlpN&)hbG&s^t8cv^jA|aP zu-lngitgEJlSBYe2wJZm_AjCZoDsV7k6N!rrEyZ$B(IPYS#|R`FUbT|TCp9Iv2W4H z_$wj_BKm2X-gf-)a}jJkYvIaT$J~0{sbmo&`+$H|^$K&X9BRDQT;V8S z)o={~JV-!X@T&Mq0(Yb89hrwS7jck$>ZXzL1yy@{A_!3q>%OiKDZ}S>{#_(V_mELR+rd?DZ|xQZrJ2c8}v%IK2thg4WEv_rH#p& zvBUp(2Ec)$iJ}ini{T!zKQ2G=x;4FY8s@(qnXu^qi@vig8f-tpArm-#)%N-d!ukk| zRt8QYFCw_AexPGMA6<#1WT_VFx~}K=G-0b>fkcN;vaX-#ogu!YGn8{@+{g7O;=RUC z$qP3@n2zOt0?lsVNlkW7@8WrT`G)$$go{Jil#dU?(FVrGe(EwhJ^$Rp5{HXk^6FGt z*f%i`!!d@a($nnq)ch;`G4lD^L#UQ1q6c$T>qNhWq{F&CXOgAiW0tcZ-G=pJsS8>z z*fDRdO9!`LOi1Q;vyymBkyV@E@dM%!MHhG_^4ap$Y?T17v|lAfwTG)q-$u@RieJ6| zGhSHWwOLS#4+8#^?L1#Q3T&AI!3kSd9i9i1LzCNjIkRB#Qvw6B(XE7AqpB7UOMk9N zlL`DA(e@t5JSH6bHd*FbzDaw2TXIM(4`d=O09dws!HZh0uHlRNQ!hW?OnAPyx_)nL zNC{b;jvOn}=B3N7D@m7m?0w#u^9q^BzT}!6c-7C6qdqGY<9T_^MXvZM>~7VF zROr=iIO_a>a0sRTZ9qwWsuW9{xyI+cJ~&s|+92X)-mY0xvq%(X55umm;R?Oa4Lwca zSQ;7&h{OrzKk0d@v^)opuDaM8JAkoDMQ*A4F`mGXlC~G;)18b_DX3iG^|1?kcU{p& zYa}So$AGzV80E)Z$rw>nHe%scFEBhi?HYp_6RyRRJ$u ztNYDlUylUaQ|60ML3PMA-P}ruS@i&jenJXS`El?t=hD^tNOz;TFd)!N&10^0mkl5< z9lDUTn3$L!m6dsGYRwx0Y3QLo`z?!+$%UNJmu^O8MiJrFj29On+fE0}Ty6IfJrjKl zem(d9@8|fK65{@ib^G5U#bi(K+?0O zTV^PMX6EKpl+L>D&-i-^DkcA|BI2HRA&_7q>c#d#!_Tkn@IoSW>gkW?iY;N_n7>t~ z=7+_oZxU>MT3S*;87ctoQ4i`q?!WlRz3RS$*1BUQLiJ$Xp<3%hZfh&a9ReO6{w}q0 z5?X@elOc@{IVU-z`U;?&))qbUyl}ua2QN%ZODiZSXb6Q8qDGtFJ89y3_N>wI$2Z$b z&_BUMoaHM@@9d$6%X+5)3Vo@ZKW=$BEHdV?BxA7NPx3K=y3yfrnMx9TvoW=+9Hg$a zjh!8vsHiUKnmGqcNhNM#Vxr^qg)0Eby0ljO+d%Uu4xi7Fbei#rh{x0KD^|%kI9c+afM(&CQ{I zo~{7!t$(f|;eZ3*KiQmL6M0t5?^)sB4}fLkKbK_xR|<&dH+~3%*qQTJ3&eo+_+JXL L;FlFI-hKEVM+eXK literal 0 HcmV?d00001 diff --git a/umn/source/access_control/security_group/importing_and_exporting_security_group_rules.rst b/umn/source/access_control/security_group/importing_and_exporting_security_group_rules.rst index bf8fe27..2630185 100644 --- a/umn/source/access_control/security_group/importing_and_exporting_security_group_rules.rst +++ b/umn/source/access_control/security_group/importing_and_exporting_security_group_rules.rst @@ -65,6 +65,11 @@ Procedure +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ | | **Port**: The port or port range over which traffic can reach your ECS. The value can be from 1 to 65535. | 22, or 22-30 | +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ + | Type | Source IP address version. You can select: | IPv4 | + | | | | + | | - IPv4 | | + | | - IPv6 | | + +-----------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+------------------------------------+ | Source | Source of the security group rule. The value can be an IP address, a security group, or an IP address group to allow access from IP addresses or instances in the security group. For example: | sg-test[96a8a93f-XXX-d7872990c314] | | | | | | | - IP address: | | diff --git a/umn/source/change_history.rst b/umn/source/change_history.rst index d8e9b47..1c35211 100644 --- a/umn/source/change_history.rst +++ b/umn/source/change_history.rst @@ -8,6 +8,16 @@ Change History +-----------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Released On | Description | +===================================+====================================================================================================================================================================================================================================================================================================================================+ +| 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 `. | 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 4462c55..48dd160 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 @@ -16,3 +16,9 @@ Security Group Configuration You can configure port 69 and configure data channel ports used by TFTP for the security group. In RFC1350, the TFTP protocol specifies that ports available to data channels range from 0 to 65535. However, not all these ports are used by the TFTP daemon processes of different applications. You can configure a smaller range of ports for the TFTP daemon. 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 + :alt: **Figure 1** Security group rules + + **Figure 1** Security group rules diff --git a/umn/source/faq/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst b/umn/source/faq/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst index 4f71fbb..8781a9e 100644 --- a/umn/source/faq/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst +++ b/umn/source/faq/vpcs_and_subnets/why_cant_i_delete_my_vpcs_and_subnets.rst @@ -75,39 +75,39 @@ Before deleting a VPC, ensure that all subnets in the VPC have been deleted. You .. table:: **Table 2** Deleting VPCs - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | Prompts | Cause | Solution | | - +===========================================================================================================================+=========================================================================================================================+===============================================================================================================+===========================================================+ - | You do not have permission to perform this operation. | Your account does not have permissions to delete VPCs. | Contact the account administrator to grant permissions to your account and then delete the VPC. | | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | Delete the VPC endpoint service or the route configured for the service from the VPC route table and then delete the VPC. | The VPC route table has custom routes. | Delete the custom routes and then delete the VPC. | | - | | | | | - | | | #. In the VPC list, locate the row that contains the VPC and click the number in the **Route Tables** column. | | - | | | | | - | | | The route table list is displayed. | | - | | | | | - | | | #. :ref:`Deleting a Route ` | | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | | The VPC is being used by a VPC endpoint service. | Search for the VPC endpoint service on the VPC endpoint service console and delete it. | | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | This VPC cannot be deleted because it has associated resources. | The VPC is being used by the following resources: | Click the resource name hyperlink as prompted to delete the resource. | | - | | | | | - | | - Subnet | - :ref:`Table 1 ` | | - | | - VPC peering connection | - :ref:`Deleting a VPC Peering Connection ` | | - | | - Custom route table | - :ref:`Deleting a Route Table ` | | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | Delete the virtual gateway that is using the VPC and then delete the VPC. | The VPC is being used by a Direct Connect virtual gateway. | On the Direct Connect console, locate the virtual gateway and delete it. | | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | Delete the VPN gateway that is using the VPC and then delete the VPC. | Delete the VPN gateway that is using the VPC and then delete the VPC. | The VPC is being used by a VPN gateway. | On the VPN console, locate the VPN gateway and delete it. | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | Delete all custom security groups in this region and then delete this last VPC. | In the current region, this is the last VPC and there are custom security groups. | Delete all custom security groups and then delete the VPC. | | - | | | | | - | | .. important:: | :ref:`Deleting a Security Group ` | | - | | | | | - | | NOTICE: | | | - | | You only need to delete the custom security groups. The default security group does not affect the deletion of VPCs. | | | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ - | Release all EIPs in this region and then delete this last VPC. | In the current region, this is the last VPC and there are EIPs. | Release all EIPs and then delete the VPC. | | - | | | | | - | | | :ref:`Unbinding an EIP from an ECS and Releasing the EIP ` | | - +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------+ + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | Prompts | Cause | Solution | + +===========================================================================================================================+=========================================================================================================================+===============================================================================================================+ + | You do not have permission to perform this operation. | Your account does not have permissions to delete VPCs. | Contact the account administrator to grant permissions to your account and then delete the VPC. | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | Delete the VPC endpoint service or the route configured for the service from the VPC route table and then delete the VPC. | The VPC route table has custom routes. | Delete the custom routes and then delete the VPC. | + | | | | + | | | #. In the VPC list, locate the row that contains the VPC and click the number in the **Route Tables** column. | + | | | | + | | | The route table list is displayed. | + | | | | + | | | #. :ref:`Deleting a Route ` | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | | The VPC is being used by a VPC endpoint service. | Search for the VPC endpoint service on the VPC endpoint service console and delete it. | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | This VPC cannot be deleted because it has associated resources. | The VPC is being used by the following resources: | Click the resource name hyperlink as prompted to delete the resource. | + | | | | + | | - Subnet | - :ref:`Table 1 ` | + | | - VPC peering connection | - :ref:`Deleting a VPC Peering Connection ` | + | | - Custom route table | - :ref:`Deleting a Route Table ` | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | Delete the virtual gateway that is using the VPC and then delete the VPC. | The VPC is being used by a Direct Connect virtual gateway. | On the Direct Connect console, locate the virtual gateway and delete it. | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | Delete the VPN gateway that is using the VPC and then delete the VPC. | The VPC is being used by a VPN gateway. | On the VPN console, locate the VPN gateway and delete it. | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | Delete all custom security groups in this region and then delete this last VPC. | In the current region, this is the last VPC and there are custom security groups. | Delete all custom security groups and then delete the VPC. | + | | | | + | | .. important:: | :ref:`Deleting a Security Group ` | + | | | | + | | NOTICE: | | + | | You only need to delete the custom security groups. The default security group does not affect the deletion of VPCs. | | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ + | Release all EIPs in this region and then delete this last VPC. | In the current region, this is the last VPC and there are EIPs. | Release all EIPs and then delete the VPC. | + | | | | + | | | :ref:`Unbinding an EIP from an ECS and Releasing the EIP ` | + +---------------------------------------------------------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------------------------+ 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 4efe30f..1f20d28 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 @@ -56,7 +56,11 @@ Configuring a VPC for ECSs That Access the Internet Using EIPs | | | | | | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + | Default Subnet | IPv4 CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | IPv6 CIDR Block | Specifies whether to set **IPv6 CIDR Block** to **Enable**. | ``-`` | + | | | | | + | | | After the IPv6 function is enabled, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ 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 e2cda31..99efccf 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 @@ -66,7 +66,11 @@ Procedure | | | | | | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + | Default Subnet | IPv4 CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | IPv6 CIDR Block | Specifies whether to set **IPv6 CIDR Block** to **Enable**. | ``-`` | + | | | | | + | | | After the IPv6 function is enabled, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ 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 da22c06..96ec641 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 @@ -48,7 +48,11 @@ Procedure | | | | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + | IPv4 CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | IPv6 CIDR Block | Specifies whether to set **IPv6 CIDR Block** to **Enable**. | ``-`` | + | | | | + | | If you select this option, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created. | | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ 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 c0f7f98..697dc5e 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 @@ -66,7 +66,11 @@ Procedure | | | | | | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + | Default Subnet | IPv4 CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | IPv6 CIDR Block | Specifies whether to set **IPv6 CIDR Block** to **Enable**. | ``-`` | + | | | | | + | | | After the IPv6 function is enabled, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ 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 686be34..7435a6c 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 @@ -48,7 +48,11 @@ Procedure | | | | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + | IPv4 CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | IPv6 CIDR Block | Specifies whether to set **IPv6 CIDR Block** to **Enable**. | ``-`` | + | | | | + | | If you select this option, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created. | | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ diff --git a/umn/source/route_tables/configuring_an_snat_server.rst b/umn/source/route_tables/configuring_an_snat_server.rst index 2b7c6f5..622ef19 100644 --- a/umn/source/route_tables/configuring_an_snat_server.rst +++ b/umn/source/route_tables/configuring_an_snat_server.rst @@ -60,7 +60,7 @@ Procedure .. code-block:: console [root@localhost ~]# ping www.google.com - PING www.XXX.com (xxx.xxx.xxx.xxx) 56(84) bytes of data. + PING www.google.com (xxx.xxx.xxx.xxx) 56(84) bytes of data. 64 bytes from xxx.xxx.xxx.xxx: icmp_seq=1 ttl=51 time=9.34 ms 64 bytes from xxx.xxx.xxx.xxx: icmp_seq=2 ttl=51 time=9.11 ms 64 bytes from xxx.xxx.xxx.xxx: icmp_seq=3 ttl=51 time=8.99 ms diff --git a/umn/source/route_tables/route_tables_and_routes.rst b/umn/source/route_tables/route_tables_and_routes.rst index 901508d..c7255a9 100644 --- a/umn/source/route_tables/route_tables_and_routes.rst +++ b/umn/source/route_tables/route_tables_and_routes.rst @@ -35,8 +35,14 @@ You can add routes to default and custom route tables and configure the destinat After a route table is created, the system automatically adds the following system routes to the route table, so that instances in a VPC can communicate with each other. - Routes whose destination is 100.64.0.0/10 or 198.19.128.0/20. + - Routes whose destination is a subnet CIDR block. + If you enable IPv6 when creating a subnet, the system automatically assigns an IPv6 CIDR block to the subnet. Then, you can view IPv6 routes in its route table. Example destinations of subnet CIDR blocks are as follows: + + - IPv4: 192.168.2.0/24 + - IPv6: 2407:c080:802:be7::/64 + .. note:: In addition to the preceding system routes, the system automatically adds a route whose destination is 127.0.0.0/8. This is the local loopback address. diff --git a/umn/source/service_overview/basic_concepts/route_table.rst b/umn/source/service_overview/basic_concepts/route_table.rst index 46e785e..99cd92a 100644 --- a/umn/source/service_overview/basic_concepts/route_table.rst +++ b/umn/source/service_overview/basic_concepts/route_table.rst @@ -35,8 +35,14 @@ You can add routes to default and custom route tables and configure the destinat After a route table is created, the system automatically adds the following system routes to the route table, so that instances in a VPC can communicate with each other. - Routes whose destination is 100.64.0.0/10 or 198.19.128.0/20. + - Routes whose destination is a subnet CIDR block. + If you enable IPv6 when creating a subnet, the system automatically assigns an IPv6 CIDR block to the subnet. Then, you can view IPv6 routes in its route table. Example destinations of subnet CIDR blocks are as follows: + + - IPv4: 192.168.2.0/24 + - IPv6: 2407:c080:802:be7::/64 + .. note:: In addition to the preceding system routes, the system automatically adds a route whose destination is 127.0.0.0/8. This is the local loopback address. 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 7ee8266..c3ea821 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 @@ -27,6 +27,11 @@ Procedure #. Click the **IP Addresses** tab and click **Assign Virtual IP Address**. +#. Select an IP address type. This parameter is available only in regions supporting IPv6. + + - IPv4 + - IPv6 + #. Select a virtual IP address assignment mode. - **Automatic**: The system assigns an IP address automatically. diff --git a/umn/source/vpc_and_subnet/index.rst b/umn/source/vpc_and_subnet/index.rst index ca02e96..786d127 100644 --- a/umn/source/vpc_and_subnet/index.rst +++ b/umn/source/vpc_and_subnet/index.rst @@ -7,6 +7,7 @@ VPC and Subnet - :ref:`VPC ` - :ref:`Subnet ` +- :ref:`IPv4 and IPv6 Dual-Stack Network ` .. toctree:: :maxdepth: 1 @@ -14,3 +15,4 @@ VPC and Subnet vpc/index subnet/index + ipv4_and_ipv6_dual-stack_network diff --git a/umn/source/vpc_and_subnet/ipv4_and_ipv6_dual-stack_network.rst b/umn/source/vpc_and_subnet/ipv4_and_ipv6_dual-stack_network.rst new file mode 100644 index 0000000..fcd107e --- /dev/null +++ b/umn/source/vpc_and_subnet/ipv4_and_ipv6_dual-stack_network.rst @@ -0,0 +1,101 @@ +:original_name: vpc_0002.html + +.. _vpc_0002: + +IPv4 and IPv6 Dual-Stack Network +================================ + +What Is an IPv4/IPv6 Dual-Stack Network? +---------------------------------------- + +IPv4 and IPv6 dual-stack allows your resources, such as ECSs, to use both IPv4 and IPv6 addresses for private and public network communications. For example, if ECSs use the IPv4/IPv6 dual-stack network: + +- ECSs can communicate with each other using private IPv4 addresses. +- ECSs can communicate with the Internet after they are bound with EIPs. +- ECSs can communicate with each other using IPv6 addresses. +- ECSs can communicate with the Internet after their IPv6 addresses are added to shared bandwidths. + +.. note:: + + If you select **Enable** for **IPv6 CIDR Block** when creating a subnet, an IPv6 CIDR block will be automatically assigned to the subnet. + + Basic operations on IPv4 and IPv6 dual-stack networks are the same as those on IPv4 networks, except some parameters. Check the console pages for details. + +Notes and Constraints +--------------------- + +- Only certain ECS specifications support IPv6 networks and can use IPv4/IPv6 dual-stack networks. You need to select such ECSs in supported regions. + + To check which ECSs support IPv6: + + - On the ECS console, click **Buy ECS**. On the displayed page, view the ECS specifications. + + If there is the **IPv6** parameter with the value of **Yes**, the ECS specifications support IPv6. + +IPv6 Application Scenarios +-------------------------- + +If your ECS supports IPv6, you can use the IPv4/IPv6 dual-stack network. :ref:`Table 1 ` shows the example application scenarios. + +.. _vpc_0002__table20563744105916: + +.. table:: **Table 1** Application scenarios of IPv4/IPv6 dual stack + + +--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+ + | Application Scenario | Description | Subnet | ECS | + +============================================+=========================================================================================================================================================+====================+===========================================================================+ + | Private communication using IPv6 addresses | Your applications deployed on ECSs need to communicate with other systems (such as databases) through private networks using IPv6 addresses. | - IPv4 CIDR block | - Private IPv4 address: used for private communication | + | | | - IPv6 CIDR block | - IPv6 address: used for private communication. | + +--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+ + | Public communication using IPv6 addresses | Your applications deployed on ECSs need to provide services accessible from the Internet using IPv6 addresses. | - IPv4 CIDR block | - Private IPv4 address + IPv4 EIP: used for public network communication | + | | | - IPv6 CIDR block | - IPv6 address + shared bandwidth: used for public network communication | + +--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+ + | | Your applications deployed on ECSs need to both provide services accessible from the Internet and analyze the access request data using IPv6 addresses. | | | + +--------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------+---------------------------------------------------------------------------+ + +Basic Operations +---------------- + +**Creating an IPv6 Subnet** + +Create an IPv6 subnet by following the instructions in :ref:`Creating a Subnet for the VPC `. Select **Enable** for **IPv6 CIDR Block**. An IPv6 CIDR block will be automatically assigned to the subnet. IPv6 cannot be disabled after the subnet is created. Currently, customizing IPv6 CIDR block is not supported. + +**Viewing In-Use IPv6 Addresses** + +In the subnet list, click the subnet name. On the displayed page, view in-use IPv4 and IPv6 addresses on the **IP Addresses** tab. + +**Adding a Security Group Rule (IPv6)** + +Add a security group rule with **Type** set to **IPv6** and **Source** or **Destination** set to an IPv6 address or IPv6 CIDR block. + +**Adding a Network ACL Rule (IPv6)** + +Add a network ACL rule with **Type** set to **IPv6** and **Source** or **Destination** set to an IPv6 address or IPv6 CIDR block. + +**Adding a Route (IPv6)** + +Add a route with **Destination** and **Next Hop** set to an IPv4 or IPv6 CIDR block. For details about how to add a route, see :ref:`Adding a Custom Route `. If the destination is an IPv6 CIDR block, the next hop can only be an IP address in the same VPC as the IPv6 CIDR block. + +.. note:: + + If the destination is an IPv6 CIDR block, the next hop type can only be an ECS, extension NIC, or virtual IP address. The next hop must also have IPv6 addresses. + +**Assigning an IPv6 Virtual IP Address** + +Assign a virtual IPv4 or IPv6 address by referring to :ref:`Assigning a Virtual IP Address `. + +.. note:: + + Each virtual IPv6 address can only be bound to one dual-stack NIC. + +**Dynamically Assigning IPv6 Addresses** + +After an ECS is created successfully, you can view the assigned IPv6 address on the ECS details page. You can also log in to the ECS and run the **ifconfig** command to view the assigned IPv6 address. + +If an IPv6 address fails to be automatically assigned or the selected image does not support the function of automatic IPv6 address assignment, manually obtain the IPv6 address by referring to "Dynamically Assigning IPv6 Addresses" in *Elastic Cloud Server User Guide*. + +.. note:: + + If an ECS is created from a public image: + + Before enabling dynamic IPv6 address assignment for a Linux public image, check whether IPv6 is supported and then check whether dynamic IPv6 address assignment has been enabled. Currently, all Linux public images support IPv6, and dynamic IPv6 address assignment is enabled for Ubuntu 16 by default. You do not need to configure dynamic IPv6 address assignment for the Ubuntu 16 OS. For other Linux public images, you need to enable this function. 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 0f6214d..cb17574 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 @@ -48,7 +48,11 @@ Procedure | | | | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + | IPv4 CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ + | IPv6 CIDR Block | Specifies whether to set **IPv6 CIDR Block** to **Enable**. | ``-`` | + | | | | + | | If you select this option, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created. | | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | +--------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ 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 81a6a3e..b793d0f 100644 --- a/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst +++ b/umn/source/vpc_and_subnet/subnet/managing_subnet_tags.rst @@ -57,14 +57,14 @@ Procedure The **Subnets** page is displayed. -#. Click **+** to add another tag key and value. - - You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for subnets, the subnets containing all specified tags will be displayed. - #. In the search box above the subnet list, click the search box. Click the tag key and then the value as required. The system filters resources based on the tag you select. + Click anywhere in the search box to add the next tag key and value. + + You can add multiple tag keys and values to refine your search results. If you add more than one tag to search for VPCs, the VPCs containing all specified tags will be displayed. + **Add, delete, edit, and view tags on the Tags tab of a subnet.** #. Log in to the management console. 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 fe8e312..4d11f6e 100644 --- a/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst +++ b/umn/source/vpc_and_subnet/vpc/creating_a_vpc.rst @@ -66,7 +66,11 @@ Procedure | | | | | | | | The name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ - | Default Subnet | CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + | Default Subnet | IPv4 CIDR Block | The CIDR block for the subnet. This value must be within the VPC CIDR block. | 192.168.0.0/24 | + +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ + | Default Subnet | IPv6 CIDR Block | Specifies whether to set **IPv6 CIDR Block** to **Enable**. | ``-`` | + | | | | | + | | | After the IPv6 function is enabled, the system automatically assigns an IPv6 CIDR block to the created subnet. Currently, the IPv6 CIDR block cannot be customized. IPv6 cannot be disabled after the subnet is created. | | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ | Default Subnet | Associated Route Table | The default route table to which the subnet will be associated. You can change the route table to a custom route table on the **Subnets** page. | Default | +-------------------------------------+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+ 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 67a95c7..0597445 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 @@ -62,7 +62,7 @@ Procedure | | - **Accepted traffic**: specifies that only accepted traffic of the specified resource will be logged. Accepted traffic refers to the traffic permitted by the security group or firewall. | | | | - **Rejected traffic**: specifies that only rejected traffic of the specified resource will be logged. Rejected traffic refers to the traffic denied by the firewall. | | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ - | Log Group | The log group created in LTS. | lts-group-wule | + | Log Group | The log group created in LTS. | lts-group-abc | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ | Log Topic | The log topic created in LTS. | LogTopic1 | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------------------+ 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 58fafcc..1945087 100644 --- a/umn/source/vpc_flow_log/vpc_flow_log_overview.rst +++ b/umn/source/vpc_flow_log/vpc_flow_log_overview.rst @@ -5,13 +5,14 @@ VPC Flow Log Overview ===================== -What Is a Flow Log? -------------------- +What Is a VPC Flow Log? +----------------------- A VPC flow log records information about the traffic going to and from a VPC. VPC flow logs help you monitor network traffic, analyze network attacks, and determine whether security group and firewall rules require modification. -VPC flow logs must be used together with the Log Tank Service (LTS). Before you create a VPC flow log, you need to create a log group and a log topic in LTS. shows the process for configuring VPC flow logs. +VPC flow logs must be used together with the Log Tank Service (LTS). Before you create a VPC flow log, you need to create a log group and a log topic in LTS. :ref:`Figure 1 ` shows the process for configuring VPC flow logs. +.. _flowlog_0002__fig1535115691415: .. figure:: /_static/images/en-us_image_0162336264.png :alt: **Figure 1** Configuring VPC flow logs