@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.js CHANGED
@@ -41,6 +41,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
41
41
  Object.defineProperty(exports, "__esModule", { value: true });
42
42
  // This file is auto-generated, don't edit it
43
43
  const $dara = __importStar(require("@darabonba/typescript"));
44
+ const gateway_pop_1 = __importDefault(require("@alicloud/gateway-pop"));
44
45
  const openapi_core_1 = __importDefault(require("@alicloud/openapi-core"));
45
46
  const openapi_core_2 = require("@alicloud/openapi-core");
46
47
  const $_model = __importStar(require("./models/model"));
@@ -48,13 +49,15 @@ __exportStar(require("./models/model"), exports);
48
49
  class Client extends openapi_core_1.default {
49
50
  constructor(config) {
50
51
  super(config);
52
+ this._productId = "Vpc";
53
+ let gatewayClient = new gateway_pop_1.default();
54
+ this._spi = gatewayClient;
51
55
  this._endpointRule = "regional";
52
56
  this._endpointMap = {
53
57
  'cn-hangzhou': "vpc.aliyuncs.com",
54
- 'cn-shanghai-finance-1': "vpc.aliyuncs.com",
55
- 'cn-shenzhen-finance-1': "vpc.aliyuncs.com",
56
- 'cn-north-2-gov-1': "vpc.aliyuncs.com",
57
58
  'ap-northeast-2-pop': "vpc.aliyuncs.com",
59
+ 'ap-south-1': "vpc.aliyuncs.com",
60
+ 'ap-southeast-2': "vpc.aliyuncs.com",
58
61
  'cn-beijing-finance-pop': "vpc.aliyuncs.com",
59
62
  'cn-beijing-gov-1': "vpc.aliyuncs.com",
60
63
  'cn-beijing-nu16-b01': "vpc.aliyuncs.com",
@@ -86,6 +89,7 @@ class Client extends openapi_core_1.default {
86
89
  'cn-zhengzhou-nebula-1': "vpc-nebula.cn-qingdao-nebula.aliyuncs.com",
87
90
  'eu-west-1-oxs': "vpc-nebula.cn-shenzhen-cloudstone.aliyuncs.com",
88
91
  'rus-west-1-pop': "vpc.aliyuncs.com",
92
+ 'cn-nanjing': "vpc-smarthosting.cn-hangzhou-cloudstone.aliyuncs.com",
89
93
  };
90
94
  this.checkConfig(config);
91
95
  this._endpoint = this.getEndpoint("vpc", this._regionId, this._endpointRule, this._network, this._suffix, this._endpointMap, this._endpoint);
@@ -293,14 +297,14 @@ class Client extends openapi_core_1.default {
293
297
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
294
298
  *
295
299
  * @remarks
296
- * Before you invoke this operation, take note of the following items:
297
- * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
298
- * - The billing method of the EIP is pay-as-you-go.
299
- * - The EIP is in the same region as the Internet Shared Bandwidth instance.
300
+ * When you call this operation, take note of the following information:
301
+ * - When you call this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following requirements:
302
+ * - The Billable methods of the EIP are pay-as-you-go billing.
303
+ * - The EIP and the Internet Shared Bandwidth instance are in the same region.
300
304
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
301
- * - 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.
302
- * - 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.
303
- * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
305
+ * - 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.
306
+ * - 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.
307
+ * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is successfully associated with the EIP.
304
308
  *
305
309
  * @param request - AddCommonBandwidthPackageIpRequest
306
310
  * @param runtime - runtime options for this request RuntimeOptions
@@ -359,14 +363,14 @@ class Client extends openapi_core_1.default {
359
363
  * Adds an elastic IP address (EIP) to an Internet Shared Bandwidth instance.
360
364
  *
361
365
  * @remarks
362
- * Before you invoke this operation, take note of the following items:
363
- * - When you invoke this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following conditions:
364
- * - The billing method of the EIP is pay-as-you-go.
365
- * - The EIP is in the same region as the Internet Shared Bandwidth instance.
366
+ * When you call this operation, take note of the following information:
367
+ * - When you call this operation to add an EIP to an Internet Shared Bandwidth instance, the EIP must meet the following requirements:
368
+ * - The Billable methods of the EIP are pay-as-you-go billing.
369
+ * - The EIP and the Internet Shared Bandwidth instance are in the same region.
366
370
  * - The line type of the EIP is the same as that of the Internet Shared Bandwidth instance.
367
- * - 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.
368
- * - 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.
369
- * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIP.
371
+ * - 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.
372
+ * - 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.
373
+ * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is successfully associated with the EIP.
370
374
  *
371
375
  * @param request - AddCommonBandwidthPackageIpRequest
372
376
  * @returns AddCommonBandwidthPackageIpResponse
@@ -381,9 +385,9 @@ class Client extends openapi_core_1.default {
381
385
  * @remarks
382
386
  * - When you call this operation to add multiple EIPs to an Internet Shared Bandwidth instance, the EIPs must meet the following requirements:
383
387
  * - The billing method of the EIPs is pay-as-you-go.
384
- * - The EIPs are in the same region as the Internet Shared Bandwidth instance.
388
+ * - The EIPs and the Internet Shared Bandwidth instance are in the same region.
385
389
  * - The line types of the EIPs are the same as the line type of the Internet Shared Bandwidth instance.
386
- * - **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.
390
+ * - 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.
387
391
  * - 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.
388
392
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIPs.
389
393
  *
@@ -443,9 +447,9 @@ class Client extends openapi_core_1.default {
443
447
  * @remarks
444
448
  * - When you call this operation to add multiple EIPs to an Internet Shared Bandwidth instance, the EIPs must meet the following requirements:
445
449
  * - The billing method of the EIPs is pay-as-you-go.
446
- * - The EIPs are in the same region as the Internet Shared Bandwidth instance.
450
+ * - The EIPs and the Internet Shared Bandwidth instance are in the same region.
447
451
  * - The line types of the EIPs are the same as the line type of the Internet Shared Bandwidth instance.
448
- * - **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.
452
+ * - 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.
449
453
  * - 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.
450
454
  * - If the association status is **BINDED**, the Internet Shared Bandwidth instance is associated with the EIPs.
451
455
  *
@@ -738,11 +742,11 @@ class Client extends openapi_core_1.default {
738
742
  return await this.addSourcesToTrafficMirrorSessionWithOptions(request, runtime);
739
743
  }
740
744
  /**
741
- * Applies for an elastic IP address (EIP).
745
+ * Allocates an elastic IP address (EIP).
742
746
  *
743
747
  * @remarks
744
- * 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).
745
- * 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.
748
+ * 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).
749
+ * 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.
746
750
  *
747
751
  * @param request - AllocateEipAddressRequest
748
752
  * @param runtime - runtime options for this request RuntimeOptions
@@ -840,11 +844,11 @@ class Client extends openapi_core_1.default {
840
844
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.AllocateEipAddressResponse({}));
841
845
  }
842
846
  /**
843
- * Applies for an elastic IP address (EIP).
847
+ * Allocates an elastic IP address (EIP).
844
848
  *
845
849
  * @remarks
846
- * 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).
847
- * 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.
850
+ * 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).
851
+ * 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.
848
852
  *
849
853
  * @param request - AllocateEipAddressRequest
850
854
  * @returns AllocateEipAddressResponse
@@ -854,7 +858,7 @@ class Client extends openapi_core_1.default {
854
858
  return await this.allocateEipAddressWithOptions(request, runtime);
855
859
  }
856
860
  /**
857
- * Applies for a specified elastic IP address (EIP) for specific network configuration requirements.
861
+ * Allocates a specified elastic IP address (EIP) for specific network configuration requirements.
858
862
  *
859
863
  * @param request - AllocateEipAddressProRequest
860
864
  * @param runtime - runtime options for this request RuntimeOptions
@@ -940,7 +944,7 @@ class Client extends openapi_core_1.default {
940
944
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.AllocateEipAddressProResponse({}));
941
945
  }
942
946
  /**
943
- * Applies for a specified elastic IP address (EIP) for specific network configuration requirements.
947
+ * Allocates a specified elastic IP address (EIP) for specific network configuration requirements.
944
948
  *
945
949
  * @param request - AllocateEipAddressProRequest
946
950
  * @returns AllocateEipAddressProResponse
@@ -950,12 +954,12 @@ class Client extends openapi_core_1.default {
950
954
  return await this.allocateEipAddressProWithOptions(request, runtime);
951
955
  }
952
956
  /**
953
- * 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.
957
+ * 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.
954
958
  *
955
959
  * @remarks
956
- * 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.
957
- * - When the contiguous EIP group is in the **Allocating** state, the group is being allocated. In this state, you can only perform query operations.
958
- * - When the contiguous EIP group is in the **Allocated** state, the group is allocated.
960
+ * 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.
961
+ * - 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.
962
+ * - When the contiguous EIP group is in the **Allocated** state, the group has been allocated.
959
963
  *
960
964
  * @deprecated OpenAPI AllocateEipSegmentAddress is deprecated
961
965
  *
@@ -1022,12 +1026,12 @@ class Client extends openapi_core_1.default {
1022
1026
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.AllocateEipSegmentAddressResponse({}));
1023
1027
  }
1024
1028
  /**
1025
- * 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.
1029
+ * 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.
1026
1030
  *
1027
1031
  * @remarks
1028
- * 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.
1029
- * - When the contiguous EIP group is in the **Allocating** state, the group is being allocated. In this state, you can only perform query operations.
1030
- * - When the contiguous EIP group is in the **Allocated** state, the group is allocated.
1032
+ * 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.
1033
+ * - 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.
1034
+ * - When the contiguous EIP group is in the **Allocated** state, the group has been allocated.
1031
1035
  *
1032
1036
  * @deprecated OpenAPI AllocateEipSegmentAddress is deprecated
1033
1037
  *
@@ -1390,11 +1394,11 @@ class Client extends openapi_core_1.default {
1390
1394
  * Associates an elastic IP address (EIP) with a cloud service instance in the same region.
1391
1395
  *
1392
1396
  * @remarks
1393
- * - 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.
1394
- * - 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:
1395
- * - 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.
1396
- * - If the EIP is in the **InUse** state, the EIP is associated.
1397
- * - The **AssociateEipAddress** operation does not support concurrently associating the same EIP with cloud service instances.
1397
+ * - 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.
1398
+ * - 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:
1399
+ * - If the EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
1400
+ * - If the EIP is in the **InUse** state, the EIP is attached.
1401
+ * - The **AssociateEipAddress** operation does not support concurrent attachment of the same EIP to cloud service instances.
1398
1402
  *
1399
1403
  * @param request - AssociateEipAddressRequest
1400
1404
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1462,11 +1466,11 @@ class Client extends openapi_core_1.default {
1462
1466
  * Associates an elastic IP address (EIP) with a cloud service instance in the same region.
1463
1467
  *
1464
1468
  * @remarks
1465
- * - 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.
1466
- * - 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:
1467
- * - 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.
1468
- * - If the EIP is in the **InUse** state, the EIP is associated.
1469
- * - The **AssociateEipAddress** operation does not support concurrently associating the same EIP with cloud service instances.
1469
+ * - 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.
1470
+ * - 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:
1471
+ * - If the EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
1472
+ * - If the EIP is in the **InUse** state, the EIP is attached.
1473
+ * - The **AssociateEipAddress** operation does not support concurrent attachment of the same EIP to cloud service instances.
1470
1474
  *
1471
1475
  * @param request - AssociateEipAddressRequest
1472
1476
  * @returns AssociateEipAddressResponse
@@ -1476,14 +1480,14 @@ class Client extends openapi_core_1.default {
1476
1480
  return await this.associateEipAddressWithOptions(request, runtime);
1477
1481
  }
1478
1482
  /**
1479
- * Associates multiple Elastic IP addresses (EIPs) with cloud service instances in the same region.
1483
+ * Associates multiple elastic IP addresses (EIPs) with cloud service instances in the same region.
1480
1484
  *
1481
1485
  * @remarks
1482
- * - **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).
1483
- * - **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:
1484
- * - If the EIP is in the **Associating** state, the EIP is being associated. In this state, you can only perform query operations.
1485
- * - If the EIP is in the **InUse** state, the EIP is associated.
1486
- * - **AssociateEipAddressBatch** does not support concurrent association of the same EIP with cloud service instances.
1486
+ * - **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).
1487
+ * - 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:
1488
+ * - If an EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
1489
+ * - If an EIP is in the **InUse** state, the EIP is attached.
1490
+ * - The **AssociateEipAddressBatch** operation does not support concurrent attachment of the same EIP to cloud service instances.
1487
1491
  *
1488
1492
  * @param request - AssociateEipAddressBatchRequest
1489
1493
  * @param runtime - runtime options for this request RuntimeOptions
@@ -1539,14 +1543,14 @@ class Client extends openapi_core_1.default {
1539
1543
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.AssociateEipAddressBatchResponse({}));
1540
1544
  }
1541
1545
  /**
1542
- * Associates multiple Elastic IP addresses (EIPs) with cloud service instances in the same region.
1546
+ * Associates multiple elastic IP addresses (EIPs) with cloud service instances in the same region.
1543
1547
  *
1544
1548
  * @remarks
1545
- * - **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).
1546
- * - **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:
1547
- * - If the EIP is in the **Associating** state, the EIP is being associated. In this state, you can only perform query operations.
1548
- * - If the EIP is in the **InUse** state, the EIP is associated.
1549
- * - **AssociateEipAddressBatch** does not support concurrent association of the same EIP with cloud service instances.
1549
+ * - **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).
1550
+ * - 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:
1551
+ * - If an EIP is in the **Associating** state, the EIP is being attached. In this state, you can only execute query operations.
1552
+ * - If an EIP is in the **InUse** state, the EIP is attached.
1553
+ * - The **AssociateEipAddressBatch** operation does not support concurrent attachment of the same EIP to cloud service instances.
1550
1554
  *
1551
1555
  * @param request - AssociateEipAddressBatchRequest
1552
1556
  * @returns AssociateEipAddressBatchResponse
@@ -2455,7 +2459,7 @@ class Client extends openapi_core_1.default {
2455
2459
  * Cancels the maximum available bandwidth setting for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
2456
2460
  *
2457
2461
  * @remarks
2458
- * Take note of the following items when you call this operation:
2462
+ * When you call this operation, note the following information:
2459
2463
  * - After the setting is canceled, the maximum available bandwidth of the EIP is the same as that of the Internet Shared Bandwidth instance.
2460
2464
  * - The **CancelCommonBandwidthPackageIpBandwidth** operation does not support concurrent calls to cancel the maximum available bandwidth setting for the same EIP.
2461
2465
  *
@@ -2472,6 +2476,12 @@ class Client extends openapi_core_1.default {
2472
2476
  if (!$dara.isNull(request.eipId)) {
2473
2477
  query["EipId"] = request.eipId;
2474
2478
  }
2479
+ if (!$dara.isNull(request.ipInstanceId)) {
2480
+ query["IpInstanceId"] = request.ipInstanceId;
2481
+ }
2482
+ if (!$dara.isNull(request.ipType)) {
2483
+ query["IpType"] = request.ipType;
2484
+ }
2475
2485
  if (!$dara.isNull(request.ownerAccount)) {
2476
2486
  query["OwnerAccount"] = request.ownerAccount;
2477
2487
  }
@@ -2507,7 +2517,7 @@ class Client extends openapi_core_1.default {
2507
2517
  * Cancels the maximum available bandwidth setting for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
2508
2518
  *
2509
2519
  * @remarks
2510
- * Take note of the following items when you call this operation:
2520
+ * When you call this operation, note the following information:
2511
2521
  * - After the setting is canceled, the maximum available bandwidth of the EIP is the same as that of the Internet Shared Bandwidth instance.
2512
2522
  * - The **CancelCommonBandwidthPackageIpBandwidth** operation does not support concurrent calls to cancel the maximum available bandwidth setting for the same EIP.
2513
2523
  *
@@ -4194,9 +4204,9 @@ class Client extends openapi_core_1.default {
4194
4204
  * Creates a flow log.
4195
4205
  *
4196
4206
  * @remarks
4197
- * *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:
4207
+ * 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:
4198
4208
  * - If the flow log is in the **Activating** state, the flow log is being created.
4199
- * - If the flow log is in the **Active** state, the flow log is created and activated.
4209
+ * - If the flow log is in the **Active** state, the flow log is created and started.
4200
4210
  *
4201
4211
  * @param request - CreateFlowLogRequest
4202
4212
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4279,9 +4289,9 @@ class Client extends openapi_core_1.default {
4279
4289
  * Creates a flow log.
4280
4290
  *
4281
4291
  * @remarks
4282
- * *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:
4292
+ * 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:
4283
4293
  * - If the flow log is in the **Activating** state, the flow log is being created.
4284
- * - If the flow log is in the **Active** state, the flow log is created and activated.
4294
+ * - If the flow log is in the **Active** state, the flow log is created and started.
4285
4295
  *
4286
4296
  * @param request - CreateFlowLogRequest
4287
4297
  * @returns CreateFlowLogResponse
@@ -4582,9 +4592,9 @@ class Client extends openapi_core_1.default {
4582
4592
  * Creates a high-availability virtual IP address (HAVIP).
4583
4593
  *
4584
4594
  * @remarks
4585
- * *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:
4586
- * - When the HAVIP is in the **Creating** state, the HAVIP is being created.
4587
- * - When the HAVIP is in the **Available** state, the HAVIP is created.
4595
+ * *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:
4596
+ * - If the HAVIP is in the **Creating** state, the HAVIP is being created.
4597
+ * - If the HAVIP is in the **Available** state, the HAVIP is created.
4588
4598
  *
4589
4599
  * @param request - CreateHaVipRequest
4590
4600
  * @param runtime - runtime options for this request RuntimeOptions
@@ -4649,9 +4659,9 @@ class Client extends openapi_core_1.default {
4649
4659
  * Creates a high-availability virtual IP address (HAVIP).
4650
4660
  *
4651
4661
  * @remarks
4652
- * *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:
4653
- * - When the HAVIP is in the **Creating** state, the HAVIP is being created.
4654
- * - When the HAVIP is in the **Available** state, the HAVIP is created.
4662
+ * *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:
4663
+ * - If the HAVIP is in the **Creating** state, the HAVIP is being created.
4664
+ * - If the HAVIP is in the **Available** state, the HAVIP is created.
4655
4665
  *
4656
4666
  * @param request - CreateHaVipRequest
4657
4667
  * @returns CreateHaVipResponse
@@ -6075,20 +6085,20 @@ class Client extends openapi_core_1.default {
6075
6085
  return await this.createPublicIpAddressPoolWithOptions(request, runtime);
6076
6086
  }
6077
6087
  /**
6078
- * Creates custom route entries in a route table of a vRouter in bulk.
6088
+ * Creates custom route entry (routing) in the routing table of a VPC vRouter.
6079
6089
  *
6080
6090
  * @remarks
6081
- * - **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:
6082
- * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
6083
- * - If the custom route entry is in the **Created** state, the custom route entry has been created.
6084
- * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
6085
- * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
6086
- * - A route table can contain a maximum of 200 custom route entries.
6087
- * - 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.
6091
+ * - 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:
6092
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
6093
+ * - If custom route entry is in the **Created** state, custom route entry is created.
6094
+ * - The **CreateRouteEntries** operation does not support concurrent creation of multiple custom route entries in the same VPC.
6095
+ * **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:**
6096
+ * - A routing table can contain at most 200 custom route entry (routing).
6097
+ * - 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.
6088
6098
  * - 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.
6089
6099
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
6090
- * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6091
- * - Multiple custom route entries can point to the same next hop (**NextHop**).
6100
+ * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, it is processed as a 32-bit mask.
6101
+ * - Multiple custom route entry (routing) can point to the same next hop (**NextHop**).
6092
6102
  * - The next hop (**NextHop**) of a custom route entry must be in the same VPC as the route table.
6093
6103
  *
6094
6104
  * @param request - CreateRouteEntriesRequest
@@ -6139,20 +6149,20 @@ class Client extends openapi_core_1.default {
6139
6149
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateRouteEntriesResponse({}));
6140
6150
  }
6141
6151
  /**
6142
- * Creates custom route entries in a route table of a vRouter in bulk.
6152
+ * Creates custom route entry (routing) in the routing table of a VPC vRouter.
6143
6153
  *
6144
6154
  * @remarks
6145
- * - **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:
6146
- * - If the custom route entry is in the **Creating** state, the custom route entry is being created.
6147
- * - If the custom route entry is in the **Created** state, the custom route entry has been created.
6148
- * - **CreateRouteEntries** does not support concurrent bulk creation of custom route entries in the same VPC.
6149
- * **When you use this operation to add custom route entries to a route table of a vRouter, take note of the following items:**
6150
- * - A route table can contain a maximum of 200 custom route entries.
6151
- * - 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.
6155
+ * - 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:
6156
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
6157
+ * - If custom route entry is in the **Created** state, custom route entry is created.
6158
+ * - The **CreateRouteEntries** operation does not support concurrent creation of multiple custom route entries in the same VPC.
6159
+ * **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:**
6160
+ * - A routing table can contain at most 200 custom route entry (routing).
6161
+ * - 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.
6152
6162
  * - 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.
6153
6163
  * - The destination CIDR blocks (**DstCidrBlock**) of route entries in the same route table must be unique.
6154
- * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6155
- * - Multiple custom route entries can point to the same next hop (**NextHop**).
6164
+ * - If the specified destination CIDR block (**DstCidrBlock**) is an IP address, it is processed as a 32-bit mask.
6165
+ * - Multiple custom route entry (routing) can point to the same next hop (**NextHop**).
6156
6166
  * - The next hop (**NextHop**) of a custom route entry must be in the same VPC as the route table.
6157
6167
  *
6158
6168
  * @param request - CreateRouteEntriesRequest
@@ -6163,47 +6173,47 @@ class Client extends openapi_core_1.default {
6163
6173
  return await this.createRouteEntriesWithOptions(request, runtime);
6164
6174
  }
6165
6175
  /**
6166
- * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
6176
+ * Creates a custom route entry on a vRouter or a Virtual Border Router (VBR).
6167
6177
  *
6168
6178
  * @remarks
6169
- * - 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:
6170
- * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
6171
- * - If the custom route entry is in the **Created** state, the custom route entry has been added.
6172
- * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
6173
- * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
6174
- * **When you use this operation to add custom route entries to a route table of a vRouter, note the following items:**
6175
- * > 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.
6176
- * - A route table can contain a maximum of 200 custom route entries.
6177
- * - 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.
6178
- * - 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.
6179
- * <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>
6180
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6181
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6182
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6179
+ * - 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:
6180
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
6181
+ * - If custom route entry is in the **Created** state, custom route entry is created.
6182
+ * - The **CreateRouteEntry** operation does not support concurrent creation of custom route entries in the same VPC or on the same VBR.
6183
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
6184
+ * **When you use this operation to add a custom route entry to the route table of a vRouter, take note of the following items:**
6185
+ * > 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.
6186
+ * - A route table can contain at most 200 custom route entries.
6187
+ * - 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.
6188
+ * - 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`.
6189
+ * <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>
6190
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6191
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
6192
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
6183
6193
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
6184
- * - You can configure ECMP routing by using the **NextHopList** parameter settings:
6185
- * * When you add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6194
+ * - You can use the **NextHopList** parameter settings to configure equal-cost multi-path (ECMP) routing:
6195
+ * * 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.
6186
6196
  *
6187
- * * When you add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
6188
- * **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), note the following items:**
6189
- * - A route table can contain a maximum of 200 custom route entries.
6197
+ * * When you add an ECMP route, you must specify the **DestinationCidrBlock** and **NextHopList** parameters, and you cannot specify the **NextHopType** and **NextHopId** parameters.
6198
+ * **When you use this operation to add a custom route entry to the route table of a VBR, take note of the following items:**
6199
+ * - A route table can contain at most 200 custom route entries.
6190
6200
  *
6191
6201
  * - The **NextHopList** parameter is not supported.
6192
6202
  *
6193
- * - 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.
6194
- * <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>
6203
+ * - 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`.
6204
+ * <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>
6195
6205
  *
6196
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6206
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6197
6207
  *
6198
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6208
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
6199
6209
  *
6200
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6210
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
6201
6211
  *
6202
6212
  * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
6203
6213
  *
6204
- * - 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.
6214
+ * - 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.
6205
6215
  *
6206
- * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6216
+ * - Only regular (non-ECMP) routing is supported. You must specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters, and you cannot specify the **NextHopList** parameter.
6207
6217
  *
6208
6218
  * @param request - CreateRouteEntryRequest
6209
6219
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6271,47 +6281,47 @@ class Client extends openapi_core_1.default {
6271
6281
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateRouteEntryResponse({}));
6272
6282
  }
6273
6283
  /**
6274
- * Creates a custom route entry on a vRouter or Virtual Border Router (VBR).
6284
+ * Creates a custom route entry on a vRouter or a Virtual Border Router (VBR).
6275
6285
  *
6276
6286
  * @remarks
6277
- * - 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:
6278
- * - If the custom route entry is in the **Creating** state, the custom route entry is being added.
6279
- * - If the custom route entry is in the **Created** state, the custom route entry has been added.
6280
- * - The **CreateRouteEntry** operation does not support concurrent addition of custom route entries in the same VPC or the same VBR.
6281
- * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as appropriate.
6282
- * **When you use this operation to add custom route entries to a route table of a vRouter, note the following items:**
6283
- * > 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.
6284
- * - A route table can contain a maximum of 200 custom route entries.
6285
- * - 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.
6286
- * - 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.
6287
- * <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>
6288
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6289
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6290
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6287
+ * - 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:
6288
+ * - If custom route entry is in the **Creating** state, custom route entry is being created.
6289
+ * - If custom route entry is in the **Created** state, custom route entry is created.
6290
+ * - The **CreateRouteEntry** operation does not support concurrent creation of custom route entries in the same VPC or on the same VBR.
6291
+ * - The **CreateRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
6292
+ * **When you use this operation to add a custom route entry to the route table of a vRouter, take note of the following items:**
6293
+ * > 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.
6294
+ * - A route table can contain at most 200 custom route entries.
6295
+ * - 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.
6296
+ * - 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`.
6297
+ * <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>
6298
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6299
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
6300
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
6291
6301
  * - The next hop (**NextHopId**) of a custom route entry must be in the same VPC as the route table.
6292
- * - You can configure ECMP routing by using the **NextHopList** parameter settings:
6293
- * * When you add a non-ECMP custom route, specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6302
+ * - You can use the **NextHopList** parameter settings to configure equal-cost multi-path (ECMP) routing:
6303
+ * * 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.
6294
6304
  *
6295
- * * When you add an ECMP route, specify the **DestinationCidrBlock** and **NextHopList** parameters. Do not specify the **NextHopType** or **NextHopId** parameter.
6296
- * **When you use this operation to add custom route entries to a route table of a Virtual Border Router (VBR), note the following items:**
6297
- * - A route table can contain a maximum of 200 custom route entries.
6305
+ * * When you add an ECMP route, you must specify the **DestinationCidrBlock** and **NextHopList** parameters, and you cannot specify the **NextHopType** and **NextHopId** parameters.
6306
+ * **When you use this operation to add a custom route entry to the route table of a VBR, take note of the following items:**
6307
+ * - A route table can contain at most 200 custom route entries.
6298
6308
  *
6299
6309
  * - The **NextHopList** parameter is not supported.
6300
6310
  *
6301
- * - 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.
6302
- * <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>
6311
+ * - 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`.
6312
+ * <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>
6303
6313
  *
6304
- * - The destination CIDR blocks (**DestinationCidrBlock**) of route entries in the same route table must be unique.
6314
+ * - Route entries in the same route table cannot have the same destination CIDR block (**DestinationCidrBlock**).
6305
6315
  *
6306
- * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, the system processes it with a 32-bit mask.
6316
+ * - If the specified destination CIDR block (**DestinationCidrBlock**) is an IP address, it is processed as a 32-bit subnet mask.
6307
6317
  *
6308
- * - Multiple custom route entries can point to the same next hop (**NextHopId**).
6318
+ * - You can point more than one custom routing entry to the same next hop (**NextHopId**).
6309
6319
  *
6310
6320
  * - The next hop (**NextHopId**) of a custom route entry must be a vRouter interface associated with the VBR.
6311
6321
  *
6312
- * - 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.
6322
+ * - 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.
6313
6323
  *
6314
- * - Only non-ECMP route entries are supported. Specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters. Do not specify the **NextHopList** parameter.
6324
+ * - Only regular (non-ECMP) routing is supported. You must specify the **DestinationCidrBlock**, **NextHopType**, and **NextHopId** parameters, and you cannot specify the **NextHopList** parameter.
6315
6325
  *
6316
6326
  * @param request - CreateRouteEntryRequest
6317
6327
  * @returns CreateRouteEntryResponse
@@ -6799,13 +6809,13 @@ class Client extends openapi_core_1.default {
6799
6809
  * Creates an SSL-VPN server.
6800
6810
  *
6801
6811
  * @remarks
6802
- * - 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:
6812
+ * - 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:
6803
6813
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
6804
6814
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
6805
6815
  * - The **CreateSslVpnServer** operation does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
6806
6816
  * ### Before you begin
6807
- * - 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).
6808
- * - 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).
6817
+ * - 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).
6818
+ * - 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).
6809
6819
  *
6810
6820
  * @param request - CreateSslVpnServerRequest
6811
6821
  * @param runtime - runtime options for this request RuntimeOptions
@@ -6894,13 +6904,13 @@ class Client extends openapi_core_1.default {
6894
6904
  * Creates an SSL-VPN server.
6895
6905
  *
6896
6906
  * @remarks
6897
- * - 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:
6907
+ * - 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:
6898
6908
  * - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
6899
6909
  * - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
6900
6910
  * - The **CreateSslVpnServer** operation does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
6901
6911
  * ### Before you begin
6902
- * - 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).
6903
- * - 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).
6912
+ * - 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).
6913
+ * - 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).
6904
6914
  *
6905
6915
  * @param request - CreateSslVpnServerRequest
6906
6916
  * @returns CreateSslVpnServerResponse
@@ -6913,7 +6923,7 @@ class Client extends openapi_core_1.default {
6913
6923
  * Creates a traffic mirror filter.
6914
6924
  *
6915
6925
  * @remarks
6916
- * 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:
6926
+ * 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:
6917
6927
  * - If the traffic mirror filter is in the **Creating** state, the traffic mirror filter is being created.
6918
6928
  * - If the traffic mirror filter is in the **Created** state, the traffic mirror filter is created.
6919
6929
  *
@@ -6983,7 +6993,7 @@ class Client extends openapi_core_1.default {
6983
6993
  * Creates a traffic mirror filter.
6984
6994
  *
6985
6995
  * @remarks
6986
- * 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:
6996
+ * 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:
6987
6997
  * - If the traffic mirror filter is in the **Creating** state, the traffic mirror filter is being created.
6988
6998
  * - If the traffic mirror filter is in the **Created** state, the traffic mirror filter is created.
6989
6999
  *
@@ -6998,10 +7008,10 @@ class Client extends openapi_core_1.default {
6998
7008
  * Invokes the CreateTrafficMirrorFilterRules operation to create inbound or outbound rules for traffic mirroring.
6999
7009
  *
7000
7010
  * @remarks
7001
- * - 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:
7002
- * - When the inbound or outbound rules for traffic mirroring are in the **Creating** state, the rules are being created.
7003
- * - When the inbound or outbound rules for traffic mirroring are in the **Created** state, the rules are created.
7004
- * - You cannot invoke the **CreateTrafficMirrorFilterRules** operation to concurrently create inbound or outbound rules for the same traffic mirror filter.
7011
+ * - 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:
7012
+ * - If the inbound or outbound rule for traffic mirroring is in the **Creating** state, the rule is being created.
7013
+ * - If the inbound or outbound rule for traffic mirroring is in the **Created** state, the rule is created.
7014
+ * - The **CreateTrafficMirrorFilterRules** operation does not support creating inbound or outbound rules concurrently for the same traffic mirror filter.
7005
7015
  *
7006
7016
  * @param request - CreateTrafficMirrorFilterRulesRequest
7007
7017
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7060,10 +7070,10 @@ class Client extends openapi_core_1.default {
7060
7070
  * Invokes the CreateTrafficMirrorFilterRules operation to create inbound or outbound rules for traffic mirroring.
7061
7071
  *
7062
7072
  * @remarks
7063
- * - 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:
7064
- * - When the inbound or outbound rules for traffic mirroring are in the **Creating** state, the rules are being created.
7065
- * - When the inbound or outbound rules for traffic mirroring are in the **Created** state, the rules are created.
7066
- * - You cannot invoke the **CreateTrafficMirrorFilterRules** operation to concurrently create inbound or outbound rules for the same traffic mirror filter.
7073
+ * - 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:
7074
+ * - If the inbound or outbound rule for traffic mirroring is in the **Creating** state, the rule is being created.
7075
+ * - If the inbound or outbound rule for traffic mirroring is in the **Created** state, the rule is created.
7076
+ * - The **CreateTrafficMirrorFilterRules** operation does not support creating inbound or outbound rules concurrently for the same traffic mirror filter.
7067
7077
  *
7068
7078
  * @param request - CreateTrafficMirrorFilterRulesRequest
7069
7079
  * @returns CreateTrafficMirrorFilterRulesResponse
@@ -7180,17 +7190,17 @@ class Client extends openapi_core_1.default {
7180
7190
  *
7181
7191
  * @remarks
7182
7192
  * When you call this operation to create a vSwitch, take note of the following items:
7183
- * - The number of vSwitches in each VPC cannot exceed 150.
7184
- * - 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.
7185
- * - 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).
7186
- * - A cloud service instance can belong to only one vSwitch.
7193
+ * - You can create up to 150 vSwitches in a VPC.
7194
+ * - 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.
7195
+ * - 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.
7196
+ * - Each cloud service instance can belong to only one vSwitch.
7187
7197
  * - vSwitches do not support multicast or broadcast.
7188
7198
  * - After a vSwitch is created, you cannot modify its CIDR block.
7189
- * - 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:
7190
- * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
7191
- * - When the vSwitch is in the **Available** state, the vSwitch is available.
7199
+ * - 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:
7200
+ * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
7201
+ * - If the vSwitch is in the **Available** state, the vSwitch is active.
7192
7202
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
7193
- * - 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.
7203
+ * - 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.
7194
7204
  *
7195
7205
  * @param request - CreateVSwitchRequest
7196
7206
  * @param runtime - runtime options for this request RuntimeOptions
@@ -7217,6 +7227,9 @@ class Client extends openapi_core_1.default {
7217
7227
  if (!$dara.isNull(request.ipv6CidrMask)) {
7218
7228
  query["Ipv6CidrMask"] = request.ipv6CidrMask;
7219
7229
  }
7230
+ if (!$dara.isNull(request.ipv6Only)) {
7231
+ query["Ipv6Only"] = request.ipv6Only;
7232
+ }
7220
7233
  if (!$dara.isNull(request.ownerAccount)) {
7221
7234
  query["OwnerAccount"] = request.ownerAccount;
7222
7235
  }
@@ -7268,17 +7281,17 @@ class Client extends openapi_core_1.default {
7268
7281
  *
7269
7282
  * @remarks
7270
7283
  * When you call this operation to create a vSwitch, take note of the following items:
7271
- * - The number of vSwitches in each VPC cannot exceed 150.
7272
- * - 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.
7273
- * - 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).
7274
- * - A cloud service instance can belong to only one vSwitch.
7284
+ * - You can create up to 150 vSwitches in a VPC.
7285
+ * - 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.
7286
+ * - 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.
7287
+ * - Each cloud service instance can belong to only one vSwitch.
7275
7288
  * - vSwitches do not support multicast or broadcast.
7276
7289
  * - After a vSwitch is created, you cannot modify its CIDR block.
7277
- * - 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:
7278
- * - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
7279
- * - When the vSwitch is in the **Available** state, the vSwitch is available.
7290
+ * - 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:
7291
+ * - If the vSwitch is in the **Pending** state, the vSwitch is being configured.
7292
+ * - If the vSwitch is in the **Available** state, the vSwitch is active.
7280
7293
  * - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
7281
- * - 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.
7294
+ * - 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.
7282
7295
  *
7283
7296
  * @param request - CreateVSwitchRequest
7284
7297
  * @returns CreateVSwitchResponse
@@ -8127,11 +8140,16 @@ class Client extends openapi_core_1.default {
8127
8140
  return await this.createVpconnFromVbrWithOptions(request, runtime);
8128
8141
  }
8129
8142
  /**
8130
- * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
8143
+ * Creates an IPsec-VPN connection to associate with a transit router instance.
8131
8144
  *
8132
8145
  * @remarks
8133
8146
  * >Notice:
8134
- * ### Before you begin.
8147
+ * - 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).
8148
+ * - 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.
8149
+ * ### Before you begin
8150
+ * 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).
8151
+ *
8152
+ * 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.
8135
8153
  *
8136
8154
  * @param request - CreateVpnAttachmentRequest
8137
8155
  * @param runtime - runtime options for this request RuntimeOptions
@@ -8236,11 +8254,16 @@ class Client extends openapi_core_1.default {
8236
8254
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.CreateVpnAttachmentResponse({}));
8237
8255
  }
8238
8256
  /**
8239
- * Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
8257
+ * Creates an IPsec-VPN connection to associate with a transit router instance.
8240
8258
  *
8241
8259
  * @remarks
8242
8260
  * >Notice:
8243
- * ### Before you begin.
8261
+ * - 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).
8262
+ * - 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.
8263
+ * ### Before you begin
8264
+ * 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).
8265
+ *
8266
+ * 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.
8244
8267
  *
8245
8268
  * @param request - CreateVpnAttachmentRequest
8246
8269
  * @returns CreateVpnAttachmentResponse
@@ -10405,7 +10428,7 @@ class Client extends openapi_core_1.default {
10405
10428
  return await this.deleteIpv6GatewayWithOptions(request, runtime);
10406
10429
  }
10407
10430
  /**
10408
- * Deletes the Internet bandwidth.
10431
+ * Deletes the Internet bandwidth of an IPv6 address.
10409
10432
  *
10410
10433
  * @remarks
10411
10434
  * The **DeleteIpv6InternetBandwidth** operation does not support concurrent deletion of the same Internet bandwidth.
@@ -10464,7 +10487,7 @@ class Client extends openapi_core_1.default {
10464
10487
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteIpv6InternetBandwidthResponse({}));
10465
10488
  }
10466
10489
  /**
10467
- * Deletes the Internet bandwidth.
10490
+ * Deletes the Internet bandwidth of an IPv6 address.
10468
10491
  *
10469
10492
  * @remarks
10470
10493
  * The **DeleteIpv6InternetBandwidth** operation does not support concurrent deletion of the same Internet bandwidth.
@@ -10695,13 +10718,13 @@ class Client extends openapi_core_1.default {
10695
10718
  return await this.deleteNatIpCidrWithOptions(request, runtime);
10696
10719
  }
10697
10720
  /**
10698
- * Deletes a rate limiting rule.
10721
+ * Deletes a rate limit rule.
10699
10722
  *
10700
10723
  * @remarks
10701
- * 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.
10702
- * - 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.
10703
- * - When the returned list of rate limiting rules is empty, it indicates that the rule is deleted.
10704
- * You cannot delete a rate limiting rule that is in the Creating state.
10724
+ * 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.
10725
+ * - When the rate limit rule is in the Deleting state, the rule is being deleted. In this state, you can only perform query operations.
10726
+ * - When the returned list of rate limit rules is empty, the rate limit rule is deleted.
10727
+ * You cannot delete a rate limit rule that is in the Creating state.
10705
10728
  *
10706
10729
  * @param request - DeleteNatRateLimitRuleRequest
10707
10730
  * @param runtime - runtime options for this request RuntimeOptions
@@ -10739,13 +10762,13 @@ class Client extends openapi_core_1.default {
10739
10762
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DeleteNatRateLimitRuleResponse({}));
10740
10763
  }
10741
10764
  /**
10742
- * Deletes a rate limiting rule.
10765
+ * Deletes a rate limit rule.
10743
10766
  *
10744
10767
  * @remarks
10745
- * 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.
10746
- * - 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.
10747
- * - When the returned list of rate limiting rules is empty, it indicates that the rule is deleted.
10748
- * You cannot delete a rate limiting rule that is in the Creating state.
10768
+ * 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.
10769
+ * - When the rate limit rule is in the Deleting state, the rule is being deleted. In this state, you can only perform query operations.
10770
+ * - When the returned list of rate limit rules is empty, the rate limit rule is deleted.
10771
+ * You cannot delete a rate limit rule that is in the Creating state.
10749
10772
  *
10750
10773
  * @param request - DeleteNatRateLimitRuleRequest
10751
10774
  * @returns DeleteNatRateLimitRuleResponse
@@ -13404,7 +13427,7 @@ class Client extends openapi_core_1.default {
13404
13427
  * Queries the elastic IP addresses (EIPs) created in a specified region.
13405
13428
  *
13406
13429
  * @remarks
13407
- * 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.
13430
+ * 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.
13408
13431
  *
13409
13432
  * @param request - DescribeEipAddressesRequest
13410
13433
  * @param runtime - runtime options for this request RuntimeOptions
@@ -13508,7 +13531,7 @@ class Client extends openapi_core_1.default {
13508
13531
  * Queries the elastic IP addresses (EIPs) created in a specified region.
13509
13532
  *
13510
13533
  * @remarks
13511
- * 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.
13534
+ * 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.
13512
13535
  *
13513
13536
  * @param request - DescribeEipAddressesRequest
13514
13537
  * @returns DescribeEipAddressesResponse
@@ -14856,7 +14879,7 @@ class Client extends openapi_core_1.default {
14856
14879
  return await this.describeIPv6TranslatorsWithOptions(request, runtime);
14857
14880
  }
14858
14881
  /**
14859
- * Queries IPv6 addresses.
14882
+ * Queries a list of IPv6 addresses.
14860
14883
  *
14861
14884
  * @param request - DescribeIpv6AddressesRequest
14862
14885
  * @param runtime - runtime options for this request RuntimeOptions
@@ -14948,7 +14971,7 @@ class Client extends openapi_core_1.default {
14948
14971
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeIpv6AddressesResponse({}));
14949
14972
  }
14950
14973
  /**
14951
- * Queries IPv6 addresses.
14974
+ * Queries a list of IPv6 addresses.
14952
14975
  *
14953
14976
  * @param request - DescribeIpv6AddressesRequest
14954
14977
  * @returns DescribeIpv6AddressesResponse
@@ -15240,7 +15263,7 @@ class Client extends openapi_core_1.default {
15240
15263
  return await this.describeNatGatewayAssociateNetworkInterfacesWithOptions(request, runtime);
15241
15264
  }
15242
15265
  /**
15243
- * Queries the capacity reservation of a NAT gateway.
15266
+ * Queries the resource reservations of NAT gateway instances.
15244
15267
  *
15245
15268
  * @param request - DescribeNatGatewayCapacityReservationRequest
15246
15269
  * @param runtime - runtime options for this request RuntimeOptions
@@ -15266,7 +15289,7 @@ class Client extends openapi_core_1.default {
15266
15289
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeNatGatewayCapacityReservationResponse({}));
15267
15290
  }
15268
15291
  /**
15269
- * Queries the capacity reservation of a NAT gateway.
15292
+ * Queries the resource reservations of NAT gateway instances.
15270
15293
  *
15271
15294
  * @param request - DescribeNatGatewayCapacityReservationRequest
15272
15295
  * @returns DescribeNatGatewayCapacityReservationResponse
@@ -15777,10 +15800,10 @@ class Client extends openapi_core_1.default {
15777
15800
  return await this.describeRegionsWithOptions(request, runtime);
15778
15801
  }
15779
15802
  /**
15780
- * Queries routes.
15803
+ * Queries a list of route entries.
15781
15804
  *
15782
15805
  * @remarks
15783
- * 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.
15806
+ * 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.
15784
15807
  *
15785
15808
  * @param request - DescribeRouteEntryListRequest
15786
15809
  * @param runtime - runtime options for this request RuntimeOptions
@@ -15860,10 +15883,10 @@ class Client extends openapi_core_1.default {
15860
15883
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeRouteEntryListResponse({}));
15861
15884
  }
15862
15885
  /**
15863
- * Queries routes.
15886
+ * Queries a list of route entries.
15864
15887
  *
15865
15888
  * @remarks
15866
- * 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.
15889
+ * 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.
15867
15890
  *
15868
15891
  * @param request - DescribeRouteEntryListRequest
15869
15892
  * @returns DescribeRouteEntryListResponse
@@ -16828,7 +16851,7 @@ class Client extends openapi_core_1.default {
16828
16851
  return await this.describeVRoutersWithOptions(request, runtime);
16829
16852
  }
16830
16853
  /**
16831
- * Queries the configuration information of a specified vSwitch by calling the DescribeVSwitchAttributes operation.
16854
+ * Queries the configuration information of a specified vSwitch.
16832
16855
  *
16833
16856
  * @param request - DescribeVSwitchAttributesRequest
16834
16857
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16875,7 +16898,7 @@ class Client extends openapi_core_1.default {
16875
16898
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeVSwitchAttributesResponse({}));
16876
16899
  }
16877
16900
  /**
16878
- * Queries the configuration information of a specified vSwitch by calling the DescribeVSwitchAttributes operation.
16901
+ * Queries the configuration information of a specified vSwitch.
16879
16902
  *
16880
16903
  * @param request - DescribeVSwitchAttributesRequest
16881
16904
  * @returns DescribeVSwitchAttributesResponse
@@ -16885,10 +16908,10 @@ class Client extends openapi_core_1.default {
16885
16908
  return await this.describeVSwitchAttributesWithOptions(request, runtime);
16886
16909
  }
16887
16910
  /**
16888
- * Queries networkable information. Internal networking is performed by vSwitch.
16911
+ * Queries networkable information. Internal networks are organized by vSwitch.
16889
16912
  *
16890
16913
  * @remarks
16891
- * 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.
16914
+ * 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.
16892
16915
  *
16893
16916
  * @param request - DescribeVSwitchesRequest
16894
16917
  * @param runtime - runtime options for this request RuntimeOptions
@@ -16903,6 +16926,9 @@ class Client extends openapi_core_1.default {
16903
16926
  if (!$dara.isNull(request.enableIpv6)) {
16904
16927
  query["EnableIpv6"] = request.enableIpv6;
16905
16928
  }
16929
+ if (!$dara.isNull(request.ipv6Only)) {
16930
+ query["Ipv6Only"] = request.ipv6Only;
16931
+ }
16906
16932
  if (!$dara.isNull(request.isDefault)) {
16907
16933
  query["IsDefault"] = request.isDefault;
16908
16934
  }
@@ -16968,10 +16994,10 @@ class Client extends openapi_core_1.default {
16968
16994
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.DescribeVSwitchesResponse({}));
16969
16995
  }
16970
16996
  /**
16971
- * Queries networkable information. Internal networking is performed by vSwitch.
16997
+ * Queries networkable information. Internal networks are organized by vSwitch.
16972
16998
  *
16973
16999
  * @remarks
16974
- * 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.
17000
+ * 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.
16975
17001
  *
16976
17002
  * @param request - DescribeVSwitchesRequest
16977
17003
  * @returns DescribeVSwitchesResponse
@@ -21134,13 +21160,13 @@ class Client extends openapi_core_1.default {
21134
21160
  return await this.listTagResourcesWithOptions(request, runtime);
21135
21161
  }
21136
21162
  /**
21137
- * Queries the tags that are bound to Express Connect resources by calling the ListTagResourcesForExpressConnect operation.
21163
+ * Queries the tags bound to Express Connect resources.
21138
21164
  *
21139
21165
  * @remarks
21140
- * - To specify the objects to query, set **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) in the request parameters.
21141
- * - **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.
21142
- * - If you specify both **Tag.N** and **ResourceId.N** to filter tags, **ResourceId.N** must match all specified tag key-value pairs.
21143
- * - If you specify multiple tag key-value pairs, the returned results contain resources that include all specified key-value pairs.
21166
+ * - To confirm the object to retrieve, you must specify the **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) request parameter.
21167
+ * - **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.
21168
+ * - 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.
21169
+ * - If you specify multiple label key-value pairs, the returned resources must contain all the specified key-value pairs.
21144
21170
  *
21145
21171
  * @param request - ListTagResourcesForExpressConnectRequest
21146
21172
  * @param runtime - runtime options for this request RuntimeOptions
@@ -21196,13 +21222,13 @@ class Client extends openapi_core_1.default {
21196
21222
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ListTagResourcesForExpressConnectResponse({}));
21197
21223
  }
21198
21224
  /**
21199
- * Queries the tags that are bound to Express Connect resources by calling the ListTagResourcesForExpressConnect operation.
21225
+ * Queries the tags bound to Express Connect resources.
21200
21226
  *
21201
21227
  * @remarks
21202
- * - To specify the objects to query, set **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) in the request parameters.
21203
- * - **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.
21204
- * - If you specify both **Tag.N** and **ResourceId.N** to filter tags, **ResourceId.N** must match all specified tag key-value pairs.
21205
- * - If you specify multiple tag key-value pairs, the returned results contain resources that include all specified key-value pairs.
21228
+ * - To confirm the object to retrieve, you must specify the **ResourceId.N** or **Tag.N** (**Tag.N.Key** and **Tag.N.Value**) request parameter.
21229
+ * - **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.
21230
+ * - 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.
21231
+ * - If you specify multiple label key-value pairs, the returned resources must contain all the specified key-value pairs.
21206
21232
  *
21207
21233
  * @param request - ListTagResourcesForExpressConnectRequest
21208
21234
  * @returns ListTagResourcesForExpressConnectResponse
@@ -21787,7 +21813,7 @@ class Client extends openapi_core_1.default {
21787
21813
  return await this.listVpnCertificateAssociationsWithOptions(request, runtime);
21788
21814
  }
21789
21815
  /**
21790
- * Modifies the configurations of a Border Gateway Protocol (BGP) group.
21816
+ * Modifies the configurations of a BGP group.
21791
21817
  *
21792
21818
  * @param request - ModifyBgpGroupAttributeRequest
21793
21819
  * @param runtime - runtime options for this request RuntimeOptions
@@ -21858,7 +21884,7 @@ class Client extends openapi_core_1.default {
21858
21884
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyBgpGroupAttributeResponse({}));
21859
21885
  }
21860
21886
  /**
21861
- * Modifies the configurations of a Border Gateway Protocol (BGP) group.
21887
+ * Modifies the configurations of a BGP group.
21862
21888
  *
21863
21889
  * @param request - ModifyBgpGroupAttributeRequest
21864
21890
  * @returns ModifyBgpGroupAttributeResponse
@@ -22000,11 +22026,11 @@ class Client extends openapi_core_1.default {
22000
22026
  * Sets the maximum available bandwidth for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
22001
22027
  *
22002
22028
  * @remarks
22003
- * 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.
22004
- * 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.
22029
+ * 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.
22030
+ * 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.
22005
22031
  * Before you call this operation, take note of the following items:
22006
- * - 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.
22007
- * - 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.
22032
+ * - 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.
22033
+ * - 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.
22008
22034
  * - This operation does not support concurrent configuration of the maximum available bandwidth for the same EIP.
22009
22035
  *
22010
22036
  * @param request - ModifyCommonBandwidthPackageIpBandwidthRequest
@@ -22023,6 +22049,12 @@ class Client extends openapi_core_1.default {
22023
22049
  if (!$dara.isNull(request.eipId)) {
22024
22050
  query["EipId"] = request.eipId;
22025
22051
  }
22052
+ if (!$dara.isNull(request.ipInstanceId)) {
22053
+ query["IpInstanceId"] = request.ipInstanceId;
22054
+ }
22055
+ if (!$dara.isNull(request.ipType)) {
22056
+ query["IpType"] = request.ipType;
22057
+ }
22026
22058
  if (!$dara.isNull(request.ownerAccount)) {
22027
22059
  query["OwnerAccount"] = request.ownerAccount;
22028
22060
  }
@@ -22058,11 +22090,11 @@ class Client extends openapi_core_1.default {
22058
22090
  * Sets the maximum available bandwidth for an elastic IP address (EIP) that is added to an Internet Shared Bandwidth instance.
22059
22091
  *
22060
22092
  * @remarks
22061
- * 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.
22062
- * 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.
22093
+ * 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.
22094
+ * 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.
22063
22095
  * Before you call this operation, take note of the following items:
22064
- * - 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.
22065
- * - 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.
22096
+ * - 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.
22097
+ * - 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.
22066
22098
  * - This operation does not support concurrent configuration of the maximum available bandwidth for the same EIP.
22067
22099
  *
22068
22100
  * @param request - ModifyCommonBandwidthPackageIpBandwidthRequest
@@ -22073,14 +22105,14 @@ class Client extends openapi_core_1.default {
22073
22105
  return await this.modifyCommonBandwidthPackageIpBandwidthWithOptions(request, runtime);
22074
22106
  }
22075
22107
  /**
22076
- * Modifies the maximum bandwidth of an Internet Shared Bandwidth instance.
22108
+ * Modifies the peak bandwidth of an Internet Shared Bandwidth instance.
22077
22109
  *
22078
22110
  * @remarks
22079
- * Before you call this operation, take note of the following information:
22080
- * - **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.
22081
- * - 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.
22082
- * - If the Internet Shared Bandwidth instance is in the **Available** state, the maximum bandwidth has been modified.
22083
- * - **ModifyCommonBandwidthPackageSpec** does not support concurrent modifications to the maximum bandwidth of the same Internet Shared Bandwidth instance.
22111
+ * When you call this operation, take note of the following items:
22112
+ * - 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.
22113
+ * - 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.
22114
+ * - If the Internet Shared Bandwidth instance is in the **Available** state, the peak bandwidth is modified.
22115
+ * - The **ModifyCommonBandwidthPackageSpec** operation does not support concurrent modifications to the peak bandwidth of the same Internet Shared Bandwidth instance.
22084
22116
  *
22085
22117
  * @param request - ModifyCommonBandwidthPackageSpecRequest
22086
22118
  * @param runtime - runtime options for this request RuntimeOptions
@@ -22127,14 +22159,14 @@ class Client extends openapi_core_1.default {
22127
22159
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyCommonBandwidthPackageSpecResponse({}));
22128
22160
  }
22129
22161
  /**
22130
- * Modifies the maximum bandwidth of an Internet Shared Bandwidth instance.
22162
+ * Modifies the peak bandwidth of an Internet Shared Bandwidth instance.
22131
22163
  *
22132
22164
  * @remarks
22133
- * Before you call this operation, take note of the following information:
22134
- * - **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.
22135
- * - 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.
22136
- * - If the Internet Shared Bandwidth instance is in the **Available** state, the maximum bandwidth has been modified.
22137
- * - **ModifyCommonBandwidthPackageSpec** does not support concurrent modifications to the maximum bandwidth of the same Internet Shared Bandwidth instance.
22165
+ * When you call this operation, take note of the following items:
22166
+ * - 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.
22167
+ * - 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.
22168
+ * - If the Internet Shared Bandwidth instance is in the **Available** state, the peak bandwidth is modified.
22169
+ * - The **ModifyCommonBandwidthPackageSpec** operation does not support concurrent modifications to the peak bandwidth of the same Internet Shared Bandwidth instance.
22138
22170
  *
22139
22171
  * @param request - ModifyCommonBandwidthPackageSpecRequest
22140
22172
  * @returns ModifyCommonBandwidthPackageSpecResponse
@@ -23836,7 +23868,7 @@ class Client extends openapi_core_1.default {
23836
23868
  return await this.modifyNatGatewayAttributeWithOptions(request, runtime);
23837
23869
  }
23838
23870
  /**
23839
- * Updates the NAT gateway resource prefetch.
23871
+ * Modifies the NAT gateway resource prefetch.
23840
23872
  *
23841
23873
  * @remarks
23842
23874
  * 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.
@@ -23888,7 +23920,7 @@ class Client extends openapi_core_1.default {
23888
23920
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyNatGatewayCapacityReservationResponse({}));
23889
23921
  }
23890
23922
  /**
23891
- * Updates the NAT gateway resource prefetch.
23923
+ * Modifies the NAT gateway resource prefetch.
23892
23924
  *
23893
23925
  * @remarks
23894
23926
  * 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.
@@ -24139,13 +24171,13 @@ class Client extends openapi_core_1.default {
24139
24171
  return await this.modifyNatIpCidrAttributeWithOptions(request, runtime);
24140
24172
  }
24141
24173
  /**
24142
- * Modifies a specified rate limit rule.
24174
+ * Modifies a specified rate limiting rule.
24143
24175
  *
24144
24176
  * @remarks
24145
- * 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.
24146
- * - When the rate limit rule is in the Modifying state, the rule is being modified. In this state, you can only perform query operations.
24147
- * - When the rate limit rule is in the Available state, the rule is modified.
24148
- * You cannot modify a rate limit rule that is in the Modifying state.
24177
+ * 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.
24178
+ * - 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.
24179
+ * - When the rate limiting rule is in the Available state, it indicates that the rule is modified.
24180
+ * If the rate limiting rule is in the Modifying state, you cannot modify it again.
24149
24181
  *
24150
24182
  * @param request - ModifyNatRateLimitRuleRequest
24151
24183
  * @param runtime - runtime options for this request RuntimeOptions
@@ -24198,13 +24230,13 @@ class Client extends openapi_core_1.default {
24198
24230
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyNatRateLimitRuleResponse({}));
24199
24231
  }
24200
24232
  /**
24201
- * Modifies a specified rate limit rule.
24233
+ * Modifies a specified rate limiting rule.
24202
24234
  *
24203
24235
  * @remarks
24204
- * 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.
24205
- * - When the rate limit rule is in the Modifying state, the rule is being modified. In this state, you can only perform query operations.
24206
- * - When the rate limit rule is in the Available state, the rule is modified.
24207
- * You cannot modify a rate limit rule that is in the Modifying state.
24236
+ * 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.
24237
+ * - 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.
24238
+ * - When the rate limiting rule is in the Available state, it indicates that the rule is modified.
24239
+ * If the rate limiting rule is in the Modifying state, you cannot modify it again.
24208
24240
  *
24209
24241
  * @param request - ModifyNatRateLimitRuleRequest
24210
24242
  * @returns ModifyNatRateLimitRuleResponse
@@ -24382,11 +24414,11 @@ class Client extends openapi_core_1.default {
24382
24414
  return await this.modifyPhysicalConnectionAttributeWithOptions(request, runtime);
24383
24415
  }
24384
24416
  /**
24385
- * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
24417
+ * Invokes ModifyRouteEntry to modify custom route entry names, descriptions, and routing next hops.
24386
24418
  *
24387
24419
  * @remarks
24388
24420
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
24389
- * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
24421
+ * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as needed.
24390
24422
  *
24391
24423
  * @param request - ModifyRouteEntryRequest
24392
24424
  * @param runtime - runtime options for this request RuntimeOptions
@@ -24451,11 +24483,11 @@ class Client extends openapi_core_1.default {
24451
24483
  return $dara.cast(await this.callApi(params, req, runtime), new $_model.ModifyRouteEntryResponse({}));
24452
24484
  }
24453
24485
  /**
24454
- * Calls the ModifyRouteEntry operation to modify the name, description, and next hop of a custom route entry.
24486
+ * Invokes ModifyRouteEntry to modify custom route entry names, descriptions, and routing next hops.
24455
24487
  *
24456
24488
  * @remarks
24457
24489
  * - The **ModifyRouteEntry** operation does not support concurrent modifications to the name and description of the same custom route entry.
24458
- * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the operation as needed.
24490
+ * - The **ModifyRouteEntry** operation may return the **TaskConflict** error code in concurrent scenarios. Retry the request as needed.
24459
24491
  *
24460
24492
  * @param request - ModifyRouteEntryRequest
24461
24493
  * @returns ModifyRouteEntryResponse