@alicloud/vpc20160428 7.2.4 → 7.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (329) hide show
  1. package/dist/client.d.ts +413 -318
  2. package/dist/client.js +479 -341
  3. package/dist/client.js.map +1 -1
  4. package/dist/models/ActivateRouterInterfaceRequest.d.ts +2 -1
  5. package/dist/models/ActivateRouterInterfaceRequest.js.map +1 -1
  6. package/dist/models/AllocateEipAddressRequest.d.ts +14 -14
  7. package/dist/models/AssociateMacSecKeyRequest.d.ts +3 -3
  8. package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.d.ts +5 -7
  9. package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.js.map +1 -1
  10. package/dist/models/AssociateVpcCidrBlockRequest.d.ts +5 -5
  11. package/dist/models/AssociateVpcCidrBlockResponseBody.d.ts +1 -1
  12. package/dist/models/AssociateVpnGatewayWithCertificateRequest.d.ts +3 -3
  13. package/dist/models/AttachDhcpOptionsSetToVpcRequest.d.ts +2 -2
  14. package/dist/models/AttachVbrToVpconnRequest.d.ts +8 -6
  15. package/dist/models/AttachVbrToVpconnRequest.js.map +1 -1
  16. package/dist/models/AttachVbrToVpconnResponseBody.d.ts +1 -1
  17. package/dist/models/CancelPhysicalConnectionRequest.d.ts +1 -1
  18. package/dist/models/CheckVpnBgpEnabledRequest.d.ts +1 -1
  19. package/dist/models/CompletePhysicalConnectionLoarequest.d.ts +10 -10
  20. package/dist/models/ConnectRouterInterfaceRequest.d.ts +1 -1
  21. package/dist/models/CreateCustomerGatewayRequest.d.ts +4 -4
  22. package/dist/models/CreateCustomerGatewayResponseBody.d.ts +1 -1
  23. package/dist/models/CreateEnhancedVpnGatewayRequest.d.ts +3 -3
  24. package/dist/models/CreateFailoverTestJobRequest.d.ts +11 -11
  25. package/dist/models/CreateFailoverTestJobResponseBody.d.ts +1 -1
  26. package/dist/models/CreateIpsecServerRequest.d.ts +2 -2
  27. package/dist/models/CreatePhysicalConnectionRequest.d.ts +13 -11
  28. package/dist/models/CreatePhysicalConnectionRequest.js.map +1 -1
  29. package/dist/models/CreatePhysicalConnectionSetupOrderRequest.d.ts +10 -8
  30. package/dist/models/CreatePhysicalConnectionSetupOrderRequest.js.map +1 -1
  31. package/dist/models/CreateRouteTargetGroupRequest.d.ts +3 -3
  32. package/dist/models/CreateSslVpnServerRequest.d.ts +11 -11
  33. package/dist/models/CreateVbrHaRequest.d.ts +5 -5
  34. package/dist/models/CreateVbrHaResponseBody.d.ts +1 -1
  35. package/dist/models/CreateVcoRouteEntryRequest.d.ts +2 -2
  36. package/dist/models/CreateVcoRouteEntryResponseBody.d.ts +1 -1
  37. package/dist/models/CreateVirtualPhysicalConnectionRequest.d.ts +9 -9
  38. package/dist/models/CreateVpconnFromVbrRequest.d.ts +2 -2
  39. package/dist/models/CreateVpnAttachmentRequest.d.ts +73 -133
  40. package/dist/models/CreateVpnAttachmentRequest.js.map +1 -1
  41. package/dist/models/CreateVpnAttachmentResponseBody.d.ts +3 -3
  42. package/dist/models/CreateVpnConnectionRequest.d.ts +95 -131
  43. package/dist/models/CreateVpnConnectionRequest.js.map +1 -1
  44. package/dist/models/CreateVpnConnectionResponseBody.d.ts +1 -1
  45. package/dist/models/CreateVpnGatewayRequest.d.ts +17 -17
  46. package/dist/models/CreateVpnGatewayResponseBody.d.ts +2 -2
  47. package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +13 -13
  48. package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +6 -6
  49. package/dist/models/CreateVswitchCidrReservationRequest.d.ts +15 -7
  50. package/dist/models/CreateVswitchCidrReservationRequest.js +2 -0
  51. package/dist/models/CreateVswitchCidrReservationRequest.js.map +1 -1
  52. package/dist/models/CreateVswitchRequest.d.ts +9 -9
  53. package/dist/models/DeleteBgpGroupRequest.d.ts +2 -2
  54. package/dist/models/DeleteBgpNetworkRequest.d.ts +4 -4
  55. package/dist/models/DeleteFailoverTestJobRequest.d.ts +4 -4
  56. package/dist/models/DeleteIpsecServerRequest.d.ts +4 -4
  57. package/dist/models/DeleteNatGatewayRequest.d.ts +4 -4
  58. package/dist/models/DeletePublicIpAddressPoolCidrBlockRequest.d.ts +3 -3
  59. package/dist/models/DeleteRouteEntriesRequest.d.ts +2 -2
  60. package/dist/models/DeleteRouteEntriesResponseBody.d.ts +2 -2
  61. package/dist/models/DeleteVbrHaRequest.d.ts +3 -3
  62. package/dist/models/DeleteVpnGatewayRequest.d.ts +3 -3
  63. package/dist/models/DeleteVpnRouteEntryRequest.d.ts +2 -2
  64. package/dist/models/DescribeCustomerGatewayRequest.d.ts +1 -1
  65. package/dist/models/DescribeCustomerGatewayResponseBody.d.ts +2 -2
  66. package/dist/models/DescribeCustomerGatewaysRequest.d.ts +1 -1
  67. package/dist/models/DescribeEipAddressesRequest.d.ts +7 -75
  68. package/dist/models/DescribeEipAddressesRequest.js.map +1 -1
  69. package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.d.ts +5 -3
  70. package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.js.map +1 -1
  71. package/dist/models/DescribeExpressConnectTrafficQosQueueResponseBody.d.ts +12 -12
  72. package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.d.ts +10 -6
  73. package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.js.map +1 -1
  74. package/dist/models/DescribeExpressConnectTrafficQosRuleResponseBody.d.ts +16 -16
  75. package/dist/models/DescribeFailoverTestJobRequest.d.ts +2 -2
  76. package/dist/models/DescribeFailoverTestJobResponseBody.d.ts +6 -6
  77. package/dist/models/DescribeFailoverTestJobsRequest.d.ts +8 -8
  78. package/dist/models/DescribeFailoverTestJobsResponseBody.d.ts +14 -14
  79. package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +3 -2
  80. package/dist/models/DescribePhysicalConnectionLoarequest.js.map +1 -1
  81. package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +14 -7
  82. package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
  83. package/dist/models/DescribePhysicalConnectionsRequest.d.ts +55 -0
  84. package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
  85. package/dist/models/DescribeRouterInterfaceAttributeResponseBody.d.ts +22 -22
  86. package/dist/models/DescribeRouterInterfacesRequest.d.ts +7 -7
  87. package/dist/models/DescribeRouterInterfacesResponseBody.d.ts +1 -1
  88. package/dist/models/DescribeSslVpnClientCertRequest.d.ts +1 -1
  89. package/dist/models/DescribeSslVpnClientCertResponseBody.d.ts +3 -3
  90. package/dist/models/DescribeSslVpnServersRequest.d.ts +1 -1
  91. package/dist/models/DescribeSslVpnServersResponseBody.d.ts +1 -1
  92. package/dist/models/DescribeTagKeysForExpressConnectRequest.d.ts +2 -0
  93. package/dist/models/DescribeTagKeysForExpressConnectRequest.js.map +1 -1
  94. package/dist/models/DescribeVbrHaRequest.d.ts +6 -6
  95. package/dist/models/DescribeVbrHaResponseBody.d.ts +2 -2
  96. package/dist/models/DescribeVcoRouteEntriesResponseBody.d.ts +10 -10
  97. package/dist/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.d.ts +3 -3
  98. package/dist/models/DescribeVirtualBorderRoutersRequest.d.ts +6 -26
  99. package/dist/models/DescribeVirtualBorderRoutersRequest.js.map +1 -1
  100. package/dist/models/DescribeVirtualBorderRoutersResponseBody.d.ts +2 -2
  101. package/dist/models/DescribeVpcGrantRulesToEcrRequest.d.ts +7 -7
  102. package/dist/models/DescribeVpcGrantRulesToEcrResponseBody.d.ts +8 -8
  103. package/dist/models/DescribeVpcsRequest.d.ts +7 -7
  104. package/dist/models/DescribeVpnAttachmentsRequest.d.ts +4 -4
  105. package/dist/models/DescribeVpnAttachmentsResponseBody.d.ts +9 -9
  106. package/dist/models/DescribeVpnConnectionLogsRequest.d.ts +2 -2
  107. package/dist/models/DescribeVpnConnectionLogsResponseBody.d.ts +1 -1
  108. package/dist/models/DescribeVpnConnectionRequest.d.ts +1 -1
  109. package/dist/models/DescribeVpnConnectionResponseBody.d.ts +21 -72
  110. package/dist/models/DescribeVpnConnectionResponseBody.js.map +1 -1
  111. package/dist/models/DescribeVpnConnectionsRequest.d.ts +6 -8
  112. package/dist/models/DescribeVpnConnectionsRequest.js.map +1 -1
  113. package/dist/models/DescribeVpnCrossAccountAuthorizationsRequest.d.ts +2 -2
  114. package/dist/models/DescribeVpnCrossAccountAuthorizationsResponseBody.d.ts +5 -5
  115. package/dist/models/DescribeVpnGatewayResponseBody.d.ts +8 -8
  116. package/dist/models/DescribeVpnGatewaysRequest.d.ts +2 -2
  117. package/dist/models/DescribeVpnGatewaysResponseBody.d.ts +1 -1
  118. package/dist/models/DescribeVpnPbrRouteEntriesRequest.d.ts +1 -1
  119. package/dist/models/DescribeVpnPbrRouteEntriesResponseBody.d.ts +1 -1
  120. package/dist/models/DescribeVpnSslServerLogsRequest.d.ts +2 -2
  121. package/dist/models/DescribeVswitchesRequest.d.ts +7 -7
  122. package/dist/models/DescribeVswitchesResponseBody.d.ts +1 -1
  123. package/dist/models/DiagnoseVpnGatewayRequest.d.ts +1 -1
  124. package/dist/models/DiagnoseVpnGatewayResponseBody.d.ts +2 -2
  125. package/dist/models/DisassociateMacSecKeyRequest.d.ts +2 -2
  126. package/dist/models/DissociateVpnGatewayWithCertificateRequest.d.ts +2 -2
  127. package/dist/models/DownloadVpnConnectionConfigResponseBody.d.ts +11 -11
  128. package/dist/models/EnablePhysicalConnectionRequest.d.ts +5 -7
  129. package/dist/models/EnablePhysicalConnectionRequest.js.map +1 -1
  130. package/dist/models/GetNatGatewayAttributeRequest.d.ts +1 -1
  131. package/dist/models/GetNatGatewayAttributeResponseBody.d.ts +20 -20
  132. package/dist/models/GetVpnGatewayDiagnoseResultRequest.d.ts +3 -3
  133. package/dist/models/GetVpnGatewayDiagnoseResultResponseBody.d.ts +12 -12
  134. package/dist/models/GrantInstanceToVbrRequest.d.ts +6 -6
  135. package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +6 -6
  136. package/dist/models/ListBusinessAccessPointsResponseBody.d.ts +40 -2
  137. package/dist/models/ListBusinessAccessPointsResponseBody.js.map +1 -1
  138. package/dist/models/ListIpsecServerLogsRequest.d.ts +2 -2
  139. package/dist/models/ListIpsecServerLogsResponseBody.d.ts +1 -1
  140. package/dist/models/ListIpsecServersRequest.d.ts +3 -3
  141. package/dist/models/ListIpsecServersResponseBody.d.ts +7 -7
  142. package/dist/models/ListVirtualPhysicalConnectionsRequest.d.ts +7 -7
  143. package/dist/models/ListVirtualPhysicalConnectionsResponseBody.d.ts +20 -20
  144. package/dist/models/ListVpnCertificateAssociationsRequest.d.ts +3 -3
  145. package/dist/models/ListVpnCertificateAssociationsResponseBody.d.ts +2 -2
  146. package/dist/models/ModifyCustomerGatewayAttributeRequest.d.ts +1 -1
  147. package/dist/models/ModifyPhysicalConnectionAttributeRequest.d.ts +10 -3
  148. package/dist/models/ModifyPhysicalConnectionAttributeRequest.js.map +1 -1
  149. package/dist/models/ModifySslVpnServerRequest.d.ts +11 -11
  150. package/dist/models/ModifySslVpnServerResponseBody.d.ts +1 -1
  151. package/dist/models/ModifyVcoRouteEntryWeightRequest.d.ts +4 -4
  152. package/dist/models/ModifyVpcAttributeRequest.d.ts +4 -4
  153. package/dist/models/ModifyVpcCidrBlockRequest.d.ts +78 -0
  154. package/dist/models/ModifyVpcCidrBlockRequest.js +68 -0
  155. package/dist/models/ModifyVpcCidrBlockRequest.js.map +1 -0
  156. package/dist/models/ModifyVpcCidrBlockResponse.d.ts +19 -0
  157. package/dist/models/ModifyVpcCidrBlockResponse.js +69 -0
  158. package/dist/models/ModifyVpcCidrBlockResponse.js.map +1 -0
  159. package/dist/models/ModifyVpcCidrBlockResponseBody.d.ts +21 -0
  160. package/dist/models/ModifyVpcCidrBlockResponseBody.js +58 -0
  161. package/dist/models/ModifyVpcCidrBlockResponseBody.js.map +1 -0
  162. package/dist/models/ModifyVpnAttachmentAttributeRequest.d.ts +57 -133
  163. package/dist/models/ModifyVpnAttachmentAttributeRequest.js.map +1 -1
  164. package/dist/models/ModifyVpnAttachmentAttributeResponseBody.d.ts +54 -96
  165. package/dist/models/ModifyVpnAttachmentAttributeResponseBody.js.map +1 -1
  166. package/dist/models/ModifyVpnConnectionAttributeRequest.d.ts +77 -148
  167. package/dist/models/ModifyVpnConnectionAttributeRequest.js.map +1 -1
  168. package/dist/models/ModifyVpnConnectionAttributeResponseBody.d.ts +25 -52
  169. package/dist/models/ModifyVpnConnectionAttributeResponseBody.js.map +1 -1
  170. package/dist/models/ModifyVpnGatewayAttributeRequest.d.ts +5 -5
  171. package/dist/models/ModifyVpnPbrRouteEntryPriorityRequest.d.ts +5 -5
  172. package/dist/models/ModifyVpnRouteEntryWeightRequest.d.ts +2 -2
  173. package/dist/models/MoveResourceGroupRequest.d.ts +1 -1
  174. package/dist/models/MoveVpnResourceGroupRequest.d.ts +2 -2
  175. package/dist/models/ReleaseEipAddressRequest.d.ts +2 -2
  176. package/dist/models/UnassociateVpcCidrBlockRequest.d.ts +3 -3
  177. package/dist/models/UpdateDhcpOptionsSetAttributeRequest.d.ts +8 -8
  178. package/dist/models/UpdateIpsecServerRequest.d.ts +1 -1
  179. package/dist/models/UpdateIpv4gatewayAttributeRequest.d.ts +6 -6
  180. package/dist/models/model.d.ts +3 -0
  181. package/dist/models/model.js +11 -5
  182. package/dist/models/model.js.map +1 -1
  183. package/package.json +1 -1
  184. package/src/client.ts +488 -341
  185. package/src/models/ActivateRouterInterfaceRequest.ts +3 -2
  186. package/src/models/AllocateEipAddressRequest.ts +14 -14
  187. package/src/models/AssociateMacSecKeyRequest.ts +3 -3
  188. package/src/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.ts +5 -7
  189. package/src/models/AssociateVpcCidrBlockRequest.ts +5 -5
  190. package/src/models/AssociateVpcCidrBlockResponseBody.ts +1 -1
  191. package/src/models/AssociateVpnGatewayWithCertificateRequest.ts +3 -3
  192. package/src/models/AttachDhcpOptionsSetToVpcRequest.ts +2 -2
  193. package/src/models/AttachVbrToVpconnRequest.ts +8 -6
  194. package/src/models/AttachVbrToVpconnResponseBody.ts +1 -1
  195. package/src/models/CancelPhysicalConnectionRequest.ts +1 -1
  196. package/src/models/CheckVpnBgpEnabledRequest.ts +1 -1
  197. package/src/models/CompletePhysicalConnectionLoarequest.ts +10 -10
  198. package/src/models/ConnectRouterInterfaceRequest.ts +1 -1
  199. package/src/models/CreateCustomerGatewayRequest.ts +4 -4
  200. package/src/models/CreateCustomerGatewayResponseBody.ts +1 -1
  201. package/src/models/CreateEnhancedVpnGatewayRequest.ts +3 -3
  202. package/src/models/CreateFailoverTestJobRequest.ts +11 -11
  203. package/src/models/CreateFailoverTestJobResponseBody.ts +1 -1
  204. package/src/models/CreateIpsecServerRequest.ts +2 -2
  205. package/src/models/CreatePhysicalConnectionRequest.ts +13 -11
  206. package/src/models/CreatePhysicalConnectionSetupOrderRequest.ts +10 -8
  207. package/src/models/CreateRouteTargetGroupRequest.ts +3 -3
  208. package/src/models/CreateSslVpnServerRequest.ts +11 -11
  209. package/src/models/CreateVbrHaRequest.ts +5 -5
  210. package/src/models/CreateVbrHaResponseBody.ts +1 -1
  211. package/src/models/CreateVcoRouteEntryRequest.ts +2 -2
  212. package/src/models/CreateVcoRouteEntryResponseBody.ts +1 -1
  213. package/src/models/CreateVirtualPhysicalConnectionRequest.ts +9 -9
  214. package/src/models/CreateVpconnFromVbrRequest.ts +2 -2
  215. package/src/models/CreateVpnAttachmentRequest.ts +75 -135
  216. package/src/models/CreateVpnAttachmentResponseBody.ts +3 -3
  217. package/src/models/CreateVpnConnectionRequest.ts +99 -135
  218. package/src/models/CreateVpnConnectionResponseBody.ts +1 -1
  219. package/src/models/CreateVpnGatewayRequest.ts +17 -17
  220. package/src/models/CreateVpnGatewayResponseBody.ts +2 -2
  221. package/src/models/CreateVpnPbrRouteEntryRequest.ts +13 -13
  222. package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +6 -6
  223. package/src/models/CreateVswitchCidrReservationRequest.ts +17 -7
  224. package/src/models/CreateVswitchRequest.ts +9 -9
  225. package/src/models/DeleteBgpGroupRequest.ts +2 -2
  226. package/src/models/DeleteBgpNetworkRequest.ts +4 -4
  227. package/src/models/DeleteFailoverTestJobRequest.ts +4 -4
  228. package/src/models/DeleteIpsecServerRequest.ts +4 -4
  229. package/src/models/DeleteNatGatewayRequest.ts +4 -4
  230. package/src/models/DeletePublicIpAddressPoolCidrBlockRequest.ts +3 -3
  231. package/src/models/DeleteRouteEntriesRequest.ts +2 -2
  232. package/src/models/DeleteRouteEntriesResponseBody.ts +2 -2
  233. package/src/models/DeleteVbrHaRequest.ts +3 -3
  234. package/src/models/DeleteVpnGatewayRequest.ts +3 -3
  235. package/src/models/DeleteVpnRouteEntryRequest.ts +2 -2
  236. package/src/models/DescribeCustomerGatewayRequest.ts +1 -1
  237. package/src/models/DescribeCustomerGatewayResponseBody.ts +2 -2
  238. package/src/models/DescribeCustomerGatewaysRequest.ts +1 -1
  239. package/src/models/DescribeEipAddressesRequest.ts +8 -76
  240. package/src/models/DescribeExpressConnectTrafficQosQueueRequest.ts +5 -3
  241. package/src/models/DescribeExpressConnectTrafficQosQueueResponseBody.ts +12 -12
  242. package/src/models/DescribeExpressConnectTrafficQosRuleRequest.ts +10 -6
  243. package/src/models/DescribeExpressConnectTrafficQosRuleResponseBody.ts +16 -16
  244. package/src/models/DescribeFailoverTestJobRequest.ts +2 -2
  245. package/src/models/DescribeFailoverTestJobResponseBody.ts +6 -6
  246. package/src/models/DescribeFailoverTestJobsRequest.ts +8 -8
  247. package/src/models/DescribeFailoverTestJobsResponseBody.ts +14 -14
  248. package/src/models/DescribePhysicalConnectionLoarequest.ts +3 -2
  249. package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +14 -7
  250. package/src/models/DescribePhysicalConnectionsRequest.ts +56 -1
  251. package/src/models/DescribeRouterInterfaceAttributeResponseBody.ts +22 -22
  252. package/src/models/DescribeRouterInterfacesRequest.ts +7 -7
  253. package/src/models/DescribeRouterInterfacesResponseBody.ts +1 -1
  254. package/src/models/DescribeSslVpnClientCertRequest.ts +1 -1
  255. package/src/models/DescribeSslVpnClientCertResponseBody.ts +3 -3
  256. package/src/models/DescribeSslVpnServersRequest.ts +1 -1
  257. package/src/models/DescribeSslVpnServersResponseBody.ts +1 -1
  258. package/src/models/DescribeTagKeysForExpressConnectRequest.ts +2 -0
  259. package/src/models/DescribeVbrHaRequest.ts +6 -6
  260. package/src/models/DescribeVbrHaResponseBody.ts +2 -2
  261. package/src/models/DescribeVcoRouteEntriesResponseBody.ts +10 -10
  262. package/src/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.ts +3 -3
  263. package/src/models/DescribeVirtualBorderRoutersRequest.ts +6 -26
  264. package/src/models/DescribeVirtualBorderRoutersResponseBody.ts +2 -2
  265. package/src/models/DescribeVpcGrantRulesToEcrRequest.ts +7 -7
  266. package/src/models/DescribeVpcGrantRulesToEcrResponseBody.ts +8 -8
  267. package/src/models/DescribeVpcsRequest.ts +7 -7
  268. package/src/models/DescribeVpnAttachmentsRequest.ts +4 -4
  269. package/src/models/DescribeVpnAttachmentsResponseBody.ts +9 -9
  270. package/src/models/DescribeVpnConnectionLogsRequest.ts +2 -2
  271. package/src/models/DescribeVpnConnectionLogsResponseBody.ts +1 -1
  272. package/src/models/DescribeVpnConnectionRequest.ts +2 -2
  273. package/src/models/DescribeVpnConnectionResponseBody.ts +21 -72
  274. package/src/models/DescribeVpnConnectionsRequest.ts +7 -9
  275. package/src/models/DescribeVpnCrossAccountAuthorizationsRequest.ts +2 -2
  276. package/src/models/DescribeVpnCrossAccountAuthorizationsResponseBody.ts +5 -5
  277. package/src/models/DescribeVpnGatewayResponseBody.ts +8 -8
  278. package/src/models/DescribeVpnGatewaysRequest.ts +2 -2
  279. package/src/models/DescribeVpnGatewaysResponseBody.ts +1 -1
  280. package/src/models/DescribeVpnPbrRouteEntriesRequest.ts +1 -1
  281. package/src/models/DescribeVpnPbrRouteEntriesResponseBody.ts +1 -1
  282. package/src/models/DescribeVpnSslServerLogsRequest.ts +2 -2
  283. package/src/models/DescribeVswitchesRequest.ts +7 -7
  284. package/src/models/DescribeVswitchesResponseBody.ts +1 -1
  285. package/src/models/DiagnoseVpnGatewayRequest.ts +1 -1
  286. package/src/models/DiagnoseVpnGatewayResponseBody.ts +2 -2
  287. package/src/models/DisassociateMacSecKeyRequest.ts +2 -2
  288. package/src/models/DissociateVpnGatewayWithCertificateRequest.ts +2 -2
  289. package/src/models/DownloadVpnConnectionConfigResponseBody.ts +11 -11
  290. package/src/models/EnablePhysicalConnectionRequest.ts +5 -7
  291. package/src/models/GetNatGatewayAttributeRequest.ts +1 -1
  292. package/src/models/GetNatGatewayAttributeResponseBody.ts +20 -20
  293. package/src/models/GetVpnGatewayDiagnoseResultRequest.ts +3 -3
  294. package/src/models/GetVpnGatewayDiagnoseResultResponseBody.ts +12 -12
  295. package/src/models/GrantInstanceToVbrRequest.ts +6 -6
  296. package/src/models/GrantInstanceToVbrShrinkRequest.ts +6 -6
  297. package/src/models/ListBusinessAccessPointsResponseBody.ts +40 -2
  298. package/src/models/ListIpsecServerLogsRequest.ts +2 -2
  299. package/src/models/ListIpsecServerLogsResponseBody.ts +1 -1
  300. package/src/models/ListIpsecServersRequest.ts +3 -3
  301. package/src/models/ListIpsecServersResponseBody.ts +7 -7
  302. package/src/models/ListVirtualPhysicalConnectionsRequest.ts +7 -7
  303. package/src/models/ListVirtualPhysicalConnectionsResponseBody.ts +20 -20
  304. package/src/models/ListVpnCertificateAssociationsRequest.ts +3 -3
  305. package/src/models/ListVpnCertificateAssociationsResponseBody.ts +2 -2
  306. package/src/models/ModifyCustomerGatewayAttributeRequest.ts +1 -1
  307. package/src/models/ModifyPhysicalConnectionAttributeRequest.ts +10 -3
  308. package/src/models/ModifySslVpnServerRequest.ts +11 -11
  309. package/src/models/ModifySslVpnServerResponseBody.ts +1 -1
  310. package/src/models/ModifyVcoRouteEntryWeightRequest.ts +4 -4
  311. package/src/models/ModifyVpcAttributeRequest.ts +4 -4
  312. package/src/models/ModifyVpcCidrBlockRequest.ts +101 -0
  313. package/src/models/ModifyVpcCidrBlockResponse.ts +40 -0
  314. package/src/models/ModifyVpcCidrBlockResponseBody.ts +34 -0
  315. package/src/models/ModifyVpnAttachmentAttributeRequest.ts +57 -133
  316. package/src/models/ModifyVpnAttachmentAttributeResponseBody.ts +55 -97
  317. package/src/models/ModifyVpnConnectionAttributeRequest.ts +84 -155
  318. package/src/models/ModifyVpnConnectionAttributeResponseBody.ts +26 -53
  319. package/src/models/ModifyVpnGatewayAttributeRequest.ts +5 -5
  320. package/src/models/ModifyVpnPbrRouteEntryPriorityRequest.ts +5 -5
  321. package/src/models/ModifyVpnRouteEntryWeightRequest.ts +2 -2
  322. package/src/models/MoveResourceGroupRequest.ts +1 -1
  323. package/src/models/MoveVpnResourceGroupRequest.ts +2 -2
  324. package/src/models/ReleaseEipAddressRequest.ts +2 -2
  325. package/src/models/UnassociateVpcCidrBlockRequest.ts +3 -3
  326. package/src/models/UpdateDhcpOptionsSetAttributeRequest.ts +8 -8
  327. package/src/models/UpdateIpsecServerRequest.ts +1 -1
  328. package/src/models/UpdateIpv4gatewayAttributeRequest.ts +6 -6
  329. package/src/models/model.ts +3 -0
