@alicloud/vpc20160428 7.2.4 → 7.2.5

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 (248) hide show
  1. package/dist/client.d.ts +232 -228
  2. package/dist/client.js +263 -255
  3. package/dist/client.js.map +1 -1
  4. package/dist/models/ActivateRouterInterfaceRequest.d.ts +1 -1
  5. package/dist/models/AssociateMacSecKeyRequest.d.ts +3 -3
  6. package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.d.ts +5 -7
  7. package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.js.map +1 -1
  8. package/dist/models/AssociateVpnGatewayWithCertificateRequest.d.ts +3 -3
  9. package/dist/models/AttachVbrToVpconnRequest.d.ts +3 -3
  10. package/dist/models/CancelPhysicalConnectionRequest.d.ts +1 -1
  11. package/dist/models/CheckVpnBgpEnabledRequest.d.ts +1 -1
  12. package/dist/models/CompletePhysicalConnectionLoarequest.d.ts +4 -4
  13. package/dist/models/CreateCustomerGatewayRequest.d.ts +4 -4
  14. package/dist/models/CreateCustomerGatewayResponseBody.d.ts +2 -2
  15. package/dist/models/CreateFailoverTestJobRequest.d.ts +5 -5
  16. package/dist/models/CreateIpsecServerRequest.d.ts +2 -2
  17. package/dist/models/CreatePhysicalConnectionRequest.d.ts +13 -11
  18. package/dist/models/CreatePhysicalConnectionRequest.js.map +1 -1
  19. package/dist/models/CreatePhysicalConnectionSetupOrderRequest.d.ts +10 -8
  20. package/dist/models/CreatePhysicalConnectionSetupOrderRequest.js.map +1 -1
  21. package/dist/models/CreateSslVpnServerRequest.d.ts +11 -11
  22. package/dist/models/CreateVbrHaRequest.d.ts +5 -5
  23. package/dist/models/CreateVbrHaResponseBody.d.ts +1 -1
  24. package/dist/models/CreateVcoRouteEntryRequest.d.ts +2 -2
  25. package/dist/models/CreateVcoRouteEntryResponseBody.d.ts +1 -1
  26. package/dist/models/CreateVpconnFromVbrRequest.d.ts +2 -2
  27. package/dist/models/CreateVpnAttachmentRequest.d.ts +73 -133
  28. package/dist/models/CreateVpnAttachmentRequest.js.map +1 -1
  29. package/dist/models/CreateVpnAttachmentResponseBody.d.ts +3 -3
  30. package/dist/models/CreateVpnConnectionRequest.d.ts +95 -131
  31. package/dist/models/CreateVpnConnectionRequest.js.map +1 -1
  32. package/dist/models/CreateVpnConnectionResponseBody.d.ts +1 -1
  33. package/dist/models/CreateVpnGatewayRequest.d.ts +17 -17
  34. package/dist/models/CreateVpnGatewayResponseBody.d.ts +2 -2
  35. package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +13 -13
  36. package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +6 -6
  37. package/dist/models/CreateVswitchCidrReservationRequest.d.ts +15 -7
  38. package/dist/models/CreateVswitchCidrReservationRequest.js +2 -0
  39. package/dist/models/CreateVswitchCidrReservationRequest.js.map +1 -1
  40. package/dist/models/CreateVswitchRequest.d.ts +9 -9
  41. package/dist/models/DeleteBgpGroupRequest.d.ts +2 -2
  42. package/dist/models/DeleteFailoverTestJobRequest.d.ts +4 -4
  43. package/dist/models/DeleteIpsecServerRequest.d.ts +4 -4
  44. package/dist/models/DeleteNatGatewayRequest.d.ts +4 -4
  45. package/dist/models/DeleteVbrHaRequest.d.ts +3 -3
  46. package/dist/models/DeleteVpnGatewayRequest.d.ts +3 -3
  47. package/dist/models/DeleteVpnRouteEntryRequest.d.ts +2 -2
  48. package/dist/models/DescribeCustomerGatewayRequest.d.ts +1 -1
  49. package/dist/models/DescribeCustomerGatewayResponseBody.d.ts +2 -2
  50. package/dist/models/DescribeCustomerGatewaysRequest.d.ts +1 -1
  51. package/dist/models/DescribeEipAddressesRequest.d.ts +7 -75
  52. package/dist/models/DescribeEipAddressesRequest.js.map +1 -1
  53. package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.d.ts +5 -3
  54. package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.js.map +1 -1
  55. package/dist/models/DescribeExpressConnectTrafficQosQueueResponseBody.d.ts +12 -12
  56. package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.d.ts +10 -6
  57. package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.js.map +1 -1
  58. package/dist/models/DescribeExpressConnectTrafficQosRuleResponseBody.d.ts +16 -16
  59. package/dist/models/DescribeFailoverTestJobRequest.d.ts +2 -2
  60. package/dist/models/DescribeFailoverTestJobResponseBody.d.ts +6 -6
  61. package/dist/models/DescribeFailoverTestJobsRequest.d.ts +8 -8
  62. package/dist/models/DescribeFailoverTestJobsResponseBody.d.ts +14 -14
  63. package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +1 -1
  64. package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +8 -4
  65. package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
  66. package/dist/models/DescribePhysicalConnectionsRequest.d.ts +4 -0
  67. package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
  68. package/dist/models/DescribeRouterInterfaceAttributeResponseBody.d.ts +22 -22
  69. package/dist/models/DescribeSslVpnClientCertRequest.d.ts +1 -1
  70. package/dist/models/DescribeSslVpnClientCertResponseBody.d.ts +3 -3
  71. package/dist/models/DescribeSslVpnServersRequest.d.ts +1 -1
  72. package/dist/models/DescribeSslVpnServersResponseBody.d.ts +1 -1
  73. package/dist/models/DescribeTagKeysForExpressConnectRequest.d.ts +2 -0
  74. package/dist/models/DescribeTagKeysForExpressConnectRequest.js.map +1 -1
  75. package/dist/models/DescribeVbrHaRequest.d.ts +6 -6
  76. package/dist/models/DescribeVbrHaResponseBody.d.ts +2 -2
  77. package/dist/models/DescribeVcoRouteEntriesResponseBody.d.ts +10 -10
  78. package/dist/models/DescribeVirtualBorderRoutersRequest.d.ts +6 -26
  79. package/dist/models/DescribeVirtualBorderRoutersRequest.js.map +1 -1
  80. package/dist/models/DescribeVirtualBorderRoutersResponseBody.d.ts +2 -2
  81. package/dist/models/DescribeVpcsRequest.d.ts +4 -4
  82. package/dist/models/DescribeVpcsResponseBody.d.ts +1 -1
  83. package/dist/models/DescribeVpnAttachmentsRequest.d.ts +4 -4
  84. package/dist/models/DescribeVpnAttachmentsResponseBody.d.ts +9 -9
  85. package/dist/models/DescribeVpnConnectionLogsRequest.d.ts +2 -2
  86. package/dist/models/DescribeVpnConnectionLogsResponseBody.d.ts +1 -1
  87. package/dist/models/DescribeVpnConnectionRequest.d.ts +1 -1
  88. package/dist/models/DescribeVpnConnectionResponseBody.d.ts +21 -72
  89. package/dist/models/DescribeVpnConnectionResponseBody.js.map +1 -1
  90. package/dist/models/DescribeVpnConnectionsRequest.d.ts +6 -8
  91. package/dist/models/DescribeVpnConnectionsRequest.js.map +1 -1
  92. package/dist/models/DescribeVpnCrossAccountAuthorizationsRequest.d.ts +2 -2
  93. package/dist/models/DescribeVpnCrossAccountAuthorizationsResponseBody.d.ts +5 -5
  94. package/dist/models/DescribeVpnGatewayResponseBody.d.ts +8 -8
  95. package/dist/models/DescribeVpnGatewaysRequest.d.ts +2 -2
  96. package/dist/models/DescribeVpnGatewaysResponseBody.d.ts +1 -1
  97. package/dist/models/DescribeVpnPbrRouteEntriesRequest.d.ts +1 -1
  98. package/dist/models/DescribeVpnPbrRouteEntriesResponseBody.d.ts +1 -1
  99. package/dist/models/DescribeVpnSslServerLogsRequest.d.ts +2 -2
  100. package/dist/models/DescribeVswitchesRequest.d.ts +7 -7
  101. package/dist/models/DescribeVswitchesResponseBody.d.ts +1 -1
  102. package/dist/models/DiagnoseVpnGatewayRequest.d.ts +1 -1
  103. package/dist/models/DiagnoseVpnGatewayResponseBody.d.ts +2 -2
  104. package/dist/models/DisassociateMacSecKeyRequest.d.ts +2 -2
  105. package/dist/models/DissociateVpnGatewayWithCertificateRequest.d.ts +2 -2
  106. package/dist/models/DownloadVpnConnectionConfigResponseBody.d.ts +11 -11
  107. package/dist/models/GetVpnGatewayDiagnoseResultRequest.d.ts +3 -3
  108. package/dist/models/GetVpnGatewayDiagnoseResultResponseBody.d.ts +12 -12
  109. package/dist/models/GrantInstanceToVbrRequest.d.ts +8 -8
  110. package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +8 -8
  111. package/dist/models/ListBusinessAccessPointsResponseBody.d.ts +40 -2
  112. package/dist/models/ListBusinessAccessPointsResponseBody.js.map +1 -1
  113. package/dist/models/ListIpsecServerLogsRequest.d.ts +2 -2
  114. package/dist/models/ListIpsecServerLogsResponseBody.d.ts +1 -1
  115. package/dist/models/ListIpsecServersRequest.d.ts +3 -3
  116. package/dist/models/ListIpsecServersResponseBody.d.ts +7 -7
  117. package/dist/models/ListVpnCertificateAssociationsRequest.d.ts +3 -3
  118. package/dist/models/ListVpnCertificateAssociationsResponseBody.d.ts +2 -2
  119. package/dist/models/ModifyCustomerGatewayAttributeRequest.d.ts +1 -1
  120. package/dist/models/ModifySslVpnServerRequest.d.ts +11 -11
  121. package/dist/models/ModifySslVpnServerResponseBody.d.ts +1 -1
  122. package/dist/models/ModifyVcoRouteEntryWeightRequest.d.ts +4 -4
  123. package/dist/models/ModifyVpnAttachmentAttributeRequest.d.ts +57 -133
  124. package/dist/models/ModifyVpnAttachmentAttributeRequest.js.map +1 -1
  125. package/dist/models/ModifyVpnAttachmentAttributeResponseBody.d.ts +54 -96
  126. package/dist/models/ModifyVpnAttachmentAttributeResponseBody.js.map +1 -1
  127. package/dist/models/ModifyVpnConnectionAttributeRequest.d.ts +77 -148
  128. package/dist/models/ModifyVpnConnectionAttributeRequest.js.map +1 -1
  129. package/dist/models/ModifyVpnConnectionAttributeResponseBody.d.ts +25 -52
  130. package/dist/models/ModifyVpnConnectionAttributeResponseBody.js.map +1 -1
  131. package/dist/models/ModifyVpnGatewayAttributeRequest.d.ts +5 -5
  132. package/dist/models/ModifyVpnPbrRouteEntryPriorityRequest.d.ts +5 -5
  133. package/dist/models/ModifyVpnRouteEntryWeightRequest.d.ts +2 -2
  134. package/dist/models/MoveVpnResourceGroupRequest.d.ts +2 -2
  135. package/dist/models/UpdateIpsecServerRequest.d.ts +1 -1
  136. package/package.json +1 -1
  137. package/src/client.ts +264 -255
  138. package/src/models/ActivateRouterInterfaceRequest.ts +1 -1
  139. package/src/models/AssociateMacSecKeyRequest.ts +3 -3
  140. package/src/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.ts +5 -7
  141. package/src/models/AssociateVpnGatewayWithCertificateRequest.ts +3 -3
  142. package/src/models/AttachVbrToVpconnRequest.ts +3 -3
  143. package/src/models/CancelPhysicalConnectionRequest.ts +1 -1
  144. package/src/models/CheckVpnBgpEnabledRequest.ts +1 -1
  145. package/src/models/CompletePhysicalConnectionLoarequest.ts +4 -4
  146. package/src/models/CreateCustomerGatewayRequest.ts +4 -4
  147. package/src/models/CreateCustomerGatewayResponseBody.ts +2 -2
  148. package/src/models/CreateFailoverTestJobRequest.ts +5 -5
  149. package/src/models/CreateIpsecServerRequest.ts +2 -2
  150. package/src/models/CreatePhysicalConnectionRequest.ts +13 -11
  151. package/src/models/CreatePhysicalConnectionSetupOrderRequest.ts +10 -8
  152. package/src/models/CreateSslVpnServerRequest.ts +11 -11
  153. package/src/models/CreateVbrHaRequest.ts +5 -5
  154. package/src/models/CreateVbrHaResponseBody.ts +1 -1
  155. package/src/models/CreateVcoRouteEntryRequest.ts +2 -2
  156. package/src/models/CreateVcoRouteEntryResponseBody.ts +1 -1
  157. package/src/models/CreateVpconnFromVbrRequest.ts +2 -2
  158. package/src/models/CreateVpnAttachmentRequest.ts +75 -135
  159. package/src/models/CreateVpnAttachmentResponseBody.ts +3 -3
  160. package/src/models/CreateVpnConnectionRequest.ts +99 -135
  161. package/src/models/CreateVpnConnectionResponseBody.ts +1 -1
  162. package/src/models/CreateVpnGatewayRequest.ts +17 -17
  163. package/src/models/CreateVpnGatewayResponseBody.ts +2 -2
  164. package/src/models/CreateVpnPbrRouteEntryRequest.ts +13 -13
  165. package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +6 -6
  166. package/src/models/CreateVswitchCidrReservationRequest.ts +17 -7
  167. package/src/models/CreateVswitchRequest.ts +9 -9
  168. package/src/models/DeleteBgpGroupRequest.ts +2 -2
  169. package/src/models/DeleteFailoverTestJobRequest.ts +4 -4
  170. package/src/models/DeleteIpsecServerRequest.ts +4 -4
  171. package/src/models/DeleteNatGatewayRequest.ts +4 -4
  172. package/src/models/DeleteVbrHaRequest.ts +3 -3
  173. package/src/models/DeleteVpnGatewayRequest.ts +3 -3
  174. package/src/models/DeleteVpnRouteEntryRequest.ts +2 -2
  175. package/src/models/DescribeCustomerGatewayRequest.ts +1 -1
  176. package/src/models/DescribeCustomerGatewayResponseBody.ts +2 -2
  177. package/src/models/DescribeCustomerGatewaysRequest.ts +1 -1
  178. package/src/models/DescribeEipAddressesRequest.ts +8 -76
  179. package/src/models/DescribeExpressConnectTrafficQosQueueRequest.ts +5 -3
  180. package/src/models/DescribeExpressConnectTrafficQosQueueResponseBody.ts +12 -12
  181. package/src/models/DescribeExpressConnectTrafficQosRuleRequest.ts +10 -6
  182. package/src/models/DescribeExpressConnectTrafficQosRuleResponseBody.ts +16 -16
  183. package/src/models/DescribeFailoverTestJobRequest.ts +2 -2
  184. package/src/models/DescribeFailoverTestJobResponseBody.ts +6 -6
  185. package/src/models/DescribeFailoverTestJobsRequest.ts +8 -8
  186. package/src/models/DescribeFailoverTestJobsResponseBody.ts +14 -14
  187. package/src/models/DescribePhysicalConnectionLoarequest.ts +1 -1
  188. package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +8 -4
  189. package/src/models/DescribePhysicalConnectionsRequest.ts +4 -0
  190. package/src/models/DescribeRouterInterfaceAttributeResponseBody.ts +22 -22
  191. package/src/models/DescribeSslVpnClientCertRequest.ts +1 -1
  192. package/src/models/DescribeSslVpnClientCertResponseBody.ts +3 -3
  193. package/src/models/DescribeSslVpnServersRequest.ts +1 -1
  194. package/src/models/DescribeSslVpnServersResponseBody.ts +1 -1
  195. package/src/models/DescribeTagKeysForExpressConnectRequest.ts +2 -0
  196. package/src/models/DescribeVbrHaRequest.ts +6 -6
  197. package/src/models/DescribeVbrHaResponseBody.ts +2 -2
  198. package/src/models/DescribeVcoRouteEntriesResponseBody.ts +10 -10
  199. package/src/models/DescribeVirtualBorderRoutersRequest.ts +6 -26
  200. package/src/models/DescribeVirtualBorderRoutersResponseBody.ts +2 -2
  201. package/src/models/DescribeVpcsRequest.ts +4 -4
  202. package/src/models/DescribeVpcsResponseBody.ts +1 -1
  203. package/src/models/DescribeVpnAttachmentsRequest.ts +4 -4
  204. package/src/models/DescribeVpnAttachmentsResponseBody.ts +9 -9
  205. package/src/models/DescribeVpnConnectionLogsRequest.ts +2 -2
  206. package/src/models/DescribeVpnConnectionLogsResponseBody.ts +1 -1
  207. package/src/models/DescribeVpnConnectionRequest.ts +2 -2
  208. package/src/models/DescribeVpnConnectionResponseBody.ts +21 -72
  209. package/src/models/DescribeVpnConnectionsRequest.ts +7 -9
  210. package/src/models/DescribeVpnCrossAccountAuthorizationsRequest.ts +2 -2
  211. package/src/models/DescribeVpnCrossAccountAuthorizationsResponseBody.ts +5 -5
  212. package/src/models/DescribeVpnGatewayResponseBody.ts +8 -8
  213. package/src/models/DescribeVpnGatewaysRequest.ts +2 -2
  214. package/src/models/DescribeVpnGatewaysResponseBody.ts +1 -1
  215. package/src/models/DescribeVpnPbrRouteEntriesRequest.ts +1 -1
  216. package/src/models/DescribeVpnPbrRouteEntriesResponseBody.ts +1 -1
  217. package/src/models/DescribeVpnSslServerLogsRequest.ts +2 -2
  218. package/src/models/DescribeVswitchesRequest.ts +7 -7
  219. package/src/models/DescribeVswitchesResponseBody.ts +1 -1
  220. package/src/models/DiagnoseVpnGatewayRequest.ts +1 -1
  221. package/src/models/DiagnoseVpnGatewayResponseBody.ts +2 -2
  222. package/src/models/DisassociateMacSecKeyRequest.ts +2 -2
  223. package/src/models/DissociateVpnGatewayWithCertificateRequest.ts +2 -2
  224. package/src/models/DownloadVpnConnectionConfigResponseBody.ts +11 -11
  225. package/src/models/GetVpnGatewayDiagnoseResultRequest.ts +3 -3
  226. package/src/models/GetVpnGatewayDiagnoseResultResponseBody.ts +12 -12
  227. package/src/models/GrantInstanceToVbrRequest.ts +8 -8
  228. package/src/models/GrantInstanceToVbrShrinkRequest.ts +8 -8
  229. package/src/models/ListBusinessAccessPointsResponseBody.ts +40 -2
  230. package/src/models/ListIpsecServerLogsRequest.ts +2 -2
  231. package/src/models/ListIpsecServerLogsResponseBody.ts +1 -1
  232. package/src/models/ListIpsecServersRequest.ts +3 -3
  233. package/src/models/ListIpsecServersResponseBody.ts +7 -7
  234. package/src/models/ListVpnCertificateAssociationsRequest.ts +3 -3
  235. package/src/models/ListVpnCertificateAssociationsResponseBody.ts +2 -2
  236. package/src/models/ModifyCustomerGatewayAttributeRequest.ts +1 -1
  237. package/src/models/ModifySslVpnServerRequest.ts +11 -11
  238. package/src/models/ModifySslVpnServerResponseBody.ts +1 -1
  239. package/src/models/ModifyVcoRouteEntryWeightRequest.ts +4 -4
  240. package/src/models/ModifyVpnAttachmentAttributeRequest.ts +57 -133
  241. package/src/models/ModifyVpnAttachmentAttributeResponseBody.ts +55 -97
  242. package/src/models/ModifyVpnConnectionAttributeRequest.ts +84 -155
  243. package/src/models/ModifyVpnConnectionAttributeResponseBody.ts +26 -53
  244. package/src/models/ModifyVpnGatewayAttributeRequest.ts +5 -5
  245. package/src/models/ModifyVpnPbrRouteEntryPriorityRequest.ts +5 -5
  246. package/src/models/ModifyVpnRouteEntryWeightRequest.ts +2 -2
  247. package/src/models/MoveVpnResourceGroupRequest.ts +2 -2
  248. package/src/models/UpdateIpsecServerRequest.ts +1 -1
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 and then enters the **Active** state after activation succeeds.
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 and then enters the **Active** state after activation succeeds.
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
@@ -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
@@ -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,10 @@ 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
+ * Completes the construction acceptance for an Express Connect circuit.
2751
+ *
2752
+ * @remarks
2753
+ * Completes the construction acceptance by calling the CompletePhysicalConnectionLOA operation. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. This operation can be called 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 resubmit the application. After the construction acceptance is completed, the LOA status changes to **Complete**.
2748
2754
  *
