@alicloud/vpc20160428 7.4.0 → 7.4.1

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 (160) hide show
  1. package/dist/client.d.ts +268 -258
  2. package/dist/client.js +289 -257
  3. package/dist/client.js.map +1 -1
  4. package/dist/models/AddCommonBandwidthPackageIpRequest.d.ts +7 -7
  5. package/dist/models/AddCommonBandwidthPackageIpsRequest.d.ts +1 -1
  6. package/dist/models/AllocateEipAddressProRequest.d.ts +49 -25
  7. package/dist/models/AllocateEipAddressProRequest.js.map +1 -1
  8. package/dist/models/AllocateEipAddressProResponseBody.d.ts +2 -2
  9. package/dist/models/AllocateEipAddressRequest.d.ts +44 -44
  10. package/dist/models/AllocateEipAddressResponseBody.d.ts +4 -4
  11. package/dist/models/AllocateEipSegmentAddressRequest.d.ts +6 -6
  12. package/dist/models/AssociateEipAddressBatchRequest.d.ts +6 -6
  13. package/dist/models/AssociateEipAddressRequest.d.ts +16 -16
  14. package/dist/models/CalculateNatGatewayCapacityUnitsRequest.d.ts +6 -6
  15. package/dist/models/CalculateNatGatewayCapacityUnitsResponseBody.d.ts +2 -2
  16. package/dist/models/CalculateNatGatewayCapacityUnitsShrinkRequest.d.ts +5 -5
  17. package/dist/models/CancelCommonBandwidthPackageIpBandwidthRequest.d.ts +21 -3
  18. package/dist/models/CancelCommonBandwidthPackageIpBandwidthRequest.js +4 -0
  19. package/dist/models/CancelCommonBandwidthPackageIpBandwidthRequest.js.map +1 -1
  20. package/dist/models/CreateFlowLogRequest.d.ts +29 -29
  21. package/dist/models/CreateFlowLogResponseBody.d.ts +3 -3
  22. package/dist/models/CreateHaVipRequest.d.ts +5 -5
  23. package/dist/models/CreateRouteEntriesRequest.d.ts +28 -28
  24. package/dist/models/CreateRouteEntriesResponseBody.d.ts +8 -8
  25. package/dist/models/CreateRouteEntryRequest.d.ts +34 -34
  26. package/dist/models/CreateRouteEntryResponseBody.d.ts +1 -1
  27. package/dist/models/CreateSslVpnServerRequest.d.ts +15 -12
  28. package/dist/models/CreateSslVpnServerRequest.js.map +1 -1
  29. package/dist/models/CreateTrafficMirrorFilterRequest.d.ts +18 -18
  30. package/dist/models/CreateTrafficMirrorFilterRulesRequest.d.ts +19 -18
  31. package/dist/models/CreateTrafficMirrorFilterRulesRequest.js.map +1 -1
  32. package/dist/models/CreateVpnAttachmentRequest.d.ts +149 -89
  33. package/dist/models/CreateVpnAttachmentRequest.js.map +1 -1
  34. package/dist/models/CreateVpnAttachmentResponseBody.d.ts +6 -6
  35. package/dist/models/CreateVswitchRequest.d.ts +33 -22
  36. package/dist/models/CreateVswitchRequest.js +2 -0
  37. package/dist/models/CreateVswitchRequest.js.map +1 -1
  38. package/dist/models/DeleteIpv6internetBandwidthRequest.d.ts +6 -6
  39. package/dist/models/DeleteNatRateLimitRuleRequest.d.ts +3 -5
  40. package/dist/models/DeleteNatRateLimitRuleRequest.js.map +1 -1
  41. package/dist/models/DescribeCommonBandwidthPackagesRequest.d.ts +17 -16
  42. package/dist/models/DescribeCommonBandwidthPackagesRequest.js.map +1 -1
  43. package/dist/models/DescribeCommonBandwidthPackagesResponseBody.d.ts +5 -2
  44. package/dist/models/DescribeCommonBandwidthPackagesResponseBody.js +6 -0
  45. package/dist/models/DescribeCommonBandwidthPackagesResponseBody.js.map +1 -1
  46. package/dist/models/DescribeEipAddressesRequest.d.ts +20 -21
  47. package/dist/models/DescribeEipAddressesRequest.js.map +1 -1
  48. package/dist/models/DescribeEipAddressesResponseBody.d.ts +1 -0
  49. package/dist/models/DescribeEipAddressesResponseBody.js +2 -0
  50. package/dist/models/DescribeEipAddressesResponseBody.js.map +1 -1
  51. package/dist/models/DescribeIpv6addressesRequest.d.ts +14 -15
  52. package/dist/models/DescribeIpv6addressesRequest.js.map +1 -1
  53. package/dist/models/DescribeIpv6addressesResponseBody.d.ts +18 -2
  54. package/dist/models/DescribeIpv6addressesResponseBody.js +29 -1
  55. package/dist/models/DescribeIpv6addressesResponseBody.js.map +1 -1
  56. package/dist/models/DescribeNatGatewayCapacityReservationRequest.d.ts +5 -6
  57. package/dist/models/DescribeNatGatewayCapacityReservationRequest.js.map +1 -1
  58. package/dist/models/DescribeNatGatewayCapacityReservationResponseBody.d.ts +11 -7
  59. package/dist/models/DescribeNatGatewayCapacityReservationResponseBody.js.map +1 -1
  60. package/dist/models/DescribeRouteEntryListRequest.d.ts +11 -11
  61. package/dist/models/DescribeRouteEntryListResponseBody.d.ts +5 -2
  62. package/dist/models/DescribeRouteEntryListResponseBody.js.map +1 -1
  63. package/dist/models/DescribeVpnConnectionRequest.d.ts +1 -1
  64. package/dist/models/DescribeVpnConnectionResponseBody.d.ts +84 -63
  65. package/dist/models/DescribeVpnConnectionResponseBody.js.map +1 -1
  66. package/dist/models/DescribeVswitchAttributesRequest.d.ts +5 -5
  67. package/dist/models/DescribeVswitchAttributesResponseBody.d.ts +27 -16
  68. package/dist/models/DescribeVswitchAttributesResponseBody.js +2 -0
  69. package/dist/models/DescribeVswitchAttributesResponseBody.js.map +1 -1
  70. package/dist/models/DescribeVswitchesRequest.d.ts +37 -22
  71. package/dist/models/DescribeVswitchesRequest.js +2 -0
  72. package/dist/models/DescribeVswitchesRequest.js.map +1 -1
  73. package/dist/models/DescribeVswitchesResponseBody.d.ts +2 -2
  74. package/dist/models/ListTagResourcesForExpressConnectRequest.d.ts +12 -12
  75. package/dist/models/ListTagResourcesForExpressConnectResponseBody.d.ts +3 -3
  76. package/dist/models/ModifyBgpGroupAttributeRequest.d.ts +7 -7
  77. package/dist/models/ModifyBgpGroupAttributeResponseBody.d.ts +1 -1
  78. package/dist/models/ModifyCommonBandwidthPackageIpBandwidthRequest.d.ts +22 -4
  79. package/dist/models/ModifyCommonBandwidthPackageIpBandwidthRequest.js +4 -0
  80. package/dist/models/ModifyCommonBandwidthPackageIpBandwidthRequest.js.map +1 -1
  81. package/dist/models/ModifyCommonBandwidthPackageSpecRequest.d.ts +5 -5
  82. package/dist/models/ModifyEipAddressAttributeRequest.d.ts +5 -5
  83. package/dist/models/ModifyNatGatewayCapacityReservationRequest.d.ts +6 -6
  84. package/dist/models/ModifyNatGatewayCapacityReservationResponseBody.d.ts +2 -7
  85. package/dist/models/ModifyNatGatewayCapacityReservationResponseBody.js.map +1 -1
  86. package/dist/models/ModifyNatGatewayCapacityReservationShrinkRequest.d.ts +6 -6
  87. package/dist/models/ModifyNatRateLimitRuleRequest.d.ts +9 -9
  88. package/dist/models/ModifyNatRateLimitRuleResponseBody.d.ts +1 -1
  89. package/dist/models/ModifyRouteEntryRequest.d.ts +22 -22
  90. package/dist/models/RemoveCommonBandwidthPackageIpRequest.d.ts +5 -5
  91. package/dist/models/SetHighDefinitionMonitorLogStatusRequest.d.ts +2 -4
  92. package/dist/models/SetHighDefinitionMonitorLogStatusRequest.js.map +1 -1
  93. package/dist/models/SetHighDefinitionMonitorLogStatusResponseBody.d.ts +1 -0
  94. package/dist/models/SetHighDefinitionMonitorLogStatusResponseBody.js.map +1 -1
  95. package/dist/models/model.d.ts +1 -0
  96. package/dist/models/model.js +42 -40
  97. package/dist/models/model.js.map +1 -1
  98. package/package.json +2 -1
  99. package/src/client.ts +295 -257
  100. package/src/models/AddCommonBandwidthPackageIpRequest.ts +7 -7
  101. package/src/models/AddCommonBandwidthPackageIpsRequest.ts +1 -1
  102. package/src/models/AllocateEipAddressProRequest.ts +49 -25
  103. package/src/models/AllocateEipAddressProResponseBody.ts +2 -2
  104. package/src/models/AllocateEipAddressRequest.ts +44 -44
  105. package/src/models/AllocateEipAddressResponseBody.ts +4 -4
  106. package/src/models/AllocateEipSegmentAddressRequest.ts +6 -6
  107. package/src/models/AssociateEipAddressBatchRequest.ts +6 -6
  108. package/src/models/AssociateEipAddressRequest.ts +16 -16
  109. package/src/models/CalculateNatGatewayCapacityUnitsRequest.ts +6 -6
  110. package/src/models/CalculateNatGatewayCapacityUnitsResponseBody.ts +2 -2
  111. package/src/models/CalculateNatGatewayCapacityUnitsShrinkRequest.ts +5 -5
  112. package/src/models/CancelCommonBandwidthPackageIpBandwidthRequest.ts +25 -3
  113. package/src/models/CreateFlowLogRequest.ts +29 -29
  114. package/src/models/CreateFlowLogResponseBody.ts +3 -3
  115. package/src/models/CreateHaVipRequest.ts +5 -5
  116. package/src/models/CreateRouteEntriesRequest.ts +28 -28
  117. package/src/models/CreateRouteEntriesResponseBody.ts +8 -8
  118. package/src/models/CreateRouteEntryRequest.ts +34 -34
  119. package/src/models/CreateRouteEntryResponseBody.ts +1 -1
  120. package/src/models/CreateSslVpnServerRequest.ts +15 -12
  121. package/src/models/CreateTrafficMirrorFilterRequest.ts +18 -18
  122. package/src/models/CreateTrafficMirrorFilterRulesRequest.ts +19 -18
  123. package/src/models/CreateVpnAttachmentRequest.ts +149 -89
  124. package/src/models/CreateVpnAttachmentResponseBody.ts +6 -6
  125. package/src/models/CreateVswitchRequest.ts +35 -22
  126. package/src/models/DeleteIpv6internetBandwidthRequest.ts +6 -6
  127. package/src/models/DeleteNatRateLimitRuleRequest.ts +3 -5
  128. package/src/models/DescribeCommonBandwidthPackagesRequest.ts +17 -16
  129. package/src/models/DescribeCommonBandwidthPackagesResponseBody.ts +11 -2
  130. package/src/models/DescribeEipAddressesRequest.ts +20 -21
  131. package/src/models/DescribeEipAddressesResponseBody.ts +3 -0
  132. package/src/models/DescribeIpv6addressesRequest.ts +14 -15
  133. package/src/models/DescribeIpv6addressesResponseBody.ts +37 -2
  134. package/src/models/DescribeNatGatewayCapacityReservationRequest.ts +5 -6
  135. package/src/models/DescribeNatGatewayCapacityReservationResponseBody.ts +11 -7
  136. package/src/models/DescribeRouteEntryListRequest.ts +11 -11
  137. package/src/models/DescribeRouteEntryListResponseBody.ts +5 -2
  138. package/src/models/DescribeVpnConnectionRequest.ts +2 -2
  139. package/src/models/DescribeVpnConnectionResponseBody.ts +84 -63
  140. package/src/models/DescribeVswitchAttributesRequest.ts +5 -5
  141. package/src/models/DescribeVswitchAttributesResponseBody.ts +29 -16
  142. package/src/models/DescribeVswitchesRequest.ts +39 -22
  143. package/src/models/DescribeVswitchesResponseBody.ts +2 -2
  144. package/src/models/ListTagResourcesForExpressConnectRequest.ts +12 -12
  145. package/src/models/ListTagResourcesForExpressConnectResponseBody.ts +3 -3
  146. package/src/models/ModifyBgpGroupAttributeRequest.ts +7 -7
  147. package/src/models/ModifyBgpGroupAttributeResponseBody.ts +1 -1
  148. package/src/models/ModifyCommonBandwidthPackageIpBandwidthRequest.ts +26 -4
  149. package/src/models/ModifyCommonBandwidthPackageSpecRequest.ts +5 -5
  150. package/src/models/ModifyEipAddressAttributeRequest.ts +5 -5
  151. package/src/models/ModifyNatGatewayCapacityReservationRequest.ts +6 -6
  152. package/src/models/ModifyNatGatewayCapacityReservationResponseBody.ts +2 -7
  153. package/src/models/ModifyNatGatewayCapacityReservationShrinkRequest.ts +6 -6
  154. package/src/models/ModifyNatRateLimitRuleRequest.ts +9 -9
  155. package/src/models/ModifyNatRateLimitRuleResponseBody.ts +1 -1
  156. package/src/models/ModifyRouteEntryRequest.ts +22 -22
  157. package/src/models/RemoveCommonBandwidthPackageIpRequest.ts +5 -5
  158. package/src/models/SetHighDefinitionMonitorLogStatusRequest.ts +2 -4
  159. package/src/models/SetHighDefinitionMonitorLogStatusResponseBody.ts +1 -0
  160. package/src/models/model.ts +1 -0