package/dist/client.js CHANGED
@@ -86,41 +86,42 @@ class Client extends openapi_core_1.default {
86
86
  'cn-zhengzhou-nebula-1': "vpc-nebula.cn-qingdao-nebula.aliyuncs.com",
87
87
  'eu-west-1-oxs': "vpc-nebula.cn-shenzhen-cloudstone.aliyuncs.com",
88
88
  'rus-west-1-pop': "vpc.aliyuncs.com",
89
- 'us-west-1': "vpc.us-west-1.aliyuncs.com",
90
- 'us-southeast-1': "vpc.us-southeast-1.aliyuncs.com",
91
- 'us-east-1': "vpc.us-east-1.aliyuncs.com",
92
- 'na-south-1': "vpc.na-south-1.aliyuncs.com",
93
- 'me-east-1': "vpc.me-east-1.aliyuncs.com",
94
- 'me-central-1': "vpc.me-central-1.aliyuncs.com",
95
- 'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
96
- 'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
97
- 'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
98
- 'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
89
+ 'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
90
+ 'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
99
91
  'cn-zhangjiakou': "vpc.cn-zhangjiakou.aliyuncs.com",
100
- 'cn-wulanchabu-gic-1': "vpc.cn-wulanchabu-gic-1.aliyuncs.com",
92
+ 'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
93
+ 'ap-northeast-1': "vpc.ap-northeast-1.aliyuncs.com",
94
+ 'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
95
+ 'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
96
+ 'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
97
+ 'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
98
+ 'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
99
+ 'ap-southeast-8': "vpc.ap-southeast-8.aliyuncs.com",
100
+ 'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
101
101
  'cn-wulanchabu': "vpc.cn-wulanchabu.aliyuncs.com",
102
+ 'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
102
103
  'cn-wuhan-lr': "vpc.cn-wuhan-lr.aliyuncs.com",
103
- 'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
104
104
  'cn-shanghai': "vpc.cn-shanghai.aliyuncs.com",
105
- 'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
106
- 'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
107
- 'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
108
105
  'cn-hongkong': "vpc.cn-hongkong.aliyuncs.com",
109
- 'cn-heyuan-acdr-1': "vpc.cn-heyuan-acdr-1.aliyuncs.com",
110
- 'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
111
- 'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
106
+ 'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
107
+ 'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
112
108
  'cn-fuzhou': "vpc.cn-fuzhou.aliyuncs.com",
113
109
  'cn-chengdu': "vpc.cn-chengdu.aliyuncs.com",
110
+ 'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
111
+ 'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
112
+ 'us-southeast-1': "vpc.us-southeast-1.aliyuncs.com",
113
+ 'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
114
+ 'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
115
+ 'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
116
+ 'us-east-1': "vpc.us-east-1.aliyuncs.com",
117
+ 'sa-east-1': "vpc.sa-east-1.aliyuncs.com",
118
+ 'us-west-1': "vpc.us-west-1.aliyuncs.com",
119
+ 'na-south-1': "vpc.na-south-1.aliyuncs.com",
120
+ 'me-east-1': "vpc.me-east-1.aliyuncs.com",
121
+ 'me-central-1': "vpc.me-central-1.aliyuncs.com",
114
122
  'cn-beijing-finance-1': "vpc.cn-beijing-finance-1.aliyuncs.com",
115
- 'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
116
- 'ap-southeast-8': "vpc.ap-southeast-8.aliyuncs.com",
117
- 'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
118
- 'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
119
- 'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
120
- 'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
121
- 'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
122
- 'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
123
- 'ap-northeast-1': "vpc.ap-northeast-1.aliyuncs.com",
123
+ 'cn-heyuan-acdr-1': "vpc.cn-heyuan-acdr-1.aliyuncs.com",
124
+ 'cn-wulanchabu-gic-1': "vpc.cn-wulanchabu-gic-1.aliyuncs.com",
124
125
  };
125
126
  this.checkConfig(config);
126
127
  this._endpoint = this.getEndpoint("vpc", this._regionId, this._endpointRule, this._network, this._suffix, this._endpointMap, this._endpoint);