2749
2755
  * @param request - CompletePhysicalConnectionLOARequest
2750
2756
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2809,7 +2815,10 @@ class Client extends openapi_core_1.default {
2809
2815
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CompletePhysicalConnectionLOAResponse({}));
2810
2816
  }
2811
2817
  /**
2812
- * Calls CompletePhysicalConnectionLOA to complete the construction.
2818
+ * Completes the construction acceptance for an Express Connect circuit.
2819
+ *
2820
+ * @remarks
2821
+ * Completes the construction acceptance by calling the CompletePhysicalConnectionLOA operation. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. This operation can be called 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 resubmit the application. After the construction acceptance is completed, the LOA status changes to **Complete**.
2813
2822
  *
2814
2823
  * @param request - CompletePhysicalConnectionLOARequest
2815
2824
  * @returns CompletePhysicalConnectionLOAResponse
@@ -4059,7 +4068,7 @@ class Client extends openapi_core_1.default {
4059
4068
  *
4060
4069
  * @remarks
4061
4070
  * 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.
4071
+ * - 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.
4063
4072
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4064
4073
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4065
4074
  *
@@ -4135,7 +4144,7 @@ class Client extends openapi_core_1.default {
4135
4144
  *
4136
4145
  * @remarks
4137
4146
  * 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.
4147
+ * - 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.
4139
4148
  * - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
4140
4149
  * - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
4141
4150
  *
@@ -6760,7 +6769,7 @@ class Client extends openapi_core_1.default {
6760
6769
  * Creates an SSL-VPN server.
6761
6770
  *
6762
6771
  * @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:
6772
+ * - **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
6773
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
6765
6774
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
6766
6775
  * - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
@@ -6855,7 +6864,7 @@ class Client extends openapi_core_1.default {
6855
6864
  * Creates an SSL-VPN server.
6856
6865
  *
6857
6866
  * @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:
6867
+ * - **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
6868
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
6860
6869
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
6861
6870
  * - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
@@ -7140,18 +7149,18 @@ class Client extends openapi_core_1.default {
7140
7149
  * Creates a vSwitch.
7141
7150
  *
7142
7151
  * @remarks
7143
- * Before you begin:
7152
+ * When you call this operation to create a vSwitch, take note of the following items:
7144
7153
  * - 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.
7154
+ * - 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
7155
  * - 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
7156
  * - A cloud service instance can belong to only one vSwitch.
7148
7157
  * - vSwitches do not support multicast or broadcast.
7149
7158
  * - 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.
7159
+ * - 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:
7160
+ * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
7161
+ * - When the vSwitch is in the **Available** state, the vSwitch is available.
7153
7162
  * - 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.
7163
+ * - 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
7164
  *
7156
7165
  * @param request - CreateVSwitchRequest
7157
7166
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7222,18 +7231,18 @@ class Client extends openapi_core_1.default {
7222
7231
  * Creates a vSwitch.
7223
7232
  *
7224
7233
  * @remarks
7225
- * Before you begin:
7234
+ * When you call this operation to create a vSwitch, take note of the following items:
7226
7235
  * - 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.
7236
+ * - 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
7237
  * - 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
7238
  * - A cloud service instance can belong to only one vSwitch.
7230
7239
  * - vSwitches do not support multicast or broadcast.
7231
7240
  * - 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.
7241
+ * - 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:
7242
+ * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
7243
+ * - When the vSwitch is in the **Available** state, the vSwitch is available.
7235
7244
  * - 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.
7245
+ * - 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
7246
  *
7238
7247
  * @param request - CreateVSwitchRequest
7239
7248
  * @returns CreateVSwitchResponse
@@ -7251,7 +7260,7 @@ class Client extends openapi_core_1.default {
7251
7260
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
7252
7261
  * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
7253
7262
  * - 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:
7263
+ * - 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
7264
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
7256
7265
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
7257
7266
  *
@@ -7268,6 +7277,9 @@ class Client extends openapi_core_1.default {
7268
7277
  if (!$dara.isNull(request.dryRun)) {
7269
7278
  query["DryRun"] = request.dryRun;
7270
7279
  }
7280
+ if (!$dara.isNull(request.ipPrefixNumber)) {
7281
+ query["IpPrefixNumber"] = request.ipPrefixNumber;
7282
+ }
7271
7283
  if (!$dara.isNull(request.ipVersion)) {
7272
7284
  query["IpVersion"] = request.ipVersion;
7273
7285
  }
@@ -7332,7 +7344,7 @@ class Client extends openapi_core_1.default {
7332
7344
  * - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
7333
7345
  * - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
7334
7346
  * - 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:
7347
+ * - 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
7348
  * - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
7337
7349
  * - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
7338
7350
  *
@@ -7344,7 +7356,7 @@ class Client extends openapi_core_1.default {
7344
7356
  return await this.createVSwitchCidrReservationWithOptions(request, runtime);
7345
7357
  }
7346
7358
  /**
7347
- * Creates a VBR failover group by calling the CreateVbrHa operation.
7359
+ * Creates a VBR failover group.
7348
7360
  *
7349
7361
  * @param request - CreateVbrHaRequest
7350
7362
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7403,7 +7415,7 @@ class Client extends openapi_core_1.default {
7403
7415
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVbrHaResponse({}));
7404
7416
  }
7405
7417
  /**
7406
- * Creates a VBR failover group by calling the CreateVbrHa operation.
7418
+ * Creates a VBR failover group.
7407
7419
  *
7408
7420
  * @param request - CreateVbrHaRequest
7409
7421
  * @returns CreateVbrHaResponse
@@ -7418,11 +7430,11 @@ class Client extends openapi_core_1.default {
7418
7430
  * @remarks
7419
7431
  * - 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
7432
  * - 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.
7433
+ * - 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
7434
  * - **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
7435
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
7424
7436
  * - 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.
7437
+ * - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
7426
7438
  *
7427
7439
  * @param request - CreateVcoRouteEntryRequest
7428
7440
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7489,11 +7501,11 @@ class Client extends openapi_core_1.default {
7489
7501
  * @remarks
7490
7502
  * - 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
7503
  * - 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.
7504
+ * - 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
7505
  * - **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
7506
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
7495
7507
  * - 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.
7508
+ * - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
7497
7509
  *
7498
7510
  * @param request - CreateVcoRouteEntryRequest
7499
7511
  * @returns CreateVcoRouteEntryResponse
@@ -7990,13 +8002,13 @@ class Client extends openapi_core_1.default {
7990
8002
  return await this.createVpcPrefixListWithOptions(request, runtime);
7991
8003
  }
7992
8004
  /**
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.
8005
+ * Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
7994
8006
  *
7995
8007
  * @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:
8008
+ * 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.
8009
+ * Before you execute the transform procedure:
7998
8010
  * 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:
8011
+ * After the transform procedure is complete:
8000
8012
  * 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
8013
  * 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
8014
  *
@@ -8039,13 +8051,13 @@ class Client extends openapi_core_1.default {
8039
8051
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpconnFromVbrResponse({}));
8040
8052
  }
8041
8053
  /**
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.
8054
+ * Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
8043
8055
  *
8044
8056
  * @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:
8057
+ * 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.
8058
+ * Before you execute the transform procedure:
8047
8059
  * 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:
8060
+ * After the transform procedure is complete:
8049
8061
  * 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
8062
  * 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
8063
  *
@@ -8057,16 +8069,11 @@ class Client extends openapi_core_1.default {
8057
8069
  return await this.createVpconnFromVbrWithOptions(request, runtime);
8058
8070
  }
8059
8071
  /**
8060
- * Creates an IPsec-VPN connection for bindng to a transit router instance by calling the CreateVpnAttachment operation.
8072
+ * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
8061
8073
  *
8062
8074
  * @remarks
8063
8075
  * >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.
8076
+ * ### Before you begin.
8070
8077
  *
8071
8078
  * @param request - CreateVpnAttachmentRequest
8072
8079
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8171,16 +8178,11 @@ class Client extends openapi_core_1.default {
8171
8178
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpnAttachmentResponse({}));
8172
8179
  }
8173
8180
  /**
8174
- * Creates an IPsec-VPN connection for bindng to a transit router instance by calling the CreateVpnAttachment operation.
8181
+ * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
8175
8182
  *
8176
8183
  * @remarks
8177
8184
  * >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.
8185
+ * ### Before you begin.
8184
8186
  *
8185
8187
  * @param request - CreateVpnAttachmentRequest
8186
8188
  * @returns CreateVpnAttachmentResponse
@@ -8196,11 +8198,8 @@ class Client extends openapi_core_1.default {
8196
8198
  * - 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
8199
  * **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
8198
8200
  * 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
8201
  * **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.
8202
+ * - 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
8203
  * - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
8205
8204
  *
8206
8205
  * @param request - CreateVpnConnectionRequest
@@ -8309,11 +8308,8 @@ class Client extends openapi_core_1.default {
8309
8308
  * - 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
8309
  * **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
8311
8310
  * 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
8311
  * **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.
8312
+ * - 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
8313
  * - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
8318
8314
  *
8319
8315
  * @param request - CreateVpnConnectionRequest
@@ -8327,8 +8323,8 @@ class Client extends openapi_core_1.default {
8327
8323
  * Creates a VPN gateway.
8328
8324
  *
8329
8325
  * @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).
8326
+ * - 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).
8327
+ * - 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
8328
  * - 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
8329
  *
8334
8330
  * - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
@@ -8421,8 +8417,8 @@ class Client extends openapi_core_1.default {
8421
8417
  * Creates a VPN gateway.
8422
8418
  *
8423
8419
  * @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).
8420
+ * - 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).
8421
+ * - 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
8422
  * - 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
8423
  *
8428
8424
  * - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
@@ -8436,18 +8432,18 @@ class Client extends openapi_core_1.default {
8436
8432
  return await this.createVpnGatewayWithOptions(request, runtime);
8437
8433
  }
8438
8434
  /**
8439
- * Creates a policy-based route for a VPN gateway by calling the CreateVpnPbrRouteEntry operation.
8435
+ * Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
8440
8436
  *
8441
8437
  * @remarks
8442
8438
  * ### 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).
8439
+ * - 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).
8440
+ * - 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
8441
  * ### 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:
8442
+ * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8443
+ * - 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.
8444
+ * - 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
8445
  * - 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.
8446
+ * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
8451
8447
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
8452
8448
  *
8453
8449
  * @param request - CreateVpnPbrRouteEntryRequest
@@ -8522,18 +8518,18 @@ class Client extends openapi_core_1.default {
8522
8518
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpnPbrRouteEntryResponse({}));
8523
8519
  }
8524
8520
  /**
8525
- * Creates a policy-based route for a VPN gateway by calling the CreateVpnPbrRouteEntry operation.
8521
+ * Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
8526
8522
  *
8527
8523
  * @remarks
8528
8524
  * ### 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).
8525
+ * - 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).
8526
+ * - 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
8527
  * ### 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:
8528
+ * - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
8529
+ * - 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.
8530
+ * - 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
8531
  * - 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.
8532
+ * - If the VPN gateway instance is in the **active** state, the policy-based route is created.
8537
8533
  * - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
8538
8534
  *
8539
8535
  * @param request - CreateVpnPbrRouteEntryRequest
@@ -8763,7 +8759,7 @@ class Client extends openapi_core_1.default {
8763
8759
  return await this.deactiveFlowLogWithOptions(request, runtime);
8764
8760
  }
8765
8761
  /**
8766
- * Deletes a specified Border Gateway Protocol (BGP) group.
8762
+ * Deletes a specified BGP group.
8767
8763
  *
8768
8764
  * @param request - DeleteBgpGroupRequest
8769
8765
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8810,7 +8806,7 @@ class Client extends openapi_core_1.default {
8810
8806
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteBgpGroupResponse({}));
8811
8807
  }
8812
8808
  /**
8813
- * Deletes a specified Border Gateway Protocol (BGP) group.
8809
+ * Deletes a specified BGP group.
8814
8810
  *
8815
8811
  * @param request - DeleteBgpGroupRequest
8816
8812
  * @returns DeleteBgpGroupResponse
@@ -9444,10 +9440,10 @@ class Client extends openapi_core_1.default {
9444
9440
  return await this.deleteExpressConnectTrafficQosRuleWithOptions(request, runtime);
9445
9441
  }
9446
9442
  /**
9447
- * Deletes an Express Connect failover test job.
9443
+ * Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
9448
9444
  *
9449
9445
  * @remarks
9450
- * Only failover test jobs in the **Pending** or **Completed** state can be deleted.
9446
+ * 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
9447
  *
9452
9448
  * @param request - DeleteFailoverTestJobRequest
9453
9449
  * @param runtime - runtime options for this request RuntimeOptions
@@ -9494,10 +9490,10 @@ class Client extends openapi_core_1.default {
9494
9490
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteFailoverTestJobResponse({}));
9495
9491
  }
9496
9492
  /**
9497
- * Deletes an Express Connect failover test job.
9493
+ * Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
9498
9494
  *
9499
9495
  * @remarks
9500
- * Only failover test jobs in the **Pending** or **Completed** state can be deleted.
9496
+ * 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
9497
  *
9502
9498
  * @param request - DeleteFailoverTestJobRequest
9503
9499
  * @returns DeleteFailoverTestJobResponse
@@ -10048,7 +10044,7 @@ class Client extends openapi_core_1.default {
10048
10044
  * Deletes an IPsec server.
10049
10045
  *
10050
10046
  * @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:
10047
+ * - **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
10048
  * - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
10053
10049
  * - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
10054
10050
  * - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
@@ -10092,7 +10088,7 @@ class Client extends openapi_core_1.default {
10092
10088
  * Deletes an IPsec server.
10093
10089
  *
10094
10090
  * @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:
10091
+ * - **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
10092
  * - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
10097
10093
  * - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
10098
10094
  * - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
@@ -10412,12 +10408,12 @@ class Client extends openapi_core_1.default {
10412
10408
  * Deletes a specified Internet NAT gateway.
10413
10409
  *
10414
10410
  * @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:
10411
+ * *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
10412
  *
10417
10413
  * - 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
10414
  * - If the NAT gateway cannot be found, the NAT gateway is deleted.
10419
10415
  *
10420
- * > The deletion of a NAT gateway is irreversible. Proceed with caution.
10416
+ * > Deleting a NAT gateway is irreversible. Proceed with caution.
10421
10417
  *
10422
10418
  * @param request - DeleteNatGatewayRequest
10423
10419
  * @param runtime - runtime options for this request RuntimeOptions
@@ -10467,12 +10463,12 @@ class Client extends openapi_core_1.default {
10467
10463
  * Deletes a specified Internet NAT gateway.
10468
10464
  *
10469
10465
  * @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:
10466
+ * *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
10467
  *
10472
10468
  * - 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
10469
  * - If the NAT gateway cannot be found, the NAT gateway is deleted.
10474
10470
  *
10475
- * > The deletion of a NAT gateway is irreversible. Proceed with caution.
10471
+ * > Deleting a NAT gateway is irreversible. Proceed with caution.
10476
10472
  *
10477
10473
  * @param request - DeleteNatGatewayRequest
10478
10474
  * @returns DeleteNatGatewayResponse
@@ -11430,10 +11426,10 @@ class Client extends openapi_core_1.default {
11430
11426
  * 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
11427
  *
11432
11428
  * @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:
11429
+ * - 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
11430
  * - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
11435
11431
  * - 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.
11432
+ * - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
11437
11433
  *
11438
11434
  * @param request - DeleteSslVpnServerRequest
11439
11435
  * @param runtime - runtime options for this request RuntimeOptions
@@ -11483,10 +11479,10 @@ class Client extends openapi_core_1.default {
11483
11479
  * 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
11480
  *
11485
11481
  * @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:
11482
+ * - 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
11483
  * - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
11488
11484
  * - 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.
11485
+ * - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
11490
11486
  *
11491
11487
  * @param request - DeleteSslVpnServerRequest
11492
11488
  * @returns DeleteSslVpnServerResponse
@@ -11864,7 +11860,7 @@ class Client extends openapi_core_1.default {
11864
11860
  return await this.deleteVSwitchCidrReservationWithOptions(request, runtime);
11865
11861
  }
11866
11862
  /**
11867
- * Deletes a VBR failover group.
11863
+ * Calls DeleteVbrHa to delete a VBR failover group.
11868
11864
  *
11869
11865
  * @param request - DeleteVbrHaRequest
11870
11866
  * @param runtime - runtime options for this request RuntimeOptions
@@ -11911,7 +11907,7 @@ class Client extends openapi_core_1.default {
11911
11907
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteVbrHaResponse({}));
11912
11908
  }
11913
11909
  /**
11914
- * Deletes a VBR failover group.
11910
+ * Calls DeleteVbrHa to delete a VBR failover group.
11915
11911
  *
11916
11912
  * @param request - DeleteVbrHaRequest
11917
11913
  * @returns DeleteVbrHaResponse
@@ -11924,7 +11920,7 @@ class Client extends openapi_core_1.default {
11924
11920
  * Deletes a destination route entry from an IPsec-VPN connection.
11925
11921
  *
11926
11922
  * @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:
11923
+ * - **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
11924
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
11929
11925
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
11930
11926
  * - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
@@ -11986,7 +11982,7 @@ class Client extends openapi_core_1.default {
11986
11982
  * Deletes a destination route entry from an IPsec-VPN connection.
11987
11983
  *
11988
11984
  * @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:
11985
+ * - **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
11986
  * - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
11991
11987
  * - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
11992
11988
  * - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
@@ -12277,11 +12273,11 @@ class Client extends openapi_core_1.default {
12277
12273
  return await this.deleteVpcPrefixListWithOptions(request, runtime);
12278
12274
  }
12279
12275
  /**
12280
- * Deletes an IPsec-VPN connection by calling the DeleteVpnAttachment operation.
12276
+ * Deletes an IPsec-VPN connection.
12281
12277
  *
12282
12278
  * @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.
12279
+ * - 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).
12280
+ * - 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
12281
  *
12286
12282
  * @param request - DeleteVpnAttachmentRequest
12287
12283
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12325,11 +12321,11 @@ class Client extends openapi_core_1.default {
12325
12321
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteVpnAttachmentResponse({}));
12326
12322
  }
12327
12323
  /**
12328
- * Deletes an IPsec-VPN connection by calling the DeleteVpnAttachment operation.
12324
+ * Deletes an IPsec-VPN connection.
12329
12325
  *
12330
12326
  * @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.
12327
+ * - 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).
12328
+ * - 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
12329
  *
12334
12330
  * @param request - DeleteVpnAttachmentRequest
12335
12331
  * @returns DeleteVpnAttachmentResponse
@@ -12342,7 +12338,7 @@ class Client extends openapi_core_1.default {
12342
12338
  * Deletes a specified IPsec-VPN connection.
12343
12339
  *
12344
12340
  * @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:
12341
+ * - **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
12342
  * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
12347
12343
  * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
12348
12344
  * - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
@@ -12396,7 +12392,7 @@ class Client extends openapi_core_1.default {
12396
12392
  * Deletes a specified IPsec-VPN connection.
12397
12393
  *
12398
12394
  * @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:
12395
+ * - **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
12396
  * - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
12401
12397
  * - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
12402
12398
  * - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
@@ -12413,7 +12409,7 @@ class Client extends openapi_core_1.default {
12413
12409
  * Deletes a specified VPN gateway.
12414
12410
  *
12415
12411
  * @remarks
12416
- * > You cannot delete a VPN gateway that has existing IPsec-VPN connections.
12412
+ * > You cannot delete a VPN gateway that has IPsec-VPN connections.
12417
12413
  *
12418
12414
  * @param request - DeleteVpnGatewayRequest
12419
12415
  * @param runtime - runtime options for this request RuntimeOptions
@@ -12463,7 +12459,7 @@ class Client extends openapi_core_1.default {
12463
12459
  * Deletes a specified VPN gateway.
12464
12460
  *
12465
12461
  * @remarks
12466
- * > You cannot delete a VPN gateway that has existing IPsec-VPN connections.
12462
+ * > You cannot delete a VPN gateway that has IPsec-VPN connections.
12467
12463
  *
12468
12464
  * @param request - DeleteVpnGatewayRequest
12469
12465
  * @returns DeleteVpnGatewayResponse
@@ -12563,7 +12559,7 @@ class Client extends openapi_core_1.default {
12563
12559
  * Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
12564
12560
  *
12565
12561
  * @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:
12562
+ * - **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
12563
  * - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
12568
12564
  * - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
12569
12565
  * - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
@@ -12628,7 +12624,7 @@ class Client extends openapi_core_1.default {
12628
12624
  * Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
12629
12625
  *
12630
12626
  * @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:
12627
+ * - **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
12628
  * - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
12633
12629
  * - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
12634
12630
  * - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
@@ -13273,10 +13269,10 @@ class Client extends openapi_core_1.default {
13273
13269
  return await this.describeEcGrantRelationWithOptions(request, runtime);
13274
13270
  }
13275
13271
  /**
13276
- * Queries Elastic IP Addresses (EIPs) created in a specified region.
13272
+ * Queries elastic IP addresses (EIPs) created in a specified region.
13277
13273
  *
13278
13274
  * @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.
13275
+ * 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
13276
  *
13281
13277
  * @param request - DescribeEipAddressesRequest
13282
13278
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13377,10 +13373,10 @@ class Client extends openapi_core_1.default {
13377
13373
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeEipAddressesResponse({}));
13378
13374
  }
13379
13375
  /**
13380
- * Queries Elastic IP Addresses (EIPs) created in a specified region.
13376
+ * Queries elastic IP addresses (EIPs) created in a specified region.
13381
13377
  *
13382
13378
  * @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.
13379
+ * 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
13380
  *
13385
13381
  * @param request - DescribeEipAddressesRequest
13386
13382
  * @returns DescribeEipAddressesResponse
@@ -13659,6 +13655,9 @@ class Client extends openapi_core_1.default {
13659
13655
  /**
13660
13656
  * Queries Express Connect QoS queues.
13661
13657
  *
13658
+ * @remarks
13659
+ * Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
13660
+ *
13662
13661
  * @param request - DescribeExpressConnectTrafficQosQueueRequest
13663
13662
  * @param runtime - runtime options for this request RuntimeOptions
13664
13663
  * @returns DescribeExpressConnectTrafficQosQueueResponse
@@ -13712,6 +13711,9 @@ class Client extends openapi_core_1.default {
13712
13711
  /**
13713
13712
  * Queries Express Connect QoS queues.
13714
13713
  *
13714
+ * @remarks
13715
+ * Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
13716
+ *
13715
13717
  * @param request - DescribeExpressConnectTrafficQosQueueRequest
13716
13718
  * @returns DescribeExpressConnectTrafficQosQueueResponse
13717
13719
  */