package/dist/client.d.ts CHANGED
@@ -79,14 +79,14 @@ export default class Client extends OpenApi {
79
79
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
80
80
  *
81
81
  * @remarks
82
- * Before you invoke this operation, take note of the following items:
83
- * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
84
- * - The billing method of the EIP is pay-as-you-go.
85
- * - The EIP is in the same region as the Internet Shared Bandwidth instance.
82
+ * When you call this operation, take note of the following information:
83
+ * - When you call this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following requirements:
84
+ * - The Billable methods of the EIP are pay-as-you-go billing.
85
+ * - The EIP and the Internet Shared Bandwidth instance are in the same region.
86
86
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
87
- * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP is not yet added to the Internet Shared Bandwidth instance. The addition node is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
88
- * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only execute query operations.
89
- * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
87
+ * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send the request, the system returns a request ID, but the EIP is not immediately added to the Internet Shared Bandwidth instance. The addition task in the background is still in progress. You can call the [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) operation to query the association status of the Internet Shared Bandwidth instance and the EIP.
88
+ * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only perform query operations and cannot perform other operations.
89
+ * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is successfully associated with the EIP.
90
90
  *
91
91
  * @param request - AddCommonBandwidthPackageIpRequest
92
92
  * @param runtime - runtime options for this request RuntimeOptions
@@ -97,14 +97,14 @@ export default class Client extends OpenApi {
97
97
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
98
98
  *
99
99
  * @remarks
100
- * Before you invoke this operation, take note of the following items:
101
- * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
102
- * - The billing method of the EIP is pay-as-you-go.
103
- * - The EIP is in the same region as the Internet Shared Bandwidth instance.
100
+ * When you call this operation, take note of the following information:
101
+ * - When you call this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following requirements:
102
+ * - The Billable methods of the EIP are pay-as-you-go billing.
103
+ * - The EIP and the Internet Shared Bandwidth instance are in the same region.
104
104
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
105
- * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP is not yet added to the Internet Shared Bandwidth instance. The addition node is still running in the background. You can invoke [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the association status between the Internet Shared Bandwidth instance and the EIP.
106
- * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only execute query operations.
107
- * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
105
+ * - The **AddCommonBandwidthPackageIp** operation is asynchronous. After you send the request, the system returns a request ID, but the EIP is not immediately added to the Internet Shared Bandwidth instance. The addition task in the background is still in progress. You can call the [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) operation to query the association status of the Internet Shared Bandwidth instance and the EIP.
106
+ * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIP. In this state, you can only perform query operations and cannot perform other operations.
107
+ * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is successfully associated with the EIP.
108
108
  *
109
109
  * @param request - AddCommonBandwidthPackageIpRequest
110
110
  * @returns AddCommonBandwidthPackageIpResponse
@@ -116,9 +116,9 @@ export default class Client extends OpenApi {
116
116
  * @remarks
117
117
  * - When you call this operation to add multiple EIPs to an Internet Shared Bandwidth instance, the EIPs must meet the following requirements:
118
118
  * - The billing method of the EIPs is pay-as-you-go.
119
- * - The EIPs are in the same region as the Internet Shared Bandwidth instance.
119
+ * - The EIPs and the Internet Shared Bandwidth instance are in the same region.
120
120
  * - The line types of the EIPs are the same as the line type of the Internet Shared Bandwidth instance.
121
- * - **AddCommonBandwidthPackageIps** is an asynchronous operation. After you call this operation, the system returns a request ID, but the EIPs are not immediately added to the Internet Shared Bandwidth instance. The addition task in the background is still in progress. You can call [DescribeCommonBandwidthPackages](~~DescribeCommonBandwidthPackages~~) to query the association status of the Internet Shared Bandwidth instance and the EIPs.
121
+ * - The **AddCommonBandwidthPackageIps** operation is asynchronous. After you send the request, the system returns a request ID, but the EIPs are not immediately added to the Internet Shared Bandwidth instance. The background addition task is still running. You can call the [DescribeCommonBandwidthPackages](~~DescribeCommonBandwidthPackages~~) operation to query the association status of the Internet Shared Bandwidth instance and the EIPs.
122
122
  * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIPs. In this state, you can only perform query operations and cannot perform other operations.
123
123
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIPs.
124
124
  *
@@ -133,9 +133,9 @@ export default class Client extends OpenApi {
133
133
  * @remarks
134
134
  * - When you call this operation to add multiple EIPs to an Internet Shared Bandwidth instance, the EIPs must meet the following requirements:
135
135
  * - The billing method of the EIPs is pay-as-you-go.
136
- * - The EIPs are in the same region as the Internet Shared Bandwidth instance.
136
+ * - The EIPs and the Internet Shared Bandwidth instance are in the same region.
137
137
  * - The line types of the EIPs are the same as the line type of the Internet Shared Bandwidth instance.
138
- * - **AddCommonBandwidthPackageIps** is an asynchronous operation. After you call this operation, the system returns a request ID, but the EIPs are not immediately added to the Internet Shared Bandwidth instance. The addition task in the background is still in progress. You can call [DescribeCommonBandwidthPackages](~~DescribeCommonBandwidthPackages~~) to query the association status of the Internet Shared Bandwidth instance and the EIPs.
138
+ * - The **AddCommonBandwidthPackageIps** operation is asynchronous. After you send the request, the system returns a request ID, but the EIPs are not immediately added to the Internet Shared Bandwidth instance. The background addition task is still running. You can call the [DescribeCommonBandwidthPackages](~~DescribeCommonBandwidthPackages~~) operation to query the association status of the Internet Shared Bandwidth instance and the EIPs.
139
139
  * - If the association status is **BINDING**, the Internet Shared Bandwidth instance is being associated with the EIPs. In this state, you can only perform query operations and cannot perform other operations.
140
140
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIPs.
141
141
  *
@@ -238,11 +238,11 @@ export default class Client extends OpenApi {
238
238
  */
239
239
  addSourcesToTrafficMirrorSession(request: $_model.AddSourcesToTrafficMirrorSessionRequest): Promise<$_model.AddSourcesToTrafficMirrorSessionResponse>;
240
240
  /**
241
- * Applies for an elastic IP address (EIP).
241
+ * Allocates an elastic IP address (EIP).
242
242
  *
243
243
  * @remarks
244
- * Before you call this operation, make sure that you fully understand the billing methods and pricing of EIPs. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
245
- * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. At the transport layer, EIPs support only ICMP, TCP, and UDP. EIPs do not support IGMP or SCTP.
244
+ * Make sure that you fully understand the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
245
+ * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. At the transport layer, EIPs support parsing only ICMP, TCP, and UDP packets, and do not support parsing packets of other protocols such as IGMP and SCTP.
246
246
  *
247
247
  * @param request - AllocateEipAddressRequest
248
248
  * @param runtime - runtime options for this request RuntimeOptions
@@ -250,18 +250,18 @@ export default class Client extends OpenApi {
250
250
  */
251
251
  allocateEipAddressWithOptions(request: $_model.AllocateEipAddressRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AllocateEipAddressResponse>;
252
252
  /**
253
- * Applies for an elastic IP address (EIP).
253
+ * Allocates an elastic IP address (EIP).
254
254
  *
255
255
  * @remarks
256
- * Before you call this operation, make sure that you fully understand the billing methods and pricing of EIPs. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
257
- * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. At the transport layer, EIPs support only ICMP, TCP, and UDP. EIPs do not support IGMP or SCTP.
256
+ * Make sure that you fully understand the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
257
+ * After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. At the transport layer, EIPs support parsing only ICMP, TCP, and UDP packets, and do not support parsing packets of other protocols such as IGMP and SCTP.
258
258
  *
259
259
  * @param request - AllocateEipAddressRequest
260
260
  * @returns AllocateEipAddressResponse
261
261
  */
262
262
  allocateEipAddress(request: $_model.AllocateEipAddressRequest): Promise<$_model.AllocateEipAddressResponse>;
263
263
  /**
264
- * Applies for a specified elastic IP address (EIP) for specific network configuration requirements.
264
+ * Allocates a specified elastic IP address (EIP) for specific network configuration requirements.
265
265
  *
266
266
  * @param request - AllocateEipAddressProRequest
267
267
  * @param runtime - runtime options for this request RuntimeOptions
@@ -269,19 +269,19 @@ export default class Client extends OpenApi {
269
269
  */
270
270
  allocateEipAddressProWithOptions(request: $_model.AllocateEipAddressProRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AllocateEipAddressProResponse>;
271
271
  /**
272
- * Applies for a specified elastic IP address (EIP) for specific network configuration requirements.
272
+ * Allocates a specified elastic IP address (EIP) for specific network configuration requirements.
273
273
  *
274
274
  * @param request - AllocateEipAddressProRequest
275
275
  * @returns AllocateEipAddressProResponse
276
276
  */
277
277
  allocateEipAddressPro(request: $_model.AllocateEipAddressProRequest): Promise<$_model.AllocateEipAddressProResponse>;
278
278
  /**
279
- * Contiguous elastic IP addresses (EIPs) are a group of sequentially arranged EIPs. During network design, you can apply for and use these IP addresses in batches for cloud resources that require contiguous public IP addresses. You can call the AllocateEipSegmentAddress operation to apply for contiguous EIPs.
279
+ * Contiguous EIPs are a group of sequential Elastic IP addresses. You can apply for and use these IP addresses in batches for cloud resources that require contiguous public IP addresses when designing networks. You can call the AllocateEipSegmentAddress operation to apply for contiguous EIPs.
280
280
  *
281
281
  * @remarks
282
- * The **AllocateEipSegmentAddress** operation is asynchronous. The system first returns the instance ID of the contiguous EIP group, but the group is not yet fully created and the creation task is still running in the background. You can call the [DescribeEipSegment](https://help.aliyun.com/document_detail/156063.html) operation to query the status of the contiguous EIP group.
283
- * - When the contiguous EIP group is in the **Allocating** state, the group is being allocated. In this state, you can only perform query operations.
284
- * - When the contiguous EIP group is in the **Allocated** state, the group is allocated.
282
+ * The **AllocateEipSegmentAddress** operation is asynchronous. The system first returns the instance ID of the contiguous EIP group, but the group is not yet created and the creation task is still running in the background. You can call the [DescribeEipSegment](https://help.aliyun.com/document_detail/156063.html) operation to query the status of the contiguous EIP group.
283
+ * - When the contiguous EIP group is in the **Allocating** state, the group is being allocated. In this state, you can only perform query operations and cannot perform other operations.
284
+ * - When the contiguous EIP group is in the **Allocated** state, the group has been allocated.
285
285
  *
286
286
  * @deprecated OpenAPI AllocateEipSegmentAddress is deprecated
287
287
  *
@@ -291,12 +291,12 @@ export default class Client extends OpenApi {
291
291
  */
292
292
  allocateEipSegmentAddressWithOptions(request: $_model.AllocateEipSegmentAddressRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AllocateEipSegmentAddressResponse>;
293
293
  /**
294
- * Contiguous elastic IP addresses (EIPs) are a group of sequentially arranged EIPs. During network design, you can apply for and use these IP addresses in batches for cloud resources that require contiguous public IP addresses. You can call the AllocateEipSegmentAddress operation to apply for contiguous EIPs.
294
+ * Contiguous EIPs are a group of sequential Elastic IP addresses. You can apply for and use these IP addresses in batches for cloud resources that require contiguous public IP addresses when designing networks. You can call the AllocateEipSegmentAddress operation to apply for contiguous EIPs.
295
295
  *
296
296
  * @remarks
297
- * The **AllocateEipSegmentAddress** operation is asynchronous. The system first returns the instance ID of the contiguous EIP group, but the group is not yet fully created and the creation task is still running in the background. You can call the [DescribeEipSegment](https://help.aliyun.com/document_detail/156063.html) operation to query the status of the contiguous EIP group.
298
- * - When the contiguous EIP group is in the **Allocating** state, the group is being allocated. In this state, you can only perform query operations.
299
- * - When the contiguous EIP group is in the **Allocated** state, the group is allocated.
297
+ * The **AllocateEipSegmentAddress** operation is asynchronous. The system first returns the instance ID of the contiguous EIP group, but the group is not yet created and the creation task is still running in the background. You can call the [DescribeEipSegment](https://help.aliyun.com/document_detail/156063.html) operation to query the status of the contiguous EIP group.
298
+ * - When the contiguous EIP group is in the **Allocating** state, the group is being allocated. In this state, you can only perform query operations and cannot perform other operations.
299
+ * - When the contiguous EIP group is in the **Allocated** state, the group has been allocated.
300
300
  *
301
301
  * @deprecated OpenAPI AllocateEipSegmentAddress is deprecated
302
302
  *
@@ -412,11 +412,11 @@ export default class Client extends OpenApi {
412
412
  * Associates an elastic IP address (EIP) with a cloud service instance in the same region.
413
413
  *
414
414
  * @remarks
415
- * - You can associate an EIP with an ECS instance in a virtual private cloud (VPC), a CLB instance in a virtual private cloud (VPC), a secondary elastic network interface controller (NIC), a NAT gateway, or a high-availability virtual IP address in the same region.
416
- * - The **AssociateEipAddress** operation is asynchronous. After you call this operation, the system returns a request ID, but the EIP is not immediately associated with the cloud service instance. The association task is still running in the background. You can call the [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) operation to query the status of the EIP:
417
- * - If the EIP is in the **Associating** state, the EIP is being associated. In this state, you can only perform query operations and cannot perform other operations.
418
- * - If the EIP is in the **InUse** state, the EIP is associated.
419
- * - The **AssociateEipAddress** operation does not support concurrently associating the same EIP with cloud service instances.
415
+ * - You can attach an EIP to an ECS instance of the virtual private cloud (VPC) network type, a CLB instance of the virtual private cloud (VPC) network type, a secondary elastic network interface controller (NIC), a NAT gateway, or a high-availability (active) virtual IP address in the same region.
416
+ * - The **AssociateEipAddress** operation is asynchronous. After you invoke this operation, the system returns a request ID, but the EIP is not immediately attached to the cloud service instance. The attachment task is still running in the background. You can invoke the [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) operation to query the status of the EIP:
417
+ * - If the EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
418
+ * - If the EIP is in the **InUse** state, the EIP is attached.
419
+ * - The **AssociateEipAddress** operation does not support concurrent attachment of the same EIP to cloud service instances.
420
420
  *
421
421
  * @param request - AssociateEipAddressRequest
422
422
  * @param runtime - runtime options for this request RuntimeOptions
@@ -427,25 +427,25 @@ export default class Client extends OpenApi {
427
427
  * Associates an elastic IP address (EIP) with a cloud service instance in the same region.
428
428
  *
429
429
  * @remarks
430
- * - You can associate an EIP with an ECS instance in a virtual private cloud (VPC), a CLB instance in a virtual private cloud (VPC), a secondary elastic network interface controller (NIC), a NAT gateway, or a high-availability virtual IP address in the same region.
431
- * - The **AssociateEipAddress** operation is asynchronous. After you call this operation, the system returns a request ID, but the EIP is not immediately associated with the cloud service instance. The association task is still running in the background. You can call the [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) operation to query the status of the EIP:
432
- * - If the EIP is in the **Associating** state, the EIP is being associated. In this state, you can only perform query operations and cannot perform other operations.
433
- * - If the EIP is in the **InUse** state, the EIP is associated.
434
- * - The **AssociateEipAddress** operation does not support concurrently associating the same EIP with cloud service instances.
430
+ * - You can attach an EIP to an ECS instance of the virtual private cloud (VPC) network type, a CLB instance of the virtual private cloud (VPC) network type, a secondary elastic network interface controller (NIC), a NAT gateway, or a high-availability (active) virtual IP address in the same region.
431
+ * - The **AssociateEipAddress** operation is asynchronous. After you invoke this operation, the system returns a request ID, but the EIP is not immediately attached to the cloud service instance. The attachment task is still running in the background. You can invoke the [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) operation to query the status of the EIP:
432
+ * - If the EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
433
+ * - If the EIP is in the **InUse** state, the EIP is attached.
434
+ * - The **AssociateEipAddress** operation does not support concurrent attachment of the same EIP to cloud service instances.
435
435
  *
436
436
  * @param request - AssociateEipAddressRequest
437
437
  * @returns AssociateEipAddressResponse
438
438
  */
439
439
  associateEipAddress(request: $_model.AssociateEipAddressRequest): Promise<$_model.AssociateEipAddressResponse>;
440
440
  /**
441
- * Associates multiple Elastic IP addresses (EIPs) with cloud service instances in the same region.
441
+ * Associates multiple elastic IP addresses (EIPs) with cloud service instances in the same region.
442
442
  *
443
443
  * @remarks
444
- * - **AssociateEipAddressBatch** associates multiple EIPs with cloud service instances in batches. This operation only supports associating EIPs with NAT gateways or secondary elastic network interfaces (ENIs) in the same region. To associate EIPs with other cloud service instances, refer to [AssociateEipAddress](https://help.aliyun.com/document_detail/120195.html).
445
- * - **AssociateEipAddressBatch** is an asynchronous operation. The system returns a request ID, but the EIPs are not immediately associated with the cloud service instances. The association tasks are still running in the background. You can call [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIPs:
446
- * - If the EIP is in the **Associating** state, the EIP is being associated. In this state, you can only perform query operations.
447
- * - If the EIP is in the **InUse** state, the EIP is associated.
448
- * - **AssociateEipAddressBatch** does not support concurrent association of the same EIP with cloud service instances.
444
+ * - **AssociateEipAddressBatch** is used to attach multiple EIPs to cloud service instances in batches. This operation only supports attaching EIPs to NAT gateway instances or secondary elastic network interface controller (NIC) instances in the same region. To attach EIPs to other cloud service instances, see [AssociateEipAddress](https://help.aliyun.com/document_detail/120195.html).
445
+ * - The **AssociateEipAddressBatch** operation is asynchronous. After you invoke this operation, the system returns a request ID, but the EIPs are not immediately attached to the cloud service instances. The attachment tasks are still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIPs:
446
+ * - If an EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
447
+ * - If an EIP is in the **InUse** state, the EIP is attached.
448
+ * - The **AssociateEipAddressBatch** operation does not support concurrent attachment of the same EIP to cloud service instances.
449
449
  *
450
450
  * @param request - AssociateEipAddressBatchRequest
451
451
  * @param runtime - runtime options for this request RuntimeOptions
@@ -453,14 +453,14 @@ export default class Client extends OpenApi {
453
453
  */
454
454
  associateEipAddressBatchWithOptions(request: $_model.AssociateEipAddressBatchRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AssociateEipAddressBatchResponse>;
455
455
  /**
456
- * Associates multiple Elastic IP addresses (EIPs) with cloud service instances in the same region.
456
+ * Associates multiple elastic IP addresses (EIPs) with cloud service instances in the same region.
457
457
  *
458
458
  * @remarks
459
- * - **AssociateEipAddressBatch** associates multiple EIPs with cloud service instances in batches. This operation only supports associating EIPs with NAT gateways or secondary elastic network interfaces (ENIs) in the same region. To associate EIPs with other cloud service instances, refer to [AssociateEipAddress](https://help.aliyun.com/document_detail/120195.html).
460
- * - **AssociateEipAddressBatch** is an asynchronous operation. The system returns a request ID, but the EIPs are not immediately associated with the cloud service instances. The association tasks are still running in the background. You can call [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIPs:
461
- * - If the EIP is in the **Associating** state, the EIP is being associated. In this state, you can only perform query operations.
462
- * - If the EIP is in the **InUse** state, the EIP is associated.
463
- * - **AssociateEipAddressBatch** does not support concurrent association of the same EIP with cloud service instances.
459
+ * - **AssociateEipAddressBatch** is used to attach multiple EIPs to cloud service instances in batches. This operation only supports attaching EIPs to NAT gateway instances or secondary elastic network interface controller (NIC) instances in the same region. To attach EIPs to other cloud service instances, see [AssociateEipAddress](https://help.aliyun.com/document_detail/120195.html).
460
+ * - The **AssociateEipAddressBatch** operation is asynchronous. After you invoke this operation, the system returns a request ID, but the EIPs are not immediately attached to the cloud service instances. The attachment tasks are still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIPs:
461
+ * - If an EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
462
+ * - If an EIP is in the **InUse** state, the EIP is attached.
463
+ * - The **AssociateEipAddressBatch** operation does not support concurrent attachment of the same EIP to cloud service instances.
464
464
  *
465
465
  * @param request - AssociateEipAddressBatchRequest
466
466
  * @returns AssociateEipAddressBatchResponse
@@ -794,7 +794,7 @@ export default class Client extends OpenApi {
794
794
  * Cancels the maximum available bandwidth setting for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
795
795
  *
796
796
  * @remarks
797
- * Take note of the following items when you call this operation:
797
+ * When you call this operation, note the following information:
798
798
  * - After the setting is canceled, the maximum available bandwidth of the EIP is the same as that of the Internet Shared Bandwidth instance.
799
799
  * - The **CancelCommonBandwidthPackageIpBandwidth** operation does not support concurrent calls to cancel the maximum available bandwidth setting for the same EIP.
800
800
  *
@@ -807,7 +807,7 @@ export default class Client extends OpenApi {
807
807
  * Cancels the maximum available bandwidth setting for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
808
808
  *
809
809
  * @remarks
810
- * Take note of the following items when you call this operation:
810
+ * When you call this operation, note the following information:
811
811
  * - After the setting is canceled, the maximum available bandwidth of the EIP is the same as that of the Internet Shared Bandwidth instance.
812
812
  * - The **CancelCommonBandwidthPackageIpBandwidth** operation does not support concurrent calls to cancel the maximum available bandwidth setting for the same EIP.
813
813
  *
@@ -1360,9 +1360,9 @@ export default class Client extends OpenApi {
1360
1360
  * Creates a flow log.
1361
1361
  *
1362
1362
  * @remarks
1363
- * *CreateFlowLog** is an asynchronous operation. After you call this operation, the system returns an instance ID, but the flow log has not been created yet. The creation task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
1363
+ * The **CreateFlowLog** operation is asynchronous. The system returns an instance ID, but the flow log is not yet created and the creation task is still running in the background. You can call the [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) operation to query the creation status of the flow log:
1364
1364
  * - If the flow log is in the **Activating** state, the flow log is being created.
1365
- * - If the flow log is in the **Active** state, the flow log is created and activated.
1365
+ * - If the flow log is in the **Active** state, the flow log is created and started.
1366
1366
  *
1367
1367
  * @param request - CreateFlowLogRequest
1368
1368
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1373,9 +1373,9 @@ export default class Client extends OpenApi {
1373
1373
  * Creates a flow log.
1374
1374
  *
1375
1375
  * @remarks
1376
- * *CreateFlowLog** is an asynchronous operation. After you call this operation, the system returns an instance ID, but the flow log has not been created yet. The creation task is still running in the background. You can call [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) to query the creation status of the flow log:
1376
+ * The **CreateFlowLog** operation is asynchronous. The system returns an instance ID, but the flow log is not yet created and the creation task is still running in the background. You can call the [DescribeFlowLogs](https://help.aliyun.com/document_detail/448670.html) operation to query the creation status of the flow log:
1377
1377
  * - If the flow log is in the **Activating** state, the flow log is being created.
1378
- * - If the flow log is in the **Active** state, the flow log is created and activated.
1378
+ * - If the flow log is in the **Active** state, the flow log is created and started.
1379
1379
  *
1380
1380
  * @param request - CreateFlowLogRequest
1381
1381
  * @returns CreateFlowLogResponse
@@ -1480,9 +1480,9 @@ export default class Client extends OpenApi {
1480
1480
  * Creates a high-availability virtual IP address (HAVIP).
1481
1481
  *
1482
1482
  * @remarks
1483
- * *CreateHaVip** is an asynchronous operation. The system returns the ID of the HAVIP, but the HAVIP is not yet created and the creation task is still running in the background. You can call [DescribeHaVips](https://help.aliyun.com/document_detail/114611.html) to query the creation status of the HAVIP:
1484
- * - When the HAVIP is in the **Creating** state, the HAVIP is being created.
1485
- * - When the HAVIP is in the **Available** state, the HAVIP is created.
1483
+ * *CreateHaVip** is an asynchronous operation. The system returns the HAVIP ID, but the HAVIP is not fully created because the backend creation task is still in progress. You can call [DescribeHaVips](https://help.aliyun.com/document_detail/114611.html) to query the creation status of the HAVIP:
1484
+ * - If the HAVIP is in the **Creating** state, the HAVIP is being created.
1485
+ * - If the HAVIP is in the **Available** state, the HAVIP is created.
1486
1486
  *
1487
1487
  * @param request - CreateHaVipRequest
1488
1488
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1493,9 +1493,9 @@ export default class Client extends OpenApi {
1493
1493
  * Creates a high-availability virtual IP address (HAVIP).
1494
1494
  *
1495
1495
  * @remarks
1496
- * *CreateHaVip** is an asynchronous operation. The system returns the ID of the HAVIP, but the HAVIP is not yet created and the creation task is still running in the background. You can call [DescribeHaVips](https://help.aliyun.com/document_detail/114611.html) to query the creation status of the HAVIP:
1497
- * - When the HAVIP is in the **Creating** state, the HAVIP is being created.
1498
- * - When the HAVIP is in the **Available** state, the HAVIP is created.
1496
+ * *CreateHaVip** is an asynchronous operation. The system returns the HAVIP ID, but the HAVIP is not fully created because the backend creation task is still in progress. You can call [DescribeHaVips](https://help.aliyun.com/document_detail/114611.html) to query the creation status of the HAVIP:
1497
+ * - If the HAVIP is in the **Creating** state, the HAVIP is being created.
1498
+ * - If the HAVIP is in the **Available** state, the HAVIP is created.
1499
1499
  *
1500
1500
  * @param request - CreateHaVipRequest
1501
1501
  * @returns CreateHaVipResponse
@@ -1888,20 +1888,20 @@ export default class Client extends OpenApi {
1888
1888
  */
1889
1889
  createPublicIpAddressPool(request: $_model.CreatePublicIpAddressPoolRequest): Promise<$_model.CreatePublicIpAddressPoolResponse>;
1890
1890
  /**
1891
- * Creates custom route entries in a route table of a vRouter in bulk.
1891
+ * Creates custom route entry (routing) in the routing table of a VPC vRouter.
1892
1892
  *
1893
1893
  * @remarks
1894
- * - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the custom route entry has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the custom route entry:
1895
- * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
1896
- * - If the custom route entry is in the **Created** state, the custom route entry has been created.
1897
- * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
1898
- * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
1899
- * - A route table can contain a maximum of 200 custom route entries.
1900
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as, contain, or be contained by the CIDR block of a vSwitch in the VPC.
1894
+ * - The **CreateRouteEntries** operation is asynchronous. After you call this operation, the system returns an instance ID, but custom route entry is not yet created and the backend task is still running. You can call the [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) operation to query the creation status of custom route entry:
1895
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
1896
+ * - If custom route entry is in the **Created** state, custom route entry is created.
1897
+ * - The **CreateRouteEntries** operation does not support concurrent creation of multiple custom route entries in the same VPC.
1898
+ * **When you use this operation to add custom route entry (routing) to the routing table of a VPC vRouter, take note of the following items:**
1899
+ * - A routing table can contain at most 200 custom route entry (routing).
1900
+ * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block cannot contain the CIDR block of the vSwitch or be contained by the CIDR block of the vSwitch.
1901
1901
  * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to 100.64.0.0/10 or be contained by 100.64.0.0/10.
1902
1902
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
1903
- * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1904
- * - Multiple custom route entries can point to the same next hop (**NextHop**).
1903
+ * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, it is processed as a 32-bit mask.
1904
+ * - Multiple custom route entry (routing) can point to the same next hop (**NextHop**).
1905
1905
  * - The next hop (**NextHop**) of a custom route entry must be in the same VPC as the route table.
1906
1906
  *
1907
1907
  * @param request - CreateRouteEntriesRequest
@@ -1910,20 +1910,20 @@ export default class Client extends OpenApi {
1910
1910
  */
1911
1911
  createRouteEntriesWithOptions(request: $_model.CreateRouteEntriesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateRouteEntriesResponse>;
1912
1912
  /**
1913
- * Creates custom route entries in a route table of a vRouter in bulk.
1913
+ * Creates custom route entry (routing) in the routing table of a VPC vRouter.
1914
1914
  *
1915
1915
  * @remarks
1916
- * - **CreateRouteEntries** is an asynchronous operation. After you invoke this operation, the system returns an instance ID, but the custom route entry has not been created yet. The system is still running the task in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of the custom route entry:
1917
- * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
1918
- * - If the custom route entry is in the **Created** state, the custom route entry has been created.
1919
- * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
1920
- * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
1921
- * - A route table can contain a maximum of 200 custom route entries.
1922
- * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as, contain, or be contained by the CIDR block of a vSwitch in the VPC.
1916
+ * - The **CreateRouteEntries** operation is asynchronous. After you call this operation, the system returns an instance ID, but custom route entry is not yet created and the backend task is still running. You can call the [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) operation to query the creation status of custom route entry:
1917
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
1918
+ * - If custom route entry is in the **Created** state, custom route entry is created.
1919
+ * - The **CreateRouteEntries** operation does not support concurrent creation of multiple custom route entries in the same VPC.
1920
+ * **When you use this operation to add custom route entry (routing) to the routing table of a VPC vRouter, take note of the following items:**
1921
+ * - A routing table can contain at most 200 custom route entry (routing).
1922
+ * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block cannot contain the CIDR block of the vSwitch or be contained by the CIDR block of the vSwitch.
1923
1923
  * - The destination CIDR block (**DstCidrBlock**) of a custom route entry cannot point to 100.64.0.0/10 or be contained by 100.64.0.0/10.
1924
1924
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
1925
- * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1926
- * - Multiple custom route entries can point to the same next hop (**NextHop**).
1925
+ * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, it is processed as a 32-bit mask.
1926
+ * - Multiple custom route entry (routing) can point to the same next hop (**NextHop**).
1927
1927
  * - The next hop (**NextHop**) of a custom route entry must be in the same VPC as the route table.
1928
1928
  *
1929
1929
  * @param request - CreateRouteEntriesRequest
@@ -1931,47 +1931,47 @@ export default class Client extends OpenApi {
1931
1931
  */
1932
1932
  createRouteEntries(request: $_model.CreateRouteEntriesRequest): Promise<$_model.CreateRouteEntriesResponse>;
1933
1933
  /**
1934
- * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
1935
- *
1936
- * @remarks
1937
- * - The **CreateRouteEntry** operation is asynchronous. After you send a request, the system returns an instance ID while the custom route entry is still being added in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the status of the custom route entry:
1938
- * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
1939
- * - If the custom route entry is in the **Created** state, the custom route entry has been added.
1940
- * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
1941
- * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
1942
- * **When you use this operation to add custom route entries to a route table of a vRouter, note the following items:**
1943
- * > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of route entries in the prefix list. The sum cannot exceed the route quota limit.
1944
- * - A route table can contain a maximum of 200 custom route entries.
1945
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of a vSwitch but cannot be contained by the CIDR block of a vSwitch.
1946
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
1947
- * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
1948
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
1949
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1950
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
1934
+ * Creates a custom route entry on a vRouter or a Virtual Border Router (VBR).
1935
+ *
1936
+ * @remarks
1937
+ * - The **CreateRouteEntry** operation is asynchronous. The system returns an instance ID, but custom route entry creation is not yet complete and a background task is still running. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of custom route entry:
1938
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
1939
+ * - If custom route entry is in the **Created** state, custom route entry is created.
1940
+ * - The **CreateRouteEntry** operation does not support concurrent creation of custom route entries in the same VPC or on the same VBR.
1941
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
1942
+ * **When you use this operation to add a custom route entry to the route table of a vRouter, take note of the following items:**
1943
+ * > If the route entry to be added is a prefix list route, the route quota is calculated based on whether the sum of the number of existing routes and the maximum number of route entries for the prefix list route exceeds the route quota limit.
1944
+ * - A route table can contain at most 200 custom route entries.
1945
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of the vSwitch, but cannot be contained by the CIDR block of the vSwitch.
1946
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` for cloud services, but cannot be the same as `100.64.0.0/10`.
1947
+ * <notice>The system route whose destination CIDR block is `100.64.0.0/10` is used for communication between cloud services in the VPC. Proceed with caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
1948
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
1949
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
1950
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
1951
1951
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
1952
- * - You can configure ECMP routing by using the **NextHopList** parameter settings:
1953
- * * When you add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
1952
+ * - You can use the **NextHopList** parameter settings to configure equal-cost multi-path (ECMP) routing:
1953
+ * * When you add a regular (non-ECMP) custom route, you must specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters, and you cannot specify the **NextHopList** parameter.
1954
1954
  *
1955
- * * When you add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
1956
- * **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), note the following items:**
1957
- * - A route table can contain a maximum of 200 custom route entries.
1955
+ * * When you add an ECMP route, you must specify the **DestinationCidrBlock** and **NextHopList** parameters, and you cannot specify the **NextHopType** and **NextHopId** parameters.
1956
+ * **When you use this operation to add a custom route entry to the route table of a VBR, take note of the following items:**
1957
+ * - A route table can contain at most 200 custom route entries.
1958
1958
  *
1959
1959
  * - The **NextHopList** parameter is not supported.
1960
1960
  *
1961
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
1962
- * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
1961
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` for cloud services, but cannot be the same as `100.64.0.0/10`.
1962
+ * <notice>The system route whose destination CIDR block is `100.64.0.0/10` is used for communication between cloud services in the VPC. Proceed with caution when you configure a more specific route. A configuration fault may prevent normal access and use of cloud services.</notice>
1963
1963
  *
1964
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
1964
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
1965
1965
  *
1966
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1966
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
1967
1967
  *
1968
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
1968
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
1969
1969
  *
1970
1970
  * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
1971
1971
  *
1972
- * - You can create route entries on a VBR only when the VBR is in the active (**Active**) state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not under overdue payment lock.
1972
+ * - You can create a route entry on a VBR only when the VBR is in the **Active** state, the associated Express Connect circuit is in the **Enabled** state, and the VBR is not locked due to overdue payments.
1973
1973
  *
1974
- * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
1974
+ * - Only regular (non-ECMP) routing is supported. You must specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters, and you cannot specify the **NextHopList** parameter.
1975
1975
  *
1976
1976
  * @param request - CreateRouteEntryRequest
1977
1977
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1979,47 +1979,47 @@ export default class Client extends OpenApi {
1979
1979
  */
1980
1980
  createRouteEntryWithOptions(request: $_model.CreateRouteEntryRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateRouteEntryResponse>;
1981
1981
  /**
1982
- * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
1983
- *
1984
- * @remarks
1985
- * - The **CreateRouteEntry** operation is asynchronous. After you send a request, the system returns an instance ID while the custom route entry is still being added in the background. You can invoke [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the status of the custom route entry:
1986
- * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
1987
- * - If the custom route entry is in the **Created** state, the custom route entry has been added.
1988
- * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
1989
- * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
1990
- * **When you use this operation to add custom route entries to a route table of a vRouter, note the following items:**
1991
- * > When the route to be added is a prefix list route, the route quota is calculated based on the sum of existing routes and the maximum number of route entries in the prefix list. The sum cannot exceed the route quota limit.
1992
- * - A route table can contain a maximum of 200 custom route entries.
1993
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of a vSwitch but cannot be contained by the CIDR block of a vSwitch.
1994
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
1995
- * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
1996
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
1997
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
1998
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
1982
+ * Creates a custom route entry on a vRouter or a Virtual Border Router (VBR).
1983
+ *
1984
+ * @remarks
1985
+ * - The **CreateRouteEntry** operation is asynchronous. The system returns an instance ID, but custom route entry creation is not yet complete and a background task is still running. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the creation status of custom route entry:
1986
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
1987
+ * - If custom route entry is in the **Created** state, custom route entry is created.
1988
+ * - The **CreateRouteEntry** operation does not support concurrent creation of custom route entries in the same VPC or on the same VBR.
1989
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
1990
+ * **When you use this operation to add a custom route entry to the route table of a vRouter, take note of the following items:**
1991
+ * > If the route entry to be added is a prefix list route, the route quota is calculated based on whether the sum of the number of existing routes and the maximum number of route entries for the prefix list route exceeds the route quota limit.
1992
+ * - A route table can contain at most 200 custom route entries.
1993
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry cannot be the same as the CIDR block of a vSwitch in the VPC. The destination CIDR block can contain the CIDR block of the vSwitch, but cannot be contained by the CIDR block of the vSwitch.
1994
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` for cloud services, but cannot be the same as `100.64.0.0/10`.
1995
+ * <notice>The system route whose destination CIDR block is `100.64.0.0/10` is used for communication between cloud services in the VPC. Proceed with caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
1996
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
1997
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
1998
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
1999
1999
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
2000
- * - You can configure ECMP routing by using the **NextHopList** parameter settings:
2001
- * * When you add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
2000
+ * - You can use the **NextHopList** parameter settings to configure equal-cost multi-path (ECMP) routing:
2001
+ * * When you add a regular (non-ECMP) custom route, you must specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters, and you cannot specify the **NextHopList** parameter.
2002
2002
  *
2003
- * * When you add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
2004
- * **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), note the following items:**
2005
- * - A route table can contain a maximum of 200 custom route entries.
2003
+ * * When you add an ECMP route, you must specify the **DestinationCidrBlock** and **NextHopList** parameters, and you cannot specify the **NextHopType** and **NextHopId** parameters.
2004
+ * **When you use this operation to add a custom route entry to the route table of a VBR, take note of the following items:**
2005
+ * - A route table can contain at most 200 custom route entries.
2006
2006
  *
2007
2007
  * - The **NextHopList** parameter is not supported.
2008
2008
  *
2009
- * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the cloud service system route CIDR block `100.64.0.0/10`, but cannot be the same as this CIDR block.
2010
- * <notice>The system route with the destination CIDR block `100.64.0.0/10` is used for communication among cloud services within the VPC. Exercise caution when you configure a more specific route. Incorrect configurations may cause cloud services to become inaccessible.</notice>
2009
+ * - The destination CIDR block (**DestinationCidrBlock**) of a custom route entry can be a more specific CIDR block than the system route CIDR block `100.64.0.0/10` for cloud services, but cannot be the same as `100.64.0.0/10`.
2010
+ * <notice>The system route whose destination CIDR block is `100.64.0.0/10` is used for communication between cloud services in the VPC. Proceed with caution when you configure a more specific route. A configuration fault may prevent normal access and use of cloud services.</notice>
2011
2011
  *
2012
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
2012
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
2013
2013
  *
2014
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
2014
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
2015
2015
  *
2016
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
2016
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
2017
2017
  *
2018
2018
  * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
2019
2019
  *
2020
- * - You can create route entries on a VBR only when the VBR is in the active (**Active**) state, the corresponding Express Connect circuit is in the **Enabled** state, and the circuit is not under overdue payment lock.
2020
+ * - You can create a route entry on a VBR only when the VBR is in the **Active** state, the associated Express Connect circuit is in the **Enabled** state, and the VBR is not locked due to overdue payments.
2021
2021
  *
2022
- * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
2022
+ * - Only regular (non-ECMP) routing is supported. You must specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters, and you cannot specify the **NextHopList** parameter.
2023
2023
  *
2024
2024
  * @param request - CreateRouteEntryRequest
2025
2025
  * @returns CreateRouteEntryResponse
@@ -2180,13 +2180,13 @@ export default class Client extends OpenApi {
2180
2180
  * Creates an SSL-VPN server.
2181
2181
  *
2182
2182
  * @remarks
2183
- * - The **CreateSslVpnServer** operation is asynchronous. 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 the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance and determine the creation status of the SSL-VPN server:
2183
+ * - The **CreateSslVpnServer** operation is asynchronous. The system returns an instance ID, but the SSL-VPN server is not yet created and the creation 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 and determine the creation status of the SSL-VPN server:
2184
2184
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
2185
2185
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
2186
2186
  * - The **CreateSslVpnServer** operation does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
2187
2187
  * ### Before you begin
2188
- * - You have created a VPN gateway and enabled the SSL-VPN feature for the VPN gateway. For more information, see [CreateVpnGateway](https://help.aliyun.com/document_detail/2794049.html).
2189
- * - If you need 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 [Two-factor authentication for SSL-VPN supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
2188
+ * - A VPN gateway is created and the SSL-VPN feature is enabled for the VPN gateway. For more information, see [CreateVpnGateway](https://help.aliyun.com/document_detail/2794049.html).
2189
+ * - 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 [IDaaS EIAM 2.0 support for SSL-VPN two-factor authentication](https://help.aliyun.com/document_detail/2785320.html).
2190
2190
  *
2191
2191
  * @param request - CreateSslVpnServerRequest
2192
2192
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2197,13 +2197,13 @@ export default class Client extends OpenApi {
2197
2197
  * Creates an SSL-VPN server.
2198
2198
  *
2199
2199
  * @remarks
2200
- * - The **CreateSslVpnServer** operation is asynchronous. 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 the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance and determine the creation status of the SSL-VPN server:
2200
+ * - The **CreateSslVpnServer** operation is asynchronous. The system returns an instance ID, but the SSL-VPN server is not yet created and the creation 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 and determine the creation status of the SSL-VPN server:
2201
2201
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
2202
2202
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
2203
2203
  * - The **CreateSslVpnServer** operation does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
2204
2204
  * ### Before you begin
2205
- * - You have created a VPN gateway and enabled the SSL-VPN feature for the VPN gateway. For more information, see [CreateVpnGateway](https://help.aliyun.com/document_detail/2794049.html).
2206
- * - If you need 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 [Two-factor authentication for SSL-VPN supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
2205
+ * - A VPN gateway is created and the SSL-VPN feature is enabled for the VPN gateway. For more information, see [CreateVpnGateway](https://help.aliyun.com/document_detail/2794049.html).
2206
+ * - 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 [IDaaS EIAM 2.0 support for SSL-VPN two-factor authentication](https://help.aliyun.com/document_detail/2785320.html).
2207
2207
  *
2208
2208
  * @param request - CreateSslVpnServerRequest
2209
2209
  * @returns CreateSslVpnServerResponse
@@ -2213,7 +2213,7 @@ export default class Client extends OpenApi {
2213
2213
  * Creates a traffic mirror filter.
2214
2214
  *
2215
2215
  * @remarks
2216
- * The **CreateTrafficMirrorFilter** operation is asynchronous. After you invoke this operation, the system returns an instance ID, but the traffic mirror filter is not yet created and the creation task is still running in the background. You can invoke the [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) operation to query the creation status of the traffic mirror filter:
2216
+ * The **CreateTrafficMirrorFilter** operation is asynchronous. The system returns an instance ID, but the traffic mirror filter is not yet created and the creation task is still running in the background. You can call the [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) operation to query the creation status of the traffic mirror filter:
2217
2217
  * - If the traffic mirror filter is in the **Creating** state, the traffic mirror filter is being created.
2218
2218
  * - If the traffic mirror filter is in the **Created** state, the traffic mirror filter is created.
2219
2219
  *
@@ -2226,7 +2226,7 @@ export default class Client extends OpenApi {
2226
2226
  * Creates a traffic mirror filter.
2227
2227
  *
2228
2228
  * @remarks
2229
- * The **CreateTrafficMirrorFilter** operation is asynchronous. After you invoke this operation, the system returns an instance ID, but the traffic mirror filter is not yet created and the creation task is still running in the background. You can invoke the [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) operation to query the creation status of the traffic mirror filter:
2229
+ * The **CreateTrafficMirrorFilter** operation is asynchronous. The system returns an instance ID, but the traffic mirror filter is not yet created and the creation task is still running in the background. You can call the [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) operation to query the creation status of the traffic mirror filter:
2230
2230
  * - If the traffic mirror filter is in the **Creating** state, the traffic mirror filter is being created.
2231
2231
  * - If the traffic mirror filter is in the **Created** state, the traffic mirror filter is created.
2232
2232
  *
@@ -2238,10 +2238,10 @@ export default class Client extends OpenApi {
2238
2238
  * Invokes the CreateTrafficMirrorFilterRules operation to create inbound or outbound rules for traffic mirroring.
2239
2239
  *
2240
2240
  * @remarks
2241
- * - The **CreateTrafficMirrorFilterRules** operation is asynchronous. After you invoke this operation, the system returns an instance ID, but the inbound or outbound rules for traffic mirroring are not yet created. The creation task is still running in the background. You can invoke [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) to query the creation status of the inbound or outbound rules for traffic mirroring:
2242
- * - When the inbound or outbound rules for traffic mirroring are in the **Creating** state, the rules are being created.
2243
- * - When the inbound or outbound rules for traffic mirroring are in the **Created** state, the rules are created.
2244
- * - You cannot invoke the **CreateTrafficMirrorFilterRules** operation to concurrently create inbound or outbound rules for the same traffic mirror filter.
2241
+ * - The **CreateTrafficMirrorFilterRules** operation is asynchronous. After you invoke this operation, the system returns an instance ID, but the inbound or outbound rules for traffic mirroring are not immediately created because the creation node is still running in the background. You can invoke the [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) operation to query the creation status of the inbound or outbound rules for traffic mirroring:
2242
+ * - If the inbound or outbound rule for traffic mirroring is in the **Creating** state, the rule is being created.
2243
+ * - If the inbound or outbound rule for traffic mirroring is in the **Created** state, the rule is created.
2244
+ * - The **CreateTrafficMirrorFilterRules** operation does not support creating inbound or outbound rules concurrently for the same traffic mirror filter.
2245
2245
  *
2246
2246
  * @param request - CreateTrafficMirrorFilterRulesRequest
2247
2247
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2252,10 +2252,10 @@ export default class Client extends OpenApi {
2252
2252
  * Invokes the CreateTrafficMirrorFilterRules operation to create inbound or outbound rules for traffic mirroring.
2253
2253
  *
2254
2254
  * @remarks
2255
- * - The **CreateTrafficMirrorFilterRules** operation is asynchronous. After you invoke this operation, the system returns an instance ID, but the inbound or outbound rules for traffic mirroring are not yet created. The creation task is still running in the background. You can invoke [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) to query the creation status of the inbound or outbound rules for traffic mirroring:
2256
- * - When the inbound or outbound rules for traffic mirroring are in the **Creating** state, the rules are being created.
2257
- * - When the inbound or outbound rules for traffic mirroring are in the **Created** state, the rules are created.
2258
- * - You cannot invoke the **CreateTrafficMirrorFilterRules** operation to concurrently create inbound or outbound rules for the same traffic mirror filter.
2255
+ * - The **CreateTrafficMirrorFilterRules** operation is asynchronous. After you invoke this operation, the system returns an instance ID, but the inbound or outbound rules for traffic mirroring are not immediately created because the creation node is still running in the background. You can invoke the [ListTrafficMirrorFilters](https://help.aliyun.com/document_detail/261353.html) operation to query the creation status of the inbound or outbound rules for traffic mirroring:
2256
+ * - If the inbound or outbound rule for traffic mirroring is in the **Creating** state, the rule is being created.
2257
+ * - If the inbound or outbound rule for traffic mirroring is in the **Created** state, the rule is created.
2258
+ * - The **CreateTrafficMirrorFilterRules** operation does not support creating inbound or outbound rules concurrently for the same traffic mirror filter.
2259
2259
  *
2260
2260
  * @param request - CreateTrafficMirrorFilterRulesRequest
2261
2261
  * @returns CreateTrafficMirrorFilterRulesResponse
@@ -2291,17 +2291,17 @@ export default class Client extends OpenApi {
2291
2291
  *
2292
2292
  * @remarks
2293
2293
  * When you call this operation to create a vSwitch, take note of the following items:
2294
- * - The number of vSwitches in each VPC cannot exceed 150.
2295
- * - 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.
2296
- * - 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).
2297
- * - A cloud service instance can belong to only one vSwitch.
2294
+ * - You can create up to 150 vSwitches in a VPC.
2295
+ * - The first and last three IP addresses in each vSwitch CIDR block are system reserved IP addresses. For example, if the CIDR block of a vSwitch is 192.168.1.0/24, the system reserved IP addresses are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
2296
+ * - The number of cloud service instances in a vSwitch cannot exceed the remaining quota of cloud service instances in the VPC, which is 15,000 minus the current number of cloud service instances.
2297
+ * - Each cloud service instance can belong to only one vSwitch.
2298
2298
  * - vSwitches do not support multicast or broadcast.
2299
2299
  * - After a vSwitch is created, you cannot modify its CIDR block.
2300
- * - 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:
2301
- * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
2302
- * - When the vSwitch is in the **Available** state, the vSwitch is available.
2300
+ * - The **CreateVSwitch** operation is asynchronous. The system returns an instance ID, but the vSwitch is not yet created and a background task is still running. You can call the [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) operation to query the creation status of the vSwitch:
2301
+ * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
2302
+ * - If the vSwitch is in the **Available** state, the vSwitch is active.
2303
2303
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
2304
- * - 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.
2304
+ * - When you call the **CreateVSwitch** operation, the CIDR block of the vSwitch cannot fall within the following reserved address ranges: 100.64.0.0/10, 127.0.0.0/8, 169.254.0.0/16, and 224.0.0.0/4.
2305
2305
  *
2306
2306
  * @param request - CreateVSwitchRequest
2307
2307
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2313,17 +2313,17 @@ export default class Client extends OpenApi {
2313
2313
  *
2314
2314
  * @remarks
2315
2315
  * When you call this operation to create a vSwitch, take note of the following items:
2316
- * - The number of vSwitches in each VPC cannot exceed 150.
2317
- * - 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.
2318
- * - 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).
2319
- * - A cloud service instance can belong to only one vSwitch.
2316
+ * - You can create up to 150 vSwitches in a VPC.
2317
+ * - The first and last three IP addresses in each vSwitch CIDR block are system reserved IP addresses. For example, if the CIDR block of a vSwitch is 192.168.1.0/24, the system reserved IP addresses are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
2318
+ * - The number of cloud service instances in a vSwitch cannot exceed the remaining quota of cloud service instances in the VPC, which is 15,000 minus the current number of cloud service instances.
2319
+ * - Each cloud service instance can belong to only one vSwitch.
2320
2320
  * - vSwitches do not support multicast or broadcast.
2321
2321
  * - After a vSwitch is created, you cannot modify its CIDR block.
2322
- * - 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:
2323
- * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
2324
- * - When the vSwitch is in the **Available** state, the vSwitch is available.
2322
+ * - The **CreateVSwitch** operation is asynchronous. The system returns an instance ID, but the vSwitch is not yet created and a background task is still running. You can call the [DescribeVSwitchAttributes](https://help.aliyun.com/document_detail/94567.html) operation to query the creation status of the vSwitch:
2323
+ * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
2324
+ * - If the vSwitch is in the **Available** state, the vSwitch is active.
2325
2325
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
2326
- * - 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.
2326
+ * - When you call the **CreateVSwitch** operation, the CIDR block of the vSwitch cannot fall within the following reserved address ranges: 100.64.0.0/10, 127.0.0.0/8, 169.254.0.0/16, and 224.0.0.0/4.
2327
2327
  *
2328
2328
  * @param request - CreateVSwitchRequest
2329
2329
  * @returns CreateVSwitchResponse
@@ -2599,11 +2599,16 @@ export default class Client extends OpenApi {
2599
2599
  */
2600
2600
  createVpconnFromVbr(request: $_model.CreateVpconnFromVbrRequest): Promise<$_model.CreateVpconnFromVbrResponse>;
2601
2601
  /**
2602
- * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
2602
+ * Creates an IPsec-VPN connection to associate with a transit router instance.
2603
2603
  *
2604
2604
  * @remarks
2605
2605
  * >Notice:
2606
- * ### Before you begin.
2606
+ * - In the scenario where an IPsec-VPN connection is associated with a transit router, the IPsec-VPN connection is upgraded to the dual-tunnel mode. When you create an IPsec-VPN connection, apart from the required parameters, you can only configure the following request parameters related to the dual-tunnel mode: **ClientToken**, **Name**, **NetworkType**, **EffectImmediately**, the **Tags** array, **ResourceGroupId**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**. For more information, see [Instructions for dual-tunnel IPsec-VPN connections associated with transit routers](https://help.aliyun.com/document_detail/2853535.html).
2607
+ * - By default, an IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not associated with any resource. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to associate the IPsec-VPN connection with a transit router instance. After the association, the system assigns 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 IP address.
2608
+ * ### Before you begin
2609
+ * 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).
2610
+ *
2611
+ * If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number (ASN) is added to the customer gateway.
2607
2612
  *
2608
2613
  * @param request - CreateVpnAttachmentRequest
2609
2614
  * @param runtime - runtime options for this request RuntimeOptions
@@ -2611,11 +2616,16 @@ export default class Client extends OpenApi {
2611
2616
  */
2612
2617
  createVpnAttachmentWithOptions(request: $_model.CreateVpnAttachmentRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpnAttachmentResponse>;
2613
2618
  /**
2614
- * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
2619
+ * Creates an IPsec-VPN connection to associate with a transit router instance.
2615
2620
  *
2616
2621
  * @remarks
2617
2622
  * >Notice:
2618
- * ### Before you begin.
2623
+ * - In the scenario where an IPsec-VPN connection is associated with a transit router, the IPsec-VPN connection is upgraded to the dual-tunnel mode. When you create an IPsec-VPN connection, apart from the required parameters, you can only configure the following request parameters related to the dual-tunnel mode: **ClientToken**, **Name**, **NetworkType**, **EffectImmediately**, the **Tags** array, **ResourceGroupId**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**. For more information, see [Instructions for dual-tunnel IPsec-VPN connections associated with transit routers](https://help.aliyun.com/document_detail/2853535.html).
2624
+ * - By default, an IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not associated with any resource. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to associate the IPsec-VPN connection with a transit router instance. After the association, the system assigns 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 IP address.
2625
+ * ### Before you begin
2626
+ * 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).
2627
+ *
2628
+ * If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number (ASN) is added to the customer gateway.
2619
2629
  *
2620
2630
  * @param request - CreateVpnAttachmentRequest
2621
2631
  * @returns CreateVpnAttachmentResponse
@@ -3346,7 +3356,7 @@ export default class Client extends OpenApi {
3346
3356
  */
3347
3357
  deleteIpv6Gateway(request: $_model.DeleteIpv6GatewayRequest): Promise<$_model.DeleteIpv6GatewayResponse>;
3348
3358
  /**
3349
- * Deletes the Internet bandwidth.
3359
+ * Deletes the Internet bandwidth of an IPv6 address.
3350
3360
  *
3351
3361
  * @remarks
3352
3362
  * The **DeleteIpv6InternetBandwidth** operation does not support concurrent deletion of the same Internet bandwidth.
@@ -3357,7 +3367,7 @@ export default class Client extends OpenApi {
3357
3367
  */
3358
3368
  deleteIpv6InternetBandwidthWithOptions(request: $_model.DeleteIpv6InternetBandwidthRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteIpv6InternetBandwidthResponse>;
3359
3369
  /**
3360
- * Deletes the Internet bandwidth.
3370
+ * Deletes the Internet bandwidth of an IPv6 address.
3361
3371
  *
3362
3372
  * @remarks
3363
3373
  * The **DeleteIpv6InternetBandwidth** operation does not support concurrent deletion of the same Internet bandwidth.
@@ -3438,13 +3448,13 @@ export default class Client extends OpenApi {
3438
3448
  */
3439
3449
  deleteNatIpCidr(request: $_model.DeleteNatIpCidrRequest): Promise<$_model.DeleteNatIpCidrResponse>;
3440
3450
  /**
3441
- * Deletes a rate limiting rule.
3451
+ * Deletes a rate limit rule.
3442
3452
  *
3443
3453
  * @remarks
3444
- * The DeleteNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limiting rule is not immediately deleted. The deletion task continues to run in the background.
3445
- * - When the rate limiting rule is in the Deleting state, it indicates that the rule is being deleted. In this state, you can only perform query operations.
3446
- * - When the returned list of rate limiting rules is empty, it indicates that the rule is deleted.
3447
- * You cannot delete a rate limiting rule that is in the Creating state.
3454
+ * The DeleteNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limit rule is not immediately deleted. The deletion task continues to run in the background.
3455
+ * - When the rate limit rule is in the Deleting state, the rule is being deleted. In this state, you can only perform query operations.
3456
+ * - When the returned list of rate limit rules is empty, the rate limit rule is deleted.
3457
+ * You cannot delete a rate limit rule that is in the Creating state.
3448
3458
  *
3449
3459
  * @param request - DeleteNatRateLimitRuleRequest
3450
3460
  * @param runtime - runtime options for this request RuntimeOptions
@@ -3452,13 +3462,13 @@ export default class Client extends OpenApi {
3452
3462
  */
3453
3463
  deleteNatRateLimitRuleWithOptions(request: $_model.DeleteNatRateLimitRuleRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteNatRateLimitRuleResponse>;
3454
3464
  /**
3455
- * Deletes a rate limiting rule.
3465
+ * Deletes a rate limit rule.
3456
3466
  *
3457
3467
  * @remarks
3458
- * The DeleteNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limiting rule is not immediately deleted. The deletion task continues to run in the background.
3459
- * - When the rate limiting rule is in the Deleting state, it indicates that the rule is being deleted. In this state, you can only perform query operations.
3460
- * - When the returned list of rate limiting rules is empty, it indicates that the rule is deleted.
3461
- * You cannot delete a rate limiting rule that is in the Creating state.
3468
+ * The DeleteNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limit rule is not immediately deleted. The deletion task continues to run in the background.
3469
+ * - When the rate limit rule is in the Deleting state, the rule is being deleted. In this state, you can only perform query operations.
3470
+ * - When the returned list of rate limit rules is empty, the rate limit rule is deleted.
3471
+ * You cannot delete a rate limit rule that is in the Creating state.
3462
3472
  *
3463
3473
  * @param request - DeleteNatRateLimitRuleRequest
3464
3474
  * @returns DeleteNatRateLimitRuleResponse
@@ -4374,7 +4384,7 @@ export default class Client extends OpenApi {
4374
4384
  * Queries the elastic IP addresses (EIPs) created in a specified region.
4375
4385
  *
4376
4386
  * @remarks
4377
- * This operation queries the information about elastic IP addresses (EIPs) created in a specified region, including the peak bandwidth, billing method, and currently attached instance type. If you frequently skip pages during deep paging, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential paging.
4387
+ * This operation queries the information about elastic IP addresses (EIPs) created in a specified region, including the peak bandwidth, billing method, and currently associated instance type. If you frequently skip pages during deep paging, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential paging.
4378
4388
  *
4379
4389
  * @param request - DescribeEipAddressesRequest
4380
4390
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4385,7 +4395,7 @@ export default class Client extends OpenApi {
4385
4395
  * Queries the elastic IP addresses (EIPs) created in a specified region.
4386
4396
  *
4387
4397
  * @remarks
4388
- * This operation queries the information about elastic IP addresses (EIPs) created in a specified region, including the peak bandwidth, billing method, and currently attached instance type. If you frequently skip pages during deep paging, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential paging.
4398
+ * This operation queries the information about elastic IP addresses (EIPs) created in a specified region, including the peak bandwidth, billing method, and currently associated instance type. If you frequently skip pages during deep paging, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential paging.
4389
4399
  *
4390
4400
  * @param request - DescribeEipAddressesRequest
4391
4401
  * @returns DescribeEipAddressesResponse
@@ -4707,7 +4717,7 @@ export default class Client extends OpenApi {
4707
4717
  */
4708
4718
  describeIPv6Translators(request: $_model.DescribeIPv6TranslatorsRequest): Promise<$_model.DescribeIPv6TranslatorsResponse>;
4709
4719
  /**
4710
- * Queries IPv6 addresses.
4720
+ * Queries a list of IPv6 addresses.
4711
4721
  *
4712
4722
  * @param request - DescribeIpv6AddressesRequest
4713
4723
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4715,7 +4725,7 @@ export default class Client extends OpenApi {
4715
4725
  */
4716
4726
  describeIpv6AddressesWithOptions(request: $_model.DescribeIpv6AddressesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeIpv6AddressesResponse>;
4717
4727
  /**
4718
- * Queries IPv6 addresses.
4728
+ * Queries a list of IPv6 addresses.
4719
4729
  *
4720
4730
  * @param request - DescribeIpv6AddressesRequest
4721
4731
  * @returns DescribeIpv6AddressesResponse
@@ -4782,7 +4792,7 @@ export default class Client extends OpenApi {
4782
4792
  */
4783
4793
  describeNatGatewayAssociateNetworkInterfaces(request: $_model.DescribeNatGatewayAssociateNetworkInterfacesRequest): Promise<$_model.DescribeNatGatewayAssociateNetworkInterfacesResponse>;
4784
4794
  /**
4785
- * Queries the capacity reservation of a NAT gateway.
4795
+ * Queries the resource reservations of NAT gateway instances.
4786
4796
  *
4787
4797
  * @param request - DescribeNatGatewayCapacityReservationRequest
4788
4798
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4790,7 +4800,7 @@ export default class Client extends OpenApi {
4790
4800
  */
4791
4801
  describeNatGatewayCapacityReservationWithOptions(request: $_model.DescribeNatGatewayCapacityReservationRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeNatGatewayCapacityReservationResponse>;
4792
4802
  /**
4793
- * Queries the capacity reservation of a NAT gateway.
4803
+ * Queries the resource reservations of NAT gateway instances.
4794
4804
  *
4795
4805
  * @param request - DescribeNatGatewayCapacityReservationRequest
4796
4806
  * @returns DescribeNatGatewayCapacityReservationResponse
@@ -4920,10 +4930,10 @@ export default class Client extends OpenApi {
4920
4930
  */
4921
4931
  describeRegions(request: $_model.DescribeRegionsRequest): Promise<$_model.DescribeRegionsResponse>;
4922
4932
  /**
4923
- * Queries routes.
4933
+ * Queries a list of route entries.
4924
4934
  *
4925
4935
  * @remarks
4926
- * Before you call the [DeleteRouteEntry](https://help.aliyun.com/document_detail/36013.html) operation to delete a route, you can call this operation to query the next hop information of the route to be deleted.
4936
+ * Before calling the [DeleteRouteEntry](https://help.aliyun.com/document_detail/36013.html) operation to delete a route entry, you can call this operation to query the next hop information of the route entry that you want to delete.
4927
4937
  *
4928
4938
  * @param request - DescribeRouteEntryListRequest
4929
4939
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4931,10 +4941,10 @@ export default class Client extends OpenApi {
4931
4941
  */
4932
4942
  describeRouteEntryListWithOptions(request: $_model.DescribeRouteEntryListRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeRouteEntryListResponse>;
4933
4943
  /**
4934
- * Queries routes.
4944
+ * Queries a list of route entries.
4935
4945
  *
4936
4946
  * @remarks
4937
- * Before you call the [DeleteRouteEntry](https://help.aliyun.com/document_detail/36013.html) operation to delete a route, you can call this operation to query the next hop information of the route to be deleted.
4947
+ * Before calling the [DeleteRouteEntry](https://help.aliyun.com/document_detail/36013.html) operation to delete a route entry, you can call this operation to query the next hop information of the route entry that you want to delete.
4938
4948
  *
4939
4949
  * @param request - DescribeRouteEntryListRequest
4940
4950
  * @returns DescribeRouteEntryListResponse
@@ -5181,7 +5191,7 @@ export default class Client extends OpenApi {
5181
5191
  */
5182
5192
  describeVRouters(request: $_model.DescribeVRoutersRequest): Promise<$_model.DescribeVRoutersResponse>;
5183
5193
  /**
5184
- * Queries the configuration information of a specified vSwitch by calling the DescribeVSwitchAttributes operation.
5194
+ * Queries the configuration information of a specified vSwitch.
5185
5195
  *
5186
5196
  * @param request - DescribeVSwitchAttributesRequest
5187
5197
  * @param runtime - runtime options for this request RuntimeOptions
@@ -5189,17 +5199,17 @@ export default class Client extends OpenApi {
5189
5199
  */
5190
5200
  describeVSwitchAttributesWithOptions(request: $_model.DescribeVSwitchAttributesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeVSwitchAttributesResponse>;
5191
5201
  /**
5192
- * Queries the configuration information of a specified vSwitch by calling the DescribeVSwitchAttributes operation.
5202
+ * Queries the configuration information of a specified vSwitch.
5193
5203
  *
5194
5204
  * @param request - DescribeVSwitchAttributesRequest
5195
5205
  * @returns DescribeVSwitchAttributesResponse
5196
5206
  */
5197
5207
  describeVSwitchAttributes(request: $_model.DescribeVSwitchAttributesRequest): Promise<$_model.DescribeVSwitchAttributesResponse>;
5198
5208
  /**
5199
- * Queries networkable information. Internal networking is performed by vSwitch.
5209
+ * Queries networkable information. Internal networks are organized by vSwitch.
5200
5210
  *
5201
5211
  * @remarks
5202
- * 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.
5212
+ * The **DescribeVSwitches** operation may return the **Throttling.DeepPageSkip** error code when deep paging and page skipping are performed frequently. Reduce the query frequency or use sequential paging.
5203
5213
  *
5204
5214
  * @param request - DescribeVSwitchesRequest
5205
5215
  * @param runtime - runtime options for this request RuntimeOptions
@@ -5207,10 +5217,10 @@ export default class Client extends OpenApi {
5207
5217
  */
5208
5218
  describeVSwitchesWithOptions(request: $_model.DescribeVSwitchesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeVSwitchesResponse>;
5209
5219
  /**
5210
- * Queries networkable information. Internal networking is performed by vSwitch.
5220
+ * Queries networkable information. Internal networks are organized by vSwitch.
5211
5221
  *
5212
5222
  * @remarks
5213
- * 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.
5223
+ * The **DescribeVSwitches** operation may return the **Throttling.DeepPageSkip** error code when deep paging and page skipping are performed frequently. Reduce the query frequency or use sequential paging.
5214
5224
  *
5215
5225
  * @param request - DescribeVSwitchesRequest
5216
5226
  * @returns DescribeVSwitchesResponse
@@ -6367,13 +6377,13 @@ export default class Client extends OpenApi {
6367
6377
  */
6368
6378
  listTagResources(request: $_model.ListTagResourcesRequest): Promise<$_model.ListTagResourcesResponse>;
6369
6379
  /**
6370
- * Queries the tags that are bound to Express Connect resources by calling the ListTagResourcesForExpressConnect operation.
6380
+ * Queries the tags bound to Express Connect resources.
6371
6381
  *
6372
6382
  * @remarks
6373
- * - To specify the objects to query, set **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) in the request parameters.
6374
- * - **Tag.N** is a tag of a resource and consists of a key-value pair. If you specify only **Tag.N.Key**, all tag values associated with the specified tag key are returned. If you specify only **Tag.N.Value**, an error is returned.
6375
- * - If you specify both **Tag.N** and **ResourceId.N** to filter tags, **ResourceId.N** must match all specified tag key-value pairs.
6376
- * - If you specify multiple tag key-value pairs, the returned results contain resources that include all specified key-value pairs.
6383
+ * - To confirm the object to retrieve, you must specify the **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) request parameter.
6384
+ * - **Tag.N** specifies the labels of the resource, which consist of key-value pairs. If you specify only **Tag.N.Key**, all label values associated with the label key are returned. If you specify only **Tag.N.Value**, an error is reported.
6385
+ * - If you specify both **Tag.N** and **ResourceId.N** to filter labels, the resources specified by **ResourceId.N** must match all the specified label key-value pairs.
6386
+ * - If you specify multiple label key-value pairs, the returned resources must contain all the specified key-value pairs.
6377
6387
  *
6378
6388
  * @param request - ListTagResourcesForExpressConnectRequest
6379
6389
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6381,13 +6391,13 @@ export default class Client extends OpenApi {
6381
6391
  */
6382
6392
  listTagResourcesForExpressConnectWithOptions(request: $_model.ListTagResourcesForExpressConnectRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListTagResourcesForExpressConnectResponse>;
6383
6393
  /**
6384
- * Queries the tags that are bound to Express Connect resources by calling the ListTagResourcesForExpressConnect operation.
6394
+ * Queries the tags bound to Express Connect resources.
6385
6395
  *
6386
6396
  * @remarks
6387
- * - To specify the objects to query, set **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) in the request parameters.
6388
- * - **Tag.N** is a tag of a resource and consists of a key-value pair. If you specify only **Tag.N.Key**, all tag values associated with the specified tag key are returned. If you specify only **Tag.N.Value**, an error is returned.
6389
- * - If you specify both **Tag.N** and **ResourceId.N** to filter tags, **ResourceId.N** must match all specified tag key-value pairs.
6390
- * - If you specify multiple tag key-value pairs, the returned results contain resources that include all specified key-value pairs.
6397
+ * - To confirm the object to retrieve, you must specify the **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) request parameter.
6398
+ * - **Tag.N** specifies the labels of the resource, which consist of key-value pairs. If you specify only **Tag.N.Key**, all label values associated with the label key are returned. If you specify only **Tag.N.Value**, an error is reported.
6399
+ * - If you specify both **Tag.N** and **ResourceId.N** to filter labels, the resources specified by **ResourceId.N** must match all the specified label key-value pairs.
6400
+ * - If you specify multiple label key-value pairs, the returned resources must contain all the specified key-value pairs.
6391
6401
  *
6392
6402
  * @param request - ListTagResourcesForExpressConnectRequest
6393
6403
  * @returns ListTagResourcesForExpressConnectResponse
@@ -6528,7 +6538,7 @@ export default class Client extends OpenApi {
6528
6538
  */
6529
6539
  listVpnCertificateAssociations(request: $_model.ListVpnCertificateAssociationsRequest): Promise<$_model.ListVpnCertificateAssociationsResponse>;
6530
6540
  /**
6531
- * Modifies the configurations of a Border Gateway Protocol (BGP) group.
6541
+ * Modifies the configurations of a BGP group.
6532
6542
  *
6533
6543
  * @param request - ModifyBgpGroupAttributeRequest
6534
6544
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6536,7 +6546,7 @@ export default class Client extends OpenApi {
6536
6546
  */
6537
6547
  modifyBgpGroupAttributeWithOptions(request: $_model.ModifyBgpGroupAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyBgpGroupAttributeResponse>;
6538
6548
  /**
6539
- * Modifies the configurations of a Border Gateway Protocol (BGP) group.
6549
+ * Modifies the configurations of a BGP group.
6540
6550
  *
6541
6551
  * @param request - ModifyBgpGroupAttributeRequest
6542
6552
  * @returns ModifyBgpGroupAttributeResponse
@@ -6576,11 +6586,11 @@ export default class Client extends OpenApi {
6576
6586
  * Sets the maximum available bandwidth for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
6577
6587
  *
6578
6588
  * @remarks
6579
- * You can call the **ModifyCommonBandwidthPackageIpBandwidth** operation to flexibly allocate the maximum available bandwidth for each EIP added to an Internet Shared Bandwidth instance. This prevents a single EIP from continuously occupying the bandwidth of the Internet Shared Bandwidth instance.
6580
- * For example, if two EIPs are added to an Internet Shared Bandwidth instance with a bandwidth of 800 Mbps, you can set the maximum available bandwidth to 500 Mbps for the first EIP and 400 Mbps for the second EIP. After the settings are applied, the available bandwidth for the first EIP will not exceed 500 Mbps, and the available bandwidth for the second EIP will not exceed 400 Mbps.
6589
+ * By calling the **ModifyCommonBandwidthPackageIpBandwidth** operation, you can flexibly allocate the maximum available bandwidth for each EIP added to an Internet Shared Bandwidth instance. This prevents the bandwidth of the Internet Shared Bandwidth instance from being continuously occupied by a single EIP.
6590
+ * For example, if two EIPs are added to an 800 Mbit/s Internet Shared Bandwidth instance, you can set the maximum available bandwidth to 500 Mbit/s for the first EIP and 400 Mbit/s for the second EIP. After the settings are applied, the available bandwidth for the first EIP will not exceed 500 Mbit/s, and the available bandwidth for the second EIP will not exceed 400 Mbit/s.
6581
6591
  * Before you call this operation, take note of the following items:
6582
- * - This operation takes effect only when you associate the EIP with an ECS instance. If the EIP is associated with a Classic Load Balancer (CLB) instance, a NAT gateway, a secondary elastic network interface controller (NIC), or a high-availability virtual IP address, this feature does not take effect.
6583
- * - This operation is in public preview. You can only use this operation to set the maximum available bandwidth for an EIP added to an Internet Shared Bandwidth instance. This feature is not supported in the console.
6592
+ * - This operation takes effect only when the EIP is associated with an ECS instance. If you associate the EIP with a Classic Load Balancer (CLB) instance, a NAT gateway, a secondary elastic network interface controller (NIC), or a high-availability virtual IP address, this feature does not take effect.
6593
+ * - This operation is in public preview. You can only set the maximum available bandwidth for an EIP added to an Internet Shared Bandwidth instance by calling this operation. This feature is not supported in the console.
6584
6594
  * - This operation does not support concurrent configuration of the maximum available bandwidth for the same EIP.
6585
6595
  *
6586
6596
  * @param request - ModifyCommonBandwidthPackageIpBandwidthRequest
@@ -6592,11 +6602,11 @@ export default class Client extends OpenApi {
6592
6602
  * Sets the maximum available bandwidth for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
6593
6603
  *
6594
6604
  * @remarks
6595
- * You can call the **ModifyCommonBandwidthPackageIpBandwidth** operation to flexibly allocate the maximum available bandwidth for each EIP added to an Internet Shared Bandwidth instance. This prevents a single EIP from continuously occupying the bandwidth of the Internet Shared Bandwidth instance.
6596
- * For example, if two EIPs are added to an Internet Shared Bandwidth instance with a bandwidth of 800 Mbps, you can set the maximum available bandwidth to 500 Mbps for the first EIP and 400 Mbps for the second EIP. After the settings are applied, the available bandwidth for the first EIP will not exceed 500 Mbps, and the available bandwidth for the second EIP will not exceed 400 Mbps.
6605
+ * By calling the **ModifyCommonBandwidthPackageIpBandwidth** operation, you can flexibly allocate the maximum available bandwidth for each EIP added to an Internet Shared Bandwidth instance. This prevents the bandwidth of the Internet Shared Bandwidth instance from being continuously occupied by a single EIP.
6606
+ * For example, if two EIPs are added to an 800 Mbit/s Internet Shared Bandwidth instance, you can set the maximum available bandwidth to 500 Mbit/s for the first EIP and 400 Mbit/s for the second EIP. After the settings are applied, the available bandwidth for the first EIP will not exceed 500 Mbit/s, and the available bandwidth for the second EIP will not exceed 400 Mbit/s.
6597
6607
  * Before you call this operation, take note of the following items:
6598
- * - This operation takes effect only when you associate the EIP with an ECS instance. If the EIP is associated with a Classic Load Balancer (CLB) instance, a NAT gateway, a secondary elastic network interface controller (NIC), or a high-availability virtual IP address, this feature does not take effect.
6599
- * - This operation is in public preview. You can only use this operation to set the maximum available bandwidth for an EIP added to an Internet Shared Bandwidth instance. This feature is not supported in the console.
6608
+ * - This operation takes effect only when the EIP is associated with an ECS instance. If you associate the EIP with a Classic Load Balancer (CLB) instance, a NAT gateway, a secondary elastic network interface controller (NIC), or a high-availability virtual IP address, this feature does not take effect.
6609
+ * - This operation is in public preview. You can only set the maximum available bandwidth for an EIP added to an Internet Shared Bandwidth instance by calling this operation. This feature is not supported in the console.
6600
6610
  * - This operation does not support concurrent configuration of the maximum available bandwidth for the same EIP.
6601
6611
  *
6602
6612
  * @param request - ModifyCommonBandwidthPackageIpBandwidthRequest
@@ -6604,14 +6614,14 @@ export default class Client extends OpenApi {
6604
6614
  */
6605
6615
  modifyCommonBandwidthPackageIpBandwidth(request: $_model.ModifyCommonBandwidthPackageIpBandwidthRequest): Promise<$_model.ModifyCommonBandwidthPackageIpBandwidthResponse>;
6606
6616
  /**
6607
- * Modifies the maximum bandwidth of an Internet Shared Bandwidth instance.
6617
+ * Modifies the peak bandwidth of an Internet Shared Bandwidth instance.
6608
6618
  *
6609
6619
  * @remarks
6610
- * Before you call this operation, take note of the following information:
6611
- * - **ModifyCommonBandwidthPackageSpec** is an asynchronous operation. After a request is sent, the system returns a request ID, but the maximum bandwidth of the Internet Shared Bandwidth instance has not been modified yet. The modification task is still running in the background. You can call [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the status of the Internet Shared Bandwidth instance.
6612
- * - If the Internet Shared Bandwidth instance is in the **Modifying** state, the maximum bandwidth is being modified. In this state, you can only perform query operations and cannot perform other operations.
6613
- * - If the Internet Shared Bandwidth instance is in the **Available** state, the maximum bandwidth has been modified.
6614
- * - **ModifyCommonBandwidthPackageSpec** does not support concurrent modifications to the maximum bandwidth of the same Internet Shared Bandwidth instance.
6620
+ * When you call this operation, take note of the following items:
6621
+ * - The **ModifyCommonBandwidthPackageSpec** operation is asynchronous. The system returns a request ID, but the peak bandwidth of the Internet Shared Bandwidth instance is not immediately modified. The modification task is still running in the background. You can call the [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) operation to query the status of the Internet Shared Bandwidth instance.
6622
+ * - If the Internet Shared Bandwidth instance is in the **Modifying** state, the peak bandwidth is being modified. In this state, you can only perform query operations.
6623
+ * - If the Internet Shared Bandwidth instance is in the **Available** state, the peak bandwidth is modified.
6624
+ * - The **ModifyCommonBandwidthPackageSpec** operation does not support concurrent modifications to the peak bandwidth of the same Internet Shared Bandwidth instance.
6615
6625
  *
6616
6626
  * @param request - ModifyCommonBandwidthPackageSpecRequest
6617
6627
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6619,14 +6629,14 @@ export default class Client extends OpenApi {
6619
6629
  */
6620
6630
  modifyCommonBandwidthPackageSpecWithOptions(request: $_model.ModifyCommonBandwidthPackageSpecRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyCommonBandwidthPackageSpecResponse>;
6621
6631
  /**
6622
- * Modifies the maximum bandwidth of an Internet Shared Bandwidth instance.
6632
+ * Modifies the peak bandwidth of an Internet Shared Bandwidth instance.
6623
6633
  *
6624
6634
  * @remarks
6625
- * Before you call this operation, take note of the following information:
6626
- * - **ModifyCommonBandwidthPackageSpec** is an asynchronous operation. After a request is sent, the system returns a request ID, but the maximum bandwidth of the Internet Shared Bandwidth instance has not been modified yet. The modification task is still running in the background. You can call [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) to query the status of the Internet Shared Bandwidth instance.
6627
- * - If the Internet Shared Bandwidth instance is in the **Modifying** state, the maximum bandwidth is being modified. In this state, you can only perform query operations and cannot perform other operations.
6628
- * - If the Internet Shared Bandwidth instance is in the **Available** state, the maximum bandwidth has been modified.
6629
- * - **ModifyCommonBandwidthPackageSpec** does not support concurrent modifications to the maximum bandwidth of the same Internet Shared Bandwidth instance.
6635
+ * When you call this operation, take note of the following items:
6636
+ * - The **ModifyCommonBandwidthPackageSpec** operation is asynchronous. The system returns a request ID, but the peak bandwidth of the Internet Shared Bandwidth instance is not immediately modified. The modification task is still running in the background. You can call the [DescribeCommonBandwidthPackages](https://help.aliyun.com/document_detail/120309.html) operation to query the status of the Internet Shared Bandwidth instance.
6637
+ * - If the Internet Shared Bandwidth instance is in the **Modifying** state, the peak bandwidth is being modified. In this state, you can only perform query operations.
6638
+ * - If the Internet Shared Bandwidth instance is in the **Available** state, the peak bandwidth is modified.
6639
+ * - The **ModifyCommonBandwidthPackageSpec** operation does not support concurrent modifications to the peak bandwidth of the same Internet Shared Bandwidth instance.
6630
6640
  *
6631
6641
  * @param request - ModifyCommonBandwidthPackageSpecRequest
6632
6642
  * @returns ModifyCommonBandwidthPackageSpecResponse
@@ -7076,7 +7086,7 @@ export default class Client extends OpenApi {
7076
7086
  */
7077
7087
  modifyNatGatewayAttribute(request: $_model.ModifyNatGatewayAttributeRequest): Promise<$_model.ModifyNatGatewayAttributeResponse>;
7078
7088
  /**
7079
- * Updates the NAT gateway resource prefetch.
7089
+ * Modifies the NAT gateway resource prefetch.
7080
7090
  *
7081
7091
  * @remarks
7082
7092
  * Before you call this operation, make sure that you understand the [billing methods](https://www.alibabacloud.com/help/en/nat-gateway/user-guide/nat-resource-reservation) and [pricing](https://www.aliyun.com/price/product?spm=openapi-amp.newDocPublishment.0.0.77e72b1bK9GnAX#/nat/detail/nat_gw) of NAT Gateway. This operation supports creating, updating, and deleting resource reservations.
@@ -7087,7 +7097,7 @@ export default class Client extends OpenApi {
7087
7097
  */
7088
7098
  modifyNatGatewayCapacityReservationWithOptions(tmpReq: $_model.ModifyNatGatewayCapacityReservationRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyNatGatewayCapacityReservationResponse>;
7089
7099
  /**
7090
- * Updates the NAT gateway resource prefetch.
7100
+ * Modifies the NAT gateway resource prefetch.
7091
7101
  *
7092
7102
  * @remarks
7093
7103
  * Before you call this operation, make sure that you understand the [billing methods](https://www.alibabacloud.com/help/en/nat-gateway/user-guide/nat-resource-reservation) and [pricing](https://www.aliyun.com/price/product?spm=openapi-amp.newDocPublishment.0.0.77e72b1bK9GnAX#/nat/detail/nat_gw) of NAT Gateway. This operation supports creating, updating, and deleting resource reservations.
@@ -7176,13 +7186,13 @@ export default class Client extends OpenApi {
7176
7186
  */
7177
7187
  modifyNatIpCidrAttribute(request: $_model.ModifyNatIpCidrAttributeRequest): Promise<$_model.ModifyNatIpCidrAttributeResponse>;
7178
7188
  /**
7179
- * Modifies a specified rate limit rule.
7189
+ * Modifies a specified rate limiting rule.
7180
7190
  *
7181
7191
  * @remarks
7182
- * The ModifyNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limit rule is not immediately modified. The modification task continues to run in the background.
7183
- * - When the rate limit rule is in the Modifying state, the rule is being modified. In this state, you can only perform query operations.
7184
- * - When the rate limit rule is in the Available state, the rule is modified.
7185
- * You cannot modify a rate limit rule that is in the Modifying state.
7192
+ * The ModifyNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limiting rule is not immediately modified. The modification task continues to run in the background.
7193
+ * - When the rate limiting rule is in the Modifying state, it indicates that the rule is being modified. In this state, you can only perform query operations.
7194
+ * - When the rate limiting rule is in the Available state, it indicates that the rule is modified.
7195
+ * If the rate limiting rule is in the Modifying state, you cannot modify it again.
7186
7196
  *
7187
7197
  * @param request - ModifyNatRateLimitRuleRequest
7188
7198
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7190,13 +7200,13 @@ export default class Client extends OpenApi {
7190
7200
  */
7191
7201
  modifyNatRateLimitRuleWithOptions(request: $_model.ModifyNatRateLimitRuleRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyNatRateLimitRuleResponse>;
7192
7202
  /**
7193
- * Modifies a specified rate limit rule.
7203
+ * Modifies a specified rate limiting rule.
7194
7204
  *
7195
7205
  * @remarks
7196
- * The ModifyNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limit rule is not immediately modified. The modification task continues to run in the background.
7197
- * - When the rate limit rule is in the Modifying state, the rule is being modified. In this state, you can only perform query operations.
7198
- * - When the rate limit rule is in the Available state, the rule is modified.
7199
- * You cannot modify a rate limit rule that is in the Modifying state.
7206
+ * The ModifyNatRateLimitRule operation is asynchronous. The system returns a request ID, but the rate limiting rule is not immediately modified. The modification task continues to run in the background.
7207
+ * - When the rate limiting rule is in the Modifying state, it indicates that the rule is being modified. In this state, you can only perform query operations.
7208
+ * - When the rate limiting rule is in the Available state, it indicates that the rule is modified.
7209
+ * If the rate limiting rule is in the Modifying state, you cannot modify it again.
7200
7210
  *
7201
7211
  * @param request - ModifyNatRateLimitRuleRequest
7202
7212
  * @returns ModifyNatRateLimitRuleResponse
@@ -7245,11 +7255,11 @@ export default class Client extends OpenApi {
7245
7255
  */
7246
7256
  modifyPhysicalConnectionAttribute(request: $_model.ModifyPhysicalConnectionAttributeRequest): Promise<$_model.ModifyPhysicalConnectionAttributeResponse>;
7247
7257
  /**
7248
- * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
7258
+ * Invokes ModifyRouteEntry to modify custom route entry names, descriptions, and routing next hops.
7249
7259
  *
7250
7260
  * @remarks
7251
7261
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
7252
- * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
7262
+ * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as needed.
7253
7263
  *
7254
7264
  * @param request - ModifyRouteEntryRequest
7255
7265
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7257,11 +7267,11 @@ export default class Client extends OpenApi {
7257
7267
  */
7258
7268
  modifyRouteEntryWithOptions(request: $_model.ModifyRouteEntryRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyRouteEntryResponse>;
7259
7269
  /**
7260
- * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
7270
+ * Invokes ModifyRouteEntry to modify custom route entry names, descriptions, and routing next hops.
7261
7271
  *
7262
7272
  * @remarks
7263
7273
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
7264
- * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
7274
+ * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as needed.
7265
7275
  *
7266
7276
  * @param request - ModifyRouteEntryRequest
7267
7277
  * @returns ModifyRouteEntryResponse