@@ -138,7 +139,8 @@ class Client extends openapi_core_1.default {
138
139
  * Activates a router interface that is in the Inactive state.
139
140
  *
140
141
  * @remarks
141
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the router interface is activated, it enters the **Active** state.
142
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
143
+ * Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
142
144
  * > You cannot activate a router interface that has an overdue payment.
143
145
  *
144
146
  * @param request - ActivateRouterInterfaceRequest
@@ -183,7 +185,8 @@ class Client extends openapi_core_1.default {
183
185
  * Activates a router interface that is in the Inactive state.
184
186
  *
185
187
  * @remarks
186
- * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the router interface is activated, it enters the **Active** state.
188
+ * After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
189
+ * Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
187
190
  * > You cannot activate a router interface that has an overdue payment.
188
191
  *
189
192
  * @param request - ActivateRouterInterfaceRequest
@@ -776,8 +779,8 @@ class Client extends openapi_core_1.default {
776
779
  * Applies for an elastic IP address (EIP).
777
780
  *
778
781
  * @remarks
779
- * Before you call this operation, make sure that you fully understand the billing methods and pricing of EIPs. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
780
- * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. EIPs do not support IGMP or SCTP.
782
+ * Make sure that you are familiar with the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
783
+ * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. IGMP and SCTP are not supported.
781
784
  *
782
785
  * @param request - AllocateEipAddressRequest
783
786
  * @param runtime - runtime options for this request RuntimeOptions
@@ -878,8 +881,8 @@ class Client extends openapi_core_1.default {
878
881
  * Applies for an elastic IP address (EIP).
879
882
  *
880
883
  * @remarks
881
- * Before you call this operation, make sure that you fully understand the billing methods and pricing of EIPs. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
882
- * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. EIPs do not support IGMP or SCTP.
884
+ * Make sure that you are familiar with the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
885
+ * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. IGMP and SCTP are not supported.
883
886
  *
884
887
  * @param request - AllocateEipAddressRequest
885
888
  * @returns AllocateEipAddressResponse
@@ -1678,7 +1681,7 @@ class Client extends openapi_core_1.default {
1678
1681
  return await this.associateHaVipWithOptions(request, runtime);
1679
1682
  }
1680
1683
  /**
1681
- * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fiber or Ethernet) to cover all traffic from sender to receiver.
1684
+ * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fibers or Ethernet) to cover all traffic from the sender to the receiver.
1682
1685
  *
1683
1686
  * @remarks
1684
1687
  * To use this feature, the following conditions must be met:
@@ -1687,7 +1690,7 @@ class Client extends openapi_core_1.default {
1687
1690
  * - Only dedicated Express Connect circuits are supported.
1688
1691
  * Other notes:
1689
1692
  * - A maximum of three CKN and CAK pairs can be configured.
1690
- * - Associating a key that is currently in the Disassociated state cancels the previously associated key.
1693
+ * - Associating a key that is currently in the Disassociated state disassociates the previously active key.
1691
1694
  * - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
1692
1695
  *
1693
1696
  * @param request - AssociateMacSecKeyRequest
@@ -1729,7 +1732,7 @@ class Client extends openapi_core_1.default {
1729
1732
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.AssociateMacSecKeyResponse({}));
1730
1733
  }
1731
1734
  /**
1732
- * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fiber or Ethernet) to cover all traffic from sender to receiver.
1735
+ * Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fibers or Ethernet) to cover all traffic from the sender to the receiver.
1733
1736
  *
1734
1737
  * @remarks
1735
1738
  * To use this feature, the following conditions must be met:
@@ -1738,7 +1741,7 @@ class Client extends openapi_core_1.default {
1738
1741
  * - Only dedicated Express Connect circuits are supported.
1739
1742
  * Other notes:
1740
1743
  * - A maximum of three CKN and CAK pairs can be configured.
1741
- * - Associating a key that is currently in the Disassociated state cancels the previously associated key.
1744
+ * - Associating a key that is currently in the Disassociated state disassociates the previously active key.
1742
1745
  * - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
1743
1746
  *
1744
1747
  * @param request - AssociateMacSecKeyRequest
@@ -2238,18 +2241,18 @@ class Client extends openapi_core_1.default {
2238
2241
  * Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
2239
2242
  *
2240
2243
  * @remarks
2241
- * Before you attach a VPN gateway to an SSL certificate, take note of the following information:
2242
- * - Only Chinese SM VPN gateways support SSL certificate attachment. You must attach two SSL certificates to a Chinese SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2243
- * - The SSL certificates must use Chinese SM algorithms.
2244
+ * Before you associate a VPN gateway with an SSL certificate, take note of the following information:
2245
+ * - Only ShangMi (SM) VPN gateways support SSL certificate binding. You must attach two SSL certificates to an SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2246
+ * - The SSL certificates must use SM algorithms.
2244
2247
  * - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
2245
2248
  * <props="china">
2246
- * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2247
- * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The attachment node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the attachment status of the SSL certificate:
2249
+ * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy named AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2250
+ * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The binding node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the binding status of the SSL certificate:
2248
2251
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
2249
2252
  * - If the VPN gateway is in the **active** state, the SSL certificate is attached.
2250
- * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate attachment for the same VPN gateway.
2253
+ * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
2251
2254
  * ### Before you begin
2252
- * Make sure that you have two SSL certificates that use Chinese SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2255
+ * Make sure that you have two SSL certificates that use SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2253
2256
  *
2254
2257
  * @param request - AssociateVpnGatewayWithCertificateRequest
2255
2258
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2296,18 +2299,18 @@ class Client extends openapi_core_1.default {
2296
2299
  * Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
2297
2300
  *
2298
2301
  * @remarks
2299
- * Before you attach a VPN gateway to an SSL certificate, take note of the following information:
2300
- * - Only Chinese SM VPN gateways support SSL certificate attachment. You must attach two SSL certificates to a Chinese SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2301
- * - The SSL certificates must use Chinese SM algorithms.
2302
+ * Before you associate a VPN gateway with an SSL certificate, take note of the following information:
2303
+ * - Only ShangMi (SM) VPN gateways support SSL certificate binding. You must attach two SSL certificates to an SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
2304
+ * - The SSL certificates must use SM algorithms.
2302
2305
  * - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
2303
2306
  * <props="china">
2304
- * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2305
- * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The attachment node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the attachment status of the SSL certificate:
2307
+ * - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy named AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
2308
+ * - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The binding node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the binding status of the SSL certificate:
2306
2309
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
2307
2310
  * - If the VPN gateway is in the **active** state, the SSL certificate is attached.
2308
- * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate attachment for the same VPN gateway.
2311
+ * - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
2309
2312
  * ### Before you begin
2310
- * Make sure that you have two SSL certificates that use Chinese SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2313
+ * Make sure that you have two SSL certificates that use SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
2311
2314
  *
2312
2315
  * @param request - AssociateVpnGatewayWithCertificateRequest
2313
2316
  * @returns AssociateVpnGatewayWithCertificateResponse
@@ -2392,7 +2395,7 @@ class Client extends openapi_core_1.default {
2392
2395
  return await this.attachDhcpOptionsSetToVpcWithOptions(request, runtime);
2393
2396
  }
2394
2397
  /**
2395
- * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
2398
+ * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits. This API is used to migrate an existing VBR that was pushed cross-account to shared Express Connect circuits (shared port), completing the shared Express Connect circuits form transformation. Only the partner (Express Connect circuit owner) can call this operation.
2396
2399
  *
2397
2400
  * @param request - AttachVbrToVpconnRequest
2398
2401
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2433,7 +2436,7 @@ class Client extends openapi_core_1.default {
2433
2436
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.AttachVbrToVpconnResponse({}));
2434
2437
  }
2435
2438
  /**
2436
- * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
2439
+ * Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits. This API is used to migrate an existing VBR that was pushed cross-account to shared Express Connect circuits (shared port), completing the shared Express Connect circuits form transformation. Only the partner (Express Connect circuit owner) can call this operation.
2437
2440
  *
2438
2441
  * @param request - AttachVbrToVpconnRequest
2439
2442
  * @returns AttachVbrToVpconnResponse
@@ -2510,10 +2513,10 @@ class Client extends openapi_core_1.default {
2510
2513
  return await this.cancelCommonBandwidthPackageIpBandwidthWithOptions(request, runtime);
2511
2514
  }
2512
2515
  /**
2513
- * Cancels access to an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2516
+ * Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2514
2517
  *
2515
2518
  * @remarks
2516
- * You can cancel access only for Express Connect circuits in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not yet activated).
2519
+ * You can cancel the access of an Express Connect circuit only when it is in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not enabled). After an Express Connect circuit is created by calling CreatePhysicalConnection, it may briefly be in the **Allocating** state, during which it cannot be canceled. Poll the status by calling DescribePhysicalConnections and call this operation after the state changes to **Allocated**.
2517
2520
  *
2518
2521
  * @param request - CancelPhysicalConnectionRequest
2519
2522
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2560,10 +2563,10 @@ class Client extends openapi_core_1.default {
2560
2563
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CancelPhysicalConnectionResponse({}));
2561
2564
  }
2562
2565
  /**
2563
- * Cancels access to an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2566
+ * Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
2564
2567
  *
2565
2568
  * @remarks
2566
- * You can cancel access only for Express Connect circuits in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not yet activated).
2569
+ * You can cancel the access of an Express Connect circuit only when it is in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not enabled). After an Express Connect circuit is created by calling CreatePhysicalConnection, it may briefly be in the **Allocating** state, during which it cannot be canceled. Poll the status by calling DescribePhysicalConnections and call this operation after the state changes to **Allocated**.
2567
2570
  *
2568
2571
  * @param request - CancelPhysicalConnectionRequest
2569
2572
  * @returns CancelPhysicalConnectionResponse
@@ -2693,7 +2696,7 @@ class Client extends openapi_core_1.default {
2693
2696
  return await this.checkCanAllocateVpcPrivateIpAddressWithOptions(request, runtime);
2694
2697
  }
2695
2698
  /**
2696
- * Calls the CheckVpnBgpEnabled operation to query whether the region of an IPsec-VPN connection supports the BGP feature.
2699
+ * Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
2697
2700
  *
2698
2701
  * @param request - CheckVpnBgpEnabledRequest
2699
2702
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2734,7 +2737,7 @@ class Client extends openapi_core_1.default {
2734
2737
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CheckVpnBgpEnabledResponse({}));
2735
2738
  }
2736
2739
  /**
2737
- * Calls the CheckVpnBgpEnabled operation to query whether the region of an IPsec-VPN connection supports the BGP feature.
2740
+ * Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
2738
2741
  *
2739
2742
  * @param request - CheckVpnBgpEnabledRequest
2740
2743
  * @returns CheckVpnBgpEnabledResponse
@@ -2744,7 +2747,12 @@ class Client extends openapi_core_1.default {
2744
2747
  return await this.checkVpnBgpEnabledWithOptions(request, runtime);
2745
2748
  }
2746
2749
  /**
2747
- * Calls CompletePhysicalConnectionLOA to complete the construction.
2750
+ * Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
2751
+ *
2752
+ * @remarks
2753
+ * Calls the CompletePhysicalConnectionLOA operation to complete the construction. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. You can call this operation only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to reapply. After the construction is completed, the LOA status changes to **Complete**.
2754
+ * Complete call chain:
2755
+ * CreatePhysicalConnection → ApplyPhysicalConnectionLOA (LOA enters the Applying state) → Wait for approval (Available after approval; Rejected if denied, in which case call SecondApplyPhysicalConnectionLOA or ApplyPhysicalConnectionLOA again to reapply) → CompletePhysicalConnectionLOA (backfill completion information, LOA enters the Completing state) → ConfirmPhysicalConnection (confirm the Express Connect circuit, LOA enters the Complete state).
2748
2756
  *
2749
2757
  * @param request - CompletePhysicalConnectionLOARequest
2750
2758
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2809,7 +2817,12 @@ class Client extends openapi_core_1.default {
2809
2817
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CompletePhysicalConnectionLOAResponse({}));
2810
2818
  }
2811
2819
  /**
2812
- * Calls CompletePhysicalConnectionLOA to complete the construction.
2820
+ * Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
2821
+ *
2822
+ * @remarks
2823
+ * Calls the CompletePhysicalConnectionLOA operation to complete the construction. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. You can call this operation only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to reapply. After the construction is completed, the LOA status changes to **Complete**.
2824
+ * Complete call chain:
2825
+ * CreatePhysicalConnection → ApplyPhysicalConnectionLOA (LOA enters the Applying state) → Wait for approval (Available after approval; Rejected if denied, in which case call SecondApplyPhysicalConnectionLOA or ApplyPhysicalConnectionLOA again to reapply) → CompletePhysicalConnectionLOA (backfill completion information, LOA enters the Completing state) → ConfirmPhysicalConnection (confirm the Express Connect circuit, LOA enters the Complete state).
2813
2826
  *
2814
2827
  * @param request - CompletePhysicalConnectionLOARequest
2815
2828
  * @returns CompletePhysicalConnectionLOAResponse
@@ -2876,11 +2889,11 @@ class Client extends openapi_core_1.default {
2876
2889
  return await this.confirmPhysicalConnectionWithOptions(request, runtime);
2877
2890
  }
2878
2891
  /**
2879
- * Initiates a connection from the requester VPC router interface to the accepter.
2892
+ * Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
2880
2893
  *
2881
2894
  * @remarks
2882
- * After you call this operation, the router interface enters the **Connecting** state. After the connection is established, the router interface enters the **Active** state.
2883
- * When you call this operation to create a VPC, note the following items:
2895
+ * After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
2896
+ * When you invoke this operation to create a VPC, note the following items:
2884
2897
  * - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
2885
2898
  * - A maximum of one pair of interconnected router interfaces can exist between any two routers.
2886
2899
  * - If your account has a router interface with an overdue payment, you cannot initiate a connection.
@@ -2924,11 +2937,11 @@ class Client extends openapi_core_1.default {
2924
2937
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ConnectRouterInterfaceResponse({}));
2925
2938
  }
2926
2939
  /**
2927
- * Initiates a connection from the requester VPC router interface to the accepter.
2940
+ * Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
2928
2941
  *
2929
2942
  * @remarks
2930
- * After you call this operation, the router interface enters the **Connecting** state. After the connection is established, the router interface enters the **Active** state.
2931
- * When you call this operation to create a VPC, note the following items:
2943
+ * After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
2944
+ * When you invoke this operation to create a VPC, note the following items:
2932
2945
  * - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
2933
2946
  * - A maximum of one pair of interconnected router interfaces can exist between any two routers.
2934
2947
  * - If your account has a router interface with an overdue payment, you cannot initiate a connection.
@@ -4055,18 +4068,28 @@ class Client extends openapi_core_1.default {
4055
4068
  return await this.createExpressConnectTrafficQosRuleWithOptions(request, runtime);
4056
4069
  }
4057
4070
  /**
4058
- * Creates a failover test job for Express Connect.
4071
+ * Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
4059
4072
  *
4060
4073
  * @remarks
4061
- * You cannot create a failover test job in the following scenarios:
4062
- * - A failover test job is already running in the current region, and the job type of the new failover test job is set to StartNow.
4074
+ * Resource status requirements (prerequisites)
4075
+ * - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
4076
+ * - ResourceType set to PHYSICALCONNECTION: The Express Connect circuit (including shared Express Connect circuits) must be in the Enabled state with normal billing status (no overdue payment). Otherwise, IncorrectStatus.ResourceId or IncorrectBusinessStatus.ResourceId is returned.
4077
+ * - ResourceType set to VIRTUALBORDERROUTER: The VBR must be in the active state with no overdue payment, and the Express Connect circuit to which the VBR belongs must also be in the Enabled state with no overdue payment.
4078
+ * - ResourceType set to BGPPEER: The BGP peer must be in the Available state, the VBR to which it belongs must be in the active state, and the Express Connect circuit to which the VBR belongs must be in the Enabled state, all with no overdue payment.
4079
+ * How to check and advance the Express Connect circuit status
4080
+ * - Call DescribePhysicalConnections to query the Status field of the Express Connect circuit. If the circuit is not in the Enabled state (for example, it is in the Allocated or Confirmed state), advance it along the following state transition path:
4081
+ * - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
4082
+ * - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
4083
+ * - When JobType is set to StartLater, the status check described above is performed during the job creation phase. When you subsequently call StartFailoverTestJob to start the job, the resource status is checked again. If the resource status does not meet the requirements at that time (for example, the circuit is no longer in the Enabled state), the start operation fails.
4084
+ * The following scenarios do not support creating failover test jobs:
4085
+ * - A failover test job is already running in the current region, and the job type of the new failover test job is set to start immediately.
4063
4086
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4064
4087
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4065
4088
  *
4066
4089
  * - The Express Connect circuit instance has more than one shared Express Connect circuit.
4067
- * - The Express Connect circuit instance has more than one cross-account Virtual Border Router (VBR).
4090
+ * - The Express Connect circuit instance has more than one cross-account VBR.
4068
4091
  * - The shared Express Connect circuit instance is not associated with a VBR.
4069
- * - The VLAN of the shared Express Connect circuit instance is set to 0.
4092
+ * - The VLAN configuration of the shared Express Connect circuit instance is 0.
4070
4093
  *
4071
4094
  * @param request - CreateFailoverTestJobRequest
4072
4095
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4131,18 +4154,28 @@ class Client extends openapi_core_1.default {
4131
4154
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateFailoverTestJobResponse({}));
4132
4155
  }
4133
4156
  /**
4134
- * Creates a failover test job for Express Connect.
4157
+ * Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
4135
4158
  *
4136
4159
  * @remarks
4137
- * You cannot create a failover test job in the following scenarios:
4138
- * - A failover test job is already running in the current region, and the job type of the new failover test job is set to StartNow.
4160
+ * Resource status requirements (prerequisites)
4161
+ * - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
4162
+ * - ResourceType set to PHYSICALCONNECTION: The Express Connect circuit (including shared Express Connect circuits) must be in the Enabled state with normal billing status (no overdue payment). Otherwise, IncorrectStatus.ResourceId or IncorrectBusinessStatus.ResourceId is returned.
4163
+ * - ResourceType set to VIRTUALBORDERROUTER: The VBR must be in the active state with no overdue payment, and the Express Connect circuit to which the VBR belongs must also be in the Enabled state with no overdue payment.
4164
+ * - ResourceType set to BGPPEER: The BGP peer must be in the Available state, the VBR to which it belongs must be in the active state, and the Express Connect circuit to which the VBR belongs must be in the Enabled state, all with no overdue payment.
4165
+ * How to check and advance the Express Connect circuit status
4166
+ * - Call DescribePhysicalConnections to query the Status field of the Express Connect circuit. If the circuit is not in the Enabled state (for example, it is in the Allocated or Confirmed state), advance it along the following state transition path:
4167
+ * - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
4168
+ * - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
4169
+ * - When JobType is set to StartLater, the status check described above is performed during the job creation phase. When you subsequently call StartFailoverTestJob to start the job, the resource status is checked again. If the resource status does not meet the requirements at that time (for example, the circuit is no longer in the Enabled state), the start operation fails.
4170
+ * The following scenarios do not support creating failover test jobs:
4171
+ * - A failover test job is already running in the current region, and the job type of the new failover test job is set to start immediately.
4139
4172
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4140
4173
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4141
4174
  *
4142
4175
  * - The Express Connect circuit instance has more than one shared Express Connect circuit.
4143
- * - The Express Connect circuit instance has more than one cross-account Virtual Border Router (VBR).
4176
+ * - The Express Connect circuit instance has more than one cross-account VBR.
4144
4177
  * - The shared Express Connect circuit instance is not associated with a VBR.
4145
- * - The VLAN of the shared Express Connect circuit instance is set to 0.
4178
+ * - The VLAN configuration of the shared Express Connect circuit instance is 0.
4146
4179
  *
4147
4180
  * @param request - CreateFailoverTestJobRequest
4148
4181
  * @returns CreateFailoverTestJobResponse
@@ -6373,8 +6406,8 @@ class Client extends openapi_core_1.default {
6373
6406
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
6374
6407
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
6375
6408
  * - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
6376
- * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks pass.
6377
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
6409
+ * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
6410
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
6378
6411
  *
6379
6412
  * @param request - CreateRouteTargetGroupRequest
6380
6413
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6434,8 +6467,8 @@ class Client extends openapi_core_1.default {
6434
6467
  * - If the routing target group is in the **Pending** state, the routing target group is being created.
6435
6468
  * - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
6436
6469
  * - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
6437
- * - **Primary instance**: The weight is 100. The primary instance handles all traffic under normal conditions and takes effect when health checks pass.
6438
- * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic when the primary instance fails, serving as disaster recovery and backup.
6470
+ * - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
6471
+ * - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
6439
6472
  *
6440
6473
  * @param request - CreateRouteTargetGroupRequest
6441
6474
  * @returns CreateRouteTargetGroupResponse
@@ -6760,7 +6793,7 @@ class Client extends openapi_core_1.default {
6760
6793
  * Creates an SSL-VPN server.
6761
6794
  *
6762
6795
  * @remarks
6763
- * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
6796
+ * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task continues in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
6764
6797
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
6765
6798
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
6766
6799
  * - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
@@ -6855,7 +6888,7 @@ class Client extends openapi_core_1.default {
6855
6888
  * Creates an SSL-VPN server.
6856
6889
  *
6857
6890
  * @remarks
6858
- * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
6891
+ * - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task continues in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
6859
6892
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
6860
6893
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
6861
6894
  * - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
@@ -7140,18 +7173,18 @@ class Client extends openapi_core_1.default {
7140
7173
  * Creates a vSwitch.
7141
7174
  *
7142
7175
  * @remarks
7143
- * Before you begin:
7176
+ * When you call this operation to create a vSwitch, take note of the following items:
7144
7177
  * - The number of vSwitches in each VPC cannot exceed 150.
7145
- * - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
7178
+ * - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
7146
7179
  * - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
7147
7180
  * - A cloud service instance can belong to only one vSwitch.
7148
7181
  * - vSwitches do not support multicast or broadcast.
7149
7182
  * - After a vSwitch is created, you cannot modify its CIDR block.
7150
- * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID, but the vSwitch is not yet created. The background node is still in progress. You can invoke [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
7151
- * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
7152
- * - If the vSwitch is in the **Available** state, the vSwitch is active.
7183
+ * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID but the vSwitch is not yet created. The background task is still in progress. You can call [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
7184
+ * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
7185
+ * - When the vSwitch is in the **Available** state, the vSwitch is available.
7153
7186
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
7154
- * - The **CreateVSwitch** operation does not support creating vSwitches with the CIDR block 100.64.0.0/10 or its subnets.
7187
+ * - When you call the **CreateVSwitch** operation, the CIDR block of the vSwitch cannot be within the following reserved address ranges: 100.64.0.0/10, 127.0.0.0/8, 169.254.0.0/16, or 224.0.0.0/4.
7155
7188
  *
7156
7189
  * @param request - CreateVSwitchRequest
7157
7190
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7222,18 +7255,18 @@ class Client extends openapi_core_1.default {
7222
7255
  * Creates a vSwitch.
7223
7256
  *
7224
7257
  * @remarks
7225
- * Before you begin:
7258
+ * When you call this operation to create a vSwitch, take note of the following items:
7226
7259
  * - The number of vSwitches in each VPC cannot exceed 150.
7227
- * - The first and last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
7260
+ * - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
7228
7261
  * - The number of cloud service instances in a vSwitch cannot exceed the remaining available cloud service instances in the VPC (15,000 minus the current number of cloud service instances).
7229
7262
  * - A cloud service instance can belong to only one vSwitch.
7230
7263
  * - vSwitches do not support multicast or broadcast.
7231
7264
  * - After a vSwitch is created, you cannot modify its CIDR block.
7232
- * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID, but the vSwitch is not yet created. The background node is still in progress. You can invoke [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
7233
- * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
7234
- * - If the vSwitch is in the **Available** state, the vSwitch is active.
7265
+ * - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID but the vSwitch is not yet created. The background task is still in progress. You can call [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) to query the creation status of the vSwitch:
7266
+ * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
7267
+ * - When the vSwitch is in the **Available** state, the vSwitch is available.
7235
7268
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
7236
- * - The **CreateVSwitch** operation does not support creating vSwitches with the CIDR block 100.64.0.0/10 or its subnets.
7269
+ * - When you call the **CreateVSwitch** operation, the CIDR block of the vSwitch cannot be within the following reserved address ranges: 100.64.0.0/10, 127.0.0.0/8, 169.254.0.0/16, or 224.0.0.0/4.
7237
7270
  *
7238
7271
  * @param request - CreateVSwitchRequest
7239
7272
  * @returns CreateVSwitchResponse
@@ -7251,7 +7284,7 @@ class Client extends openapi_core_1.default {
7251
7284
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
7252
7285
  * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
7253
7286
  * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
7254
- * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The system continues to run the background node. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7287
+ * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The background node is still in progress. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7255
7288
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
7256
7289
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
7257
7290
  *
@@ -7268,6 +7301,9 @@ class Client extends openapi_core_1.default {
7268
7301
  if (!$dara.isNull(request.dryRun)) {
7269
7302
  query["DryRun"] = request.dryRun;
7270
7303
  }
7304
+ if (!$dara.isNull(request.ipPrefixNumber)) {
7305
+ query["IpPrefixNumber"] = request.ipPrefixNumber;
7306
+ }
7271
7307
  if (!$dara.isNull(request.ipVersion)) {
7272
7308
  query["IpVersion"] = request.ipVersion;
7273
7309
  }
@@ -7332,7 +7368,7 @@ class Client extends openapi_core_1.default {
7332
7368
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
7333
7369
  * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
7334
7370
  * - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
7335
- * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The system continues to run the background node. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7371
+ * - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The background node is still in progress. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
7336
7372
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
7337
7373
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
7338
7374
  *
@@ -7344,7 +7380,7 @@ class Client extends openapi_core_1.default {
7344
7380
  return await this.createVSwitchCidrReservationWithOptions(request, runtime);
7345
7381
  }
7346
7382
  /**
7347
- * Creates a VBR failover group by calling the CreateVbrHa operation.
7383
+ * Creates a VBR failover group.
7348
7384
  *
7349
7385
  * @param request - CreateVbrHaRequest
7350
7386
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7403,7 +7439,7 @@ class Client extends openapi_core_1.default {
7403
7439
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVbrHaResponse({}));
7404
7440
  }
7405
7441
  /**
7406
- * Creates a VBR failover group by calling the CreateVbrHa operation.
7442
+ * Creates a VBR failover group.
7407
7443
  *
7408
7444
  * @param request - CreateVbrHaRequest
7409
7445
  * @returns CreateVbrHaResponse
@@ -7418,11 +7454,11 @@ class Client extends openapi_core_1.default {
7418
7454
  * @remarks
7419
7455
  * - The IPsec-VPN connection must be associated with a transit router instance. For more information, see [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468249.html).
7420
7456
  * - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
7421
- * - Do not add a destination route with a destination CIDR block of 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
7457
+ * - Do not add a destination route whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
7422
7458
  * - **CreateVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns an instance ID but the destination route entry is not yet created. The creation task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the creation status of the destination route entry:
7423
7459
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
7424
7460
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
7425
- * - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
7461
+ * - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
7426
7462
  *
7427
7463
  * @param request - CreateVcoRouteEntryRequest
7428
7464
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7489,11 +7525,11 @@ class Client extends openapi_core_1.default {
7489
7525
  * @remarks
7490
7526
  * - The IPsec-VPN connection must be associated with a transit router instance. For more information, see [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468249.html).
7491
7527
  * - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
7492
- * - Do not add a destination route with a destination CIDR block of 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
7528
+ * - Do not add a destination route whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
7493
7529
  * - **CreateVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns an instance ID but the destination route entry is not yet created. The creation task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the creation status of the destination route entry:
7494
7530
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
7495
7531
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
7496
- * - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
7532
+ * - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
7497
7533
  *
7498
7534
  * @param request - CreateVcoRouteEntryRequest
7499
7535
  * @returns CreateVcoRouteEntryResponse
@@ -7614,7 +7650,18 @@ class Client extends openapi_core_1.default {
7614
7650
  * Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
7615
7651
  *
7616
7652
  * @remarks
7617
- * Before calling this operation, understand the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
7653
+ * Before you call this operation, familiarize yourself with the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
7654
+ * Before you call this operation, make sure the following conditions are met:
7655
+ * - The Express Connect circuit specified by PhysicalConnectionId is in the Enabled state. The complete process for an Express Connect circuit to reach the Enabled state includes payment and manual steps that cannot be fully automated through OpenAPI:
7656
+ * - CreatePhysicalConnection: Creates an Express Connect circuit.
7657
+ * - LOA construction authorization: If you need to enter the data center for construction, call ApplyPhysicalConnectionLOA → wait for manual LOA approval → CompletePhysicalConnectionLOA (FinishWork=true). LOA approval and construction are manual/offline steps.
7658
+ * - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
7659
+ * - After the Confirmed state, port usage fees must be paid before the circuit enters the Enabled state. For automation scenarios, call DescribePhysicalConnections first to confirm the target circuit is in the Enabled state before calling this operation.
7660
+ * - The VlanId is not already used by an existing VBR or shared Express Connect circuit on the Express Connect circuit (valid values: 0 to 2999).
7661
+ * - The Spec value does not exceed the remaining allocatable bandwidth of the Express Connect circuit or the shared circuit bandwidth limit configured for the account that owns the Express Connect circuit.
7662
+ * - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
7663
+ * - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
7664
+ * - The Express Connect circuit is not bound to a QoS policy, the access device supports MPBGP, and the access point allows the creation of shared Express Connect circuits.
7618
7665
  *
7619
7666
  * @param request - CreateVirtualPhysicalConnectionRequest
7620
7667
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7679,7 +7726,18 @@ class Client extends openapi_core_1.default {
7679
7726
  * Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
7680
7727
  *
7681
7728
  * @remarks
7682
- * Before calling this operation, understand the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
7729
+ * Before you call this operation, familiarize yourself with the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
7730
+ * Before you call this operation, make sure the following conditions are met:
7731
+ * - The Express Connect circuit specified by PhysicalConnectionId is in the Enabled state. The complete process for an Express Connect circuit to reach the Enabled state includes payment and manual steps that cannot be fully automated through OpenAPI:
7732
+ * - CreatePhysicalConnection: Creates an Express Connect circuit.
7733
+ * - LOA construction authorization: If you need to enter the data center for construction, call ApplyPhysicalConnectionLOA → wait for manual LOA approval → CompletePhysicalConnectionLOA (FinishWork=true). LOA approval and construction are manual/offline steps.
7734
+ * - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
7735
+ * - After the Confirmed state, port usage fees must be paid before the circuit enters the Enabled state. For automation scenarios, call DescribePhysicalConnections first to confirm the target circuit is in the Enabled state before calling this operation.
7736
+ * - The VlanId is not already used by an existing VBR or shared Express Connect circuit on the Express Connect circuit (valid values: 0 to 2999).
7737
+ * - The Spec value does not exceed the remaining allocatable bandwidth of the Express Connect circuit or the shared circuit bandwidth limit configured for the account that owns the Express Connect circuit.
7738
+ * - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
7739
+ * - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
7740
+ * - The Express Connect circuit is not bound to a QoS policy, the access device supports MPBGP, and the access point allows the creation of shared Express Connect circuits.
7683
7741
  *
7684
7742
  * @param request - CreateVirtualPhysicalConnectionRequest
7685
7743
  * @returns CreateVirtualPhysicalConnectionResponse
@@ -7990,13 +8048,13 @@ class Client extends openapi_core_1.default {
7990
8048
  return await this.createVpcPrefixListWithOptions(request, runtime);
7991
8049
  }
7992
8050
  /**
7993
- * Transforms the sharing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) routing push to cross-account shared port push.
8051
+ * Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
7994
8052
  *
7995
8053
  * @remarks
7996
- * By invoking the CreateVpconnFromVbr operation, a partner can transform the sharing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
7997
- * Before you execute the transform:
8054
+ * By invoking the CreateVpconnFromVbr operation, a partner can transform the routing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
8055
+ * Before you execute the transform procedure:
7998
8056
  * The partner must notify the tenant about the service upgrade in advance and ensure that the tenant has enabled outbound traffic billing. For information about how to enable outbound traffic billing, see [Enable outbound traffic billing](https://help.aliyun.com/document_detail/274385.html).
7999
- * After the transform is complete:
8057
+ * After the transform procedure is complete:
8000
8058
  * 1. A shared port is added to the tenant\\"s account. The tenant must invoke the [ConfirmPhysicalConnection](https://help.aliyun.com/document_detail/324198.html) operation to accept the shared port.
8001
8059
  * 2. After the tenant accepts the shared port, the partner must invoke the [AttachVbrToVpconn](https://help.aliyun.com/document_detail/324191.html) operation to associate the VBR instance with the tenant\\"s shared Express Connect circuits instance.
8002
8060
  *
@@ -8039,13 +8097,13 @@ class Client extends openapi_core_1.default {
8039
8097
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpconnFromVbrResponse({}));
8040
8098
  }
8041
8099
  /**
8042
- * Transforms the sharing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) routing push to cross-account shared port push.
8100
+ * Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
8043
8101
  *
8044
8102
  * @remarks
8045
- * By invoking the CreateVpconnFromVbr operation, a partner can transform the sharing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
8046
- * Before you execute the transform:
8103
+ * By invoking the CreateVpconnFromVbr operation, a partner can transform the routing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
8104
+ * Before you execute the transform procedure:
8047
8105
  * The partner must notify the tenant about the service upgrade in advance and ensure that the tenant has enabled outbound traffic billing. For information about how to enable outbound traffic billing, see [Enable outbound traffic billing](https://help.aliyun.com/document_detail/274385.html).
8048
- * After the transform is complete:
8106
+ * After the transform procedure is complete:
8049
8107
  * 1. A shared port is added to the tenant\\"s account. The tenant must invoke the [ConfirmPhysicalConnection](https://help.aliyun.com/document_detail/324198.html) operation to accept the shared port.
8050
8108
  * 2. After the tenant accepts the shared port, the partner must invoke the [AttachVbrToVpconn](https://help.aliyun.com/document_detail/324191.html) operation to associate the VBR instance with the tenant\\"s shared Express Connect circuits instance.
8051
8109
  *
@@ -8057,16 +8115,11 @@ class Client extends openapi_core_1.default {
8057
8115
  return await this.createVpconnFromVbrWithOptions(request, runtime);
8058
8116
  }
8059
8117
  /**
8060
- * Creates an IPsec-VPN connection for bindng to a transit router instance by calling the CreateVpnAttachment operation.
8118
+ * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
8061
8119
  *
8062
8120
  * @remarks
8063
8121
  * >Notice:
8064
- * - In the transit router binding scenario, IPsec-VPN connections have been upgraded to dual-tunnel mode. When you create an IPsec-VPN connection, in addition to the required request parameters, only the following dual-tunnel mode-related request parameters are supported: **ClientToken**, **Name**, **NetworkType**, **EffectImmediately**, **Tags** array, **ResourceGroupId**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**. For more information, see [Dual-tunnel IPsec-VPN connections bound to transit routers](https://help.aliyun.com/document_detail/2853535.html).
8065
- * - An IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not bound to any resource by default. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to bind the IPsec-VPN connection to a transit router instance. After the IPsec-VPN connection is bound to a transit router instance, the system allocates a gateway IP address to the IPsec-VPN connection. You can call the [DescribeVpnConnection](https://help.aliyun.com/document_detail/2526951.html) operation to view the gateway IP address.
8066
- * ### Before you begin
8067
- * Before you create an IPsec-VPN connection, make sure that you have created a customer gateway in the region where the IPsec-VPN connection resides. For more information, see [CreateCustomerGateway](https://help.aliyun.com/document_detail/120368.html).
8068
- *
8069
- * If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number has been added to the customer gateway.
8122
+ * ### Before you begin.
8070
8123
  *
8071
8124
  * @param request - CreateVpnAttachmentRequest
8072
8125
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8171,16 +8224,11 @@ class Client extends openapi_core_1.default {
8171
8224
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpnAttachmentResponse({}));
8172
8225
  }
8173
8226
  /**
8174
- * Creates an IPsec-VPN connection for bindng to a transit router instance by calling the CreateVpnAttachment operation.
8227
+ * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
8175
8228
  *
8176
8229
  * @remarks
8177
8230
  * >Notice:
8178
- * - In the transit router binding scenario, IPsec-VPN connections have been upgraded to dual-tunnel mode. When you create an IPsec-VPN connection, in addition to the required request parameters, only the following dual-tunnel mode-related request parameters are supported: **ClientToken**, **Name**, **NetworkType**, **EffectImmediately**, **Tags** array, **ResourceGroupId**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**. For more information, see [Dual-tunnel IPsec-VPN connections bound to transit routers](https://help.aliyun.com/document_detail/2853535.html).
8179
- * - An IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not bound to any resource by default. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to bind the IPsec-VPN connection to a transit router instance. After the IPsec-VPN connection is bound to a transit router instance, the system allocates a gateway IP address to the IPsec-VPN connection. You can call the [DescribeVpnConnection](https://help.aliyun.com/document_detail/2526951.html) operation to view the gateway IP address.
8180
- * ### Before you begin
8181
- * Before you create an IPsec-VPN connection, make sure that you have created a customer gateway in the region where the IPsec-VPN connection resides. For more information, see [CreateCustomerGateway](https://help.aliyun.com/document_detail/120368.html).
8182
- *
8183
- * If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number has been added to the customer gateway.
8231
+ * ### Before you begin.
8184
8232
  *
8185
8233
  * @param request - CreateVpnAttachmentRequest
8186
8234
  * @returns CreateVpnAttachmentResponse
@@ -8196,11 +8244,8 @@ class Client extends openapi_core_1.default {
8196
8244
  * - If the VPN gateway instance supports creating IPsec-VPN connections in dual-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
8197
8245
  * **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
8198
8246
  * For information about the regions and zones that support IPsec-VPN connections in dual-tunnel mode, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
8199
- * - If the VPN gateway instance supports only creating IPsec-VPN connections in single-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
8200
8247
  * **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
8201
- * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection:
8202
- * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
8203
- * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
8248
+ * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection.
8204
8249
  * - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
8205
8250
  *
8206
8251
  * @param request - CreateVpnConnectionRequest
@@ -8309,11 +8354,8 @@ class Client extends openapi_core_1.default {
8309
8354
  * - If the VPN gateway instance supports creating IPsec-VPN connections in dual-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
8310
8355
  * **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
8311
8356
  * For information about the regions and zones that support IPsec-VPN connections in dual-tunnel mode, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
8312
- * - If the VPN gateway instance supports only creating IPsec-VPN connections in single-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
8313
8357
  * **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
8314
- * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection:
8315
- * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
8316
- * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
8358
+ * - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection.
8317
8359
  * - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
8318
8360
  *
8319
8361
  * @param request - CreateVpnConnectionRequest
@@ -8327,8 +8369,8 @@ class Client extends openapi_core_1.default {
8327
8369
  * Creates a VPN gateway.
8328
8370
  *
8329
8371
  * @remarks
8330
- * - Before you create a VPN gateway, familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
8331
- * - VPN gateway instances in some regions support only dual-tunnel IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
8372
+ * - Before you create a VPN gateway, we recommend that you familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
8373
+ * - VPN gateway instances in some regions support only dual-tunnel mode IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel mode IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
8332
8374
  * - The **CreateVpnGateway** operation is asynchronous. After you call this operation, the system returns an instance ID, but the VPN gateway is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the VPN gateway:
8333
8375
  *
8334
8376
  * - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
@@ -8421,8 +8463,8 @@ class Client extends openapi_core_1.default {
8421
8463
  * Creates a VPN gateway.
8422
8464
  *
8423
8465
  * @remarks
8424
- * - Before you create a VPN gateway, familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
8425
- * - VPN gateway instances in some regions support only dual-tunnel IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
8466
+ * - Before you create a VPN gateway, we recommend that you familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
8467
+ * - VPN gateway instances in some regions support only dual-tunnel mode IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel mode IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
8426
8468
  * - The **CreateVpnGateway** operation is asynchronous. After you call this operation, the system returns an instance ID, but the VPN gateway is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the VPN gateway:
8427
8469
  *
8428
8470
  * - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
@@ -8436,18 +8478,18 @@ class Client extends openapi_core_1.default {
8436
8478
  return await this.createVpnGatewayWithOptions(request, runtime);
8437
8479
  }
8438
8480
  /**
8439
- * Creates a policy-based route for a VPN gateway by calling the CreateVpnPbrRouteEntry operation.
8481
+ * Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
8440
8482
  *
8441
8483
  * @remarks
8442
8484
  * ### Before you begin
8443
- * - Before creating a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
8444
- * - Before creating a policy-based route, we recommend that you understand the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
8485
+ * - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
8486
+ * - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
8445
8487
  * ### Limits
8446
- * - Adding a policy-based route whose destination CIDR block is 0.0.0.0/0 is not supported.
8447
- * - Do not add a policy-based route whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes cause the console to fail to display instance status of the IPsec-VPN connection or cause IPsec-VPN connection negotiation failures.
8448
- * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you call this operation, the system returns the information about the policy-based route, but the route has not been created yet. The system creates the route in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
8488
+ * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8489
+ * - Do not add policy-based routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes may cause the console to fail to display instance status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
8490
+ * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you invoke this operation, the system returns the information about the policy-based route, but the routing has not been created. The creation node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
8449
8491
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
8450
- * - If the VPN gateway instance is in the **active** state, the policy-based route has been created.
8492
+ * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
8451
8493
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
8452
8494
  *
8453
8495
  * @param request - CreateVpnPbrRouteEntryRequest
@@ -8522,18 +8564,18 @@ class Client extends openapi_core_1.default {
8522
8564
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpnPbrRouteEntryResponse({}));
8523
8565
  }
8524
8566
  /**
8525
- * Creates a policy-based route for a VPN gateway by calling the CreateVpnPbrRouteEntry operation.
8567
+ * Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
8526
8568
  *
8527
8569
  * @remarks
8528
8570
  * ### Before you begin
8529
- * - Before creating a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
8530
- * - Before creating a policy-based route, we recommend that you understand the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
8571
+ * - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
8572
+ * - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
8531
8573
  * ### Limits
8532
- * - Adding a policy-based route whose destination CIDR block is 0.0.0.0/0 is not supported.
8533
- * - Do not add a policy-based route whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes cause the console to fail to display instance status of the IPsec-VPN connection or cause IPsec-VPN connection negotiation failures.
8534
- * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you call this operation, the system returns the information about the policy-based route, but the route has not been created yet. The system creates the route in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
8574
+ * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8575
+ * - Do not add policy-based routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes may cause the console to fail to display instance status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
8576
+ * - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you invoke this operation, the system returns the information about the policy-based route, but the routing has not been created. The creation node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
8535
8577
  * - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
8536
- * - If the VPN gateway instance is in the **active** state, the policy-based route has been created.
8578
+ * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
8537
8579
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
8538
8580
  *
8539
8581
  * @param request - CreateVpnPbrRouteEntryRequest
@@ -8763,7 +8805,7 @@ class Client extends openapi_core_1.default {
8763
8805
  return await this.deactiveFlowLogWithOptions(request, runtime);
8764
8806
  }
8765
8807
  /**
8766
- * Deletes a specified Border Gateway Protocol (BGP) group.
8808
+ * Deletes a specified BGP group.
8767
8809
  *
8768
8810
  * @param request - DeleteBgpGroupRequest
8769
8811
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8810,7 +8852,7 @@ class Client extends openapi_core_1.default {
8810
8852
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteBgpGroupResponse({}));
8811
8853
  }
8812
8854
  /**
8813
- * Deletes a specified Border Gateway Protocol (BGP) group.
8855
+ * Deletes a specified BGP group.
8814
8856
  *
8815
8857
  * @param request - DeleteBgpGroupRequest
8816
8858
  * @returns DeleteBgpGroupResponse
@@ -8822,6 +8864,9 @@ class Client extends openapi_core_1.default {
8822
8864
  /**
8823
8865
  * Deletes an advertised Border Gateway Protocol (BGP) network.
8824
8866
  *
8867
+ * @remarks
8868
+ * Before calling this operation, ensure that the BgpNetwork is in the Available state. You can query the Status field by calling DescribeBgpNetworks. After a resource is created by AddBgpNetwork, it enters the Pending state. Wait until the state changes to Available before calling this operation.
8869
+ *
8825
8870
  * @param request - DeleteBgpNetworkRequest
8826
8871
  * @param runtime - runtime options for this request RuntimeOptions
8827
8872
  * @returns DeleteBgpNetworkResponse
@@ -8872,6 +8917,9 @@ class Client extends openapi_core_1.default {
8872
8917
  /**
8873
8918
  * Deletes an advertised Border Gateway Protocol (BGP) network.
8874
8919
  *
8920
+ * @remarks
8921
+ * Before calling this operation, ensure that the BgpNetwork is in the Available state. You can query the Status field by calling DescribeBgpNetworks. After a resource is created by AddBgpNetwork, it enters the Pending state. Wait until the state changes to Available before calling this operation.
8922
+ *
8875
8923
  * @param request - DeleteBgpNetworkRequest
8876
8924
  * @returns DeleteBgpNetworkResponse
8877
8925
  */
@@ -9444,10 +9492,10 @@ class Client extends openapi_core_1.default {
9444
9492
  return await this.deleteExpressConnectTrafficQosRuleWithOptions(request, runtime);
9445
9493
  }
9446
9494
  /**
9447
- * Deletes an Express Connect failover test job.
9495
+ * Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
9448
9496
  *
9449
9497
  * @remarks
9450
- * Only failover test jobs in the **Pending** or **Completed** state can be deleted.
9498
+ * Only failover test jobs in the **Pending** or **Completed** state can be deleted. Before calling this operation, create a failover test job by calling CreateFailoverTestJob and obtain the **JobId**. If the test resource is an Express Connect circuit, the circuit must be in the **Enabled** state and its business status must be **Normal**.
9451
9499
  *
9452
9500
  * @param request - DeleteFailoverTestJobRequest
9453
9501
  * @param runtime - runtime options for this request RuntimeOptions
@@ -9494,10 +9542,10 @@ class Client extends openapi_core_1.default {
9494
9542
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteFailoverTestJobResponse({}));
9495
9543
  }
9496
9544
  /**
9497
- * Deletes an Express Connect failover test job.
9545
+ * Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
9498
9546
  *
9499
9547
  * @remarks
9500
- * Only failover test jobs in the **Pending** or **Completed** state can be deleted.
9548
+ * Only failover test jobs in the **Pending** or **Completed** state can be deleted. Before calling this operation, create a failover test job by calling CreateFailoverTestJob and obtain the **JobId**. If the test resource is an Express Connect circuit, the circuit must be in the **Enabled** state and its business status must be **Normal**.
9501
9549
  *
9502
9550
  * @param request - DeleteFailoverTestJobRequest
9503
9551
  * @returns DeleteFailoverTestJobResponse
@@ -10048,7 +10096,7 @@ class Client extends openapi_core_1.default {
10048
10096
  * Deletes an IPsec server.
10049
10097
  *
10050
10098
  * @remarks
10051
- * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID. However, the IPsec server is not yet deleted. The deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway and determine the deletion status of the IPsec server:
10099
+ * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec server is not yet deleted. The deletion node continues to run in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway to determine the deletion status of the IPsec server:
10052
10100
  * - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
10053
10101
  * - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
10054
10102
  * - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
@@ -10092,7 +10140,7 @@ class Client extends openapi_core_1.default {
10092
10140
  * Deletes an IPsec server.
10093
10141
  *
10094
10142
  * @remarks
10095
- * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID. However, the IPsec server is not yet deleted. The deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway and determine the deletion status of the IPsec server:
10143
+ * - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec server is not yet deleted. The deletion node continues to run in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway to determine the deletion status of the IPsec server:
10096
10144
  * - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
10097
10145
  * - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
10098
10146
  * - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
@@ -10412,12 +10460,12 @@ class Client extends openapi_core_1.default {
10412
10460
  * Deletes a specified Internet NAT gateway.
10413
10461
  *
10414
10462
  * @remarks
10415
- * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://help.aliyun.com/document_detail/36054.html) to query the status of the NAT gateway:
10463
+ * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://www.alibabacloud.com/help/en/nat-gateway/developer-reference/api-vpc-2016-04-28-describenatgateways-natgws) to query the status of the NAT gateway:
10416
10464
  *
10417
10465
  * - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
10418
10466
  * - If the NAT gateway cannot be found, the NAT gateway is deleted.
10419
10467
  *
10420
- * > The deletion of a NAT gateway is irreversible. Proceed with caution.
10468
+ * > Deleting a NAT gateway is irreversible. Proceed with caution.
10421
10469
  *
10422
10470
  * @param request - DeleteNatGatewayRequest
10423
10471
  * @param runtime - runtime options for this request RuntimeOptions
@@ -10467,12 +10515,12 @@ class Client extends openapi_core_1.default {
10467
10515
  * Deletes a specified Internet NAT gateway.
10468
10516
  *
10469
10517
  * @remarks
10470
- * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://help.aliyun.com/document_detail/36054.html) to query the status of the NAT gateway:
10518
+ * *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://www.alibabacloud.com/help/en/nat-gateway/developer-reference/api-vpc-2016-04-28-describenatgateways-natgws) to query the status of the NAT gateway:
10471
10519
  *
10472
10520
  * - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
10473
10521
  * - If the NAT gateway cannot be found, the NAT gateway is deleted.
10474
10522
  *
10475
- * > The deletion of a NAT gateway is irreversible. Proceed with caution.
10523
+ * > Deleting a NAT gateway is irreversible. Proceed with caution.
10476
10524
  *
10477
10525
  * @param request - DeleteNatGatewayRequest
10478
10526
  * @returns DeleteNatGatewayResponse
@@ -10763,11 +10811,11 @@ class Client extends openapi_core_1.default {
10763
10811
  *
10764
10812
  * @remarks
10765
10813
  * Before you call this operation, take note of the following items:
10766
- * - Before deleting an IP address pool, make sure that the IP addresses in the pool are not in use.
10814
+ * - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
10767
10815
  * - **DeletePublicIpAddressPool** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call [ListPublicIpAddressPools](https://help.aliyun.com/document_detail/429433.html) to query the status of the IP address pool.
10768
10816
  * - If the IP address pool is in the **Deleting** state, the IP address pool is being deleted. In this state, you can only perform query operations.
10769
10817
  * - If the IP address pool cannot be found, the IP address pool is deleted.
10770
- * - **DeletePublicIpAddressPool** does not support concurrent deletion of the same IP address pool.
10818
+ * - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
10771
10819
  *
10772
10820
  * @param request - DeletePublicIpAddressPoolRequest
10773
10821
  * @param runtime - runtime options for this request RuntimeOptions
@@ -10821,11 +10869,11 @@ class Client extends openapi_core_1.default {
10821
10869
  *
10822
10870
  * @remarks
10823
10871
  * Before you call this operation, take note of the following items:
10824
- * - Before deleting an IP address pool, make sure that the IP addresses in the pool are not in use.
10872
+ * - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
10825
10873
  * - **DeletePublicIpAddressPool** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call [ListPublicIpAddressPools](https://help.aliyun.com/document_detail/429433.html) to query the status of the IP address pool.
10826
10874
  * - If the IP address pool is in the **Deleting** state, the IP address pool is being deleted. In this state, you can only perform query operations.
10827
10875
  * - If the IP address pool cannot be found, the IP address pool is deleted.
10828
- * - **DeletePublicIpAddressPool** does not support concurrent deletion of the same IP address pool.
10876
+ * - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
10829
10877
  *
10830
10878
  * @param request - DeletePublicIpAddressPoolRequest
10831
10879
  * @returns DeletePublicIpAddressPoolResponse
@@ -10840,7 +10888,7 @@ class Client extends openapi_core_1.default {
10840
10888
  * @remarks
10841
10889
  * Before you call this operation, take note of the following information:
10842
10890
  * - Before deleting a CIDR block, make sure that the CIDR block is not in use.
10843
- * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID, but the CIDR block is not yet deleted. The deletion task continues to run in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
10891
+ * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the deletion task in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
10844
10892
  * - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
10845
10893
  * - If the CIDR block cannot be found, the CIDR block is deleted.
10846
10894
  * - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
@@ -10901,7 +10949,7 @@ class Client extends openapi_core_1.default {
10901
10949
  * @remarks
10902
10950
  * Before you call this operation, take note of the following information:
10903
10951
  * - Before deleting a CIDR block, make sure that the CIDR block is not in use.
10904
- * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID, but the CIDR block is not yet deleted. The deletion task continues to run in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
10952
+ * - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the deletion task in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
10905
10953
  * - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
10906
10954
  * - If the CIDR block cannot be found, the CIDR block is deleted.
10907
10955
  * - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
@@ -10914,16 +10962,16 @@ class Client extends openapi_core_1.default {
10914
10962
  return await this.deletePublicIpAddressPoolCidrBlockWithOptions(request, runtime);
10915
10963
  }
10916
10964
  /**
10917
- * Batch deletes custom route entries.
10965
+ * Calls DeleteRouteEntries to batch delete custom route entries.
10918
10966
  *
10919
10967
  * @remarks
10920
10968
  * When you call this operation to delete routing entries, note the following items:
10921
10969
  * - Only routing entries in the **Available** state can be deleted.
10922
- * - Routing entries cannot be deleted if the VPC to which the route table belongs is creating or deleting a vSwitch or routing entries.
10923
- * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the custom route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the custom route entry:
10924
- * - If the custom route entry is in the **Deleting** state, the custom route entry is being deleted.
10925
- * - If the specified custom route entry cannot be found, the custom route entry is deleted.
10926
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries from route tables in the same VPC.
10970
+ * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
10971
+ * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
10972
+ * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
10973
+ * - If the specified routing entry cannot be found, the routing entry is deleted.
10974
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
10927
10975
  *
10928
10976
  * @param request - DeleteRouteEntriesRequest
10929
10977
  * @param runtime - runtime options for this request RuntimeOptions
@@ -10973,16 +11021,16 @@ class Client extends openapi_core_1.default {
10973
11021
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteRouteEntriesResponse({}));
10974
11022
  }
10975
11023
  /**
10976
- * Batch deletes custom route entries.
11024
+ * Calls DeleteRouteEntries to batch delete custom route entries.
10977
11025
  *
10978
11026
  * @remarks
10979
11027
  * When you call this operation to delete routing entries, note the following items:
10980
11028
  * - Only routing entries in the **Available** state can be deleted.
10981
- * - Routing entries cannot be deleted if the VPC to which the route table belongs is creating or deleting a vSwitch or routing entries.
10982
- * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the custom route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the custom route entry:
10983
- * - If the custom route entry is in the **Deleting** state, the custom route entry is being deleted.
10984
- * - If the specified custom route entry cannot be found, the custom route entry is deleted.
10985
- * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries from route tables in the same VPC.
11029
+ * - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
11030
+ * - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
11031
+ * - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
11032
+ * - If the specified routing entry cannot be found, the routing entry is deleted.
11033
+ * - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
10986
11034
  *
10987
11035
  * @param request - DeleteRouteEntriesRequest
10988
11036
  * @returns DeleteRouteEntriesResponse
@@ -11430,10 +11478,10 @@ class Client extends openapi_core_1.default {
11430
11478
  * Deletes an SSL server. After the SSL server is deleted, the system automatically deletes all SSL client certificates associated with the SSL server, and clients that have installed these SSL client certificates are automatically disconnected from the SSL-VPN connection.
11431
11479
  *
11432
11480
  * @remarks
11433
- * - **DeleteSslVpnServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the SSL server has not yet been deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
11481
+ * - The **DeleteSslVpnServer** operation is asynchronous. After you send a request, the system returns a request ID. However, the SSL server is not yet deleted. The deletion task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
11434
11482
  * - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
11435
11483
  * - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
11436
- * - **DeleteSslVpnServer** does not support concurrent deletion of SSL server instances under the same VPN gateway.
11484
+ * - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
11437
11485
  *
11438
11486
  * @param request - DeleteSslVpnServerRequest
11439
11487
  * @param runtime - runtime options for this request RuntimeOptions
@@ -11483,10 +11531,10 @@ class Client extends openapi_core_1.default {
11483
11531
  * Deletes an SSL server. After the SSL server is deleted, the system automatically deletes all SSL client certificates associated with the SSL server, and clients that have installed these SSL client certificates are automatically disconnected from the SSL-VPN connection.
11484
11532
  *
11485
11533
  * @remarks
11486
- * - **DeleteSslVpnServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the SSL server has not yet been deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
11534
+ * - The **DeleteSslVpnServer** operation is asynchronous. After you send a request, the system returns a request ID. However, the SSL server is not yet deleted. The deletion task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
11487
11535
  * - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
11488
11536
  * - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
11489
- * - **DeleteSslVpnServer** does not support concurrent deletion of SSL server instances under the same VPN gateway.
11537
+ * - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
11490
11538
  *
11491
11539
  * @param request - DeleteSslVpnServerRequest
11492
11540
  * @returns DeleteSslVpnServerResponse
@@ -11864,7 +11912,7 @@ class Client extends openapi_core_1.default {
11864
11912
  return await this.deleteVSwitchCidrReservationWithOptions(request, runtime);
11865
11913
  }
11866
11914
  /**
11867
- * Deletes a VBR failover group.
11915
+ * Calls DeleteVbrHa to delete a VBR failover group.
11868
11916
  *
11869
11917
  * @param request - DeleteVbrHaRequest
11870
11918
  * @param runtime - runtime options for this request RuntimeOptions
@@ -11911,7 +11959,7 @@ class Client extends openapi_core_1.default {
11911
11959
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteVbrHaResponse({}));
11912
11960
  }
11913
11961
  /**
11914
- * Deletes a VBR failover group.
11962
+ * Calls DeleteVbrHa to delete a VBR failover group.
11915
11963
  *
11916
11964
  * @param request - DeleteVbrHaRequest
11917
11965
  * @returns DeleteVbrHaResponse
@@ -11924,7 +11972,7 @@ class Client extends openapi_core_1.default {
11924
11972
  * Deletes a destination route entry from an IPsec-VPN connection.
11925
11973
  *
11926
11974
  * @remarks
11927
- * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry has not been deleted yet. The deletion task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
11975
+ * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
11928
11976
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
11929
11977
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
11930
11978
  * - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
@@ -11986,7 +12034,7 @@ class Client extends openapi_core_1.default {
11986
12034
  * Deletes a destination route entry from an IPsec-VPN connection.
11987
12035
  *
11988
12036
  * @remarks
11989
- * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry has not been deleted yet. The deletion task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
12037
+ * - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
11990
12038
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
11991
12039
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
11992
12040
  * - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
@@ -12277,11 +12325,11 @@ class Client extends openapi_core_1.default {
12277
12325
  return await this.deleteVpcPrefixListWithOptions(request, runtime);
12278
12326
  }
12279
12327
  /**
12280
- * Deletes an IPsec-VPN connection by calling the DeleteVpnAttachment operation.
12328
+ * Deletes an IPsec-VPN connection.
12281
12329
  *
12282
12330
  * @remarks
12283
- * - If the IPsec-VPN connection is associated with a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
12284
- * - If the IPsec-VPN connection is not associated with any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
12331
+ * - If the IPsec-VPN connection is bindded to a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
12332
+ * - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
12285
12333
  *
12286
12334
  * @param request - DeleteVpnAttachmentRequest
12287
12335
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12325,11 +12373,11 @@ class Client extends openapi_core_1.default {
12325
12373
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteVpnAttachmentResponse({}));
12326
12374
  }
12327
12375
  /**
12328
- * Deletes an IPsec-VPN connection by calling the DeleteVpnAttachment operation.
12376
+ * Deletes an IPsec-VPN connection.
12329
12377
  *
12330
12378
  * @remarks
12331
- * - If the IPsec-VPN connection is associated with a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
12332
- * - If the IPsec-VPN connection is not associated with any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
12379
+ * - If the IPsec-VPN connection is bindded to a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
12380
+ * - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
12333
12381
  *
12334
12382
  * @param request - DeleteVpnAttachmentRequest
12335
12383
  * @returns DeleteVpnAttachmentResponse
@@ -12342,7 +12390,7 @@ class Client extends openapi_core_1.default {
12342
12390
  * Deletes a specified IPsec-VPN connection.
12343
12391
  *
12344
12392
  * @remarks
12345
- * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance and determine the deletion status of the IPsec-VPN connection:
12393
+ * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the deletion status of the IPsec-VPN connection:
12346
12394
  * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
12347
12395
  * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
12348
12396
  * - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
@@ -12396,7 +12444,7 @@ class Client extends openapi_core_1.default {
12396
12444
  * Deletes a specified IPsec-VPN connection.
12397
12445
  *
12398
12446
  * @remarks
12399
- * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance and determine the deletion status of the IPsec-VPN connection:
12447
+ * - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the deletion status of the IPsec-VPN connection:
12400
12448
  * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
12401
12449
  * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
12402
12450
  * - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
@@ -12413,7 +12461,7 @@ class Client extends openapi_core_1.default {
12413
12461
  * Deletes a specified VPN gateway.
12414
12462
  *
12415
12463
  * @remarks
12416
- * > You cannot delete a VPN gateway that has existing IPsec-VPN connections.
12464
+ * > You cannot delete a VPN gateway that has IPsec-VPN connections.
12417
12465
  *
12418
12466
  * @param request - DeleteVpnGatewayRequest
12419
12467
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12463,7 +12511,7 @@ class Client extends openapi_core_1.default {
12463
12511
  * Deletes a specified VPN gateway.
12464
12512
  *
12465
12513
  * @remarks
12466
- * > You cannot delete a VPN gateway that has existing IPsec-VPN connections.
12514
+ * > You cannot delete a VPN gateway that has IPsec-VPN connections.
12467
12515
  *
12468
12516
  * @param request - DeleteVpnGatewayRequest
12469
12517
  * @returns DeleteVpnGatewayResponse
@@ -12563,7 +12611,7 @@ class Client extends openapi_core_1.default {
12563
12611
  * Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
12564
12612
  *
12565
12613
  * @remarks
12566
- * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway and determine the deletion status of the VPN destination routing:
12614
+ * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway, and determine the deletion status of the VPN destination routing:
12567
12615
  * - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
12568
12616
  * - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
12569
12617
  * - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
@@ -12628,7 +12676,7 @@ class Client extends openapi_core_1.default {
12628
12676
  * Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
12629
12677
  *
12630
12678
  * @remarks
12631
- * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway and determine the deletion status of the VPN destination routing:
12679
+ * - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway, and determine the deletion status of the VPN destination routing:
12632
12680
  * - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
12633
12681
  * - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
12634
12682
  * - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
@@ -13273,10 +13321,10 @@ class Client extends openapi_core_1.default {
13273
13321
  return await this.describeEcGrantRelationWithOptions(request, runtime);
13274
13322
  }
13275
13323
  /**
13276
- * Queries Elastic IP Addresses (EIPs) created in a specified region.
13324
+ * Queries elastic IP addresses (EIPs) created in a specified region.
13277
13325
  *
13278
13326
  * @remarks
13279
- * Queries information about EIPs created in a specified region, including the bandwidth peak, billing method, and the type of instance currently attached with each EIP.
13327
+ * This operation queries information about EIPs created in a specified region, including the maximum bandwidth, billing method, and the type of instance currently attached to each EIP. If you frequently perform deep paging or page skipping, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential pagination.
13280
13328
  *
13281
13329
  * @param request - DescribeEipAddressesRequest
13282
13330
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13377,10 +13425,10 @@ class Client extends openapi_core_1.default {
13377
13425
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeEipAddressesResponse({}));
13378
13426
  }
13379
13427
  /**
13380
- * Queries Elastic IP Addresses (EIPs) created in a specified region.
13428
+ * Queries elastic IP addresses (EIPs) created in a specified region.
13381
13429
  *
13382
13430
  * @remarks
13383
- * Queries information about EIPs created in a specified region, including the bandwidth peak, billing method, and the type of instance currently attached with each EIP.
13431
+ * This operation queries information about EIPs created in a specified region, including the maximum bandwidth, billing method, and the type of instance currently attached to each EIP. If you frequently perform deep paging or page skipping, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential pagination.
13384
13432
  *
13385
13433
  * @param request - DescribeEipAddressesRequest
13386
13434
  * @returns DescribeEipAddressesResponse
@@ -13659,6 +13707,9 @@ class Client extends openapi_core_1.default {
13659
13707
  /**
13660
13708
  * Queries Express Connect QoS queues.
13661
13709
  *
13710
+ * @remarks
13711
+ * Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
13712
+ *
13662
13713
  * @param request - DescribeExpressConnectTrafficQosQueueRequest
13663
13714
  * @param runtime - runtime options for this request RuntimeOptions
13664
13715
  * @returns DescribeExpressConnectTrafficQosQueueResponse
@@ -13712,6 +13763,9 @@ class Client extends openapi_core_1.default {
13712
13763
  /**
13713
13764
  * Queries Express Connect QoS queues.
13714
13765
  *
13766
+ * @remarks
13767
+ * Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
13768
+ *
13715
13769
  * @param request - DescribeExpressConnectTrafficQosQueueRequest
13716
13770
  * @returns DescribeExpressConnectTrafficQosQueueResponse
13717
13771
  */
@@ -13786,7 +13840,7 @@ class Client extends openapi_core_1.default {
13786
13840
  return await this.describeExpressConnectTrafficQosRuleWithOptions(request, runtime);
13787
13841
  }
13788
13842
  /**
13789
- * Queries the details of an Express Connect failover test job by calling the DescribeFailoverTestJob operation.
13843
+ * Queries the details of an Express Connect failover test job.
13790
13844
  *
13791
13845
  * @param request - DescribeFailoverTestJobRequest
13792
13846
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13833,7 +13887,7 @@ class Client extends openapi_core_1.default {
13833
13887
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeFailoverTestJobResponse({}));
13834
13888
  }
13835
13889
  /**
13836
- * Queries the details of an Express Connect failover test job by calling the DescribeFailoverTestJob operation.
13890
+ * Queries the details of an Express Connect failover test job.
13837
13891
  *
13838
13892
  * @param request - DescribeFailoverTestJobRequest
13839
13893
  * @returns DescribeFailoverTestJobResponse
@@ -13843,7 +13897,7 @@ class Client extends openapi_core_1.default {
13843
13897
  return await this.describeFailoverTestJobWithOptions(request, runtime);
13844
13898
  }
13845
13899
  /**
13846
- * Queries failover test jobs of Express Connect in batches.
13900
+ * Queries Express Connect failover test jobs in batches.
13847
13901
  *
13848
13902
  * @param request - DescribeFailoverTestJobsRequest
13849
13903
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13896,7 +13950,7 @@ class Client extends openapi_core_1.default {
13896
13950
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeFailoverTestJobsResponse({}));
13897
13951
  }
13898
13952
  /**
13899
- * Queries failover test jobs of Express Connect in batches.
13953
+ * Queries Express Connect failover test jobs in batches.
13900
13954
  *
13901
13955
  * @param request - DescribeFailoverTestJobsRequest
13902
13956
  * @returns DescribeFailoverTestJobsResponse
@@ -15409,7 +15463,7 @@ class Client extends openapi_core_1.default {
15409
15463
  * Queries information about Express Connect circuits in a specified region.
15410
15464
  *
15411
15465
  * @remarks
15412
- * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, refer to the description of **Key** in the **request parameters** section of this topic.
15466
+ * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, see the description of **Key** in the **request parameters** section of this topic.
15413
15467
  *
15414
15468
  * @param request - DescribePhysicalConnectionsRequest
15415
15469
  * @param runtime - runtime options for this request RuntimeOptions
@@ -15474,7 +15528,7 @@ class Client extends openapi_core_1.default {
15474
15528
  * Queries information about Express Connect circuits in a specified region.
15475
15529
  *
15476
15530
  * @remarks
15477
- * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, refer to the description of **Key** in the **request parameters** section of this topic.
15531
+ * By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, see the description of **Key** in the **request parameters** section of this topic.
15478
15532
  *
15479
15533
  * @param request - DescribePhysicalConnectionsRequest
15480
15534
  * @returns DescribePhysicalConnectionsResponse
@@ -15918,7 +15972,7 @@ class Client extends openapi_core_1.default {
15918
15972
  return await this.describeRouterInterfaceAttributeWithOptions(request, runtime);
15919
15973
  }
15920
15974
  /**
15921
- * Queries router interfaces in a specified region by calling the DescribeRouterInterfaces operation.
15975
+ * Queries router interfaces in a specified region.
15922
15976
  *
15923
15977
  * @param request - DescribeRouterInterfacesRequest
15924
15978
  * @param runtime - runtime options for this request RuntimeOptions
@@ -15974,7 +16028,7 @@ class Client extends openapi_core_1.default {
15974
16028
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeRouterInterfacesResponse({}));
15975
16029
  }
15976
16030
  /**
15977
- * Queries router interfaces in a specified region by calling the DescribeRouterInterfaces operation.
16031
+ * Queries router interfaces in a specified region.
15978
16032
  *
15979
16033
  * @param request - DescribeRouterInterfacesRequest
15980
16034
  * @returns DescribeRouterInterfacesResponse
@@ -16454,7 +16508,7 @@ class Client extends openapi_core_1.default {
16454
16508
  return await this.describeTagKeysWithOptions(request, runtime);
16455
16509
  }
16456
16510
  /**
16457
- * Calls the DescribeTagKeysForExpressConnect operation to return the tag list of Express Connect.
16511
+ * Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
16458
16512
  *
16459
16513
  * @param request - DescribeTagKeysForExpressConnectRequest
16460
16514
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16510,7 +16564,7 @@ class Client extends openapi_core_1.default {
16510
16564
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeTagKeysForExpressConnectResponse({}));
16511
16565
  }
16512
16566
  /**
16513
- * Calls the DescribeTagKeysForExpressConnect operation to return the tag list of Express Connect.
16567
+ * Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
16514
16568
  *
16515
16569
  * @param request - DescribeTagKeysForExpressConnectRequest
16516
16570
  * @returns DescribeTagKeysForExpressConnectResponse
@@ -16717,6 +16771,9 @@ class Client extends openapi_core_1.default {
16717
16771
  /**
16718
16772
  * Queries networkable information. Internal networking is performed by vSwitch.
16719
16773
  *
16774
+ * @remarks
16775
+ * The **DescribeVSwitches** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
16776
+ *
16720
16777
  * @param request - DescribeVSwitchesRequest
16721
16778
  * @param runtime - runtime options for this request RuntimeOptions
16722
16779
  * @returns DescribeVSwitchesResponse
@@ -16797,6 +16854,9 @@ class Client extends openapi_core_1.default {
16797
16854
  /**
16798
16855
  * Queries networkable information. Internal networking is performed by vSwitch.
16799
16856
  *
16857
+ * @remarks
16858
+ * The **DescribeVSwitches** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
16859
+ *
16800
16860
  * @param request - DescribeVSwitchesRequest
16801
16861
  * @returns DescribeVSwitchesResponse
16802
16862
  */
@@ -16931,7 +16991,7 @@ class Client extends openapi_core_1.default {
16931
16991
  return await this.describeVcoRouteEntriesWithOptions(request, runtime);
16932
16992
  }
16933
16993
  /**
16934
- * Queries the Virtual Border Routers (VBRs) that you have created.
16994
+ * Queries Virtual Border Routers (VBRs) that are created.
16935
16995
  *
16936
16996
  * @param request - DescribeVirtualBorderRoutersRequest
16937
16997
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16987,7 +17047,7 @@ class Client extends openapi_core_1.default {
16987
17047
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeVirtualBorderRoutersResponse({}));
16988
17048
  }
16989
17049
  /**
16990
- * Queries the Virtual Border Routers (VBRs) that you have created.
17050
+ * Queries Virtual Border Routers (VBRs) that are created.
16991
17051
  *
16992
17052
  * @param request - DescribeVirtualBorderRoutersRequest
16993
17053
  * @returns DescribeVirtualBorderRoutersResponse
@@ -17194,6 +17254,9 @@ class Client extends openapi_core_1.default {
17194
17254
  /**
17195
17255
  * Queries created VPCs.
17196
17256
  *
17257
+ * @remarks
17258
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
17259
+ *
17197
17260
  * @param request - DescribeVpcsRequest
17198
17261
  * @param runtime - runtime options for this request RuntimeOptions
17199
17262
  * @returns DescribeVpcsResponse
@@ -17268,6 +17331,9 @@ class Client extends openapi_core_1.default {
17268
17331
  /**
17269
17332
  * Queries created VPCs.
17270
17333
  *
17334
+ * @remarks
17335
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
17336
+ *
17271
17337
  * @param request - DescribeVpcsRequest
17272
17338
  * @returns DescribeVpcsResponse
17273
17339
  */
@@ -17894,7 +17960,7 @@ class Client extends openapi_core_1.default {
17894
17960
  return await this.describeVpnRouteEntriesWithOptions(request, runtime);
17895
17961
  }
17896
17962
  /**
17897
- * Queries the logs of an SSL server by calling the DescribeVpnSslServerLogs operation.
17963
+ * Queries the logs of an SSL server.
17898
17964
  *
17899
17965
  * @param request - DescribeVpnSslServerLogsRequest
17900
17966
  * @param runtime - runtime options for this request RuntimeOptions
@@ -17956,7 +18022,7 @@ class Client extends openapi_core_1.default {
17956
18022
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeVpnSslServerLogsResponse({}));
17957
18023
  }
17958
18024
  /**
17959
- * Queries the logs of an SSL server by calling the DescribeVpnSslServerLogs operation.
18025
+ * Queries the logs of an SSL server.
17960
18026
  *
17961
18027
  * @param request - DescribeVpnSslServerLogsRequest
17962
18028
  * @returns DescribeVpnSslServerLogsResponse
@@ -18165,10 +18231,10 @@ class Client extends openapi_core_1.default {
18165
18231
  return await this.diagnoseVpnConnectionsWithOptions(request, runtime);
18166
18232
  }
18167
18233
  /**
18168
- * Diagnoses a specified VPN gateway instance with one click by calling the DiagnoseVpnGateway operation.
18234
+ * Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
18169
18235
  *
18170
18236
  * @remarks
18171
- * Only VPN gateway instances in specific regions support the one-click diagnostics feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
18237
+ * Only VPN gateway instances in specific regions support the one-click diagnosis feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
18172
18238
  *
18173
18239
  * @param request - DiagnoseVpnGatewayRequest
18174
18240
  * @param runtime - runtime options for this request RuntimeOptions
@@ -18212,10 +18278,10 @@ class Client extends openapi_core_1.default {
18212
18278
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DiagnoseVpnGatewayResponse({}));
18213
18279
  }
18214
18280
  /**
18215
- * Diagnoses a specified VPN gateway instance with one click by calling the DiagnoseVpnGateway operation.
18281
+ * Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
18216
18282
  *
18217
18283
  * @remarks
18218
- * Only VPN gateway instances in specific regions support the one-click diagnostics feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
18284
+ * Only VPN gateway instances in specific regions support the one-click diagnosis feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
18219
18285
  *
18220
18286
  * @param request - DiagnoseVpnGatewayRequest
18221
18287
  * @returns DiagnoseVpnGatewayResponse
@@ -18475,10 +18541,10 @@ class Client extends openapi_core_1.default {
18475
18541
  * Dissociates a VPN gateway from a certificate.
18476
18542
  *
18477
18543
  * @remarks
18478
- * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the VPN gateway is not yet dissociated from the SSL certificate, and the dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and check the dissociation status of the SSL certificate:
18544
+ * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID, but the VPN gateway has not yet been dissociated from the SSL certificate. The dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and confirm the dissociation status of the SSL certificate:
18479
18545
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
18480
18546
  * - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
18481
- * - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL certificate dissociation for the same VPN gateway.
18547
+ * - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
18482
18548
  *
18483
18549
  * @param request - DissociateVpnGatewayWithCertificateRequest
18484
18550
  * @param runtime - runtime options for this request RuntimeOptions
@@ -18525,10 +18591,10 @@ class Client extends openapi_core_1.default {
18525
18591
  * Dissociates a VPN gateway from a certificate.
18526
18592
  *
18527
18593
  * @remarks
18528
- * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the VPN gateway is not yet dissociated from the SSL certificate, and the dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and check the dissociation status of the SSL certificate:
18594
+ * - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID, but the VPN gateway has not yet been dissociated from the SSL certificate. The dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and confirm the dissociation status of the SSL certificate:
18529
18595
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
18530
18596
  * - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
18531
- * - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL certificate dissociation for the same VPN gateway.
18597
+ * - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
18532
18598
  *
18533
18599
  * @param request - DissociateVpnGatewayWithCertificateRequest
18534
18600
  * @returns DissociateVpnGatewayWithCertificateResponse
@@ -18595,11 +18661,12 @@ class Client extends openapi_core_1.default {
18595
18661
  * Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
18596
18662
  *
18597
18663
  * @remarks
18598
- * When you call this operation, take note of the following items:
18599
- * - You can enable only an Express Connect circuit that is in the **Confirmed** state.
18600
- * - After the circuit is enabled, it enters the **Enabled** state.
18601
- * - **EnablePhysicalConnection** is an asynchronous operation. After you send a request, the system returns an instance ID, but the Express Connect circuit is not yet enabled. The enabling task is still running in the background. You can call [DescribePhysicalConnections](https://help.aliyun.com/document_detail/2982519.html) to query the status of the Express Connect circuit.
18602
- * - **EnablePhysicalConnection** does not support concurrent enabling of the same Express Connect circuit that is in the **Confirmed** state.
18664
+ * When you invoke this operation, note the following items:
18665
+ * - You can enable only an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state. To reach the Confirmed state, complete the following steps in sequence: call CreatePhysicalConnection to create a circuit (Initial → Allocating), wait for resource allocation to complete (Allocating → Allocated), and then call ConfirmPhysicalConnection after construction is complete (Allocated → Confirmed).
18666
+ * - A billing activation step occurs between the Confirmed and Enabled states. By default (if ByPassSp is not specified or ByPassSp is set to false), the system automatically creates a billing order in the sales and billing system when you invoke this operation. The circuit is enabled only after the order is created. To skip the billing order flow and directly enable the circuit, set ByPassSp to true. This capability is available only to whitelist accounts. For more information, see the ByPassSp parameter description.
18667
+ * - The EnablePhysicalConnection operation is asynchronous. The system returns a success response, but the Express Connect circuit is not yet fully enabled because the backend enablement task is still in progress. You can invoke DescribePhysicalConnections to query the enablement status of the Express Connect circuit.
18668
+ * - The EnablePhysicalConnection operation does not support concurrent enablement of the same Express Connect circuit that is in the Confirmed state. Concurrent invocations return an error.
18669
+ * If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
18603
18670
  *
18604
18671
  * @param request - EnablePhysicalConnectionRequest
18605
18672
  * @param runtime - runtime options for this request RuntimeOptions
@@ -18652,11 +18719,12 @@ class Client extends openapi_core_1.default {
18652
18719
  * Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
18653
18720
  *
18654
18721
  * @remarks
18655
- * When you call this operation, take note of the following items:
18656
- * - You can enable only an Express Connect circuit that is in the **Confirmed** state.
18657
- * - After the circuit is enabled, it enters the **Enabled** state.
18658
- * - **EnablePhysicalConnection** is an asynchronous operation. After you send a request, the system returns an instance ID, but the Express Connect circuit is not yet enabled. The enabling task is still running in the background. You can call [DescribePhysicalConnections](https://help.aliyun.com/document_detail/2982519.html) to query the status of the Express Connect circuit.
18659
- * - **EnablePhysicalConnection** does not support concurrent enabling of the same Express Connect circuit that is in the **Confirmed** state.
18722
+ * When you invoke this operation, note the following items:
18723
+ * - You can enable only an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state. To reach the Confirmed state, complete the following steps in sequence: call CreatePhysicalConnection to create a circuit (Initial → Allocating), wait for resource allocation to complete (Allocating → Allocated), and then call ConfirmPhysicalConnection after construction is complete (Allocated → Confirmed).
18724
+ * - A billing activation step occurs between the Confirmed and Enabled states. By default (if ByPassSp is not specified or ByPassSp is set to false), the system automatically creates a billing order in the sales and billing system when you invoke this operation. The circuit is enabled only after the order is created. To skip the billing order flow and directly enable the circuit, set ByPassSp to true. This capability is available only to whitelist accounts. For more information, see the ByPassSp parameter description.
18725
+ * - The EnablePhysicalConnection operation is asynchronous. The system returns a success response, but the Express Connect circuit is not yet fully enabled because the backend enablement task is still in progress. You can invoke DescribePhysicalConnections to query the enablement status of the Express Connect circuit.
18726
+ * - The EnablePhysicalConnection operation does not support concurrent enablement of the same Express Connect circuit that is in the Confirmed state. Concurrent invocations return an error.
18727
+ * If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
18660
18728
  *
18661
18729
  * @param request - EnablePhysicalConnectionRequest
18662
18730
  * @returns EnablePhysicalConnectionResponse
@@ -18977,7 +19045,7 @@ class Client extends openapi_core_1.default {
18977
19045
  * Queries the information about a single NAT gateway instance.
18978
19046
  *
18979
19047
  * @remarks
18980
- * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic refers to both types without distinction.
19048
+ * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic does not distinguish between the two types.
18981
19049
  *
18982
19050
  * @param request - GetNatGatewayAttributeRequest
18983
19051
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19027,7 +19095,7 @@ class Client extends openapi_core_1.default {
19027
19095
  * Queries the information about a single NAT gateway instance.
19028
19096
  *
19029
19097
  * @remarks
19030
- * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic refers to both types without distinction.
19098
+ * This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic does not distinguish between the two types.
19031
19099
  *
19032
19100
  * @param request - GetNatGatewayAttributeRequest
19033
19101
  * @returns GetNatGatewayAttributeResponse
@@ -19558,10 +19626,10 @@ class Client extends openapi_core_1.default {
19558
19626
  return await this.getVpcRouteEntrySummaryWithOptions(request, runtime);
19559
19627
  }
19560
19628
  /**
19561
- * Queries the one-click diagnostic result of a VPN gateway instance by calling the GetVpnGatewayDiagnoseResult operation.
19629
+ * Queries the one-click diagnosis result of a VPN gateway instance.
19562
19630
  *
19563
19631
  * @remarks
19564
- * When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters in addition to the required parameters.
19632
+ * When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
19565
19633
  *
19566
19634
  * @param request - GetVpnGatewayDiagnoseResultRequest
19567
19635
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19599,10 +19667,10 @@ class Client extends openapi_core_1.default {
19599
19667
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.GetVpnGatewayDiagnoseResultResponse({}));
19600
19668
  }
19601
19669
  /**
19602
- * Queries the one-click diagnostic result of a VPN gateway instance by calling the GetVpnGatewayDiagnoseResult operation.
19670
+ * Queries the one-click diagnosis result of a VPN gateway instance.
19603
19671
  *
19604
19672
  * @remarks
19605
- * When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters in addition to the required parameters.
19673
+ * When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
19606
19674
  *
19607
19675
  * @param request - GetVpnGatewayDiagnoseResultRequest
19608
19676
  * @returns GetVpnGatewayDiagnoseResultResponse
@@ -19691,7 +19759,18 @@ class Client extends openapi_core_1.default {
19691
19759
  * Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
19692
19760
  *
19693
19761
  * @remarks
19694
- * When creating a cross-account VBR uplink connection, you must grant authorization of the VPC-connected instance to the VBR instance.
19762
+ * This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
19763
+ * **Account A (VPC owner, the caller of this operation):**
19764
+ * - A VPC has been created and is in the Available state (CreateVpc).
19765
+ * **Account B (VBR owner, the account specified by VbrOwnerUid):** When GrantType=Specify, the VBRs specified in VbrInstanceIds must already be created. Creating a VBR depends on the complete Express Connect circuit lifecycle:
19766
+ * 1. Call CreatePhysicalConnection to create an Express Connect circuit.
19767
+ * 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
19768
+ * 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
19769
+ * 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
19770
+ * After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
19771
+ * - GrantType=All: Grants authorization to all VBRs under Account B (only the validity of VbrOwnerUid is verified. The VBRs do not need to be created yet).
19772
+ * - GrantType=Specify: Grants authorization to specified VBRs. The instances in VbrInstanceIds must already exist in the region specified by VbrRegionNo under the account specified by VbrOwnerUid. Otherwise, the error Instance.NotExist is returned.
19773
+ * Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
19695
19774
  *
19696
19775
  * @param tmpReq - GrantInstanceToVbrRequest
19697
19776
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19743,7 +19822,18 @@ class Client extends openapi_core_1.default {
19743
19822
  * Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
19744
19823
  *
19745
19824
  * @remarks
19746
- * When creating a cross-account VBR uplink connection, you must grant authorization of the VPC-connected instance to the VBR instance.
19825
+ * This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
19826
+ * **Account A (VPC owner, the caller of this operation):**
19827
+ * - A VPC has been created and is in the Available state (CreateVpc).
19828
+ * **Account B (VBR owner, the account specified by VbrOwnerUid):** When GrantType=Specify, the VBRs specified in VbrInstanceIds must already be created. Creating a VBR depends on the complete Express Connect circuit lifecycle:
19829
+ * 1. Call CreatePhysicalConnection to create an Express Connect circuit.
19830
+ * 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
19831
+ * 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
19832
+ * 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
19833
+ * After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
19834
+ * - GrantType=All: Grants authorization to all VBRs under Account B (only the validity of VbrOwnerUid is verified. The VBRs do not need to be created yet).
19835
+ * - GrantType=Specify: Grants authorization to specified VBRs. The instances in VbrInstanceIds must already exist in the region specified by VbrRegionNo under the account specified by VbrOwnerUid. Otherwise, the error Instance.NotExist is returned.
19836
+ * Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
19747
19837
  *
19748
19838
  * @param request - GrantInstanceToVbrRequest
19749
19839
  * @returns GrantInstanceToVbrResponse
@@ -19753,7 +19843,7 @@ class Client extends openapi_core_1.default {
19753
19843
  return await this.grantInstanceToVbrWithOptions(request, runtime);
19754
19844
  }
19755
19845
  /**
19756
- * Calls the ListBusinessAccessPoints operation to query access point information for Express Connect circuits.
19846
+ * Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
19757
19847
  *
19758
19848
  * @param request - ListBusinessAccessPointsRequest
19759
19849
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19785,7 +19875,7 @@ class Client extends openapi_core_1.default {
19785
19875
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListBusinessAccessPointsResponse({}));
19786
19876
  }
19787
19877
  /**
19788
- * Calls the ListBusinessAccessPoints operation to query access point information for Express Connect circuits.
19878
+ * Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
19789
19879
  *
19790
19880
  * @param request - ListBusinessAccessPointsRequest
19791
19881
  * @returns ListBusinessAccessPointsResponse
@@ -21234,7 +21324,7 @@ class Client extends openapi_core_1.default {
21234
21324
  return await this.listVSwitchCidrReservationsWithOptions(request, runtime);
21235
21325
  }
21236
21326
  /**
21237
- * Queries information about shared Express Connect circuits by calling the ListVirtualPhysicalConnections operation.
21327
+ * Queries information about shared Express Connect circuits.
21238
21328
  *
21239
21329
  * @param request - ListVirtualPhysicalConnectionsRequest
21240
21330
  * @param runtime - runtime options for this request RuntimeOptions
@@ -21296,7 +21386,7 @@ class Client extends openapi_core_1.default {
21296
21386
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListVirtualPhysicalConnectionsResponse({}));
21297
21387
  }
21298
21388
  /**
21299
- * Queries information about shared Express Connect circuits by calling the ListVirtualPhysicalConnections operation.
21389
+ * Queries information about shared Express Connect circuits.
21300
21390
  *
21301
21391
  * @param request - ListVirtualPhysicalConnectionsRequest
21302
21392
  * @returns ListVirtualPhysicalConnectionsResponse
@@ -21518,7 +21608,7 @@ class Client extends openapi_core_1.default {
21518
21608
  * @remarks
21519
21609
  * When you call **ListVpnCertificateAssociations**:
21520
21610
  * - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
21521
- * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified certificate type in the specified region are queried.
21611
+ * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified type in the specified region are queried.
21522
21612
  * - If you specify the **RegionId** and **VpnGatewayId** parameters, the associations between the specified VPN gateway instances and SSL certificates in the specified region are queried.
21523
21613
  * - If you specify the **RegionId** and **CertificateId** parameters, the associations between the specified SSL certificates and VPN gateway instances in the specified region are queried.
21524
21614
  *
@@ -21569,7 +21659,7 @@ class Client extends openapi_core_1.default {
21569
21659
  * @remarks
21570
21660
  * When you call **ListVpnCertificateAssociations**:
21571
21661
  * - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
21572
- * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified certificate type in the specified region are queried.
21662
+ * - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified type in the specified region are queried.
21573
21663
  * - If you specify the **RegionId** and **VpnGatewayId** parameters, the associations between the specified VPN gateway instances and SSL certificates in the specified region are queried.
21574
21664
  * - If you specify the **RegionId** and **CertificateId** parameters, the associations between the specified SSL certificates and VPN gateway instances in the specified region are queried.
21575
21665
  *
@@ -21938,7 +22028,7 @@ class Client extends openapi_core_1.default {
21938
22028
  return await this.modifyCommonBandwidthPackageSpecWithOptions(request, runtime);
21939
22029
  }
21940
22030
  /**
21941
- * Modifies the configuration of a customer gateway by calling the ModifyCustomerGatewayAttribute operation.
22031
+ * Modifies the configuration of a customer gateway.
21942
22032
  *
21943
22033
  * @remarks
21944
22034
  * - When you call the **ModifyCustomerGatewayAttribute** operation, if the **AuthKey** parameter is not empty, this operation is asynchronous. The system returns the customer gateway information first, but the configuration has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the customer gateway configuration:
@@ -22001,7 +22091,7 @@ class Client extends openapi_core_1.default {
22001
22091
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyCustomerGatewayAttributeResponse({}));
22002
22092
  }
22003
22093
  /**
22004
- * Modifies the configuration of a customer gateway by calling the ModifyCustomerGatewayAttribute operation.
22094
+ * Modifies the configuration of a customer gateway.
22005
22095
  *
22006
22096
  * @remarks
22007
22097
  * - When you call the **ModifyCustomerGatewayAttribute** operation, if the **AuthKey** parameter is not empty, this operation is asynchronous. The system returns the customer gateway information first, but the configuration has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the customer gateway configuration:
@@ -22267,12 +22357,12 @@ class Client extends openapi_core_1.default {
22267
22357
  return await this.modifyExpressCloudConnectionBandwidthWithOptions(request, runtime);
22268
22358
  }
22269
22359
  /**
22270
- * Calls the ModifyExpressConnectTrafficQos operation to modify an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits.
22360
+ * Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
22271
22361
  *
22272
22362
  * @remarks
22273
22363
  * - Only dedicated Express Connect circuits that are in the Normal state and do not have overdue payments can be associated. Shared Express Connect circuit ports and Virtual Border Router (VBR) instances are not supported.
22274
- * - When associating dedicated Express Connect circuits, only full operations are supported. To dissociate all circuits, pass an empty string.
22275
- * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must apply for a whitelist before you can associate it.
22364
+ * - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
22365
+ * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must be added to the whitelist before you can associate it.
22276
22366
  * - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
22277
22367
  * - If a single VBR is associated with multiple Express Connect circuits, you must associate all Express Connect circuits of the VBR at the same time.
22278
22368
  *
@@ -22333,12 +22423,12 @@ class Client extends openapi_core_1.default {
22333
22423
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyExpressConnectTrafficQosResponse({}));
22334
22424
  }
22335
22425
  /**
22336
- * Calls the ModifyExpressConnectTrafficQos operation to modify an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits.
22426
+ * Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
22337
22427
  *
22338
22428
  * @remarks
22339
22429
  * - Only dedicated Express Connect circuits that are in the Normal state and do not have overdue payments can be associated. Shared Express Connect circuit ports and Virtual Border Router (VBR) instances are not supported.
22340
- * - When associating dedicated Express Connect circuits, only full operations are supported. To dissociate all circuits, pass an empty string.
22341
- * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must apply for a whitelist before you can associate it.
22430
+ * - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
22431
+ * - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must be added to the whitelist before you can associate it.
22342
22432
  * - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
22343
22433
  * - If a single VBR is associated with multiple Express Connect circuits, you must associate all Express Connect circuits of the VBR at the same time.
22344
22434
  *
@@ -23937,13 +24027,13 @@ class Client extends openapi_core_1.default {
23937
24027
  return await this.modifyNetworkAclAttributesWithOptions(request, runtime);
23938
24028
  }
23939
24029
  /**
23940
- * Modifies the configuration of an Express Connect circuit.
24030
+ * Modifies the configurations of an Express Connect circuit.
23941
24031
  *
23942
24032
  * @remarks
23943
24033
  * When you call this operation, note the following items:
23944
24034
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
23945
24035
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
23946
- * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
24036
+ * - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
23947
24037
  *
23948
24038
  * @param request - ModifyPhysicalConnectionAttributeRequest
23949
24039
  * @param runtime - runtime options for this request RuntimeOptions
@@ -24020,13 +24110,13 @@ class Client extends openapi_core_1.default {
24020
24110
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyPhysicalConnectionAttributeResponse({}));
24021
24111
  }
24022
24112
  /**
24023
- * Modifies the configuration of an Express Connect circuit.
24113
+ * Modifies the configurations of an Express Connect circuit.
24024
24114
  *
24025
24115
  * @remarks
24026
24116
  * When you call this operation, note the following items:
24027
24117
  * - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
24028
24118
  * - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
24029
- * - An Express Connect circuit in the **Rejected** state enters the **Initial** state after it is modified.
24119
+ * - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
24030
24120
  *
24031
24121
  * @param request - ModifyPhysicalConnectionAttributeRequest
24032
24122
  * @returns ModifyPhysicalConnectionAttributeResponse
@@ -24497,15 +24587,15 @@ class Client extends openapi_core_1.default {
24497
24587
  return await this.modifySslVpnClientCertWithOptions(request, runtime);
24498
24588
  }
24499
24589
  /**
24500
- * Modifies the configuration of an SSL-VPN server.
24590
+ * Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
24501
24591
  *
24502
24592
  * @remarks
24503
- * - If you want to enable two-factor identity authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
24504
- * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify any configuration other than **Name**, this operation is asynchronous.
24505
- * - When **ModifySslVpnServer** is asynchronous, the system returns a request ID first, but the configuration of the SSL-VPN server has not been modified yet. The modification task continues in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
24593
+ * - If you want to enable two-factor authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
24594
+ * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify configurations other than **Name**, this operation is asynchronous.
24595
+ * - When the **ModifySslVpnServer** operation is asynchronous, the system returns a request ID but the configuration of the SSL-VPN server has not been modified. The modification task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
24506
24596
  * - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
24507
24597
  * - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
24508
- * - The **ModifySslVpnServer** operation does not support concurrent modifications to the configuration of SSL-VPN servers under the same VPN gateway.
24598
+ * - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
24509
24599
  *
24510
24600
  * @param request - ModifySslVpnServerRequest
24511
24601
  * @param runtime - runtime options for this request RuntimeOptions
@@ -24591,15 +24681,15 @@ class Client extends openapi_core_1.default {
24591
24681
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifySslVpnServerResponse({}));
24592
24682
  }
24593
24683
  /**
24594
- * Modifies the configuration of an SSL-VPN server.
24684
+ * Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
24595
24685
  *
24596
24686
  * @remarks
24597
- * - If you want to enable two-factor identity authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
24598
- * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify any configuration other than **Name**, this operation is asynchronous.
24599
- * - When **ModifySslVpnServer** is asynchronous, the system returns a request ID first, but the configuration of the SSL-VPN server has not been modified yet. The modification task continues in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
24687
+ * - If you want to enable two-factor authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
24688
+ * - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify configurations other than **Name**, this operation is asynchronous.
24689
+ * - When the **ModifySslVpnServer** operation is asynchronous, the system returns a request ID but the configuration of the SSL-VPN server has not been modified. The modification task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
24600
24690
  * - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
24601
24691
  * - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
24602
- * - The **ModifySslVpnServer** operation does not support concurrent modifications to the configuration of SSL-VPN servers under the same VPN gateway.
24692
+ * - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
24603
24693
  *
24604
24694
  * @param request - ModifySslVpnServerRequest
24605
24695
  * @returns ModifySslVpnServerResponse
@@ -24896,7 +24986,7 @@ class Client extends openapi_core_1.default {
24896
24986
  * @remarks
24897
24987
  * - **ModifyVcoRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID, but the weight of the destination route entry has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the destination route entry weight:
24898
24988
  * - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
24899
- * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry has been modified.
24989
+ * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
24900
24990
  * - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
24901
24991
  *
24902
24992
  * @param request - ModifyVcoRouteEntryWeightRequest
@@ -24961,7 +25051,7 @@ class Client extends openapi_core_1.default {
24961
25051
  * @remarks
24962
25052
  * - **ModifyVcoRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID, but the weight of the destination route entry has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the destination route entry weight:
24963
25053
  * - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
24964
- * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry has been modified.
25054
+ * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
24965
25055
  * - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
24966
25056
  *
24967
25057
  * @param request - ModifyVcoRouteEntryWeightRequest
@@ -25181,6 +25271,60 @@ class Client extends openapi_core_1.default {
25181
25271
  let runtime = new $dara.RuntimeOptions({});
25182
25272
  return await this.modifyVpcAttributeWithOptions(request, runtime);
25183
25273
  }
25274
+ /**
25275
+ * Modifies the primary or secondary CIDR block of a VPC.
25276
+ *
25277
+ * @param request - ModifyVpcCidrBlockRequest
25278
+ * @param runtime - runtime options for this request RuntimeOptions
25279
+ * @returns ModifyVpcCidrBlockResponse
25280
+ */
25281
+ async modifyVpcCidrBlockWithOptions(request, runtime) {
25282
+ request.validate();
25283
+ let query = {};
25284
+ if (!$dara.isNull(request.clientToken)) {
25285
+ query["ClientToken"] = request.clientToken;
25286
+ }
25287
+ if (!$dara.isNull(request.dryRun)) {
25288
+ query["DryRun"] = request.dryRun;
25289
+ }
25290
+ if (!$dara.isNull(request.originalCidrBlock)) {
25291
+ query["OriginalCidrBlock"] = request.originalCidrBlock;
25292
+ }
25293
+ if (!$dara.isNull(request.regionId)) {
25294
+ query["RegionId"] = request.regionId;
25295
+ }
25296
+ if (!$dara.isNull(request.targetCidrBlock)) {
25297
+ query["TargetCidrBlock"] = request.targetCidrBlock;
25298
+ }
25299
+ if (!$dara.isNull(request.vpcId)) {
25300
+ query["VpcId"] = request.vpcId;
25301
+ }
25302
+ let req = new openapi_core_2.$OpenApiUtil.OpenApiRequest({
25303
+ query: openapi_core_2.OpenApiUtil.query(query),
25304
+ });
25305
+ let params = new openapi_core_2.$OpenApiUtil.Params({
25306
+ action: "ModifyVpcCidrBlock",
25307
+ version: "2016-04-28",
25308
+ protocol: "HTTPS",
25309
+ pathname: "/",
25310
+ method: "POST",
25311
+ authType: "AK",
25312
+ style: "RPC",
25313
+ reqBodyType: "formData",
25314
+ bodyType: "json",
25315
+ });
25316
+ return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyVpcCidrBlockResponse({}));
25317
+ }
25318
+ /**
25319
+ * Modifies the primary or secondary CIDR block of a VPC.
25320
+ *
25321
+ * @param request - ModifyVpcCidrBlockRequest
25322
+ * @returns ModifyVpcCidrBlockResponse
25323
+ */
25324
+ async modifyVpcCidrBlock(request) {
25325
+ let runtime = new $dara.RuntimeOptions({});
25326
+ return await this.modifyVpcCidrBlockWithOptions(request, runtime);
25327
+ }
25184
25328
  /**
25185
25329
  * Modifies the configuration of a prefix list.
25186
25330
  *
@@ -25274,13 +25418,13 @@ class Client extends openapi_core_1.default {
25274
25418
  * Modifies the configuration of an IPsec-VPN connection.
25275
25419
  *
25276
25420
  * @remarks
25277
- * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
25278
- * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
25279
- * - **ModifyVpnAttachmentAttribute** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the operation is still being performed in the system background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection:
25421
+ * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
25422
+ * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
25423
+ * - The **ModifyVpnAttachmentAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the IPsec-VPN connection configuration has not been modified. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection configuration:
25280
25424
  * - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
25281
25425
  * - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
25282
- * - **ModifyVpnAttachmentAttribute** does not support concurrent modification of the IPsec-VPN connection configuration.
25283
- * - When you call **ModifyVpnAttachmentAttribute**, you cannot modify the gateway type of the IPsec-VPN connection.
25426
+ * - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
25427
+ * - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
25284
25428
  *
25285
25429
  * @param request - ModifyVpnAttachmentAttributeRequest
25286
25430
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25379,13 +25523,13 @@ class Client extends openapi_core_1.default {
25379
25523
  * Modifies the configuration of an IPsec-VPN connection.
25380
25524
  *
25381
25525
  * @remarks
25382
- * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
25383
- * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, you can configure the following request parameters: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
25384
- * - **ModifyVpnAttachmentAttribute** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the operation is still being performed in the system background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection:
25526
+ * - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
25527
+ * - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
25528
+ * - The **ModifyVpnAttachmentAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the IPsec-VPN connection configuration has not been modified. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection configuration:
25385
25529
  * - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
25386
25530
  * - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
25387
- * - **ModifyVpnAttachmentAttribute** does not support concurrent modification of the IPsec-VPN connection configuration.
25388
- * - When you call **ModifyVpnAttachmentAttribute**, you cannot modify the gateway type of the IPsec-VPN connection.
25531
+ * - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
25532
+ * - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
25389
25533
  *
25390
25534
  * @param request - ModifyVpnAttachmentAttributeRequest
25391
25535
  * @returns ModifyVpnAttachmentAttributeResponse
@@ -25398,14 +25542,11 @@ class Client extends openapi_core_1.default {
25398
25542
  * Modifies the configuration of an IPsec-VPN connection.
25399
25543
  *
25400
25544
  * @remarks
25401
- * - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25545
+ * - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25402
25546
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
25403
- * - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25547
+ * - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25404
25548
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
25405
- * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the configuration of the IPsec-VPN connection is not yet modified. The modification node runs in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
25406
- * - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
25407
- * - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
25408
- * - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
25549
+ * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID, but the configuration of the IPsec-VPN connection has not been modified yet. The modification node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
25409
25550
  *
25410
25551
  * @param request - ModifyVpnConnectionAttributeRequest
25411
25552
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25501,14 +25642,11 @@ class Client extends openapi_core_1.default {
25501
25642
  * Modifies the configuration of an IPsec-VPN connection.
25502
25643
  *
25503
25644
  * @remarks
25504
- * - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25645
+ * - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25505
25646
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
25506
- * - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25647
+ * - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25507
25648
  * **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
25508
- * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the configuration of the IPsec-VPN connection is not yet modified. The modification node runs in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
25509
- * - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
25510
- * - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
25511
- * - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
25649
+ * - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID, but the configuration of the IPsec-VPN connection has not been modified yet. The modification node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
25512
25650
  *
25513
25651
  * @param request - ModifyVpnConnectionAttributeRequest
25514
25652
  * @returns ModifyVpnConnectionAttributeResponse
@@ -25521,7 +25659,7 @@ class Client extends openapi_core_1.default {
25521
25659
  * Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
25522
25660
  *
25523
25661
  * @remarks
25524
- * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
25662
+ * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration of the VPN gateway has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
25525
25663
  * - If the VPN gateway is in the **updating** state, the configuration is being modified.
25526
25664
  * - If the VPN gateway is in the **active** state, the configuration has been modified.
25527
25665
  * - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
@@ -25583,7 +25721,7 @@ class Client extends openapi_core_1.default {
25583
25721
  * Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
25584
25722
  *
25585
25723
  * @remarks
25586
- * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
25724
+ * - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration of the VPN gateway has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
25587
25725
  * - If the VPN gateway is in the **updating** state, the configuration is being modified.
25588
25726
  * - If the VPN gateway is in the **active** state, the configuration has been modified.
25589
25727
  * - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
@@ -25696,13 +25834,13 @@ class Client extends openapi_core_1.default {
25696
25834
  return await this.modifyVpnPbrRouteEntryAttributeWithOptions(request, runtime);
25697
25835
  }
25698
25836
  /**
25699
- * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing entry.
25837
+ * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
25700
25838
  *
25701
25839
  * @remarks
25702
- * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID, but the policy-based routing entry has not been modified yet. The modification node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway to determine the modification status of the policy-based routing entry:
25703
- * - If the VPN gateway instance is in the **updating** state, the policy-based routing entry is being modified.
25704
- * - If the VPN gateway instance is in the **active** state, the policy-based routing entry has been modified.
25705
- * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing entries on the same VPN gateway instance.
25840
+ * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID. However, the policy-based routing has not been modified yet because the modification node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway and determine the modification status of the policy-based routing:
25841
+ * - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
25842
+ * - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
25843
+ * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
25706
25844
  *
25707
25845
  * @param request - ModifyVpnPbrRouteEntryPriorityRequest
25708
25846
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25767,13 +25905,13 @@ class Client extends openapi_core_1.default {
25767
25905
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyVpnPbrRouteEntryPriorityResponse({}));
25768
25906
  }
25769
25907
  /**
25770
- * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing entry.
25908
+ * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
25771
25909
  *
25772
25910
  * @remarks
25773
- * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID, but the policy-based routing entry has not been modified yet. The modification node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway to determine the modification status of the policy-based routing entry:
25774
- * - If the VPN gateway instance is in the **updating** state, the policy-based routing entry is being modified.
25775
- * - If the VPN gateway instance is in the **active** state, the policy-based routing entry has been modified.
25776
- * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing entries on the same VPN gateway instance.
25911
+ * - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID. However, the policy-based routing has not been modified yet because the modification node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway and determine the modification status of the policy-based routing:
25912
+ * - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
25913
+ * - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
25914
+ * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
25777
25915
  *
25778
25916
  * @param request - ModifyVpnPbrRouteEntryPriorityRequest
25779
25917
  * @returns ModifyVpnPbrRouteEntryPriorityResponse
@@ -25880,12 +26018,12 @@ class Client extends openapi_core_1.default {
25880
26018
  * Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
25881
26019
  *
25882
26020
  * @remarks
25883
- * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if you successfully modify it by calling this operation.
26021
+ * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if it is modified by calling this operation.
25884
26022
  * - If active/standby destination routes exist on a VPN gateway instance and you want to modify the weight of the active destination route, delete the standby destination route first. After the active destination route is modified, reconfigure the standby destination route. If you want to modify the weight of the standby destination route, delete the active destination route first. After the standby destination route is modified, reconfigure the active destination route. To delete a destination route, see [DeleteVpnRouteEntry](https://help.aliyun.com/document_detail/2526961.html).
25885
- * - The **ModifyVpnRouteEntryWeight** operation is asynchronous. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route is not yet modified, and the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
26023
+ * - **ModifyVpnRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
25886
26024
  * - If the VPN destination route is in the **updating** state, the weight is being modified.
25887
- * - If the VPN destination route is in the **active** state, the weight is modified.
25888
- * - The **ModifyVpnRouteEntryWeight** operation does not support concurrent weight modifications for destination routes on the same VPN gateway.
26025
+ * - If the VPN destination route is in the **active** state, the weight has been modified.
26026
+ * - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
25889
26027
  *
25890
26028
  * @param request - ModifyVpnRouteEntryWeightRequest
25891
26029
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25950,12 +26088,12 @@ class Client extends openapi_core_1.default {
25950
26088
  * Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
25951
26089
  *
25952
26090
  * @remarks
25953
- * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if you successfully modify it by calling this operation.
26091
+ * > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if it is modified by calling this operation.
25954
26092
  * - If active/standby destination routes exist on a VPN gateway instance and you want to modify the weight of the active destination route, delete the standby destination route first. After the active destination route is modified, reconfigure the standby destination route. If you want to modify the weight of the standby destination route, delete the active destination route first. After the standby destination route is modified, reconfigure the active destination route. To delete a destination route, see [DeleteVpnRouteEntry](https://help.aliyun.com/document_detail/2526961.html).
25955
- * - The **ModifyVpnRouteEntryWeight** operation is asynchronous. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route is not yet modified, and the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
26093
+ * - **ModifyVpnRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
25956
26094
  * - If the VPN destination route is in the **updating** state, the weight is being modified.
25957
- * - If the VPN destination route is in the **active** state, the weight is modified.
25958
- * - The **ModifyVpnRouteEntryWeight** operation does not support concurrent weight modifications for destination routes on the same VPN gateway.
26095
+ * - If the VPN destination route is in the **active** state, the weight has been modified.
26096
+ * - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
25959
26097
  *
25960
26098
  * @param request - ModifyVpnRouteEntryWeightRequest
25961
26099
  * @returns ModifyVpnRouteEntryWeightResponse
@@ -25968,7 +26106,7 @@ class Client extends openapi_core_1.default {
25968
26106
  * Modifies the resource group to which a cloud resource belongs.
25969
26107
  *
25970
26108
  * @remarks
25971
- * The **ChangeResourceGroup** operation does not support concurrent modifications to the resource group of Express Connect circuit resources within the same Express Connect circuit instance.
26109
+ * The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
25972
26110
  *
25973
26111
  * @param request - MoveResourceGroupRequest
25974
26112
  * @param runtime - runtime options for this request RuntimeOptions
@@ -26021,7 +26159,7 @@ class Client extends openapi_core_1.default {
26021
26159
  * Modifies the resource group to which a cloud resource belongs.
26022
26160
  *
26023
26161
  * @remarks
26024
- * The **ChangeResourceGroup** operation does not support concurrent modifications to the resource group of Express Connect circuit resources within the same Express Connect circuit instance.
26162
+ * The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
26025
26163
  *
26026
26164
  * @param request - MoveResourceGroupRequest
26027
26165
  * @returns MoveResourceGroupResponse
@@ -26597,16 +26735,16 @@ class Client extends openapi_core_1.default {
26597
26735
  return await this.recoverVirtualBorderRouterWithOptions(request, runtime);
26598
26736
  }
26599
26737
  /**
26600
- * Releases a specified Elastic IP Address (EIP).
26738
+ * Releases a specified elastic IP address (EIP).
26601
26739
  *
26602
26740
  * @remarks
26603
- * Before you invoke this operation, take note of the following items:
26604
- * - Before releasing an EIP, make sure the following conditions are met:
26741
+ * Before you invoke this operation, take note of the following information:
26742
+ * - Before you release an EIP, make sure that the following conditions are met:
26605
26743
  * - Only EIPs in the **Available** state can be released.
26606
26744
  * - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
26607
- * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID, but the EIP instance has not been released yet. The release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
26608
- * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
26609
- * - If the EIP instance cannot be found, the EIP instance has been released.
26745
+ * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP instance is not immediately released because the release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
26746
+ * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations and cannot execute other operations.
26747
+ * - If the EIP instance cannot be found, the EIP instance is released.
26610
26748
  * - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
26611
26749
  *
26612
26750
  * @param request - ReleaseEipAddressRequest
@@ -26651,16 +26789,16 @@ class Client extends openapi_core_1.default {
26651
26789
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ReleaseEipAddressResponse({}));
26652
26790
  }
26653
26791
  /**
26654
- * Releases a specified Elastic IP Address (EIP).
26792
+ * Releases a specified elastic IP address (EIP).
26655
26793
  *
26656
26794
  * @remarks
26657
- * Before you invoke this operation, take note of the following items:
26658
- * - Before releasing an EIP, make sure the following conditions are met:
26795
+ * Before you invoke this operation, take note of the following information:
26796
+ * - Before you release an EIP, make sure that the following conditions are met:
26659
26797
  * - Only EIPs in the **Available** state can be released.
26660
26798
  * - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
26661
- * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID, but the EIP instance has not been released yet. The release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
26662
- * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
26663
- * - If the EIP instance cannot be found, the EIP instance has been released.
26799
+ * - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP instance is not immediately released because the release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
26800
+ * - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations and cannot execute other operations.
26801
+ * - If the EIP instance cannot be found, the EIP instance is released.
26664
26802
  * - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
26665
26803
  *
26666
26804
  * @param request - ReleaseEipAddressRequest
@@ -28532,10 +28670,10 @@ class Client extends openapi_core_1.default {
28532
28670
  return await this.unassociateRouteTableWithOptions(request, runtime);
28533
28671
  }
28534
28672
  /**
28535
- * Calls the UnassociateVpcCidrBlock operation to delete a secondary CIDR block from a VPC.
28673
+ * Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
28536
28674
  *
28537
28675
  * @remarks
28538
- * - Before you delete a secondary CIDR block from a VPC, delete the vSwitches created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
28676
+ * - Before deleting a secondary CIDR block from a VPC, delete the vSwitches that are created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
28539
28677
  * - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
28540
28678
  *
28541
28679
  * @param request - UnassociateVpcCidrBlockRequest
@@ -28589,10 +28727,10 @@ class Client extends openapi_core_1.default {
28589
28727
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.UnassociateVpcCidrBlockResponse({}));
28590
28728
  }
28591
28729
  /**
28592
- * Calls the UnassociateVpcCidrBlock operation to delete a secondary CIDR block from a VPC.
28730
+ * Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
28593
28731
  *
28594
28732
  * @remarks
28595
- * - Before you delete a secondary CIDR block from a VPC, delete the vSwitches created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
28733
+ * - Before deleting a secondary CIDR block from a VPC, delete the vSwitches that are created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
28596
28734
  * - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
28597
28735
  *
28598
28736
  * @param request - UnassociateVpcCidrBlockRequest
@@ -28666,7 +28804,7 @@ class Client extends openapi_core_1.default {
28666
28804
  return await this.untagResourcesForExpressConnectWithOptions(request, runtime);
28667
28805
  }
28668
28806
  /**
28669
- * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
28807
+ * Modifies the configuration of a DHCP options set.
28670
28808
  *
28671
28809
  * @param request - UpdateDhcpOptionsSetAttributeRequest
28672
28810
  * @param runtime - runtime options for this request RuntimeOptions
@@ -28734,7 +28872,7 @@ class Client extends openapi_core_1.default {
28734
28872
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateDhcpOptionsSetAttributeResponse({}));
28735
28873
  }
28736
28874
  /**
28737
- * Modifies the configuration of a DHCP options set by calling the UpdateDhcpOptionsSetAttribute operation.
28875
+ * Modifies the configuration of a DHCP options set.
28738
28876
  *
28739
28877
  * @param request - UpdateDhcpOptionsSetAttributeRequest
28740
28878
  * @returns UpdateDhcpOptionsSetAttributeResponse
@@ -28981,7 +29119,7 @@ class Client extends openapi_core_1.default {
28981
29119
  return await this.updateGatewayRouteTableEntryAttributeWithOptions(request, runtime);
28982
29120
  }
28983
29121
  /**
28984
- * Updates the configuration of an IPsec server by calling the UpdateIpsecServer operation.
29122
+ * Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
28985
29123
  *
28986
29124
  * @remarks
28987
29125
  * - If you modify only the **IpsecServerName** of the IPsec server, this operation is synchronous. If you modify configurations other than **IpsecServerName**, this operation is asynchronous.
@@ -29050,7 +29188,7 @@ class Client extends openapi_core_1.default {
29050
29188
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateIpsecServerResponse({}));
29051
29189
  }
29052
29190
  /**
29053
- * Updates the configuration of an IPsec server by calling the UpdateIpsecServer operation.
29191
+ * Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
29054
29192
  *
29055
29193
  * @remarks
29056
29194
  * - If you modify only the **IpsecServerName** of the IPsec server, this operation is synchronous. If you modify configurations other than **IpsecServerName**, this operation is asynchronous.