@@ -13786,7 +13788,7 @@ class Client extends openapi_core_1.default {
13786
13788
  return await this.describeExpressConnectTrafficQosRuleWithOptions(request, runtime);
13787
13789
  }
13788
13790
  /**
13789
- * Queries the details of an Express Connect failover test job by calling the DescribeFailoverTestJob operation.
13791
+ * Queries the details of an Express Connect failover test job.
13790
13792
  *
13791
13793
  * @param request - DescribeFailoverTestJobRequest
13792
13794
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13833,7 +13835,7 @@ class Client extends openapi_core_1.default {
13833
13835
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeFailoverTestJobResponse({}));
13834
13836
  }
13835
13837
  /**
13836
- * Queries the details of an Express Connect failover test job by calling the DescribeFailoverTestJob operation.
13838
+ * Queries the details of an Express Connect failover test job.
13837
13839
  *
13838
13840
  * @param request - DescribeFailoverTestJobRequest
13839
13841
  * @returns DescribeFailoverTestJobResponse
@@ -13843,7 +13845,7 @@ class Client extends openapi_core_1.default {
13843
13845
  return await this.describeFailoverTestJobWithOptions(request, runtime);
13844
13846
  }
13845
13847
  /**
13846
- * Queries failover test jobs of Express Connect in batches.
13848
+ * Queries Express Connect failover test jobs in batches.
13847
13849
  *
13848
13850
  * @param request - DescribeFailoverTestJobsRequest
13849
13851
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13896,7 +13898,7 @@ class Client extends openapi_core_1.default {
13896
13898
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeFailoverTestJobsResponse({}));
13897
13899
  }
13898
13900
  /**
13899
- * Queries failover test jobs of Express Connect in batches.
13901
+ * Queries Express Connect failover test jobs in batches.
13900
13902
  *
13901
13903
  * @param request - DescribeFailoverTestJobsRequest
13902
13904
  * @returns DescribeFailoverTestJobsResponse
@@ -15409,7 +15411,7 @@ class Client extends openapi_core_1.default {
15409
15411
  * Queries information about Express Connect circuits in a specified region.
15410
15412
  *
15411
15413
  * @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.
15414
+ * 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 supported filter options, refer to the description of **Key** in the **request parameters** section of this topic.
15413
15415
  *
15414
15416
  * @param request - DescribePhysicalConnectionsRequest
15415
15417
  * @param runtime - runtime options for this request RuntimeOptions
@@ -15474,7 +15476,7 @@ class Client extends openapi_core_1.default {
15474
15476
  * Queries information about Express Connect circuits in a specified region.
15475
15477
  *
15476
15478
  * @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.
15479
+ * 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 supported filter options, refer to the description of **Key** in the **request parameters** section of this topic.
15478
15480
  *
15479
15481
  * @param request - DescribePhysicalConnectionsRequest
15480
15482
  * @returns DescribePhysicalConnectionsResponse
@@ -16454,7 +16456,7 @@ class Client extends openapi_core_1.default {
16454
16456
  return await this.describeTagKeysWithOptions(request, runtime);
16455
16457
  }
16456
16458
  /**
16457
- * Calls the DescribeTagKeysForExpressConnect operation to return the tag list of Express Connect.
16459
+ * Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
16458
16460
  *
16459
16461
  * @param request - DescribeTagKeysForExpressConnectRequest
16460
16462
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16510,7 +16512,7 @@ class Client extends openapi_core_1.default {
16510
16512
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeTagKeysForExpressConnectResponse({}));
16511
16513
  }
16512
16514
  /**
16513
- * Calls the DescribeTagKeysForExpressConnect operation to return the tag list of Express Connect.
16515
+ * Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
16514
16516
  *
16515
16517
  * @param request - DescribeTagKeysForExpressConnectRequest
16516
16518
  * @returns DescribeTagKeysForExpressConnectResponse
@@ -16717,6 +16719,9 @@ class Client extends openapi_core_1.default {
16717
16719
  /**
16718
16720
  * Queries networkable information. Internal networking is performed by vSwitch.
16719
16721
  *
16722
+ * @remarks
16723
+ * 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.
16724
+ *
16720
16725
  * @param request - DescribeVSwitchesRequest
16721
16726
  * @param runtime - runtime options for this request RuntimeOptions
16722
16727
  * @returns DescribeVSwitchesResponse
@@ -16797,6 +16802,9 @@ class Client extends openapi_core_1.default {
16797
16802
  /**
16798
16803
  * Queries networkable information. Internal networking is performed by vSwitch.
16799
16804
  *
16805
+ * @remarks
16806
+ * 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.
16807
+ *
16800
16808
  * @param request - DescribeVSwitchesRequest
16801
16809
  * @returns DescribeVSwitchesResponse
16802
16810
  */
@@ -16931,7 +16939,7 @@ class Client extends openapi_core_1.default {
16931
16939
  return await this.describeVcoRouteEntriesWithOptions(request, runtime);
16932
16940
  }
16933
16941
  /**
16934
- * Queries the Virtual Border Routers (VBRs) that you have created.
16942
+ * Queries Virtual Border Routers (VBRs) that are created.
16935
16943
  *
16936
16944
  * @param request - DescribeVirtualBorderRoutersRequest
16937
16945
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16987,7 +16995,7 @@ class Client extends openapi_core_1.default {
16987
16995
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeVirtualBorderRoutersResponse({}));
16988
16996
  }
16989
16997
  /**
16990
- * Queries the Virtual Border Routers (VBRs) that you have created.
16998
+ * Queries Virtual Border Routers (VBRs) that are created.
16991
16999
  *
16992
17000
  * @param request - DescribeVirtualBorderRoutersRequest
16993
17001
  * @returns DescribeVirtualBorderRoutersResponse
@@ -17194,6 +17202,9 @@ class Client extends openapi_core_1.default {
17194
17202
  /**
17195
17203
  * Queries created VPCs.
17196
17204
  *
17205
+ * @remarks
17206
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
17207
+ *
17197
17208
  * @param request - DescribeVpcsRequest
17198
17209
  * @param runtime - runtime options for this request RuntimeOptions
17199
17210
  * @returns DescribeVpcsResponse
@@ -17268,6 +17279,9 @@ class Client extends openapi_core_1.default {
17268
17279
  /**
17269
17280
  * Queries created VPCs.
17270
17281
  *
17282
+ * @remarks
17283
+ * The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging operations. Reduce the query frequency or use sequential paging.
17284
+ *
17271
17285
  * @param request - DescribeVpcsRequest
17272
17286
  * @returns DescribeVpcsResponse
17273
17287
  */
@@ -17894,7 +17908,7 @@ class Client extends openapi_core_1.default {
17894
17908
  return await this.describeVpnRouteEntriesWithOptions(request, runtime);
17895
17909
  }
17896
17910
  /**
17897
- * Queries the logs of an SSL server by calling the DescribeVpnSslServerLogs operation.
17911
+ * Queries the logs of an SSL server.
17898
17912
  *
17899
17913
  * @param request - DescribeVpnSslServerLogsRequest
17900
17914
  * @param runtime - runtime options for this request RuntimeOptions
@@ -17956,7 +17970,7 @@ class Client extends openapi_core_1.default {
17956
17970
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeVpnSslServerLogsResponse({}));
17957
17971
  }
17958
17972
  /**
17959
- * Queries the logs of an SSL server by calling the DescribeVpnSslServerLogs operation.
17973
+ * Queries the logs of an SSL server.
17960
17974
  *
17961
17975
  * @param request - DescribeVpnSslServerLogsRequest
17962
17976
  * @returns DescribeVpnSslServerLogsResponse
@@ -18165,10 +18179,10 @@ class Client extends openapi_core_1.default {
18165
18179
  return await this.diagnoseVpnConnectionsWithOptions(request, runtime);
18166
18180
  }
18167
18181
  /**
18168
- * Diagnoses a specified VPN gateway instance with one click by calling the DiagnoseVpnGateway operation.
18182
+ * Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
18169
18183
  *
18170
18184
  * @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).
18185
+ * 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
18186
  *
18173
18187
  * @param request - DiagnoseVpnGatewayRequest
18174
18188
  * @param runtime - runtime options for this request RuntimeOptions
@@ -18212,10 +18226,10 @@ class Client extends openapi_core_1.default {
18212
18226
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DiagnoseVpnGatewayResponse({}));
18213
18227
  }
18214
18228
  /**
18215
- * Diagnoses a specified VPN gateway instance with one click by calling the DiagnoseVpnGateway operation.
18229
+ * Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
18216
18230
  *
18217
18231
  * @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).
18232
+ * 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
18233
  *
18220
18234
  * @param request - DiagnoseVpnGatewayRequest
18221
18235
  * @returns DiagnoseVpnGatewayResponse
@@ -18475,10 +18489,10 @@ class Client extends openapi_core_1.default {
18475
18489
  * Dissociates a VPN gateway from a certificate.
18476
18490
  *
18477
18491
  * @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:
18492
+ * - **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
18493
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
18480
18494
  * - 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.
18495
+ * - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
18482
18496
  *
18483
18497
  * @param request - DissociateVpnGatewayWithCertificateRequest
18484
18498
  * @param runtime - runtime options for this request RuntimeOptions
@@ -18525,10 +18539,10 @@ class Client extends openapi_core_1.default {
18525
18539
  * Dissociates a VPN gateway from a certificate.
18526
18540
  *
18527
18541
  * @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:
18542
+ * - **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
18543
  * - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
18530
18544
  * - 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.
18545
+ * - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
18532
18546
  *
18533
18547
  * @param request - DissociateVpnGatewayWithCertificateRequest
18534
18548
  * @returns DissociateVpnGatewayWithCertificateResponse
@@ -19558,10 +19572,10 @@ class Client extends openapi_core_1.default {
19558
19572
  return await this.getVpcRouteEntrySummaryWithOptions(request, runtime);
19559
19573
  }
19560
19574
  /**
19561
- * Queries the one-click diagnostic result of a VPN gateway instance by calling the GetVpnGatewayDiagnoseResult operation.
19575
+ * Queries the one-click diagnosis result of a VPN gateway instance.
19562
19576
  *
19563
19577
  * @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.
19578
+ * 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
19579
  *
19566
19580
  * @param request - GetVpnGatewayDiagnoseResultRequest
19567
19581
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19599,10 +19613,10 @@ class Client extends openapi_core_1.default {
19599
19613
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.GetVpnGatewayDiagnoseResultResponse({}));
19600
19614
  }
19601
19615
  /**
19602
- * Queries the one-click diagnostic result of a VPN gateway instance by calling the GetVpnGatewayDiagnoseResult operation.
19616
+ * Queries the one-click diagnosis result of a VPN gateway instance.
19603
19617
  *
19604
19618
  * @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.
19619
+ * 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
19620
  *
19607
19621
  * @param request - GetVpnGatewayDiagnoseResultRequest
19608
19622
  * @returns GetVpnGatewayDiagnoseResultResponse
@@ -19753,7 +19767,7 @@ class Client extends openapi_core_1.default {
19753
19767
  return await this.grantInstanceToVbrWithOptions(request, runtime);
19754
19768
  }
19755
19769
  /**
19756
- * Calls the ListBusinessAccessPoints operation to query access point information for Express Connect circuits.
19770
+ * Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
19757
19771
  *
19758
19772
  * @param request - ListBusinessAccessPointsRequest
19759
19773
  * @param runtime - runtime options for this request RuntimeOptions
@@ -19785,7 +19799,7 @@ class Client extends openapi_core_1.default {
19785
19799
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListBusinessAccessPointsResponse({}));
19786
19800
  }
19787
19801
  /**
19788
- * Calls the ListBusinessAccessPoints operation to query access point information for Express Connect circuits.
19802
+ * Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
19789
19803
  *
19790
19804
  * @param request - ListBusinessAccessPointsRequest
19791
19805
  * @returns ListBusinessAccessPointsResponse
@@ -21518,7 +21532,7 @@ class Client extends openapi_core_1.default {
21518
21532
  * @remarks
21519
21533
  * When you call **ListVpnCertificateAssociations**:
21520
21534
  * - 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.
21535
+ * - 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
21536
  * - 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
21537
  * - 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
21538
  *
@@ -21569,7 +21583,7 @@ class Client extends openapi_core_1.default {
21569
21583
  * @remarks
21570
21584
  * When you call **ListVpnCertificateAssociations**:
21571
21585
  * - 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.
21586
+ * - 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
21587
  * - 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
21588
  * - 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
21589
  *
@@ -21938,7 +21952,7 @@ class Client extends openapi_core_1.default {
21938
21952
  return await this.modifyCommonBandwidthPackageSpecWithOptions(request, runtime);
21939
21953
  }
21940
21954
  /**
21941
- * Modifies the configuration of a customer gateway by calling the ModifyCustomerGatewayAttribute operation.
21955
+ * Modifies the configuration of a customer gateway.
21942
21956
  *
21943
21957
  * @remarks
21944
21958
  * - 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 +22015,7 @@ class Client extends openapi_core_1.default {
22001
22015
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyCustomerGatewayAttributeResponse({}));
22002
22016
  }
22003
22017
  /**
22004
- * Modifies the configuration of a customer gateway by calling the ModifyCustomerGatewayAttribute operation.
22018
+ * Modifies the configuration of a customer gateway.
22005
22019
  *
22006
22020
  * @remarks
22007
22021
  * - 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 +22281,12 @@ class Client extends openapi_core_1.default {
22267
22281
  return await this.modifyExpressCloudConnectionBandwidthWithOptions(request, runtime);
22268
22282
  }
22269
22283
  /**
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.
22284
+ * 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
22285
  *
22272
22286
  * @remarks
22273
22287
  * - 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.
22288
+ * - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
22289
+ * - 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
22290
  * - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
22277
22291
  * - 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
22292
  *
@@ -22333,12 +22347,12 @@ class Client extends openapi_core_1.default {
22333
22347
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyExpressConnectTrafficQosResponse({}));
22334
22348
  }
22335
22349
  /**
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.
22350
+ * 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
22351
  *
22338
22352
  * @remarks
22339
22353
  * - 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.
22354
+ * - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
22355
+ * - 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
22356
  * - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
22343
22357
  * - 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
22358
  *
@@ -24497,15 +24511,15 @@ class Client extends openapi_core_1.default {
24497
24511
  return await this.modifySslVpnClientCertWithOptions(request, runtime);
24498
24512
  }
24499
24513
  /**
24500
- * Modifies the configuration of an SSL-VPN server.
24514
+ * Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
24501
24515
  *
24502
24516
  * @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:
24517
+ * - 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).
24518
+ * - 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.
24519
+ * - 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
24520
  * - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
24507
24521
  * - 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.
24522
+ * - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
24509
24523
  *
24510
24524
  * @param request - ModifySslVpnServerRequest
24511
24525
  * @param runtime - runtime options for this request RuntimeOptions
@@ -24591,15 +24605,15 @@ class Client extends openapi_core_1.default {
24591
24605
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifySslVpnServerResponse({}));
24592
24606
  }
24593
24607
  /**
24594
- * Modifies the configuration of an SSL-VPN server.
24608
+ * Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
24595
24609
  *
24596
24610
  * @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:
24611
+ * - 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).
24612
+ * - 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.
24613
+ * - 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
24614
  * - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
24601
24615
  * - 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.
24616
+ * - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
24603
24617
  *
24604
24618
  * @param request - ModifySslVpnServerRequest
24605
24619
  * @returns ModifySslVpnServerResponse
@@ -24896,7 +24910,7 @@ class Client extends openapi_core_1.default {
24896
24910
  * @remarks
24897
24911
  * - **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
24912
  * - 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.
24913
+ * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
24900
24914
  * - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
24901
24915
  *
24902
24916
  * @param request - ModifyVcoRouteEntryWeightRequest
@@ -24961,7 +24975,7 @@ class Client extends openapi_core_1.default {
24961
24975
  * @remarks
24962
24976
  * - **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
24977
  * - 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.
24978
+ * - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
24965
24979
  * - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
24966
24980
  *
24967
24981
  * @param request - ModifyVcoRouteEntryWeightRequest
@@ -25274,13 +25288,13 @@ class Client extends openapi_core_1.default {
25274
25288
  * Modifies the configuration of an IPsec-VPN connection.
25275
25289
  *
25276
25290
  * @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:
25291
+ * - 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**.
25292
+ * - 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**.
25293
+ * - 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
25294
  * - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
25281
25295
  * - 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.
25296
+ * - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
25297
+ * - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
25284
25298
  *
25285
25299
  * @param request - ModifyVpnAttachmentAttributeRequest
25286
25300
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25379,13 +25393,13 @@ class Client extends openapi_core_1.default {
25379
25393
  * Modifies the configuration of an IPsec-VPN connection.
25380
25394
  *
25381
25395
  * @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:
25396
+ * - 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**.
25397
+ * - 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**.
25398
+ * - 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
25399
  * - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
25386
25400
  * - 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.
25401
+ * - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
25402
+ * - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
25389
25403
  *
25390
25404
  * @param request - ModifyVpnAttachmentAttributeRequest
25391
25405
  * @returns ModifyVpnAttachmentAttributeResponse
@@ -25398,14 +25412,11 @@ class Client extends openapi_core_1.default {
25398
25412
  * Modifies the configuration of an IPsec-VPN connection.
25399
25413
  *
25400
25414
  * @remarks
25401
- * - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25415
+ * - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25402
25416
  * **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:
25417
+ * - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25404
25418
  * **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.
25419
+ * - 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
25420
  *
25410
25421
  * @param request - ModifyVpnConnectionAttributeRequest
25411
25422
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25501,14 +25512,11 @@ class Client extends openapi_core_1.default {
25501
25512
  * Modifies the configuration of an IPsec-VPN connection.
25502
25513
  *
25503
25514
  * @remarks
25504
- * - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25515
+ * - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25505
25516
  * **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:
25517
+ * - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
25507
25518
  * **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.
25519
+ * - 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
25520
  *
25513
25521
  * @param request - ModifyVpnConnectionAttributeRequest
25514
25522
  * @returns ModifyVpnConnectionAttributeResponse
@@ -25521,7 +25529,7 @@ class Client extends openapi_core_1.default {
25521
25529
  * Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
25522
25530
  *
25523
25531
  * @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:
25532
+ * - **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
25533
  * - If the VPN gateway is in the **updating** state, the configuration is being modified.
25526
25534
  * - If the VPN gateway is in the **active** state, the configuration has been modified.
25527
25535
  * - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
@@ -25583,7 +25591,7 @@ class Client extends openapi_core_1.default {
25583
25591
  * Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
25584
25592
  *
25585
25593
  * @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:
25594
+ * - **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
25595
  * - If the VPN gateway is in the **updating** state, the configuration is being modified.
25588
25596
  * - If the VPN gateway is in the **active** state, the configuration has been modified.
25589
25597
  * - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
@@ -25696,13 +25704,13 @@ class Client extends openapi_core_1.default {
25696
25704
  return await this.modifyVpnPbrRouteEntryAttributeWithOptions(request, runtime);
25697
25705
  }
25698
25706
  /**
25699
- * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing entry.
25707
+ * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
25700
25708
  *
25701
25709
  * @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.
25710
+ * - **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:
25711
+ * - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
25712
+ * - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
25713
+ * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
25706
25714
  *
25707
25715
  * @param request - ModifyVpnPbrRouteEntryPriorityRequest
25708
25716
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25767,13 +25775,13 @@ class Client extends openapi_core_1.default {
25767
25775
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyVpnPbrRouteEntryPriorityResponse({}));
25768
25776
  }
25769
25777
  /**
25770
- * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing entry.
25778
+ * Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
25771
25779
  *
25772
25780
  * @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.
25781
+ * - **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:
25782
+ * - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
25783
+ * - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
25784
+ * - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
25777
25785
  *
25778
25786
  * @param request - ModifyVpnPbrRouteEntryPriorityRequest
25779
25787
  * @returns ModifyVpnPbrRouteEntryPriorityResponse
@@ -25880,12 +25888,12 @@ class Client extends openapi_core_1.default {
25880
25888
  * Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
25881
25889
  *
25882
25890
  * @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.
25891
+ * > 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
25892
  * - 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:
25893
+ * - **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
25894
  * - 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.
25895
+ * - If the VPN destination route is in the **active** state, the weight has been modified.
25896
+ * - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
25889
25897
  *
25890
25898
  * @param request - ModifyVpnRouteEntryWeightRequest
25891
25899
  * @param runtime - runtime options for this request RuntimeOptions
@@ -25950,12 +25958,12 @@ class Client extends openapi_core_1.default {
25950
25958
  * Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
25951
25959
  *
25952
25960
  * @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.
25961
+ * > 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
25962
  * - 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:
25963
+ * - **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
25964
  * - 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.
25965
+ * - If the VPN destination route is in the **active** state, the weight has been modified.
25966
+ * - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
25959
25967
  *
25960
25968
  * @param request - ModifyVpnRouteEntryWeightRequest
25961
25969
  * @returns ModifyVpnRouteEntryWeightResponse
@@ -28981,7 +28989,7 @@ class Client extends openapi_core_1.default {
28981
28989
  return await this.updateGatewayRouteTableEntryAttributeWithOptions(request, runtime);
28982
28990
  }
28983
28991
  /**
28984
- * Updates the configuration of an IPsec server by calling the UpdateIpsecServer operation.
28992
+ * Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
28985
28993
  *
28986
28994
  * @remarks
28987
28995
  * - 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 +29058,7 @@ class Client extends openapi_core_1.default {
29050
29058
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.UpdateIpsecServerResponse({}));
29051
29059
  }
29052
29060
  /**
29053
- * Updates the configuration of an IPsec server by calling the UpdateIpsecServer operation.
29061
+ * Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
29054
29062
  *
29055
29063
  * @remarks
29056
29064
  * - 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.