@alicloud/vpc20160428 7.2.4 → 7.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/client.d.ts +413 -318
- package/dist/client.js +479 -341
- package/dist/client.js.map +1 -1
- package/dist/models/ActivateRouterInterfaceRequest.d.ts +2 -1
- package/dist/models/ActivateRouterInterfaceRequest.js.map +1 -1
- package/dist/models/AllocateEipAddressRequest.d.ts +14 -14
- package/dist/models/AssociateMacSecKeyRequest.d.ts +3 -3
- package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.d.ts +5 -7
- package/dist/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.js.map +1 -1
- package/dist/models/AssociateVpcCidrBlockRequest.d.ts +5 -5
- package/dist/models/AssociateVpcCidrBlockResponseBody.d.ts +1 -1
- package/dist/models/AssociateVpnGatewayWithCertificateRequest.d.ts +3 -3
- package/dist/models/AttachDhcpOptionsSetToVpcRequest.d.ts +2 -2
- package/dist/models/AttachVbrToVpconnRequest.d.ts +8 -6
- package/dist/models/AttachVbrToVpconnRequest.js.map +1 -1
- package/dist/models/AttachVbrToVpconnResponseBody.d.ts +1 -1
- package/dist/models/CancelPhysicalConnectionRequest.d.ts +1 -1
- package/dist/models/CheckVpnBgpEnabledRequest.d.ts +1 -1
- package/dist/models/CompletePhysicalConnectionLoarequest.d.ts +10 -10
- package/dist/models/ConnectRouterInterfaceRequest.d.ts +1 -1
- package/dist/models/CreateCustomerGatewayRequest.d.ts +4 -4
- package/dist/models/CreateCustomerGatewayResponseBody.d.ts +1 -1
- package/dist/models/CreateEnhancedVpnGatewayRequest.d.ts +3 -3
- package/dist/models/CreateFailoverTestJobRequest.d.ts +11 -11
- package/dist/models/CreateFailoverTestJobResponseBody.d.ts +1 -1
- package/dist/models/CreateIpsecServerRequest.d.ts +2 -2
- package/dist/models/CreatePhysicalConnectionRequest.d.ts +13 -11
- package/dist/models/CreatePhysicalConnectionRequest.js.map +1 -1
- package/dist/models/CreatePhysicalConnectionSetupOrderRequest.d.ts +10 -8
- package/dist/models/CreatePhysicalConnectionSetupOrderRequest.js.map +1 -1
- package/dist/models/CreateRouteTargetGroupRequest.d.ts +3 -3
- package/dist/models/CreateSslVpnServerRequest.d.ts +11 -11
- package/dist/models/CreateVbrHaRequest.d.ts +5 -5
- package/dist/models/CreateVbrHaResponseBody.d.ts +1 -1
- package/dist/models/CreateVcoRouteEntryRequest.d.ts +2 -2
- package/dist/models/CreateVcoRouteEntryResponseBody.d.ts +1 -1
- package/dist/models/CreateVirtualPhysicalConnectionRequest.d.ts +9 -9
- package/dist/models/CreateVpconnFromVbrRequest.d.ts +2 -2
- package/dist/models/CreateVpnAttachmentRequest.d.ts +73 -133
- package/dist/models/CreateVpnAttachmentRequest.js.map +1 -1
- package/dist/models/CreateVpnAttachmentResponseBody.d.ts +3 -3
- package/dist/models/CreateVpnConnectionRequest.d.ts +95 -131
- package/dist/models/CreateVpnConnectionRequest.js.map +1 -1
- package/dist/models/CreateVpnConnectionResponseBody.d.ts +1 -1
- package/dist/models/CreateVpnGatewayRequest.d.ts +17 -17
- package/dist/models/CreateVpnGatewayResponseBody.d.ts +2 -2
- package/dist/models/CreateVpnPbrRouteEntryRequest.d.ts +13 -13
- package/dist/models/CreateVpnPbrRouteEntryResponseBody.d.ts +6 -6
- package/dist/models/CreateVswitchCidrReservationRequest.d.ts +15 -7
- package/dist/models/CreateVswitchCidrReservationRequest.js +2 -0
- package/dist/models/CreateVswitchCidrReservationRequest.js.map +1 -1
- package/dist/models/CreateVswitchRequest.d.ts +9 -9
- package/dist/models/DeleteBgpGroupRequest.d.ts +2 -2
- package/dist/models/DeleteBgpNetworkRequest.d.ts +4 -4
- package/dist/models/DeleteFailoverTestJobRequest.d.ts +4 -4
- package/dist/models/DeleteIpsecServerRequest.d.ts +4 -4
- package/dist/models/DeleteNatGatewayRequest.d.ts +4 -4
- package/dist/models/DeletePublicIpAddressPoolCidrBlockRequest.d.ts +3 -3
- package/dist/models/DeleteRouteEntriesRequest.d.ts +2 -2
- package/dist/models/DeleteRouteEntriesResponseBody.d.ts +2 -2
- package/dist/models/DeleteVbrHaRequest.d.ts +3 -3
- package/dist/models/DeleteVpnGatewayRequest.d.ts +3 -3
- package/dist/models/DeleteVpnRouteEntryRequest.d.ts +2 -2
- package/dist/models/DescribeCustomerGatewayRequest.d.ts +1 -1
- package/dist/models/DescribeCustomerGatewayResponseBody.d.ts +2 -2
- package/dist/models/DescribeCustomerGatewaysRequest.d.ts +1 -1
- package/dist/models/DescribeEipAddressesRequest.d.ts +7 -75
- package/dist/models/DescribeEipAddressesRequest.js.map +1 -1
- package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.d.ts +5 -3
- package/dist/models/DescribeExpressConnectTrafficQosQueueRequest.js.map +1 -1
- package/dist/models/DescribeExpressConnectTrafficQosQueueResponseBody.d.ts +12 -12
- package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.d.ts +10 -6
- package/dist/models/DescribeExpressConnectTrafficQosRuleRequest.js.map +1 -1
- package/dist/models/DescribeExpressConnectTrafficQosRuleResponseBody.d.ts +16 -16
- package/dist/models/DescribeFailoverTestJobRequest.d.ts +2 -2
- package/dist/models/DescribeFailoverTestJobResponseBody.d.ts +6 -6
- package/dist/models/DescribeFailoverTestJobsRequest.d.ts +8 -8
- package/dist/models/DescribeFailoverTestJobsResponseBody.d.ts +14 -14
- package/dist/models/DescribePhysicalConnectionLoarequest.d.ts +3 -2
- package/dist/models/DescribePhysicalConnectionLoarequest.js.map +1 -1
- package/dist/models/DescribePhysicalConnectionLoaresponseBody.d.ts +14 -7
- package/dist/models/DescribePhysicalConnectionLoaresponseBody.js.map +1 -1
- package/dist/models/DescribePhysicalConnectionsRequest.d.ts +55 -0
- package/dist/models/DescribePhysicalConnectionsRequest.js.map +1 -1
- package/dist/models/DescribeRouterInterfaceAttributeResponseBody.d.ts +22 -22
- package/dist/models/DescribeRouterInterfacesRequest.d.ts +7 -7
- package/dist/models/DescribeRouterInterfacesResponseBody.d.ts +1 -1
- package/dist/models/DescribeSslVpnClientCertRequest.d.ts +1 -1
- package/dist/models/DescribeSslVpnClientCertResponseBody.d.ts +3 -3
- package/dist/models/DescribeSslVpnServersRequest.d.ts +1 -1
- package/dist/models/DescribeSslVpnServersResponseBody.d.ts +1 -1
- package/dist/models/DescribeTagKeysForExpressConnectRequest.d.ts +2 -0
- package/dist/models/DescribeTagKeysForExpressConnectRequest.js.map +1 -1
- package/dist/models/DescribeVbrHaRequest.d.ts +6 -6
- package/dist/models/DescribeVbrHaResponseBody.d.ts +2 -2
- package/dist/models/DescribeVcoRouteEntriesResponseBody.d.ts +10 -10
- package/dist/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.d.ts +3 -3
- package/dist/models/DescribeVirtualBorderRoutersRequest.d.ts +6 -26
- package/dist/models/DescribeVirtualBorderRoutersRequest.js.map +1 -1
- package/dist/models/DescribeVirtualBorderRoutersResponseBody.d.ts +2 -2
- package/dist/models/DescribeVpcGrantRulesToEcrRequest.d.ts +7 -7
- package/dist/models/DescribeVpcGrantRulesToEcrResponseBody.d.ts +8 -8
- package/dist/models/DescribeVpcsRequest.d.ts +7 -7
- package/dist/models/DescribeVpnAttachmentsRequest.d.ts +4 -4
- package/dist/models/DescribeVpnAttachmentsResponseBody.d.ts +9 -9
- package/dist/models/DescribeVpnConnectionLogsRequest.d.ts +2 -2
- package/dist/models/DescribeVpnConnectionLogsResponseBody.d.ts +1 -1
- package/dist/models/DescribeVpnConnectionRequest.d.ts +1 -1
- package/dist/models/DescribeVpnConnectionResponseBody.d.ts +21 -72
- package/dist/models/DescribeVpnConnectionResponseBody.js.map +1 -1
- package/dist/models/DescribeVpnConnectionsRequest.d.ts +6 -8
- package/dist/models/DescribeVpnConnectionsRequest.js.map +1 -1
- package/dist/models/DescribeVpnCrossAccountAuthorizationsRequest.d.ts +2 -2
- package/dist/models/DescribeVpnCrossAccountAuthorizationsResponseBody.d.ts +5 -5
- package/dist/models/DescribeVpnGatewayResponseBody.d.ts +8 -8
- package/dist/models/DescribeVpnGatewaysRequest.d.ts +2 -2
- package/dist/models/DescribeVpnGatewaysResponseBody.d.ts +1 -1
- package/dist/models/DescribeVpnPbrRouteEntriesRequest.d.ts +1 -1
- package/dist/models/DescribeVpnPbrRouteEntriesResponseBody.d.ts +1 -1
- package/dist/models/DescribeVpnSslServerLogsRequest.d.ts +2 -2
- package/dist/models/DescribeVswitchesRequest.d.ts +7 -7
- package/dist/models/DescribeVswitchesResponseBody.d.ts +1 -1
- package/dist/models/DiagnoseVpnGatewayRequest.d.ts +1 -1
- package/dist/models/DiagnoseVpnGatewayResponseBody.d.ts +2 -2
- package/dist/models/DisassociateMacSecKeyRequest.d.ts +2 -2
- package/dist/models/DissociateVpnGatewayWithCertificateRequest.d.ts +2 -2
- package/dist/models/DownloadVpnConnectionConfigResponseBody.d.ts +11 -11
- package/dist/models/EnablePhysicalConnectionRequest.d.ts +5 -7
- package/dist/models/EnablePhysicalConnectionRequest.js.map +1 -1
- package/dist/models/GetNatGatewayAttributeRequest.d.ts +1 -1
- package/dist/models/GetNatGatewayAttributeResponseBody.d.ts +20 -20
- package/dist/models/GetVpnGatewayDiagnoseResultRequest.d.ts +3 -3
- package/dist/models/GetVpnGatewayDiagnoseResultResponseBody.d.ts +12 -12
- package/dist/models/GrantInstanceToVbrRequest.d.ts +6 -6
- package/dist/models/GrantInstanceToVbrShrinkRequest.d.ts +6 -6
- package/dist/models/ListBusinessAccessPointsResponseBody.d.ts +40 -2
- package/dist/models/ListBusinessAccessPointsResponseBody.js.map +1 -1
- package/dist/models/ListIpsecServerLogsRequest.d.ts +2 -2
- package/dist/models/ListIpsecServerLogsResponseBody.d.ts +1 -1
- package/dist/models/ListIpsecServersRequest.d.ts +3 -3
- package/dist/models/ListIpsecServersResponseBody.d.ts +7 -7
- package/dist/models/ListVirtualPhysicalConnectionsRequest.d.ts +7 -7
- package/dist/models/ListVirtualPhysicalConnectionsResponseBody.d.ts +20 -20
- package/dist/models/ListVpnCertificateAssociationsRequest.d.ts +3 -3
- package/dist/models/ListVpnCertificateAssociationsResponseBody.d.ts +2 -2
- package/dist/models/ModifyCustomerGatewayAttributeRequest.d.ts +1 -1
- package/dist/models/ModifyPhysicalConnectionAttributeRequest.d.ts +10 -3
- package/dist/models/ModifyPhysicalConnectionAttributeRequest.js.map +1 -1
- package/dist/models/ModifySslVpnServerRequest.d.ts +11 -11
- package/dist/models/ModifySslVpnServerResponseBody.d.ts +1 -1
- package/dist/models/ModifyVcoRouteEntryWeightRequest.d.ts +4 -4
- package/dist/models/ModifyVpcAttributeRequest.d.ts +4 -4
- package/dist/models/ModifyVpcCidrBlockRequest.d.ts +78 -0
- package/dist/models/ModifyVpcCidrBlockRequest.js +68 -0
- package/dist/models/ModifyVpcCidrBlockRequest.js.map +1 -0
- package/dist/models/ModifyVpcCidrBlockResponse.d.ts +19 -0
- package/dist/models/ModifyVpcCidrBlockResponse.js +69 -0
- package/dist/models/ModifyVpcCidrBlockResponse.js.map +1 -0
- package/dist/models/ModifyVpcCidrBlockResponseBody.d.ts +21 -0
- package/dist/models/ModifyVpcCidrBlockResponseBody.js +58 -0
- package/dist/models/ModifyVpcCidrBlockResponseBody.js.map +1 -0
- package/dist/models/ModifyVpnAttachmentAttributeRequest.d.ts +57 -133
- package/dist/models/ModifyVpnAttachmentAttributeRequest.js.map +1 -1
- package/dist/models/ModifyVpnAttachmentAttributeResponseBody.d.ts +54 -96
- package/dist/models/ModifyVpnAttachmentAttributeResponseBody.js.map +1 -1
- package/dist/models/ModifyVpnConnectionAttributeRequest.d.ts +77 -148
- package/dist/models/ModifyVpnConnectionAttributeRequest.js.map +1 -1
- package/dist/models/ModifyVpnConnectionAttributeResponseBody.d.ts +25 -52
- package/dist/models/ModifyVpnConnectionAttributeResponseBody.js.map +1 -1
- package/dist/models/ModifyVpnGatewayAttributeRequest.d.ts +5 -5
- package/dist/models/ModifyVpnPbrRouteEntryPriorityRequest.d.ts +5 -5
- package/dist/models/ModifyVpnRouteEntryWeightRequest.d.ts +2 -2
- package/dist/models/MoveResourceGroupRequest.d.ts +1 -1
- package/dist/models/MoveVpnResourceGroupRequest.d.ts +2 -2
- package/dist/models/ReleaseEipAddressRequest.d.ts +2 -2
- package/dist/models/UnassociateVpcCidrBlockRequest.d.ts +3 -3
- package/dist/models/UpdateDhcpOptionsSetAttributeRequest.d.ts +8 -8
- package/dist/models/UpdateIpsecServerRequest.d.ts +1 -1
- package/dist/models/UpdateIpv4gatewayAttributeRequest.d.ts +6 -6
- package/dist/models/model.d.ts +3 -0
- package/dist/models/model.js +11 -5
- package/dist/models/model.js.map +1 -1
- package/package.json +1 -1
- package/src/client.ts +488 -341
- package/src/models/ActivateRouterInterfaceRequest.ts +3 -2
- package/src/models/AllocateEipAddressRequest.ts +14 -14
- package/src/models/AssociateMacSecKeyRequest.ts +3 -3
- package/src/models/AssociatePhysicalConnectionToVirtualBorderRouterRequest.ts +5 -7
- package/src/models/AssociateVpcCidrBlockRequest.ts +5 -5
- package/src/models/AssociateVpcCidrBlockResponseBody.ts +1 -1
- package/src/models/AssociateVpnGatewayWithCertificateRequest.ts +3 -3
- package/src/models/AttachDhcpOptionsSetToVpcRequest.ts +2 -2
- package/src/models/AttachVbrToVpconnRequest.ts +8 -6
- package/src/models/AttachVbrToVpconnResponseBody.ts +1 -1
- package/src/models/CancelPhysicalConnectionRequest.ts +1 -1
- package/src/models/CheckVpnBgpEnabledRequest.ts +1 -1
- package/src/models/CompletePhysicalConnectionLoarequest.ts +10 -10
- package/src/models/ConnectRouterInterfaceRequest.ts +1 -1
- package/src/models/CreateCustomerGatewayRequest.ts +4 -4
- package/src/models/CreateCustomerGatewayResponseBody.ts +1 -1
- package/src/models/CreateEnhancedVpnGatewayRequest.ts +3 -3
- package/src/models/CreateFailoverTestJobRequest.ts +11 -11
- package/src/models/CreateFailoverTestJobResponseBody.ts +1 -1
- package/src/models/CreateIpsecServerRequest.ts +2 -2
- package/src/models/CreatePhysicalConnectionRequest.ts +13 -11
- package/src/models/CreatePhysicalConnectionSetupOrderRequest.ts +10 -8
- package/src/models/CreateRouteTargetGroupRequest.ts +3 -3
- package/src/models/CreateSslVpnServerRequest.ts +11 -11
- package/src/models/CreateVbrHaRequest.ts +5 -5
- package/src/models/CreateVbrHaResponseBody.ts +1 -1
- package/src/models/CreateVcoRouteEntryRequest.ts +2 -2
- package/src/models/CreateVcoRouteEntryResponseBody.ts +1 -1
- package/src/models/CreateVirtualPhysicalConnectionRequest.ts +9 -9
- package/src/models/CreateVpconnFromVbrRequest.ts +2 -2
- package/src/models/CreateVpnAttachmentRequest.ts +75 -135
- package/src/models/CreateVpnAttachmentResponseBody.ts +3 -3
- package/src/models/CreateVpnConnectionRequest.ts +99 -135
- package/src/models/CreateVpnConnectionResponseBody.ts +1 -1
- package/src/models/CreateVpnGatewayRequest.ts +17 -17
- package/src/models/CreateVpnGatewayResponseBody.ts +2 -2
- package/src/models/CreateVpnPbrRouteEntryRequest.ts +13 -13
- package/src/models/CreateVpnPbrRouteEntryResponseBody.ts +6 -6
- package/src/models/CreateVswitchCidrReservationRequest.ts +17 -7
- package/src/models/CreateVswitchRequest.ts +9 -9
- package/src/models/DeleteBgpGroupRequest.ts +2 -2
- package/src/models/DeleteBgpNetworkRequest.ts +4 -4
- package/src/models/DeleteFailoverTestJobRequest.ts +4 -4
- package/src/models/DeleteIpsecServerRequest.ts +4 -4
- package/src/models/DeleteNatGatewayRequest.ts +4 -4
- package/src/models/DeletePublicIpAddressPoolCidrBlockRequest.ts +3 -3
- package/src/models/DeleteRouteEntriesRequest.ts +2 -2
- package/src/models/DeleteRouteEntriesResponseBody.ts +2 -2
- package/src/models/DeleteVbrHaRequest.ts +3 -3
- package/src/models/DeleteVpnGatewayRequest.ts +3 -3
- package/src/models/DeleteVpnRouteEntryRequest.ts +2 -2
- package/src/models/DescribeCustomerGatewayRequest.ts +1 -1
- package/src/models/DescribeCustomerGatewayResponseBody.ts +2 -2
- package/src/models/DescribeCustomerGatewaysRequest.ts +1 -1
- package/src/models/DescribeEipAddressesRequest.ts +8 -76
- package/src/models/DescribeExpressConnectTrafficQosQueueRequest.ts +5 -3
- package/src/models/DescribeExpressConnectTrafficQosQueueResponseBody.ts +12 -12
- package/src/models/DescribeExpressConnectTrafficQosRuleRequest.ts +10 -6
- package/src/models/DescribeExpressConnectTrafficQosRuleResponseBody.ts +16 -16
- package/src/models/DescribeFailoverTestJobRequest.ts +2 -2
- package/src/models/DescribeFailoverTestJobResponseBody.ts +6 -6
- package/src/models/DescribeFailoverTestJobsRequest.ts +8 -8
- package/src/models/DescribeFailoverTestJobsResponseBody.ts +14 -14
- package/src/models/DescribePhysicalConnectionLoarequest.ts +3 -2
- package/src/models/DescribePhysicalConnectionLoaresponseBody.ts +14 -7
- package/src/models/DescribePhysicalConnectionsRequest.ts +56 -1
- package/src/models/DescribeRouterInterfaceAttributeResponseBody.ts +22 -22
- package/src/models/DescribeRouterInterfacesRequest.ts +7 -7
- package/src/models/DescribeRouterInterfacesResponseBody.ts +1 -1
- package/src/models/DescribeSslVpnClientCertRequest.ts +1 -1
- package/src/models/DescribeSslVpnClientCertResponseBody.ts +3 -3
- package/src/models/DescribeSslVpnServersRequest.ts +1 -1
- package/src/models/DescribeSslVpnServersResponseBody.ts +1 -1
- package/src/models/DescribeTagKeysForExpressConnectRequest.ts +2 -0
- package/src/models/DescribeVbrHaRequest.ts +6 -6
- package/src/models/DescribeVbrHaResponseBody.ts +2 -2
- package/src/models/DescribeVcoRouteEntriesResponseBody.ts +10 -10
- package/src/models/DescribeVirtualBorderRoutersForPhysicalConnectionRequest.ts +3 -3
- package/src/models/DescribeVirtualBorderRoutersRequest.ts +6 -26
- package/src/models/DescribeVirtualBorderRoutersResponseBody.ts +2 -2
- package/src/models/DescribeVpcGrantRulesToEcrRequest.ts +7 -7
- package/src/models/DescribeVpcGrantRulesToEcrResponseBody.ts +8 -8
- package/src/models/DescribeVpcsRequest.ts +7 -7
- package/src/models/DescribeVpnAttachmentsRequest.ts +4 -4
- package/src/models/DescribeVpnAttachmentsResponseBody.ts +9 -9
- package/src/models/DescribeVpnConnectionLogsRequest.ts +2 -2
- package/src/models/DescribeVpnConnectionLogsResponseBody.ts +1 -1
- package/src/models/DescribeVpnConnectionRequest.ts +2 -2
- package/src/models/DescribeVpnConnectionResponseBody.ts +21 -72
- package/src/models/DescribeVpnConnectionsRequest.ts +7 -9
- package/src/models/DescribeVpnCrossAccountAuthorizationsRequest.ts +2 -2
- package/src/models/DescribeVpnCrossAccountAuthorizationsResponseBody.ts +5 -5
- package/src/models/DescribeVpnGatewayResponseBody.ts +8 -8
- package/src/models/DescribeVpnGatewaysRequest.ts +2 -2
- package/src/models/DescribeVpnGatewaysResponseBody.ts +1 -1
- package/src/models/DescribeVpnPbrRouteEntriesRequest.ts +1 -1
- package/src/models/DescribeVpnPbrRouteEntriesResponseBody.ts +1 -1
- package/src/models/DescribeVpnSslServerLogsRequest.ts +2 -2
- package/src/models/DescribeVswitchesRequest.ts +7 -7
- package/src/models/DescribeVswitchesResponseBody.ts +1 -1
- package/src/models/DiagnoseVpnGatewayRequest.ts +1 -1
- package/src/models/DiagnoseVpnGatewayResponseBody.ts +2 -2
- package/src/models/DisassociateMacSecKeyRequest.ts +2 -2
- package/src/models/DissociateVpnGatewayWithCertificateRequest.ts +2 -2
- package/src/models/DownloadVpnConnectionConfigResponseBody.ts +11 -11
- package/src/models/EnablePhysicalConnectionRequest.ts +5 -7
- package/src/models/GetNatGatewayAttributeRequest.ts +1 -1
- package/src/models/GetNatGatewayAttributeResponseBody.ts +20 -20
- package/src/models/GetVpnGatewayDiagnoseResultRequest.ts +3 -3
- package/src/models/GetVpnGatewayDiagnoseResultResponseBody.ts +12 -12
- package/src/models/GrantInstanceToVbrRequest.ts +6 -6
- package/src/models/GrantInstanceToVbrShrinkRequest.ts +6 -6
- package/src/models/ListBusinessAccessPointsResponseBody.ts +40 -2
- package/src/models/ListIpsecServerLogsRequest.ts +2 -2
- package/src/models/ListIpsecServerLogsResponseBody.ts +1 -1
- package/src/models/ListIpsecServersRequest.ts +3 -3
- package/src/models/ListIpsecServersResponseBody.ts +7 -7
- package/src/models/ListVirtualPhysicalConnectionsRequest.ts +7 -7
- package/src/models/ListVirtualPhysicalConnectionsResponseBody.ts +20 -20
- package/src/models/ListVpnCertificateAssociationsRequest.ts +3 -3
- package/src/models/ListVpnCertificateAssociationsResponseBody.ts +2 -2
- package/src/models/ModifyCustomerGatewayAttributeRequest.ts +1 -1
- package/src/models/ModifyPhysicalConnectionAttributeRequest.ts +10 -3
- package/src/models/ModifySslVpnServerRequest.ts +11 -11
- package/src/models/ModifySslVpnServerResponseBody.ts +1 -1
- package/src/models/ModifyVcoRouteEntryWeightRequest.ts +4 -4
- package/src/models/ModifyVpcAttributeRequest.ts +4 -4
- package/src/models/ModifyVpcCidrBlockRequest.ts +101 -0
- package/src/models/ModifyVpcCidrBlockResponse.ts +40 -0
- package/src/models/ModifyVpcCidrBlockResponseBody.ts +34 -0
- package/src/models/ModifyVpnAttachmentAttributeRequest.ts +57 -133
- package/src/models/ModifyVpnAttachmentAttributeResponseBody.ts +55 -97
- package/src/models/ModifyVpnConnectionAttributeRequest.ts +84 -155
- package/src/models/ModifyVpnConnectionAttributeResponseBody.ts +26 -53
- package/src/models/ModifyVpnGatewayAttributeRequest.ts +5 -5
- package/src/models/ModifyVpnPbrRouteEntryPriorityRequest.ts +5 -5
- package/src/models/ModifyVpnRouteEntryWeightRequest.ts +2 -2
- package/src/models/MoveResourceGroupRequest.ts +1 -1
- package/src/models/MoveVpnResourceGroupRequest.ts +2 -2
- package/src/models/ReleaseEipAddressRequest.ts +2 -2
- package/src/models/UnassociateVpcCidrBlockRequest.ts +3 -3
- package/src/models/UpdateDhcpOptionsSetAttributeRequest.ts +8 -8
- package/src/models/UpdateIpsecServerRequest.ts +1 -1
- package/src/models/UpdateIpv4gatewayAttributeRequest.ts +6 -6
- package/src/models/model.ts +3 -0
package/src/client.ts
CHANGED
|
@@ -49,41 +49,42 @@ export default class Client extends OpenApi {
|
|
|
49
49
|
'cn-zhengzhou-nebula-1': "vpc-nebula.cn-qingdao-nebula.aliyuncs.com",
|
|
50
50
|
'eu-west-1-oxs': "vpc-nebula.cn-shenzhen-cloudstone.aliyuncs.com",
|
|
51
51
|
'rus-west-1-pop': "vpc.aliyuncs.com",
|
|
52
|
-
'
|
|
53
|
-
'
|
|
54
|
-
'us-east-1': "vpc.us-east-1.aliyuncs.com",
|
|
55
|
-
'na-south-1': "vpc.na-south-1.aliyuncs.com",
|
|
56
|
-
'me-east-1': "vpc.me-east-1.aliyuncs.com",
|
|
57
|
-
'me-central-1': "vpc.me-central-1.aliyuncs.com",
|
|
58
|
-
'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
|
|
59
|
-
'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
|
|
60
|
-
'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
|
|
61
|
-
'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
|
|
52
|
+
'cn-beijing': "vpc.cn-beijing.aliyuncs.com",
|
|
53
|
+
'cn-heyuan': "vpc.cn-heyuan.aliyuncs.com",
|
|
62
54
|
'cn-zhangjiakou': "vpc.cn-zhangjiakou.aliyuncs.com",
|
|
63
|
-
'
|
|
55
|
+
'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
|
|
56
|
+
'ap-northeast-1': "vpc.ap-northeast-1.aliyuncs.com",
|
|
57
|
+
'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
|
|
58
|
+
'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
|
|
59
|
+
'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
|
|
60
|
+
'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
|
|
61
|
+
'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
|
|
62
|
+
'ap-southeast-8': "vpc.ap-southeast-8.aliyuncs.com",
|
|
63
|
+
'cn-zhongwei': "vpc.cn-zhongwei.aliyuncs.com",
|
|
64
64
|
'cn-wulanchabu': "vpc.cn-wulanchabu.aliyuncs.com",
|
|
65
|
+
'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
|
|
65
66
|
'cn-wuhan-lr': "vpc.cn-wuhan-lr.aliyuncs.com",
|
|
66
|
-
'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
|
|
67
67
|
'cn-shanghai': "vpc.cn-shanghai.aliyuncs.com",
|
|
68
|
-
'cn-qingdao': "vpc.cn-qingdao.aliyuncs.com",
|
|
69
|
-
'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
|
|
70
|
-
'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
|
|
71
68
|
'cn-hongkong': "vpc.cn-hongkong.aliyuncs.com",
|
|
72
|
-
'cn-
|
|
73
|
-
'cn-
|
|
74
|
-
'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
|
|
69
|
+
'cn-shenzhen': "vpc.cn-shenzhen.aliyuncs.com",
|
|
70
|
+
'cn-nanjing': "vpc.cn-nanjing.aliyuncs.com",
|
|
75
71
|
'cn-fuzhou': "vpc.cn-fuzhou.aliyuncs.com",
|
|
76
72
|
'cn-chengdu': "vpc.cn-chengdu.aliyuncs.com",
|
|
73
|
+
'cn-guangzhou': "vpc.cn-guangzhou.aliyuncs.com",
|
|
74
|
+
'cn-huhehaote': "vpc.cn-huhehaote.aliyuncs.com",
|
|
75
|
+
'us-southeast-1': "vpc.us-southeast-1.aliyuncs.com",
|
|
76
|
+
'eu-west-1': "vpc.eu-west-1.aliyuncs.com",
|
|
77
|
+
'eu-west-2': "vpc.eu-west-2.aliyuncs.com",
|
|
78
|
+
'eu-central-1': "vpc.eu-central-1.aliyuncs.com",
|
|
79
|
+
'us-east-1': "vpc.us-east-1.aliyuncs.com",
|
|
80
|
+
'sa-east-1': "vpc.sa-east-1.aliyuncs.com",
|
|
81
|
+
'us-west-1': "vpc.us-west-1.aliyuncs.com",
|
|
82
|
+
'na-south-1': "vpc.na-south-1.aliyuncs.com",
|
|
83
|
+
'me-east-1': "vpc.me-east-1.aliyuncs.com",
|
|
84
|
+
'me-central-1': "vpc.me-central-1.aliyuncs.com",
|
|
77
85
|
'cn-beijing-finance-1': "vpc.cn-beijing-finance-1.aliyuncs.com",
|
|
78
|
-
'cn-
|
|
79
|
-
'
|
|
80
|
-
'ap-southeast-7': "vpc.ap-southeast-7.aliyuncs.com",
|
|
81
|
-
'ap-southeast-6': "vpc.ap-southeast-6.aliyuncs.com",
|
|
82
|
-
'ap-southeast-5': "vpc.ap-southeast-5.aliyuncs.com",
|
|
83
|
-
'ap-southeast-3': "vpc.ap-southeast-3.aliyuncs.com",
|
|
84
|
-
'ap-southeast-1': "vpc.ap-southeast-1.aliyuncs.com",
|
|
85
|
-
'ap-northeast-2': "vpc.ap-northeast-2.aliyuncs.com",
|
|
86
|
-
'ap-northeast-1': "vpc.ap-northeast-1.aliyuncs.com",
|
|
86
|
+
'cn-heyuan-acdr-1': "vpc.cn-heyuan-acdr-1.aliyuncs.com",
|
|
87
|
+
'cn-wulanchabu-gic-1': "vpc.cn-wulanchabu-gic-1.aliyuncs.com",
|
|
87
88
|
};
|
|
88
89
|
this.checkConfig(config);
|
|
89
90
|
this._endpoint = this.getEndpoint("vpc", this._regionId, this._endpointRule, this._network, this._suffix, this._endpointMap, this._endpoint);
|
|
@@ -106,7 +107,8 @@ export default class Client extends OpenApi {
|
|
|
106
107
|
* Activates a router interface that is in the Inactive state.
|
|
107
108
|
*
|
|
108
109
|
* @remarks
|
|
109
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the
|
|
110
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
|
|
111
|
+
* Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
|
|
110
112
|
* > You cannot activate a router interface that has an overdue payment.
|
|
111
113
|
*
|
|
112
114
|
* @param request - ActivateRouterInterfaceRequest
|
|
@@ -157,7 +159,8 @@ export default class Client extends OpenApi {
|
|
|
157
159
|
* Activates a router interface that is in the Inactive state.
|
|
158
160
|
*
|
|
159
161
|
* @remarks
|
|
160
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the
|
|
162
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
|
|
163
|
+
* Before you call this operation, the router interface must be in the **Inactive** state. The initial state of a newly created router interface is **Idle**. In non-express connect mode, you can call CreateRouterInterface to create both ends of the connection, call ModifyRouterInterfaceAttribute to configure peer information for each end, and then call ConnectRouterInterface to establish the connection. When the interface is in the **Active** state, you can call DeactivateRouterInterface to change it to the **Inactive** state, and then call this operation to reactivate it. You can call DescribeRouterInterfaceAttribute to query the current state.
|
|
161
164
|
* > You cannot activate a router interface that has an overdue payment.
|
|
162
165
|
*
|
|
163
166
|
* @param request - ActivateRouterInterfaceRequest
|
|
@@ -835,8 +838,8 @@ export default class Client extends OpenApi {
|
|
|
835
838
|
* Applies for an elastic IP address (EIP).
|
|
836
839
|
*
|
|
837
840
|
* @remarks
|
|
838
|
-
*
|
|
839
|
-
* After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer.
|
|
841
|
+
* Make sure that you are familiar with the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
|
|
842
|
+
* After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. IGMP and SCTP are not supported.
|
|
840
843
|
*
|
|
841
844
|
* @param request - AllocateEipAddressRequest
|
|
842
845
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -962,8 +965,8 @@ export default class Client extends OpenApi {
|
|
|
962
965
|
* Applies for an elastic IP address (EIP).
|
|
963
966
|
*
|
|
964
967
|
* @remarks
|
|
965
|
-
*
|
|
966
|
-
* After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer.
|
|
968
|
+
* Make sure that you are familiar with the billing methods and pricing of EIPs before you call this operation. For more information, see [Billing overview](https://help.aliyun.com/document_detail/122035.html).
|
|
969
|
+
* After you call this operation, an EIP in the **Available** state is randomly allocated in the specified region. EIPs support only ICMP, TCP, and UDP at the transport layer. IGMP and SCTP are not supported.
|
|
967
970
|
*
|
|
968
971
|
* @param request - AllocateEipAddressRequest
|
|
969
972
|
* @returns AllocateEipAddressResponse
|
|
@@ -1899,7 +1902,7 @@ export default class Client extends OpenApi {
|
|
|
1899
1902
|
}
|
|
1900
1903
|
|
|
1901
1904
|
/**
|
|
1902
|
-
* Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical
|
|
1905
|
+
* Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fibers or Ethernet) to cover all traffic from the sender to the receiver.
|
|
1903
1906
|
*
|
|
1904
1907
|
* @remarks
|
|
1905
1908
|
* To use this feature, the following conditions must be met:
|
|
@@ -1908,7 +1911,7 @@ export default class Client extends OpenApi {
|
|
|
1908
1911
|
* - Only dedicated Express Connect circuits are supported.
|
|
1909
1912
|
* Other notes:
|
|
1910
1913
|
* - A maximum of three CKN and CAK pairs can be configured.
|
|
1911
|
-
* - Associating a key that is currently in the Disassociated state
|
|
1914
|
+
* - Associating a key that is currently in the Disassociated state disassociates the previously active key.
|
|
1912
1915
|
* - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
|
|
1913
1916
|
*
|
|
1914
1917
|
* @param request - AssociateMacSecKeyRequest
|
|
@@ -1956,7 +1959,7 @@ export default class Client extends OpenApi {
|
|
|
1956
1959
|
}
|
|
1957
1960
|
|
|
1958
1961
|
/**
|
|
1959
|
-
* Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical
|
|
1962
|
+
* Associates a MACsec key with a dedicated Express Connect circuit port. MACsec uses dedicated encryption chips (such as NICs or switches) to implement low-latency encryption and decryption, directly encrypting physical links (such as optical fibers or Ethernet) to cover all traffic from the sender to the receiver.
|
|
1960
1963
|
*
|
|
1961
1964
|
* @remarks
|
|
1962
1965
|
* To use this feature, the following conditions must be met:
|
|
@@ -1965,7 +1968,7 @@ export default class Client extends OpenApi {
|
|
|
1965
1968
|
* - Only dedicated Express Connect circuits are supported.
|
|
1966
1969
|
* Other notes:
|
|
1967
1970
|
* - A maximum of three CKN and CAK pairs can be configured.
|
|
1968
|
-
* - Associating a key that is currently in the Disassociated state
|
|
1971
|
+
* - Associating a key that is currently in the Disassociated state disassociates the previously active key.
|
|
1969
1972
|
* - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
|
|
1970
1973
|
*
|
|
1971
1974
|
* @param request - AssociateMacSecKeyRequest
|
|
@@ -2548,18 +2551,18 @@ export default class Client extends OpenApi {
|
|
|
2548
2551
|
* Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
|
|
2549
2552
|
*
|
|
2550
2553
|
* @remarks
|
|
2551
|
-
* Before you
|
|
2552
|
-
* - Only
|
|
2553
|
-
* - The SSL certificates must use
|
|
2554
|
+
* Before you associate a VPN gateway with an SSL certificate, take note of the following information:
|
|
2555
|
+
* - Only ShangMi (SM) VPN gateways support SSL certificate binding. You must attach two SSL certificates to an SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
|
|
2556
|
+
* - The SSL certificates must use SM algorithms.
|
|
2554
2557
|
* - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
|
|
2555
2558
|
* <props="china">
|
|
2556
|
-
* - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
|
|
2557
|
-
* - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The
|
|
2559
|
+
* - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy named AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
|
|
2560
|
+
* - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The binding node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the binding status of the SSL certificate:
|
|
2558
2561
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
|
|
2559
2562
|
* - If the VPN gateway is in the **active** state, the SSL certificate is attached.
|
|
2560
|
-
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate
|
|
2563
|
+
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
|
|
2561
2564
|
* ### Before you begin
|
|
2562
|
-
* Make sure that you have two SSL certificates that use
|
|
2565
|
+
* Make sure that you have two SSL certificates that use SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
|
|
2563
2566
|
*
|
|
2564
2567
|
* @param request - AssociateVpnGatewayWithCertificateRequest
|
|
2565
2568
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2613,18 +2616,18 @@ export default class Client extends OpenApi {
|
|
|
2613
2616
|
* Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
|
|
2614
2617
|
*
|
|
2615
2618
|
* @remarks
|
|
2616
|
-
* Before you
|
|
2617
|
-
* - Only
|
|
2618
|
-
* - The SSL certificates must use
|
|
2619
|
+
* Before you associate a VPN gateway with an SSL certificate, take note of the following information:
|
|
2620
|
+
* - Only ShangMi (SM) VPN gateways support SSL certificate binding. You must attach two SSL certificates to an SM VPN gateway: one as the encryption certificate and the other as the signing certificate.
|
|
2621
|
+
* - The SSL certificates must use SM algorithms.
|
|
2619
2622
|
* - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
|
|
2620
2623
|
* <props="china">
|
|
2621
|
-
* - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
|
|
2622
|
-
* - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The
|
|
2624
|
+
* - When you attach a VPN gateway to an SSL certificate for the first time, the system performs automatic creation of a service-linked role named AliyunServiceRoleForVPNCertificate and adds the access policy named AliyunServiceRolePolicyForVPNCertificate to the role. This grants the VPN gateway permissions to access other cloud resources. For more information, see [AliyunServiceRoleForVPNCertificate](https://help.aliyun.com/document_detail/203323.html).
|
|
2625
|
+
* - The **AssociateVpnGatewayWithCertificate** operation is asynchronous. After you send a request, the system returns a request ID, but the SSL certificate is not yet attached to the VPN gateway. The binding node continues to run in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the binding status of the SSL certificate:
|
|
2623
2626
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
|
|
2624
2627
|
* - If the VPN gateway is in the **active** state, the SSL certificate is attached.
|
|
2625
|
-
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate
|
|
2628
|
+
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
|
|
2626
2629
|
* ### Before you begin
|
|
2627
|
-
* Make sure that you have two SSL certificates that use
|
|
2630
|
+
* Make sure that you have two SSL certificates that use SM algorithms in the Alibaba Cloud Certificate Management Service console. For more information about SSL certificates, see [What is Certificate Management Service?](https://help.aliyun.com/document_detail/28535.html).
|
|
2628
2631
|
*
|
|
2629
2632
|
* @param request - AssociateVpnGatewayWithCertificateRequest
|
|
2630
2633
|
* @returns AssociateVpnGatewayWithCertificateResponse
|
|
@@ -2721,7 +2724,7 @@ export default class Client extends OpenApi {
|
|
|
2721
2724
|
}
|
|
2722
2725
|
|
|
2723
2726
|
/**
|
|
2724
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2727
|
+
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits. This API is used to migrate an existing VBR that was pushed cross-account to shared Express Connect circuits (shared port), completing the shared Express Connect circuits form transformation. Only the partner (Express Connect circuit owner) can call this operation.
|
|
2725
2728
|
*
|
|
2726
2729
|
* @param request - AttachVbrToVpconnRequest
|
|
2727
2730
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2768,7 +2771,7 @@ export default class Client extends OpenApi {
|
|
|
2768
2771
|
}
|
|
2769
2772
|
|
|
2770
2773
|
/**
|
|
2771
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
2774
|
+
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits. This API is used to migrate an existing VBR that was pushed cross-account to shared Express Connect circuits (shared port), completing the shared Express Connect circuits form transformation. Only the partner (Express Connect circuit owner) can call this operation.
|
|
2772
2775
|
*
|
|
2773
2776
|
* @param request - AttachVbrToVpconnRequest
|
|
2774
2777
|
* @returns AttachVbrToVpconnResponse
|
|
@@ -2855,10 +2858,10 @@ export default class Client extends OpenApi {
|
|
|
2855
2858
|
}
|
|
2856
2859
|
|
|
2857
2860
|
/**
|
|
2858
|
-
* Cancels access
|
|
2861
|
+
* Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
|
|
2859
2862
|
*
|
|
2860
2863
|
* @remarks
|
|
2861
|
-
* You can cancel access
|
|
2864
|
+
* You can cancel the access of an Express Connect circuit only when it is in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not enabled). After an Express Connect circuit is created by calling CreatePhysicalConnection, it may briefly be in the **Allocating** state, during which it cannot be canceled. Poll the status by calling DescribePhysicalConnections and call this operation after the state changes to **Allocated**.
|
|
2862
2865
|
*
|
|
2863
2866
|
* @param request - CancelPhysicalConnectionRequest
|
|
2864
2867
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2913,10 +2916,10 @@ export default class Client extends OpenApi {
|
|
|
2913
2916
|
}
|
|
2914
2917
|
|
|
2915
2918
|
/**
|
|
2916
|
-
* Cancels access
|
|
2919
|
+
* Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
|
|
2917
2920
|
*
|
|
2918
2921
|
* @remarks
|
|
2919
|
-
* You can cancel access
|
|
2922
|
+
* You can cancel the access of an Express Connect circuit only when it is in the **Initial**, **Approved**, **Allocated**, or **Confirmed** state (not enabled). After an Express Connect circuit is created by calling CreatePhysicalConnection, it may briefly be in the **Allocating** state, during which it cannot be canceled. Poll the status by calling DescribePhysicalConnections and call this operation after the state changes to **Allocated**.
|
|
2920
2923
|
*
|
|
2921
2924
|
* @param request - CancelPhysicalConnectionRequest
|
|
2922
2925
|
* @returns CancelPhysicalConnectionResponse
|
|
@@ -3063,7 +3066,7 @@ export default class Client extends OpenApi {
|
|
|
3063
3066
|
}
|
|
3064
3067
|
|
|
3065
3068
|
/**
|
|
3066
|
-
* Calls the CheckVpnBgpEnabled operation to query whether the region
|
|
3069
|
+
* Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
|
|
3067
3070
|
*
|
|
3068
3071
|
* @param request - CheckVpnBgpEnabledRequest
|
|
3069
3072
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3110,7 +3113,7 @@ export default class Client extends OpenApi {
|
|
|
3110
3113
|
}
|
|
3111
3114
|
|
|
3112
3115
|
/**
|
|
3113
|
-
* Calls the CheckVpnBgpEnabled operation to query whether the region
|
|
3116
|
+
* Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
|
|
3114
3117
|
*
|
|
3115
3118
|
* @param request - CheckVpnBgpEnabledRequest
|
|
3116
3119
|
* @returns CheckVpnBgpEnabledResponse
|
|
@@ -3121,7 +3124,12 @@ export default class Client extends OpenApi {
|
|
|
3121
3124
|
}
|
|
3122
3125
|
|
|
3123
3126
|
/**
|
|
3124
|
-
* Calls CompletePhysicalConnectionLOA to complete the construction.
|
|
3127
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
3128
|
+
*
|
|
3129
|
+
* @remarks
|
|
3130
|
+
* Calls the CompletePhysicalConnectionLOA operation to complete the construction. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. You can call this operation only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to reapply. After the construction is completed, the LOA status changes to **Complete**.
|
|
3131
|
+
* Complete call chain:
|
|
3132
|
+
* CreatePhysicalConnection → ApplyPhysicalConnectionLOA (LOA enters the Applying state) → Wait for approval (Available after approval; Rejected if denied, in which case call SecondApplyPhysicalConnectionLOA or ApplyPhysicalConnectionLOA again to reapply) → CompletePhysicalConnectionLOA (backfill completion information, LOA enters the Completing state) → ConfirmPhysicalConnection (confirm the Express Connect circuit, LOA enters the Complete state).
|
|
3125
3133
|
*
|
|
3126
3134
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
3127
3135
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3200,7 +3208,12 @@ export default class Client extends OpenApi {
|
|
|
3200
3208
|
}
|
|
3201
3209
|
|
|
3202
3210
|
/**
|
|
3203
|
-
* Calls CompletePhysicalConnectionLOA to complete the construction.
|
|
3211
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
3212
|
+
*
|
|
3213
|
+
* @remarks
|
|
3214
|
+
* Calls the CompletePhysicalConnectionLOA operation to complete the construction. Before calling this operation, call DescribePhysicalConnectionLOA to query the LOA status. You can call this operation only when the status is **Available** or **Complete**. After an LOA application is submitted, the status changes to **Applying**. After the application is approved, the status changes to **Available**. If the application is rejected, the status changes to **Rejected**. For a rejected application, call SecondApplyPhysicalConnectionLOA to reapply. After the construction is completed, the LOA status changes to **Complete**.
|
|
3215
|
+
* Complete call chain:
|
|
3216
|
+
* CreatePhysicalConnection → ApplyPhysicalConnectionLOA (LOA enters the Applying state) → Wait for approval (Available after approval; Rejected if denied, in which case call SecondApplyPhysicalConnectionLOA or ApplyPhysicalConnectionLOA again to reapply) → CompletePhysicalConnectionLOA (backfill completion information, LOA enters the Completing state) → ConfirmPhysicalConnection (confirm the Express Connect circuit, LOA enters the Complete state).
|
|
3204
3217
|
*
|
|
3205
3218
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
3206
3219
|
* @returns CompletePhysicalConnectionLOAResponse
|
|
@@ -3277,11 +3290,11 @@ export default class Client extends OpenApi {
|
|
|
3277
3290
|
}
|
|
3278
3291
|
|
|
3279
3292
|
/**
|
|
3280
|
-
*
|
|
3293
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
3281
3294
|
*
|
|
3282
3295
|
* @remarks
|
|
3283
|
-
* After you
|
|
3284
|
-
* When you
|
|
3296
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
3297
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
3285
3298
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
3286
3299
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
3287
3300
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -3331,11 +3344,11 @@ export default class Client extends OpenApi {
|
|
|
3331
3344
|
}
|
|
3332
3345
|
|
|
3333
3346
|
/**
|
|
3334
|
-
*
|
|
3347
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
3335
3348
|
*
|
|
3336
3349
|
* @remarks
|
|
3337
|
-
* After you
|
|
3338
|
-
* When you
|
|
3350
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
3351
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
3339
3352
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
3340
3353
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
3341
3354
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -4657,18 +4670,28 @@ export default class Client extends OpenApi {
|
|
|
4657
4670
|
}
|
|
4658
4671
|
|
|
4659
4672
|
/**
|
|
4660
|
-
*
|
|
4673
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4661
4674
|
*
|
|
4662
4675
|
* @remarks
|
|
4663
|
-
*
|
|
4664
|
-
* -
|
|
4676
|
+
* Resource status requirements (prerequisites)
|
|
4677
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4678
|
+
* - ResourceType set to PHYSICALCONNECTION: The Express Connect circuit (including shared Express Connect circuits) must be in the Enabled state with normal billing status (no overdue payment). Otherwise, IncorrectStatus.ResourceId or IncorrectBusinessStatus.ResourceId is returned.
|
|
4679
|
+
* - ResourceType set to VIRTUALBORDERROUTER: The VBR must be in the active state with no overdue payment, and the Express Connect circuit to which the VBR belongs must also be in the Enabled state with no overdue payment.
|
|
4680
|
+
* - ResourceType set to BGPPEER: The BGP peer must be in the Available state, the VBR to which it belongs must be in the active state, and the Express Connect circuit to which the VBR belongs must be in the Enabled state, all with no overdue payment.
|
|
4681
|
+
* How to check and advance the Express Connect circuit status
|
|
4682
|
+
* - Call DescribePhysicalConnections to query the Status field of the Express Connect circuit. If the circuit is not in the Enabled state (for example, it is in the Allocated or Confirmed state), advance it along the following state transition path:
|
|
4683
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4684
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4685
|
+
* - When JobType is set to StartLater, the status check described above is performed during the job creation phase. When you subsequently call StartFailoverTestJob to start the job, the resource status is checked again. If the resource status does not meet the requirements at that time (for example, the circuit is no longer in the Enabled state), the start operation fails.
|
|
4686
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4687
|
+
* - A failover test job is already running in the current region, and the job type of the new failover test job is set to start immediately.
|
|
4665
4688
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4666
4689
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4667
4690
|
*
|
|
4668
4691
|
* - The Express Connect circuit instance has more than one shared Express Connect circuit.
|
|
4669
|
-
* - The Express Connect circuit instance has more than one cross-account
|
|
4692
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4670
4693
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4671
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4694
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4672
4695
|
*
|
|
4673
4696
|
* @param request - CreateFailoverTestJobRequest
|
|
4674
4697
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4747,18 +4770,28 @@ export default class Client extends OpenApi {
|
|
|
4747
4770
|
}
|
|
4748
4771
|
|
|
4749
4772
|
/**
|
|
4750
|
-
*
|
|
4773
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
4751
4774
|
*
|
|
4752
4775
|
* @remarks
|
|
4753
|
-
*
|
|
4754
|
-
* -
|
|
4776
|
+
* Resource status requirements (prerequisites)
|
|
4777
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
4778
|
+
* - ResourceType set to PHYSICALCONNECTION: The Express Connect circuit (including shared Express Connect circuits) must be in the Enabled state with normal billing status (no overdue payment). Otherwise, IncorrectStatus.ResourceId or IncorrectBusinessStatus.ResourceId is returned.
|
|
4779
|
+
* - ResourceType set to VIRTUALBORDERROUTER: The VBR must be in the active state with no overdue payment, and the Express Connect circuit to which the VBR belongs must also be in the Enabled state with no overdue payment.
|
|
4780
|
+
* - ResourceType set to BGPPEER: The BGP peer must be in the Available state, the VBR to which it belongs must be in the active state, and the Express Connect circuit to which the VBR belongs must be in the Enabled state, all with no overdue payment.
|
|
4781
|
+
* How to check and advance the Express Connect circuit status
|
|
4782
|
+
* - Call DescribePhysicalConnections to query the Status field of the Express Connect circuit. If the circuit is not in the Enabled state (for example, it is in the Allocated or Confirmed state), advance it along the following state transition path:
|
|
4783
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
4784
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
4785
|
+
* - When JobType is set to StartLater, the status check described above is performed during the job creation phase. When you subsequently call StartFailoverTestJob to start the job, the resource status is checked again. If the resource status does not meet the requirements at that time (for example, the circuit is no longer in the Enabled state), the start operation fails.
|
|
4786
|
+
* The following scenarios do not support creating failover test jobs:
|
|
4787
|
+
* - A failover test job is already running in the current region, and the job type of the new failover test job is set to start immediately.
|
|
4755
4788
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
4756
4789
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
4757
4790
|
*
|
|
4758
4791
|
* - The Express Connect circuit instance has more than one shared Express Connect circuit.
|
|
4759
|
-
* - The Express Connect circuit instance has more than one cross-account
|
|
4792
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
4760
4793
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
4761
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
4794
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
4762
4795
|
*
|
|
4763
4796
|
* @param request - CreateFailoverTestJobRequest
|
|
4764
4797
|
* @returns CreateFailoverTestJobResponse
|
|
@@ -7374,8 +7407,8 @@ export default class Client extends OpenApi {
|
|
|
7374
7407
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
7375
7408
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
7376
7409
|
* - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
|
|
7377
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
7378
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
7410
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
7411
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
7379
7412
|
*
|
|
7380
7413
|
* @param request - CreateRouteTargetGroupRequest
|
|
7381
7414
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7445,8 +7478,8 @@ export default class Client extends OpenApi {
|
|
|
7445
7478
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
7446
7479
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
7447
7480
|
* - **Active/standby pattern**: When you create a routing target group, you must configure primary and secondary instances that are in different zones and of the same type.
|
|
7448
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
7449
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
7481
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
7482
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
7450
7483
|
*
|
|
7451
7484
|
* @param request - CreateRouteTargetGroupRequest
|
|
7452
7485
|
* @returns CreateRouteTargetGroupResponse
|
|
@@ -7830,7 +7863,7 @@ export default class Client extends OpenApi {
|
|
|
7830
7863
|
* Creates an SSL-VPN server.
|
|
7831
7864
|
*
|
|
7832
7865
|
* @remarks
|
|
7833
|
-
* - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task
|
|
7866
|
+
* - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task continues in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
|
|
7834
7867
|
* - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
|
|
7835
7868
|
* - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
|
|
7836
7869
|
* - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
|
|
@@ -7946,7 +7979,7 @@ export default class Client extends OpenApi {
|
|
|
7946
7979
|
* Creates an SSL-VPN server.
|
|
7947
7980
|
*
|
|
7948
7981
|
* @remarks
|
|
7949
|
-
* - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task
|
|
7982
|
+
* - **CreateSslVpnServer** is an asynchronous operation. After you call this operation, the system returns an instance ID but the SSL-VPN server is not yet created. The creation task continues in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the creation status of the SSL-VPN server:
|
|
7950
7983
|
* - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
|
|
7951
7984
|
* - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
|
|
7952
7985
|
* - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
|
|
@@ -8280,18 +8313,18 @@ export default class Client extends OpenApi {
|
|
|
8280
8313
|
* Creates a vSwitch.
|
|
8281
8314
|
*
|
|
8282
8315
|
* @remarks
|
|
8283
|
-
*
|
|
8316
|
+
* When you call this operation to create a vSwitch, take note of the following items:
|
|
8284
8317
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
8285
|
-
* - 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.
|
|
8318
|
+
* - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
|
|
8286
8319
|
* - 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).
|
|
8287
8320
|
* - A cloud service instance can belong to only one vSwitch.
|
|
8288
8321
|
* - vSwitches do not support multicast or broadcast.
|
|
8289
8322
|
* - After a vSwitch is created, you cannot modify its CIDR block.
|
|
8290
|
-
* - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID
|
|
8291
|
-
* -
|
|
8292
|
-
* -
|
|
8323
|
+
* - 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:
|
|
8324
|
+
* - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
|
|
8325
|
+
* - When the vSwitch is in the **Available** state, the vSwitch is available.
|
|
8293
8326
|
* - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
|
|
8294
|
-
* -
|
|
8327
|
+
* - 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.
|
|
8295
8328
|
*
|
|
8296
8329
|
* @param request - CreateVSwitchRequest
|
|
8297
8330
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -8377,18 +8410,18 @@ export default class Client extends OpenApi {
|
|
|
8377
8410
|
* Creates a vSwitch.
|
|
8378
8411
|
*
|
|
8379
8412
|
* @remarks
|
|
8380
|
-
*
|
|
8413
|
+
* When you call this operation to create a vSwitch, take note of the following items:
|
|
8381
8414
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
8382
|
-
* - 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.
|
|
8415
|
+
* - The first IP address and the last three IP addresses of each vSwitch CIDR block are reserved by the system. For example, the system reserved IP addresses of 192.168.1.0/24 are 192.168.1.0, 192.168.1.253, 192.168.1.254, and 192.168.1.255.
|
|
8383
8416
|
* - 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).
|
|
8384
8417
|
* - A cloud service instance can belong to only one vSwitch.
|
|
8385
8418
|
* - vSwitches do not support multicast or broadcast.
|
|
8386
8419
|
* - After a vSwitch is created, you cannot modify its CIDR block.
|
|
8387
|
-
* - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID
|
|
8388
|
-
* -
|
|
8389
|
-
* -
|
|
8420
|
+
* - 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:
|
|
8421
|
+
* - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
|
|
8422
|
+
* - When the vSwitch is in the **Available** state, the vSwitch is available.
|
|
8390
8423
|
* - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
|
|
8391
|
-
* -
|
|
8424
|
+
* - 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.
|
|
8392
8425
|
*
|
|
8393
8426
|
* @param request - CreateVSwitchRequest
|
|
8394
8427
|
* @returns CreateVSwitchResponse
|
|
@@ -8407,7 +8440,7 @@ export default class Client extends OpenApi {
|
|
|
8407
8440
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
8408
8441
|
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
8409
8442
|
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
8410
|
-
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The
|
|
8443
|
+
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The background node is still in progress. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
|
|
8411
8444
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
8412
8445
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
8413
8446
|
*
|
|
@@ -8426,6 +8459,10 @@ export default class Client extends OpenApi {
|
|
|
8426
8459
|
query["DryRun"] = request.dryRun;
|
|
8427
8460
|
}
|
|
8428
8461
|
|
|
8462
|
+
if (!$dara.isNull(request.ipPrefixNumber)) {
|
|
8463
|
+
query["IpPrefixNumber"] = request.ipPrefixNumber;
|
|
8464
|
+
}
|
|
8465
|
+
|
|
8429
8466
|
if (!$dara.isNull(request.ipVersion)) {
|
|
8430
8467
|
query["IpVersion"] = request.ipVersion;
|
|
8431
8468
|
}
|
|
@@ -8504,7 +8541,7 @@ export default class Client extends OpenApi {
|
|
|
8504
8541
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
8505
8542
|
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
8506
8543
|
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
8507
|
-
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The
|
|
8544
|
+
* - The **CreateVSwitchCidrReservation** operation is asynchronous. After you send a request, the system returns an instance ID, but the reserved CIDR block for a vSwitch has not been created. The background node is still in progress. You can invoke [ListVSwitchCidrReservations](https://help.aliyun.com/document_detail/610155.html) to query the creation status of the reserved CIDR block for a vSwitch:
|
|
8508
8545
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
8509
8546
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
8510
8547
|
*
|
|
@@ -8517,7 +8554,7 @@ export default class Client extends OpenApi {
|
|
|
8517
8554
|
}
|
|
8518
8555
|
|
|
8519
8556
|
/**
|
|
8520
|
-
* Creates a VBR failover group
|
|
8557
|
+
* Creates a VBR failover group.
|
|
8521
8558
|
*
|
|
8522
8559
|
* @param request - CreateVbrHaRequest
|
|
8523
8560
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -8588,7 +8625,7 @@ export default class Client extends OpenApi {
|
|
|
8588
8625
|
}
|
|
8589
8626
|
|
|
8590
8627
|
/**
|
|
8591
|
-
* Creates a VBR failover group
|
|
8628
|
+
* Creates a VBR failover group.
|
|
8592
8629
|
*
|
|
8593
8630
|
* @param request - CreateVbrHaRequest
|
|
8594
8631
|
* @returns CreateVbrHaResponse
|
|
@@ -8604,11 +8641,11 @@ export default class Client extends OpenApi {
|
|
|
8604
8641
|
* @remarks
|
|
8605
8642
|
* - The IPsec-VPN connection must be associated with a transit router instance. For more information, see [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468249.html).
|
|
8606
8643
|
* - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
|
|
8607
|
-
* - Do not add a destination route
|
|
8644
|
+
* - Do not add a destination route whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
|
|
8608
8645
|
* - **CreateVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns an instance ID but the destination route entry is not yet created. The creation task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the creation status of the destination route entry:
|
|
8609
8646
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
|
|
8610
8647
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
|
|
8611
|
-
* - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
8648
|
+
* - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
8612
8649
|
*
|
|
8613
8650
|
* @param request - CreateVcoRouteEntryRequest
|
|
8614
8651
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -8688,11 +8725,11 @@ export default class Client extends OpenApi {
|
|
|
8688
8725
|
* @remarks
|
|
8689
8726
|
* - The IPsec-VPN connection must be associated with a transit router instance. For more information, see [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468249.html).
|
|
8690
8727
|
* - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
|
|
8691
|
-
* - Do not add a destination route
|
|
8728
|
+
* - Do not add a destination route whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such route entries cause the console to fail to display the status of the IPsec-VPN connection or cause IPsec negotiation to fail.
|
|
8692
8729
|
* - **CreateVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns an instance ID but the destination route entry is not yet created. The creation task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the creation status of the destination route entry:
|
|
8693
8730
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
|
|
8694
8731
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
|
|
8695
|
-
* - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
8732
|
+
* - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
8696
8733
|
*
|
|
8697
8734
|
* @param request - CreateVcoRouteEntryRequest
|
|
8698
8735
|
* @returns CreateVcoRouteEntryResponse
|
|
@@ -8838,7 +8875,18 @@ export default class Client extends OpenApi {
|
|
|
8838
8875
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
8839
8876
|
*
|
|
8840
8877
|
* @remarks
|
|
8841
|
-
* Before
|
|
8878
|
+
* Before you call this operation, familiarize yourself with the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
|
|
8879
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
8880
|
+
* - The Express Connect circuit specified by PhysicalConnectionId is in the Enabled state. The complete process for an Express Connect circuit to reach the Enabled state includes payment and manual steps that cannot be fully automated through OpenAPI:
|
|
8881
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
8882
|
+
* - LOA construction authorization: If you need to enter the data center for construction, call ApplyPhysicalConnectionLOA → wait for manual LOA approval → CompletePhysicalConnectionLOA (FinishWork=true). LOA approval and construction are manual/offline steps.
|
|
8883
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
8884
|
+
* - After the Confirmed state, port usage fees must be paid before the circuit enters the Enabled state. For automation scenarios, call DescribePhysicalConnections first to confirm the target circuit is in the Enabled state before calling this operation.
|
|
8885
|
+
* - The VlanId is not already used by an existing VBR or shared Express Connect circuit on the Express Connect circuit (valid values: 0 to 2999).
|
|
8886
|
+
* - The Spec value does not exceed the remaining allocatable bandwidth of the Express Connect circuit or the shared circuit bandwidth limit configured for the account that owns the Express Connect circuit.
|
|
8887
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
8888
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
8889
|
+
* - The Express Connect circuit is not bound to a QoS policy, the access device supports MPBGP, and the access point allows the creation of shared Express Connect circuits.
|
|
8842
8890
|
*
|
|
8843
8891
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
8844
8892
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -8916,7 +8964,18 @@ export default class Client extends OpenApi {
|
|
|
8916
8964
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
8917
8965
|
*
|
|
8918
8966
|
* @remarks
|
|
8919
|
-
* Before
|
|
8967
|
+
* Before you call this operation, familiarize yourself with the creation process and environment requirements for shared Express Connect circuits. For more information, see [Overview of shared Express Connect circuits](https://help.aliyun.com/document_detail/146571.html) and [Partner operation guide](https://help.aliyun.com/document_detail/155987.html).
|
|
8968
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
8969
|
+
* - The Express Connect circuit specified by PhysicalConnectionId is in the Enabled state. The complete process for an Express Connect circuit to reach the Enabled state includes payment and manual steps that cannot be fully automated through OpenAPI:
|
|
8970
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
8971
|
+
* - LOA construction authorization: If you need to enter the data center for construction, call ApplyPhysicalConnectionLOA → wait for manual LOA approval → CompletePhysicalConnectionLOA (FinishWork=true). LOA approval and construction are manual/offline steps.
|
|
8972
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
8973
|
+
* - After the Confirmed state, port usage fees must be paid before the circuit enters the Enabled state. For automation scenarios, call DescribePhysicalConnections first to confirm the target circuit is in the Enabled state before calling this operation.
|
|
8974
|
+
* - The VlanId is not already used by an existing VBR or shared Express Connect circuit on the Express Connect circuit (valid values: 0 to 2999).
|
|
8975
|
+
* - The Spec value does not exceed the remaining allocatable bandwidth of the Express Connect circuit or the shared circuit bandwidth limit configured for the account that owns the Express Connect circuit.
|
|
8976
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
8977
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
8978
|
+
* - The Express Connect circuit is not bound to a QoS policy, the access device supports MPBGP, and the access point allows the creation of shared Express Connect circuits.
|
|
8920
8979
|
*
|
|
8921
8980
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
8922
8981
|
* @returns CreateVirtualPhysicalConnectionResponse
|
|
@@ -9283,13 +9342,13 @@ export default class Client extends OpenApi {
|
|
|
9283
9342
|
}
|
|
9284
9343
|
|
|
9285
9344
|
/**
|
|
9286
|
-
* Transforms the
|
|
9345
|
+
* Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
|
|
9287
9346
|
*
|
|
9288
9347
|
* @remarks
|
|
9289
|
-
* By invoking the CreateVpconnFromVbr operation, a partner can transform the
|
|
9290
|
-
* Before you execute the transform:
|
|
9348
|
+
* By invoking the CreateVpconnFromVbr operation, a partner can transform the routing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
|
|
9349
|
+
* Before you execute the transform procedure:
|
|
9291
9350
|
* The partner must notify the tenant about the service upgrade in advance and ensure that the tenant has enabled outbound traffic billing. For information about how to enable outbound traffic billing, see [Enable outbound traffic billing](https://help.aliyun.com/document_detail/274385.html).
|
|
9292
|
-
* After the transform is complete:
|
|
9351
|
+
* After the transform procedure is complete:
|
|
9293
9352
|
* 1. A shared port is added to the tenant\\"s account. The tenant must invoke the [ConfirmPhysicalConnection](https://help.aliyun.com/document_detail/324198.html) operation to accept the shared port.
|
|
9294
9353
|
* 2. After the tenant accepts the shared port, the partner must invoke the [AttachVbrToVpconn](https://help.aliyun.com/document_detail/324191.html) operation to associate the VBR instance with the tenant\\"s shared Express Connect circuits instance.
|
|
9295
9354
|
*
|
|
@@ -9338,13 +9397,13 @@ export default class Client extends OpenApi {
|
|
|
9338
9397
|
}
|
|
9339
9398
|
|
|
9340
9399
|
/**
|
|
9341
|
-
* Transforms the
|
|
9400
|
+
* Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
|
|
9342
9401
|
*
|
|
9343
9402
|
* @remarks
|
|
9344
|
-
* By invoking the CreateVpconnFromVbr operation, a partner can transform the
|
|
9345
|
-
* Before you execute the transform:
|
|
9403
|
+
* By invoking the CreateVpconnFromVbr operation, a partner can transform the routing mode of shared Express Connect circuits used by a tenant from cross-account VBR push to cross-account shared port push. The transform procedure does not affect the tenant\\"s services.
|
|
9404
|
+
* Before you execute the transform procedure:
|
|
9346
9405
|
* The partner must notify the tenant about the service upgrade in advance and ensure that the tenant has enabled outbound traffic billing. For information about how to enable outbound traffic billing, see [Enable outbound traffic billing](https://help.aliyun.com/document_detail/274385.html).
|
|
9347
|
-
* After the transform is complete:
|
|
9406
|
+
* After the transform procedure is complete:
|
|
9348
9407
|
* 1. A shared port is added to the tenant\\"s account. The tenant must invoke the [ConfirmPhysicalConnection](https://help.aliyun.com/document_detail/324198.html) operation to accept the shared port.
|
|
9349
9408
|
* 2. After the tenant accepts the shared port, the partner must invoke the [AttachVbrToVpconn](https://help.aliyun.com/document_detail/324191.html) operation to associate the VBR instance with the tenant\\"s shared Express Connect circuits instance.
|
|
9350
9409
|
*
|
|
@@ -9357,16 +9416,11 @@ export default class Client extends OpenApi {
|
|
|
9357
9416
|
}
|
|
9358
9417
|
|
|
9359
9418
|
/**
|
|
9360
|
-
* Creates an IPsec-VPN connection
|
|
9419
|
+
* Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
|
|
9361
9420
|
*
|
|
9362
9421
|
* @remarks
|
|
9363
9422
|
* >Notice:
|
|
9364
|
-
*
|
|
9365
|
-
* - An IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not bound to any resource by default. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to bind the IPsec-VPN connection to a transit router instance. After the IPsec-VPN connection is bound to a transit router instance, the system allocates a gateway IP address to the IPsec-VPN connection. You can call the [DescribeVpnConnection](https://help.aliyun.com/document_detail/2526951.html) operation to view the gateway IP address.
|
|
9366
|
-
* ### Before you begin
|
|
9367
|
-
* 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).
|
|
9368
|
-
*
|
|
9369
|
-
* If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number has been added to the customer gateway.
|
|
9423
|
+
* ### Before you begin.
|
|
9370
9424
|
*
|
|
9371
9425
|
* @param request - CreateVpnAttachmentRequest
|
|
9372
9426
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -9500,16 +9554,11 @@ export default class Client extends OpenApi {
|
|
|
9500
9554
|
}
|
|
9501
9555
|
|
|
9502
9556
|
/**
|
|
9503
|
-
* Creates an IPsec-VPN connection
|
|
9557
|
+
* Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
|
|
9504
9558
|
*
|
|
9505
9559
|
* @remarks
|
|
9506
9560
|
* >Notice:
|
|
9507
|
-
*
|
|
9508
|
-
* - An IPsec-VPN connection created by calling the `CreateVpnAttachment` operation is not bound to any resource by default. You can call the [CreateTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/443993.html) operation to bind the IPsec-VPN connection to a transit router instance. After the IPsec-VPN connection is bound to a transit router instance, the system allocates a gateway IP address to the IPsec-VPN connection. You can call the [DescribeVpnConnection](https://help.aliyun.com/document_detail/2526951.html) operation to view the gateway IP address.
|
|
9509
|
-
* ### Before you begin
|
|
9510
|
-
* 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).
|
|
9511
|
-
*
|
|
9512
|
-
* If you want to add BGP configurations to the IPsec-VPN connection, make sure that an autonomous system number has been added to the customer gateway.
|
|
9561
|
+
* ### Before you begin.
|
|
9513
9562
|
*
|
|
9514
9563
|
* @param request - CreateVpnAttachmentRequest
|
|
9515
9564
|
* @returns CreateVpnAttachmentResponse
|
|
@@ -9526,11 +9575,8 @@ export default class Client extends OpenApi {
|
|
|
9526
9575
|
* - If the VPN gateway instance supports creating IPsec-VPN connections in dual-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
|
|
9527
9576
|
* **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
9528
9577
|
* For information about the regions and zones that support IPsec-VPN connections in dual-tunnel mode, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
|
|
9529
|
-
* - If the VPN gateway instance supports only creating IPsec-VPN connections in single-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
|
|
9530
9578
|
* **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
|
|
9531
|
-
* - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection
|
|
9532
|
-
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
|
|
9533
|
-
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
|
|
9579
|
+
* - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection.
|
|
9534
9580
|
* - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
|
|
9535
9581
|
*
|
|
9536
9582
|
* @param request - CreateVpnConnectionRequest
|
|
@@ -9667,11 +9713,8 @@ export default class Client extends OpenApi {
|
|
|
9667
9713
|
* - If the VPN gateway instance supports creating IPsec-VPN connections in dual-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
|
|
9668
9714
|
* **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
9669
9715
|
* For information about the regions and zones that support IPsec-VPN connections in dual-tunnel mode, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
|
|
9670
|
-
* - If the VPN gateway instance supports only creating IPsec-VPN connections in single-tunnel mode, you can configure the following request parameters in addition to the required parameters when you call the `CreateVpnConnection` operation:
|
|
9671
9716
|
* **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
|
|
9672
|
-
* - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection
|
|
9673
|
-
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
|
|
9674
|
-
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
|
|
9717
|
+
* - The **CreateVpnConnection** operation is asynchronous. After you send a request, the system returns an instance ID, but the IPsec-VPN connection is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the creation status of the IPsec-VPN connection.
|
|
9675
9718
|
* - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
|
|
9676
9719
|
*
|
|
9677
9720
|
* @param request - CreateVpnConnectionRequest
|
|
@@ -9686,8 +9729,8 @@ export default class Client extends OpenApi {
|
|
|
9686
9729
|
* Creates a VPN gateway.
|
|
9687
9730
|
*
|
|
9688
9731
|
* @remarks
|
|
9689
|
-
* - Before you create a VPN gateway, familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
|
|
9690
|
-
* - VPN gateway instances in some regions support only dual-tunnel IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
|
|
9732
|
+
* - Before you create a VPN gateway, we recommend that you familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
|
|
9733
|
+
* - VPN gateway instances in some regions support only dual-tunnel mode IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel mode IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
|
|
9691
9734
|
* - The **CreateVpnGateway** operation is asynchronous. After you call this operation, the system returns an instance ID, but the VPN gateway is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the VPN gateway:
|
|
9692
9735
|
*
|
|
9693
9736
|
* - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
|
|
@@ -9801,8 +9844,8 @@ export default class Client extends OpenApi {
|
|
|
9801
9844
|
* Creates a VPN gateway.
|
|
9802
9845
|
*
|
|
9803
9846
|
* @remarks
|
|
9804
|
-
* - Before you create a VPN gateway, familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
|
|
9805
|
-
* - VPN gateway instances in some regions support only dual-tunnel IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
|
|
9847
|
+
* - Before you create a VPN gateway, we recommend that you familiarize yourself with the limits of VPN gateways. For more information, see [VPN gateway limits](https://help.aliyun.com/document_detail/65290.html).
|
|
9848
|
+
* - VPN gateway instances in some regions support only dual-tunnel mode IPsec-VPN connections by default. When you call the `CreateVpnGateway` operation to create a VPN gateway instance in these regions, you must specify the **VSwitchId** and **DisasterRecoveryVSwitchId** parameters in addition to the required parameters. For information about the regions and zones that support dual-tunnel mode IPsec-VPN connections, see [Upgrade an IPsec-VPN connection to dual-tunnel mode](https://help.aliyun.com/document_detail/2358946.html).
|
|
9806
9849
|
* - The **CreateVpnGateway** operation is asynchronous. After you call this operation, the system returns an instance ID, but the VPN gateway is not yet created. The creation task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the creation status of the VPN gateway:
|
|
9807
9850
|
*
|
|
9808
9851
|
* - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
|
|
@@ -9817,18 +9860,18 @@ export default class Client extends OpenApi {
|
|
|
9817
9860
|
}
|
|
9818
9861
|
|
|
9819
9862
|
/**
|
|
9820
|
-
* Creates a policy-based route
|
|
9863
|
+
* Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
|
|
9821
9864
|
*
|
|
9822
9865
|
* @remarks
|
|
9823
9866
|
* ### Before you begin
|
|
9824
|
-
* - Before
|
|
9825
|
-
* - Before
|
|
9867
|
+
* - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
|
|
9868
|
+
* - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
|
|
9826
9869
|
* ### Limits
|
|
9827
|
-
* -
|
|
9828
|
-
* - Do not add
|
|
9829
|
-
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you
|
|
9870
|
+
* - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
|
|
9871
|
+
* - Do not add policy-based routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes may cause the console to fail to display instance status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
|
|
9872
|
+
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you invoke this operation, the system returns the information about the policy-based route, but the routing has not been created. The creation node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
|
|
9830
9873
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
9831
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based route
|
|
9874
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
9832
9875
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
9833
9876
|
*
|
|
9834
9877
|
* @param request - CreateVpnPbrRouteEntryRequest
|
|
@@ -9920,18 +9963,18 @@ export default class Client extends OpenApi {
|
|
|
9920
9963
|
}
|
|
9921
9964
|
|
|
9922
9965
|
/**
|
|
9923
|
-
* Creates a policy-based route
|
|
9966
|
+
* Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
|
|
9924
9967
|
*
|
|
9925
9968
|
* @remarks
|
|
9926
9969
|
* ### Before you begin
|
|
9927
|
-
* - Before
|
|
9928
|
-
* - Before
|
|
9970
|
+
* - Before you create a policy-based route, make sure that you have created an IPsec-VPN connection. For more information, see [CreateVpnConnection](https://help.aliyun.com/document_detail/120391.html).
|
|
9971
|
+
* - Before you create a policy-based route, we recommend that you familiarize yourself with the limits and matching rules of policy-based routes. For more information, see [Use policy-based routes](https://help.aliyun.com/document_detail/110777.html).
|
|
9929
9972
|
* ### Limits
|
|
9930
|
-
* -
|
|
9931
|
-
* - Do not add
|
|
9932
|
-
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you
|
|
9973
|
+
* - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
|
|
9974
|
+
* - Do not add policy-based routes whose destination CIDR block is 100.64.0.0/10, a subnet of 100.64.0.0/10, or a CIDR block that contains 100.64.0.0/10. Such policy-based routes may cause the console to fail to display instance status of IPsec-VPN connections or cause IPsec-VPN connection negotiation to be failed.
|
|
9975
|
+
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you invoke this operation, the system returns the information about the policy-based route, but the routing has not been created. The creation node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query instance status of the VPN gateway instance to determine the creation status of the policy-based route:
|
|
9933
9976
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
9934
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based route
|
|
9977
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
9935
9978
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
9936
9979
|
*
|
|
9937
9980
|
* @param request - CreateVpnPbrRouteEntryRequest
|
|
@@ -10193,7 +10236,7 @@ export default class Client extends OpenApi {
|
|
|
10193
10236
|
}
|
|
10194
10237
|
|
|
10195
10238
|
/**
|
|
10196
|
-
* Deletes a specified
|
|
10239
|
+
* Deletes a specified BGP group.
|
|
10197
10240
|
*
|
|
10198
10241
|
* @param request - DeleteBgpGroupRequest
|
|
10199
10242
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -10248,7 +10291,7 @@ export default class Client extends OpenApi {
|
|
|
10248
10291
|
}
|
|
10249
10292
|
|
|
10250
10293
|
/**
|
|
10251
|
-
* Deletes a specified
|
|
10294
|
+
* Deletes a specified BGP group.
|
|
10252
10295
|
*
|
|
10253
10296
|
* @param request - DeleteBgpGroupRequest
|
|
10254
10297
|
* @returns DeleteBgpGroupResponse
|
|
@@ -10261,6 +10304,9 @@ export default class Client extends OpenApi {
|
|
|
10261
10304
|
/**
|
|
10262
10305
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
10263
10306
|
*
|
|
10307
|
+
* @remarks
|
|
10308
|
+
* Before calling this operation, ensure that the BgpNetwork is in the Available state. You can query the Status field by calling DescribeBgpNetworks. After a resource is created by AddBgpNetwork, it enters the Pending state. Wait until the state changes to Available before calling this operation.
|
|
10309
|
+
*
|
|
10264
10310
|
* @param request - DeleteBgpNetworkRequest
|
|
10265
10311
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
10266
10312
|
* @returns DeleteBgpNetworkResponse
|
|
@@ -10320,6 +10366,9 @@ export default class Client extends OpenApi {
|
|
|
10320
10366
|
/**
|
|
10321
10367
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
10322
10368
|
*
|
|
10369
|
+
* @remarks
|
|
10370
|
+
* Before calling this operation, ensure that the BgpNetwork is in the Available state. You can query the Status field by calling DescribeBgpNetworks. After a resource is created by AddBgpNetwork, it enters the Pending state. Wait until the state changes to Available before calling this operation.
|
|
10371
|
+
*
|
|
10323
10372
|
* @param request - DeleteBgpNetworkRequest
|
|
10324
10373
|
* @returns DeleteBgpNetworkResponse
|
|
10325
10374
|
*/
|
|
@@ -10979,10 +11028,10 @@ export default class Client extends OpenApi {
|
|
|
10979
11028
|
}
|
|
10980
11029
|
|
|
10981
11030
|
/**
|
|
10982
|
-
* Deletes an Express Connect failover test job.
|
|
11031
|
+
* Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
|
|
10983
11032
|
*
|
|
10984
11033
|
* @remarks
|
|
10985
|
-
* Only failover test jobs in the **Pending** or **Completed** state can be deleted.
|
|
11034
|
+
* Only failover test jobs in the **Pending** or **Completed** state can be deleted. Before calling this operation, create a failover test job by calling CreateFailoverTestJob and obtain the **JobId**. If the test resource is an Express Connect circuit, the circuit must be in the **Enabled** state and its business status must be **Normal**.
|
|
10986
11035
|
*
|
|
10987
11036
|
* @param request - DeleteFailoverTestJobRequest
|
|
10988
11037
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -11037,10 +11086,10 @@ export default class Client extends OpenApi {
|
|
|
11037
11086
|
}
|
|
11038
11087
|
|
|
11039
11088
|
/**
|
|
11040
|
-
* Deletes an Express Connect failover test job.
|
|
11089
|
+
* Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
|
|
11041
11090
|
*
|
|
11042
11091
|
* @remarks
|
|
11043
|
-
* Only failover test jobs in the **Pending** or **Completed** state can be deleted.
|
|
11092
|
+
* Only failover test jobs in the **Pending** or **Completed** state can be deleted. Before calling this operation, create a failover test job by calling CreateFailoverTestJob and obtain the **JobId**. If the test resource is an Express Connect circuit, the circuit must be in the **Enabled** state and its business status must be **Normal**.
|
|
11044
11093
|
*
|
|
11045
11094
|
* @param request - DeleteFailoverTestJobRequest
|
|
11046
11095
|
* @returns DeleteFailoverTestJobResponse
|
|
@@ -11666,7 +11715,7 @@ export default class Client extends OpenApi {
|
|
|
11666
11715
|
* Deletes an IPsec server.
|
|
11667
11716
|
*
|
|
11668
11717
|
* @remarks
|
|
11669
|
-
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID
|
|
11718
|
+
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec server is not yet deleted. The deletion node continues to run in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway to determine the deletion status of the IPsec server:
|
|
11670
11719
|
* - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
|
|
11671
11720
|
* - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
|
|
11672
11721
|
* - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
|
|
@@ -11715,7 +11764,7 @@ export default class Client extends OpenApi {
|
|
|
11715
11764
|
* Deletes an IPsec server.
|
|
11716
11765
|
*
|
|
11717
11766
|
* @remarks
|
|
11718
|
-
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID
|
|
11767
|
+
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec server is not yet deleted. The deletion node continues to run in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the instance status of the VPN gateway to determine the deletion status of the IPsec server:
|
|
11719
11768
|
* - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
|
|
11720
11769
|
* - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
|
|
11721
11770
|
* - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
|
|
@@ -12082,12 +12131,12 @@ export default class Client extends OpenApi {
|
|
|
12082
12131
|
* Deletes a specified Internet NAT gateway.
|
|
12083
12132
|
*
|
|
12084
12133
|
* @remarks
|
|
12085
|
-
* *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://
|
|
12134
|
+
* *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://www.alibabacloud.com/help/en/nat-gateway/developer-reference/api-vpc-2016-04-28-describenatgateways-natgws) to query the status of the NAT gateway:
|
|
12086
12135
|
*
|
|
12087
12136
|
* - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
|
|
12088
12137
|
* - If the NAT gateway cannot be found, the NAT gateway is deleted.
|
|
12089
12138
|
*
|
|
12090
|
-
* >
|
|
12139
|
+
* > Deleting a NAT gateway is irreversible. Proceed with caution.
|
|
12091
12140
|
*
|
|
12092
12141
|
* @param request - DeleteNatGatewayRequest
|
|
12093
12142
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -12145,12 +12194,12 @@ export default class Client extends OpenApi {
|
|
|
12145
12194
|
* Deletes a specified Internet NAT gateway.
|
|
12146
12195
|
*
|
|
12147
12196
|
* @remarks
|
|
12148
|
-
* *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://
|
|
12197
|
+
* *DeleteNatGateway** is an asynchronous operation. After you send a request, the system returns a request ID. However, the NAT gateway is not immediately deleted. The deletion task runs in the background. You can call [DescribeNatGateways](https://www.alibabacloud.com/help/en/nat-gateway/developer-reference/api-vpc-2016-04-28-describenatgateways-natgws) to query the status of the NAT gateway:
|
|
12149
12198
|
*
|
|
12150
12199
|
* - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
|
|
12151
12200
|
* - If the NAT gateway cannot be found, the NAT gateway is deleted.
|
|
12152
12201
|
*
|
|
12153
|
-
* >
|
|
12202
|
+
* > Deleting a NAT gateway is irreversible. Proceed with caution.
|
|
12154
12203
|
*
|
|
12155
12204
|
* @param request - DeleteNatGatewayRequest
|
|
12156
12205
|
* @returns DeleteNatGatewayResponse
|
|
@@ -12487,11 +12536,11 @@ export default class Client extends OpenApi {
|
|
|
12487
12536
|
*
|
|
12488
12537
|
* @remarks
|
|
12489
12538
|
* Before you call this operation, take note of the following items:
|
|
12490
|
-
* - Before
|
|
12539
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
12491
12540
|
* - **DeletePublicIpAddressPool** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call [ListPublicIpAddressPools](https://help.aliyun.com/document_detail/429433.html) to query the status of the IP address pool.
|
|
12492
12541
|
* - If the IP address pool is in the **Deleting** state, the IP address pool is being deleted. In this state, you can only perform query operations.
|
|
12493
12542
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
12494
|
-
* - **DeletePublicIpAddressPool**
|
|
12543
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
12495
12544
|
*
|
|
12496
12545
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
12497
12546
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -12554,11 +12603,11 @@ export default class Client extends OpenApi {
|
|
|
12554
12603
|
*
|
|
12555
12604
|
* @remarks
|
|
12556
12605
|
* Before you call this operation, take note of the following items:
|
|
12557
|
-
* - Before
|
|
12606
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
12558
12607
|
* - **DeletePublicIpAddressPool** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the task in the background. You can call [ListPublicIpAddressPools](https://help.aliyun.com/document_detail/429433.html) to query the status of the IP address pool.
|
|
12559
12608
|
* - If the IP address pool is in the **Deleting** state, the IP address pool is being deleted. In this state, you can only perform query operations.
|
|
12560
12609
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
12561
|
-
* - **DeletePublicIpAddressPool**
|
|
12610
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
12562
12611
|
*
|
|
12563
12612
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
12564
12613
|
* @returns DeletePublicIpAddressPoolResponse
|
|
@@ -12574,7 +12623,7 @@ export default class Client extends OpenApi {
|
|
|
12574
12623
|
* @remarks
|
|
12575
12624
|
* Before you call this operation, take note of the following information:
|
|
12576
12625
|
* - Before deleting a CIDR block, make sure that the CIDR block is not in use.
|
|
12577
|
-
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
12626
|
+
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the deletion task in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
|
|
12578
12627
|
* - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
|
|
12579
12628
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
12580
12629
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -12645,7 +12694,7 @@ export default class Client extends OpenApi {
|
|
|
12645
12694
|
* @remarks
|
|
12646
12695
|
* Before you call this operation, take note of the following information:
|
|
12647
12696
|
* - Before deleting a CIDR block, make sure that the CIDR block is not in use.
|
|
12648
|
-
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
12697
|
+
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID and runs the deletion task in the background. You can call [ListPublicIpAddressPoolCidrBlocks](https://help.aliyun.com/document_detail/429436.html) to query the status of the CIDR block in the IP address pool.
|
|
12649
12698
|
* - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
|
|
12650
12699
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
12651
12700
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -12659,16 +12708,16 @@ export default class Client extends OpenApi {
|
|
|
12659
12708
|
}
|
|
12660
12709
|
|
|
12661
12710
|
/**
|
|
12662
|
-
*
|
|
12711
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
12663
12712
|
*
|
|
12664
12713
|
* @remarks
|
|
12665
12714
|
* When you call this operation to delete routing entries, note the following items:
|
|
12666
12715
|
* - Only routing entries in the **Available** state can be deleted.
|
|
12667
|
-
* - Routing entries cannot be deleted if the VPC
|
|
12668
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
12669
|
-
* - If the
|
|
12670
|
-
* - If the specified
|
|
12671
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
12716
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
12717
|
+
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
|
|
12718
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
12719
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
12720
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
12672
12721
|
*
|
|
12673
12722
|
* @param request - DeleteRouteEntriesRequest
|
|
12674
12723
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -12727,16 +12776,16 @@ export default class Client extends OpenApi {
|
|
|
12727
12776
|
}
|
|
12728
12777
|
|
|
12729
12778
|
/**
|
|
12730
|
-
*
|
|
12779
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
12731
12780
|
*
|
|
12732
12781
|
* @remarks
|
|
12733
12782
|
* When you call this operation to delete routing entries, note the following items:
|
|
12734
12783
|
* - Only routing entries in the **Available** state can be deleted.
|
|
12735
|
-
* - Routing entries cannot be deleted if the VPC
|
|
12736
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
12737
|
-
* - If the
|
|
12738
|
-
* - If the specified
|
|
12739
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
12784
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
12785
|
+
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the routing entry is not yet deleted. The deletion task is still running in the background. You can call [DescribeRouteEntryList](https://help.aliyun.com/document_detail/138148.html) to query the deletion status of the routing entry:
|
|
12786
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
12787
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
12788
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
12740
12789
|
*
|
|
12741
12790
|
* @param request - DeleteRouteEntriesRequest
|
|
12742
12791
|
* @returns DeleteRouteEntriesResponse
|
|
@@ -13242,10 +13291,10 @@ export default class Client extends OpenApi {
|
|
|
13242
13291
|
* Deletes an SSL server. After the SSL server is deleted, the system automatically deletes all SSL client certificates associated with the SSL server, and clients that have installed these SSL client certificates are automatically disconnected from the SSL-VPN connection.
|
|
13243
13292
|
*
|
|
13244
13293
|
* @remarks
|
|
13245
|
-
* - **DeleteSslVpnServer** is
|
|
13294
|
+
* - The **DeleteSslVpnServer** operation is asynchronous. After you send a request, the system returns a request ID. However, the SSL server is not yet deleted. The deletion task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
|
|
13246
13295
|
* - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
|
|
13247
13296
|
* - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
|
|
13248
|
-
* - **DeleteSslVpnServer** does not support concurrent deletion of SSL
|
|
13297
|
+
* - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
|
|
13249
13298
|
*
|
|
13250
13299
|
* @param request - DeleteSslVpnServerRequest
|
|
13251
13300
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -13303,10 +13352,10 @@ export default class Client extends OpenApi {
|
|
|
13303
13352
|
* Deletes an SSL server. After the SSL server is deleted, the system automatically deletes all SSL client certificates associated with the SSL server, and clients that have installed these SSL client certificates are automatically disconnected from the SSL-VPN connection.
|
|
13304
13353
|
*
|
|
13305
13354
|
* @remarks
|
|
13306
|
-
* - **DeleteSslVpnServer** is
|
|
13355
|
+
* - The **DeleteSslVpnServer** operation is asynchronous. After you send a request, the system returns a request ID. However, the SSL server is not yet deleted. The deletion task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) to query the status of the VPN gateway instance to determine the deletion status of the SSL server:
|
|
13307
13356
|
* - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
|
|
13308
13357
|
* - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
|
|
13309
|
-
* - **DeleteSslVpnServer** does not support concurrent deletion of SSL
|
|
13358
|
+
* - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
|
|
13310
13359
|
*
|
|
13311
13360
|
* @param request - DeleteSslVpnServerRequest
|
|
13312
13361
|
* @returns DeleteSslVpnServerResponse
|
|
@@ -13735,7 +13784,7 @@ export default class Client extends OpenApi {
|
|
|
13735
13784
|
}
|
|
13736
13785
|
|
|
13737
13786
|
/**
|
|
13738
|
-
*
|
|
13787
|
+
* Calls DeleteVbrHa to delete a VBR failover group.
|
|
13739
13788
|
*
|
|
13740
13789
|
* @param request - DeleteVbrHaRequest
|
|
13741
13790
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -13790,7 +13839,7 @@ export default class Client extends OpenApi {
|
|
|
13790
13839
|
}
|
|
13791
13840
|
|
|
13792
13841
|
/**
|
|
13793
|
-
*
|
|
13842
|
+
* Calls DeleteVbrHa to delete a VBR failover group.
|
|
13794
13843
|
*
|
|
13795
13844
|
* @param request - DeleteVbrHaRequest
|
|
13796
13845
|
* @returns DeleteVbrHaResponse
|
|
@@ -13804,7 +13853,7 @@ export default class Client extends OpenApi {
|
|
|
13804
13853
|
* Deletes a destination route entry from an IPsec-VPN connection.
|
|
13805
13854
|
*
|
|
13806
13855
|
* @remarks
|
|
13807
|
-
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry
|
|
13856
|
+
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
|
|
13808
13857
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
|
|
13809
13858
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
|
|
13810
13859
|
* - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
|
|
@@ -13877,7 +13926,7 @@ export default class Client extends OpenApi {
|
|
|
13877
13926
|
* Deletes a destination route entry from an IPsec-VPN connection.
|
|
13878
13927
|
*
|
|
13879
13928
|
* @remarks
|
|
13880
|
-
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry
|
|
13929
|
+
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the deletion status of the destination route entry:
|
|
13881
13930
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
|
|
13882
13931
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
|
|
13883
13932
|
* - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
|
|
@@ -14209,11 +14258,11 @@ export default class Client extends OpenApi {
|
|
|
14209
14258
|
}
|
|
14210
14259
|
|
|
14211
14260
|
/**
|
|
14212
|
-
* Deletes an IPsec-VPN connection
|
|
14261
|
+
* Deletes an IPsec-VPN connection.
|
|
14213
14262
|
*
|
|
14214
14263
|
* @remarks
|
|
14215
|
-
* - If the IPsec-VPN connection is
|
|
14216
|
-
* - If the IPsec-VPN connection is not
|
|
14264
|
+
* - If the IPsec-VPN connection is bindded to a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
|
|
14265
|
+
* - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
|
|
14217
14266
|
*
|
|
14218
14267
|
* @param request - DeleteVpnAttachmentRequest
|
|
14219
14268
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -14264,11 +14313,11 @@ export default class Client extends OpenApi {
|
|
|
14264
14313
|
}
|
|
14265
14314
|
|
|
14266
14315
|
/**
|
|
14267
|
-
* Deletes an IPsec-VPN connection
|
|
14316
|
+
* Deletes an IPsec-VPN connection.
|
|
14268
14317
|
*
|
|
14269
14318
|
* @remarks
|
|
14270
|
-
* - If the IPsec-VPN connection is
|
|
14271
|
-
* - If the IPsec-VPN connection is not
|
|
14319
|
+
* - If the IPsec-VPN connection is bindded to a transit router instance, disassociate the IPsec-VPN connection from the transit router instance before you delete the IPsec-VPN connection. For more information, see [DeleteTransitRouterVpnAttachment](https://help.aliyun.com/document_detail/468251.html).
|
|
14320
|
+
* - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
|
|
14272
14321
|
*
|
|
14273
14322
|
* @param request - DeleteVpnAttachmentRequest
|
|
14274
14323
|
* @returns DeleteVpnAttachmentResponse
|
|
@@ -14282,7 +14331,7 @@ export default class Client extends OpenApi {
|
|
|
14282
14331
|
* Deletes a specified IPsec-VPN connection.
|
|
14283
14332
|
*
|
|
14284
14333
|
* @remarks
|
|
14285
|
-
* - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance
|
|
14334
|
+
* - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the deletion status of the IPsec-VPN connection:
|
|
14286
14335
|
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
|
|
14287
14336
|
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
|
|
14288
14337
|
* - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
|
|
@@ -14344,7 +14393,7 @@ export default class Client extends OpenApi {
|
|
|
14344
14393
|
* Deletes a specified IPsec-VPN connection.
|
|
14345
14394
|
*
|
|
14346
14395
|
* @remarks
|
|
14347
|
-
* - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance
|
|
14396
|
+
* - **DeleteVpnConnection** is an asynchronous operation. After you send a request, the system returns a request ID, but the IPsec-VPN connection is not yet deleted. The deletion task continues to run in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the status of the VPN gateway instance to determine the deletion status of the IPsec-VPN connection:
|
|
14348
14397
|
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
|
|
14349
14398
|
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
|
|
14350
14399
|
* - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
|
|
@@ -14362,7 +14411,7 @@ export default class Client extends OpenApi {
|
|
|
14362
14411
|
* Deletes a specified VPN gateway.
|
|
14363
14412
|
*
|
|
14364
14413
|
* @remarks
|
|
14365
|
-
* > You cannot delete a VPN gateway that has
|
|
14414
|
+
* > You cannot delete a VPN gateway that has IPsec-VPN connections.
|
|
14366
14415
|
*
|
|
14367
14416
|
* @param request - DeleteVpnGatewayRequest
|
|
14368
14417
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -14420,7 +14469,7 @@ export default class Client extends OpenApi {
|
|
|
14420
14469
|
* Deletes a specified VPN gateway.
|
|
14421
14470
|
*
|
|
14422
14471
|
* @remarks
|
|
14423
|
-
* > You cannot delete a VPN gateway that has
|
|
14472
|
+
* > You cannot delete a VPN gateway that has IPsec-VPN connections.
|
|
14424
14473
|
*
|
|
14425
14474
|
* @param request - DeleteVpnGatewayRequest
|
|
14426
14475
|
* @returns DeleteVpnGatewayResponse
|
|
@@ -14536,7 +14585,7 @@ export default class Client extends OpenApi {
|
|
|
14536
14585
|
* Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
|
|
14537
14586
|
*
|
|
14538
14587
|
* @remarks
|
|
14539
|
-
* - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway and determine the deletion status of the VPN destination routing:
|
|
14588
|
+
* - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway, and determine the deletion status of the VPN destination routing:
|
|
14540
14589
|
* - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
|
|
14541
14590
|
* - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
|
|
14542
14591
|
* - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
|
|
@@ -14613,7 +14662,7 @@ export default class Client extends OpenApi {
|
|
|
14613
14662
|
* Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
|
|
14614
14663
|
*
|
|
14615
14664
|
* @remarks
|
|
14616
|
-
* - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway and determine the deletion status of the VPN destination routing:
|
|
14665
|
+
* - **DeleteVpnRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID. However, the VPN destination route is not yet deleted, and the deletion node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway, and determine the deletion status of the VPN destination routing:
|
|
14617
14666
|
* - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
|
|
14618
14667
|
* - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
|
|
14619
14668
|
* - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
|
|
@@ -15367,10 +15416,10 @@ export default class Client extends OpenApi {
|
|
|
15367
15416
|
}
|
|
15368
15417
|
|
|
15369
15418
|
/**
|
|
15370
|
-
* Queries
|
|
15419
|
+
* Queries elastic IP addresses (EIPs) created in a specified region.
|
|
15371
15420
|
*
|
|
15372
15421
|
* @remarks
|
|
15373
|
-
*
|
|
15422
|
+
* This operation queries information about EIPs created in a specified region, including the maximum bandwidth, billing method, and the type of instance currently attached to each EIP. If you frequently perform deep paging or page skipping, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential pagination.
|
|
15374
15423
|
*
|
|
15375
15424
|
* @param request - DescribeEipAddressesRequest
|
|
15376
15425
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -15497,10 +15546,10 @@ export default class Client extends OpenApi {
|
|
|
15497
15546
|
}
|
|
15498
15547
|
|
|
15499
15548
|
/**
|
|
15500
|
-
* Queries
|
|
15549
|
+
* Queries elastic IP addresses (EIPs) created in a specified region.
|
|
15501
15550
|
*
|
|
15502
15551
|
* @remarks
|
|
15503
|
-
*
|
|
15552
|
+
* This operation queries information about EIPs created in a specified region, including the maximum bandwidth, billing method, and the type of instance currently attached to each EIP. If you frequently perform deep paging or page skipping, the **Throttling.DeepPageSkip** error code may be returned. Reduce the query frequency or use sequential pagination.
|
|
15504
15553
|
*
|
|
15505
15554
|
* @param request - DescribeEipAddressesRequest
|
|
15506
15555
|
* @returns DescribeEipAddressesResponse
|
|
@@ -15825,6 +15874,9 @@ export default class Client extends OpenApi {
|
|
|
15825
15874
|
/**
|
|
15826
15875
|
* Queries Express Connect QoS queues.
|
|
15827
15876
|
*
|
|
15877
|
+
* @remarks
|
|
15878
|
+
* Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
|
|
15879
|
+
*
|
|
15828
15880
|
* @param request - DescribeExpressConnectTrafficQosQueueRequest
|
|
15829
15881
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
15830
15882
|
* @returns DescribeExpressConnectTrafficQosQueueResponse
|
|
@@ -15888,6 +15940,9 @@ export default class Client extends OpenApi {
|
|
|
15888
15940
|
/**
|
|
15889
15941
|
* Queries Express Connect QoS queues.
|
|
15890
15942
|
*
|
|
15943
|
+
* @remarks
|
|
15944
|
+
* Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
|
|
15945
|
+
*
|
|
15891
15946
|
* @param request - DescribeExpressConnectTrafficQosQueueRequest
|
|
15892
15947
|
* @returns DescribeExpressConnectTrafficQosQueueResponse
|
|
15893
15948
|
*/
|
|
@@ -15975,7 +16030,7 @@ export default class Client extends OpenApi {
|
|
|
15975
16030
|
}
|
|
15976
16031
|
|
|
15977
16032
|
/**
|
|
15978
|
-
* Queries the details of an Express Connect failover test job
|
|
16033
|
+
* Queries the details of an Express Connect failover test job.
|
|
15979
16034
|
*
|
|
15980
16035
|
* @param request - DescribeFailoverTestJobRequest
|
|
15981
16036
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -16030,7 +16085,7 @@ export default class Client extends OpenApi {
|
|
|
16030
16085
|
}
|
|
16031
16086
|
|
|
16032
16087
|
/**
|
|
16033
|
-
* Queries the details of an Express Connect failover test job
|
|
16088
|
+
* Queries the details of an Express Connect failover test job.
|
|
16034
16089
|
*
|
|
16035
16090
|
* @param request - DescribeFailoverTestJobRequest
|
|
16036
16091
|
* @returns DescribeFailoverTestJobResponse
|
|
@@ -16041,7 +16096,7 @@ export default class Client extends OpenApi {
|
|
|
16041
16096
|
}
|
|
16042
16097
|
|
|
16043
16098
|
/**
|
|
16044
|
-
* Queries failover test jobs
|
|
16099
|
+
* Queries Express Connect failover test jobs in batches.
|
|
16045
16100
|
*
|
|
16046
16101
|
* @param request - DescribeFailoverTestJobsRequest
|
|
16047
16102
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -16104,7 +16159,7 @@ export default class Client extends OpenApi {
|
|
|
16104
16159
|
}
|
|
16105
16160
|
|
|
16106
16161
|
/**
|
|
16107
|
-
* Queries failover test jobs
|
|
16162
|
+
* Queries Express Connect failover test jobs in batches.
|
|
16108
16163
|
*
|
|
16109
16164
|
* @param request - DescribeFailoverTestJobsRequest
|
|
16110
16165
|
* @returns DescribeFailoverTestJobsResponse
|
|
@@ -17911,7 +17966,7 @@ export default class Client extends OpenApi {
|
|
|
17911
17966
|
* Queries information about Express Connect circuits in a specified region.
|
|
17912
17967
|
*
|
|
17913
17968
|
* @remarks
|
|
17914
|
-
* By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system,
|
|
17969
|
+
* By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, see the description of **Key** in the **request parameters** section of this topic.
|
|
17915
17970
|
*
|
|
17916
17971
|
* @param request - DescribePhysicalConnectionsRequest
|
|
17917
17972
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -17989,7 +18044,7 @@ export default class Client extends OpenApi {
|
|
|
17989
18044
|
* Queries information about Express Connect circuits in a specified region.
|
|
17990
18045
|
*
|
|
17991
18046
|
* @remarks
|
|
17992
|
-
* By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system,
|
|
18047
|
+
* By default, the system queries information about all Express Connect circuits in the specified region. You can use the filter options provided by the **DescribePhysicalConnections** operation to query information about specific Express Connect circuits. For the filter options supported by the system, see the description of **Key** in the **request parameters** section of this topic.
|
|
17993
18048
|
*
|
|
17994
18049
|
* @param request - DescribePhysicalConnectionsRequest
|
|
17995
18050
|
* @returns DescribePhysicalConnectionsResponse
|
|
@@ -18513,7 +18568,7 @@ export default class Client extends OpenApi {
|
|
|
18513
18568
|
}
|
|
18514
18569
|
|
|
18515
18570
|
/**
|
|
18516
|
-
* Queries router interfaces in a specified region
|
|
18571
|
+
* Queries router interfaces in a specified region.
|
|
18517
18572
|
*
|
|
18518
18573
|
* @param request - DescribeRouterInterfacesRequest
|
|
18519
18574
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -18580,7 +18635,7 @@ export default class Client extends OpenApi {
|
|
|
18580
18635
|
}
|
|
18581
18636
|
|
|
18582
18637
|
/**
|
|
18583
|
-
* Queries router interfaces in a specified region
|
|
18638
|
+
* Queries router interfaces in a specified region.
|
|
18584
18639
|
*
|
|
18585
18640
|
* @param request - DescribeRouterInterfacesRequest
|
|
18586
18641
|
* @returns DescribeRouterInterfacesResponse
|
|
@@ -19143,7 +19198,7 @@ export default class Client extends OpenApi {
|
|
|
19143
19198
|
}
|
|
19144
19199
|
|
|
19145
19200
|
/**
|
|
19146
|
-
*
|
|
19201
|
+
* Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
|
|
19147
19202
|
*
|
|
19148
19203
|
* @param request - DescribeTagKeysForExpressConnectRequest
|
|
19149
19204
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -19210,7 +19265,7 @@ export default class Client extends OpenApi {
|
|
|
19210
19265
|
}
|
|
19211
19266
|
|
|
19212
19267
|
/**
|
|
19213
|
-
*
|
|
19268
|
+
* Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
|
|
19214
19269
|
*
|
|
19215
19270
|
* @param request - DescribeTagKeysForExpressConnectRequest
|
|
19216
19271
|
* @returns DescribeTagKeysForExpressConnectResponse
|
|
@@ -19449,6 +19504,9 @@ export default class Client extends OpenApi {
|
|
|
19449
19504
|
/**
|
|
19450
19505
|
* Queries networkable information. Internal networking is performed by vSwitch.
|
|
19451
19506
|
*
|
|
19507
|
+
* @remarks
|
|
19508
|
+
* 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.
|
|
19509
|
+
*
|
|
19452
19510
|
* @param request - DescribeVSwitchesRequest
|
|
19453
19511
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
19454
19512
|
* @returns DescribeVSwitchesResponse
|
|
@@ -19548,6 +19606,9 @@ export default class Client extends OpenApi {
|
|
|
19548
19606
|
/**
|
|
19549
19607
|
* Queries networkable information. Internal networking is performed by vSwitch.
|
|
19550
19608
|
*
|
|
19609
|
+
* @remarks
|
|
19610
|
+
* 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.
|
|
19611
|
+
*
|
|
19551
19612
|
* @param request - DescribeVSwitchesRequest
|
|
19552
19613
|
* @returns DescribeVSwitchesResponse
|
|
19553
19614
|
*/
|
|
@@ -19705,7 +19766,7 @@ export default class Client extends OpenApi {
|
|
|
19705
19766
|
}
|
|
19706
19767
|
|
|
19707
19768
|
/**
|
|
19708
|
-
* Queries
|
|
19769
|
+
* Queries Virtual Border Routers (VBRs) that are created.
|
|
19709
19770
|
*
|
|
19710
19771
|
* @param request - DescribeVirtualBorderRoutersRequest
|
|
19711
19772
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -19772,7 +19833,7 @@ export default class Client extends OpenApi {
|
|
|
19772
19833
|
}
|
|
19773
19834
|
|
|
19774
19835
|
/**
|
|
19775
|
-
* Queries
|
|
19836
|
+
* Queries Virtual Border Routers (VBRs) that are created.
|
|
19776
19837
|
*
|
|
19777
19838
|
* @param request - DescribeVirtualBorderRoutersRequest
|
|
19778
19839
|
* @returns DescribeVirtualBorderRoutersResponse
|
|
@@ -20015,6 +20076,9 @@ export default class Client extends OpenApi {
|
|
|
20015
20076
|
/**
|
|
20016
20077
|
* Queries created VPCs.
|
|
20017
20078
|
*
|
|
20079
|
+
* @remarks
|
|
20080
|
+
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
|
|
20081
|
+
*
|
|
20018
20082
|
* @param request - DescribeVpcsRequest
|
|
20019
20083
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
20020
20084
|
* @returns DescribeVpcsResponse
|
|
@@ -20106,6 +20170,9 @@ export default class Client extends OpenApi {
|
|
|
20106
20170
|
/**
|
|
20107
20171
|
* Queries created VPCs.
|
|
20108
20172
|
*
|
|
20173
|
+
* @remarks
|
|
20174
|
+
* The **DescribeVpcs** operation may return the **Throttling.DeepPageSkip** error code during frequent deep paging or page skipping. Reduce the query frequency or use sequential paging.
|
|
20175
|
+
*
|
|
20109
20176
|
* @param request - DescribeVpcsRequest
|
|
20110
20177
|
* @returns DescribeVpcsResponse
|
|
20111
20178
|
*/
|
|
@@ -20839,7 +20906,7 @@ export default class Client extends OpenApi {
|
|
|
20839
20906
|
}
|
|
20840
20907
|
|
|
20841
20908
|
/**
|
|
20842
|
-
* Queries the logs of an SSL server
|
|
20909
|
+
* Queries the logs of an SSL server.
|
|
20843
20910
|
*
|
|
20844
20911
|
* @param request - DescribeVpnSslServerLogsRequest
|
|
20845
20912
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -20914,7 +20981,7 @@ export default class Client extends OpenApi {
|
|
|
20914
20981
|
}
|
|
20915
20982
|
|
|
20916
20983
|
/**
|
|
20917
|
-
* Queries the logs of an SSL server
|
|
20984
|
+
* Queries the logs of an SSL server.
|
|
20918
20985
|
*
|
|
20919
20986
|
* @param request - DescribeVpnSslServerLogsRequest
|
|
20920
20987
|
* @returns DescribeVpnSslServerLogsResponse
|
|
@@ -21153,10 +21220,10 @@ export default class Client extends OpenApi {
|
|
|
21153
21220
|
}
|
|
21154
21221
|
|
|
21155
21222
|
/**
|
|
21156
|
-
*
|
|
21223
|
+
* Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
|
|
21157
21224
|
*
|
|
21158
21225
|
* @remarks
|
|
21159
|
-
* Only VPN gateway instances in specific regions support the one-click
|
|
21226
|
+
* Only VPN gateway instances in specific regions support the one-click diagnosis feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
|
|
21160
21227
|
*
|
|
21161
21228
|
* @param request - DiagnoseVpnGatewayRequest
|
|
21162
21229
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -21207,10 +21274,10 @@ export default class Client extends OpenApi {
|
|
|
21207
21274
|
}
|
|
21208
21275
|
|
|
21209
21276
|
/**
|
|
21210
|
-
*
|
|
21277
|
+
* Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
|
|
21211
21278
|
*
|
|
21212
21279
|
* @remarks
|
|
21213
|
-
* Only VPN gateway instances in specific regions support the one-click
|
|
21280
|
+
* Only VPN gateway instances in specific regions support the one-click diagnosis feature. For more information about regions, see [Regions that support VPN Gateway features](https://help.aliyun.com/document_detail/430697.html).
|
|
21214
21281
|
*
|
|
21215
21282
|
* @param request - DiagnoseVpnGatewayRequest
|
|
21216
21283
|
* @returns DiagnoseVpnGatewayResponse
|
|
@@ -21509,10 +21576,10 @@ export default class Client extends OpenApi {
|
|
|
21509
21576
|
* Dissociates a VPN gateway from a certificate.
|
|
21510
21577
|
*
|
|
21511
21578
|
* @remarks
|
|
21512
|
-
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
21579
|
+
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID, but the VPN gateway has not yet been dissociated from the SSL certificate. The dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and confirm the dissociation status of the SSL certificate:
|
|
21513
21580
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
|
|
21514
21581
|
* - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
|
|
21515
|
-
* - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL
|
|
21582
|
+
* - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
|
|
21516
21583
|
*
|
|
21517
21584
|
* @param request - DissociateVpnGatewayWithCertificateRequest
|
|
21518
21585
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -21566,10 +21633,10 @@ export default class Client extends OpenApi {
|
|
|
21566
21633
|
* Dissociates a VPN gateway from a certificate.
|
|
21567
21634
|
*
|
|
21568
21635
|
* @remarks
|
|
21569
|
-
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
21636
|
+
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID, but the VPN gateway has not yet been dissociated from the SSL certificate. The dissociation task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the status of the VPN gateway instance and confirm the dissociation status of the SSL certificate:
|
|
21570
21637
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
|
|
21571
21638
|
* - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
|
|
21572
|
-
* - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL
|
|
21639
|
+
* - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
|
|
21573
21640
|
*
|
|
21574
21641
|
* @param request - DissociateVpnGatewayWithCertificateRequest
|
|
21575
21642
|
* @returns DissociateVpnGatewayWithCertificateResponse
|
|
@@ -21645,11 +21712,12 @@ export default class Client extends OpenApi {
|
|
|
21645
21712
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
21646
21713
|
*
|
|
21647
21714
|
* @remarks
|
|
21648
|
-
* When you
|
|
21649
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
21650
|
-
* -
|
|
21651
|
-
* -
|
|
21652
|
-
* -
|
|
21715
|
+
* When you invoke this operation, note the following items:
|
|
21716
|
+
* - You can enable only an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state. To reach the Confirmed state, complete the following steps in sequence: call CreatePhysicalConnection to create a circuit (Initial → Allocating), wait for resource allocation to complete (Allocating → Allocated), and then call ConfirmPhysicalConnection after construction is complete (Allocated → Confirmed).
|
|
21717
|
+
* - A billing activation step occurs between the Confirmed and Enabled states. By default (if ByPassSp is not specified or ByPassSp is set to false), the system automatically creates a billing order in the sales and billing system when you invoke this operation. The circuit is enabled only after the order is created. To skip the billing order flow and directly enable the circuit, set ByPassSp to true. This capability is available only to whitelist accounts. For more information, see the ByPassSp parameter description.
|
|
21718
|
+
* - The EnablePhysicalConnection operation is asynchronous. The system returns a success response, but the Express Connect circuit is not yet fully enabled because the backend enablement task is still in progress. You can invoke DescribePhysicalConnections to query the enablement status of the Express Connect circuit.
|
|
21719
|
+
* - The EnablePhysicalConnection operation does not support concurrent enablement of the same Express Connect circuit that is in the Confirmed state. Concurrent invocations return an error.
|
|
21720
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
21653
21721
|
*
|
|
21654
21722
|
* @param request - EnablePhysicalConnectionRequest
|
|
21655
21723
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -21711,11 +21779,12 @@ export default class Client extends OpenApi {
|
|
|
21711
21779
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
21712
21780
|
*
|
|
21713
21781
|
* @remarks
|
|
21714
|
-
* When you
|
|
21715
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
21716
|
-
* -
|
|
21717
|
-
* -
|
|
21718
|
-
* -
|
|
21782
|
+
* When you invoke this operation, note the following items:
|
|
21783
|
+
* - You can enable only an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state. To reach the Confirmed state, complete the following steps in sequence: call CreatePhysicalConnection to create a circuit (Initial → Allocating), wait for resource allocation to complete (Allocating → Allocated), and then call ConfirmPhysicalConnection after construction is complete (Allocated → Confirmed).
|
|
21784
|
+
* - A billing activation step occurs between the Confirmed and Enabled states. By default (if ByPassSp is not specified or ByPassSp is set to false), the system automatically creates a billing order in the sales and billing system when you invoke this operation. The circuit is enabled only after the order is created. To skip the billing order flow and directly enable the circuit, set ByPassSp to true. This capability is available only to whitelist accounts. For more information, see the ByPassSp parameter description.
|
|
21785
|
+
* - The EnablePhysicalConnection operation is asynchronous. The system returns a success response, but the Express Connect circuit is not yet fully enabled because the backend enablement task is still in progress. You can invoke DescribePhysicalConnections to query the enablement status of the Express Connect circuit.
|
|
21786
|
+
* - The EnablePhysicalConnection operation does not support concurrent enablement of the same Express Connect circuit that is in the Confirmed state. Concurrent invocations return an error.
|
|
21787
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
21719
21788
|
*
|
|
21720
21789
|
* @param request - EnablePhysicalConnectionRequest
|
|
21721
21790
|
* @returns EnablePhysicalConnectionResponse
|
|
@@ -22084,7 +22153,7 @@ export default class Client extends OpenApi {
|
|
|
22084
22153
|
* Queries the information about a single NAT gateway instance.
|
|
22085
22154
|
*
|
|
22086
22155
|
* @remarks
|
|
22087
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
22156
|
+
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic does not distinguish between the two types.
|
|
22088
22157
|
*
|
|
22089
22158
|
* @param request - GetNatGatewayAttributeRequest
|
|
22090
22159
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -22142,7 +22211,7 @@ export default class Client extends OpenApi {
|
|
|
22142
22211
|
* Queries the information about a single NAT gateway instance.
|
|
22143
22212
|
*
|
|
22144
22213
|
* @remarks
|
|
22145
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
22214
|
+
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic does not distinguish between the two types.
|
|
22146
22215
|
*
|
|
22147
22216
|
* @param request - GetNatGatewayAttributeRequest
|
|
22148
22217
|
* @returns GetNatGatewayAttributeResponse
|
|
@@ -22753,10 +22822,10 @@ export default class Client extends OpenApi {
|
|
|
22753
22822
|
}
|
|
22754
22823
|
|
|
22755
22824
|
/**
|
|
22756
|
-
* Queries the one-click
|
|
22825
|
+
* Queries the one-click diagnosis result of a VPN gateway instance.
|
|
22757
22826
|
*
|
|
22758
22827
|
* @remarks
|
|
22759
|
-
* When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters
|
|
22828
|
+
* When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
|
|
22760
22829
|
*
|
|
22761
22830
|
* @param request - GetVpnGatewayDiagnoseResultRequest
|
|
22762
22831
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -22799,10 +22868,10 @@ export default class Client extends OpenApi {
|
|
|
22799
22868
|
}
|
|
22800
22869
|
|
|
22801
22870
|
/**
|
|
22802
|
-
* Queries the one-click
|
|
22871
|
+
* Queries the one-click diagnosis result of a VPN gateway instance.
|
|
22803
22872
|
*
|
|
22804
22873
|
* @remarks
|
|
22805
|
-
* When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters
|
|
22874
|
+
* When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
|
|
22806
22875
|
*
|
|
22807
22876
|
* @param request - GetVpnGatewayDiagnoseResultRequest
|
|
22808
22877
|
* @returns GetVpnGatewayDiagnoseResultResponse
|
|
@@ -22904,7 +22973,18 @@ export default class Client extends OpenApi {
|
|
|
22904
22973
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
22905
22974
|
*
|
|
22906
22975
|
* @remarks
|
|
22907
|
-
*
|
|
22976
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
22977
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
22978
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
22979
|
+
* **Account B (VBR owner, the account specified by VbrOwnerUid):** When GrantType=Specify, the VBRs specified in VbrInstanceIds must already be created. Creating a VBR depends on the complete Express Connect circuit lifecycle:
|
|
22980
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
22981
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
22982
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
22983
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
22984
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
22985
|
+
* - GrantType=All: Grants authorization to all VBRs under Account B (only the validity of VbrOwnerUid is verified. The VBRs do not need to be created yet).
|
|
22986
|
+
* - GrantType=Specify: Grants authorization to specified VBRs. The instances in VbrInstanceIds must already exist in the region specified by VbrRegionNo under the account specified by VbrOwnerUid. Otherwise, the error Instance.NotExist is returned.
|
|
22987
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
22908
22988
|
*
|
|
22909
22989
|
* @param tmpReq - GrantInstanceToVbrRequest
|
|
22910
22990
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -22964,7 +23044,18 @@ export default class Client extends OpenApi {
|
|
|
22964
23044
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
22965
23045
|
*
|
|
22966
23046
|
* @remarks
|
|
22967
|
-
*
|
|
23047
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
23048
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
23049
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
23050
|
+
* **Account B (VBR owner, the account specified by VbrOwnerUid):** When GrantType=Specify, the VBRs specified in VbrInstanceIds must already be created. Creating a VBR depends on the complete Express Connect circuit lifecycle:
|
|
23051
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
23052
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
23053
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
23054
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
23055
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
23056
|
+
* - GrantType=All: Grants authorization to all VBRs under Account B (only the validity of VbrOwnerUid is verified. The VBRs do not need to be created yet).
|
|
23057
|
+
* - GrantType=Specify: Grants authorization to specified VBRs. The instances in VbrInstanceIds must already exist in the region specified by VbrRegionNo under the account specified by VbrOwnerUid. Otherwise, the error Instance.NotExist is returned.
|
|
23058
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
22968
23059
|
*
|
|
22969
23060
|
* @param request - GrantInstanceToVbrRequest
|
|
22970
23061
|
* @returns GrantInstanceToVbrResponse
|
|
@@ -22975,7 +23066,7 @@ export default class Client extends OpenApi {
|
|
|
22975
23066
|
}
|
|
22976
23067
|
|
|
22977
23068
|
/**
|
|
22978
|
-
*
|
|
23069
|
+
* Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
|
|
22979
23070
|
*
|
|
22980
23071
|
* @param request - ListBusinessAccessPointsRequest
|
|
22981
23072
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -23010,7 +23101,7 @@ export default class Client extends OpenApi {
|
|
|
23010
23101
|
}
|
|
23011
23102
|
|
|
23012
23103
|
/**
|
|
23013
|
-
*
|
|
23104
|
+
* Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
|
|
23014
23105
|
*
|
|
23015
23106
|
* @param request - ListBusinessAccessPointsRequest
|
|
23016
23107
|
* @returns ListBusinessAccessPointsResponse
|
|
@@ -24720,7 +24811,7 @@ export default class Client extends OpenApi {
|
|
|
24720
24811
|
}
|
|
24721
24812
|
|
|
24722
24813
|
/**
|
|
24723
|
-
* Queries information about shared Express Connect circuits
|
|
24814
|
+
* Queries information about shared Express Connect circuits.
|
|
24724
24815
|
*
|
|
24725
24816
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
24726
24817
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -24795,7 +24886,7 @@ export default class Client extends OpenApi {
|
|
|
24795
24886
|
}
|
|
24796
24887
|
|
|
24797
24888
|
/**
|
|
24798
|
-
* Queries information about shared Express Connect circuits
|
|
24889
|
+
* Queries information about shared Express Connect circuits.
|
|
24799
24890
|
*
|
|
24800
24891
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
24801
24892
|
* @returns ListVirtualPhysicalConnectionsResponse
|
|
@@ -25057,7 +25148,7 @@ export default class Client extends OpenApi {
|
|
|
25057
25148
|
* @remarks
|
|
25058
25149
|
* When you call **ListVpnCertificateAssociations**:
|
|
25059
25150
|
* - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
|
|
25060
|
-
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified
|
|
25151
|
+
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified type in the specified region are queried.
|
|
25061
25152
|
* - If you specify the **RegionId** and **VpnGatewayId** parameters, the associations between the specified VPN gateway instances and SSL certificates in the specified region are queried.
|
|
25062
25153
|
* - If you specify the **RegionId** and **CertificateId** parameters, the associations between the specified SSL certificates and VPN gateway instances in the specified region are queried.
|
|
25063
25154
|
*
|
|
@@ -25115,7 +25206,7 @@ export default class Client extends OpenApi {
|
|
|
25115
25206
|
* @remarks
|
|
25116
25207
|
* When you call **ListVpnCertificateAssociations**:
|
|
25117
25208
|
* - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
|
|
25118
|
-
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified
|
|
25209
|
+
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified type in the specified region are queried.
|
|
25119
25210
|
* - If you specify the **RegionId** and **VpnGatewayId** parameters, the associations between the specified VPN gateway instances and SSL certificates in the specified region are queried.
|
|
25120
25211
|
* - If you specify the **RegionId** and **CertificateId** parameters, the associations between the specified SSL certificates and VPN gateway instances in the specified region are queried.
|
|
25121
25212
|
*
|
|
@@ -25544,7 +25635,7 @@ export default class Client extends OpenApi {
|
|
|
25544
25635
|
}
|
|
25545
25636
|
|
|
25546
25637
|
/**
|
|
25547
|
-
* Modifies the configuration of a customer gateway
|
|
25638
|
+
* Modifies the configuration of a customer gateway.
|
|
25548
25639
|
*
|
|
25549
25640
|
* @remarks
|
|
25550
25641
|
* - When you call the **ModifyCustomerGatewayAttribute** operation, if the **AuthKey** parameter is not empty, this operation is asynchronous. The system returns the customer gateway information first, but the configuration has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the customer gateway configuration:
|
|
@@ -25618,7 +25709,7 @@ export default class Client extends OpenApi {
|
|
|
25618
25709
|
}
|
|
25619
25710
|
|
|
25620
25711
|
/**
|
|
25621
|
-
* Modifies the configuration of a customer gateway
|
|
25712
|
+
* Modifies the configuration of a customer gateway.
|
|
25622
25713
|
*
|
|
25623
25714
|
* @remarks
|
|
25624
25715
|
* - When you call the **ModifyCustomerGatewayAttribute** operation, if the **AuthKey** parameter is not empty, this operation is asynchronous. The system returns the customer gateway information first, but the configuration has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the customer gateway configuration:
|
|
@@ -25928,12 +26019,12 @@ export default class Client extends OpenApi {
|
|
|
25928
26019
|
}
|
|
25929
26020
|
|
|
25930
26021
|
/**
|
|
25931
|
-
*
|
|
26022
|
+
* Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
|
|
25932
26023
|
*
|
|
25933
26024
|
* @remarks
|
|
25934
26025
|
* - Only dedicated Express Connect circuits that are in the Normal state and do not have overdue payments can be associated. Shared Express Connect circuit ports and Virtual Border Router (VBR) instances are not supported.
|
|
25935
|
-
* - When associating dedicated Express Connect circuits, only full
|
|
25936
|
-
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must
|
|
26026
|
+
* - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
|
|
26027
|
+
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must be added to the whitelist before you can associate it.
|
|
25937
26028
|
* - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
|
|
25938
26029
|
* - If a single VBR is associated with multiple Express Connect circuits, you must associate all Express Connect circuits of the VBR at the same time.
|
|
25939
26030
|
*
|
|
@@ -26006,12 +26097,12 @@ export default class Client extends OpenApi {
|
|
|
26006
26097
|
}
|
|
26007
26098
|
|
|
26008
26099
|
/**
|
|
26009
|
-
*
|
|
26100
|
+
* Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
|
|
26010
26101
|
*
|
|
26011
26102
|
* @remarks
|
|
26012
26103
|
* - Only dedicated Express Connect circuits that are in the Normal state and do not have overdue payments can be associated. Shared Express Connect circuit ports and Virtual Border Router (VBR) instances are not supported.
|
|
26013
|
-
* - When associating dedicated Express Connect circuits, only full
|
|
26014
|
-
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must
|
|
26104
|
+
* - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
|
|
26105
|
+
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must be added to the whitelist before you can associate it.
|
|
26015
26106
|
* - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
|
|
26016
26107
|
* - If a single VBR is associated with multiple Express Connect circuits, you must associate all Express Connect circuits of the VBR at the same time.
|
|
26017
26108
|
*
|
|
@@ -27894,13 +27985,13 @@ export default class Client extends OpenApi {
|
|
|
27894
27985
|
}
|
|
27895
27986
|
|
|
27896
27987
|
/**
|
|
27897
|
-
* Modifies the
|
|
27988
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
27898
27989
|
*
|
|
27899
27990
|
* @remarks
|
|
27900
27991
|
* When you call this operation, note the following items:
|
|
27901
27992
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
27902
27993
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
27903
|
-
* -
|
|
27994
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
27904
27995
|
*
|
|
27905
27996
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
27906
27997
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -27995,13 +28086,13 @@ export default class Client extends OpenApi {
|
|
|
27995
28086
|
}
|
|
27996
28087
|
|
|
27997
28088
|
/**
|
|
27998
|
-
* Modifies the
|
|
28089
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
27999
28090
|
*
|
|
28000
28091
|
* @remarks
|
|
28001
28092
|
* When you call this operation, note the following items:
|
|
28002
28093
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
28003
28094
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
28004
|
-
* -
|
|
28095
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
28005
28096
|
*
|
|
28006
28097
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
28007
28098
|
* @returns ModifyPhysicalConnectionAttributeResponse
|
|
@@ -28552,15 +28643,15 @@ export default class Client extends OpenApi {
|
|
|
28552
28643
|
}
|
|
28553
28644
|
|
|
28554
28645
|
/**
|
|
28555
|
-
* Modifies the configuration of an SSL-VPN server.
|
|
28646
|
+
* Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
|
|
28556
28647
|
*
|
|
28557
28648
|
* @remarks
|
|
28558
|
-
* - If you want to enable two-factor
|
|
28559
|
-
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify
|
|
28560
|
-
* - When **ModifySslVpnServer** is asynchronous, the system returns a request ID
|
|
28649
|
+
* - If you want to enable two-factor authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
|
|
28650
|
+
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify configurations other than **Name**, this operation is asynchronous.
|
|
28651
|
+
* - When the **ModifySslVpnServer** operation is asynchronous, the system returns a request ID but the configuration of the SSL-VPN server has not been modified. The modification task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
|
|
28561
28652
|
* - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
|
|
28562
28653
|
* - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
|
|
28563
|
-
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the
|
|
28654
|
+
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
|
|
28564
28655
|
*
|
|
28565
28656
|
* @param request - ModifySslVpnServerRequest
|
|
28566
28657
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -28667,15 +28758,15 @@ export default class Client extends OpenApi {
|
|
|
28667
28758
|
}
|
|
28668
28759
|
|
|
28669
28760
|
/**
|
|
28670
|
-
* Modifies the configuration of an SSL-VPN server.
|
|
28761
|
+
* Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
|
|
28671
28762
|
*
|
|
28672
28763
|
* @remarks
|
|
28673
|
-
* - If you want to enable two-factor
|
|
28674
|
-
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify
|
|
28675
|
-
* - When **ModifySslVpnServer** is asynchronous, the system returns a request ID
|
|
28764
|
+
* - If you want to enable two-factor authentication for the SSL server, make sure that the VPN gateway instance supports this feature. You may need to upgrade the VPN gateway instance. For more information, see [SSL-VPN two-factor authentication supports IDaaS EIAM 2.0](https://help.aliyun.com/document_detail/2785320.html).
|
|
28765
|
+
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify configurations other than **Name**, this operation is asynchronous.
|
|
28766
|
+
* - When the **ModifySslVpnServer** operation is asynchronous, the system returns a request ID but the configuration of the SSL-VPN server has not been modified. The modification task is still running in the background. You can call the [DescribeVpnGateway](https://help.aliyun.com/document_detail/2794055.html) operation to query the status of the VPN gateway instance associated with the SSL-VPN server to check the modification status:
|
|
28676
28767
|
* - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
|
|
28677
28768
|
* - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
|
|
28678
|
-
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the
|
|
28769
|
+
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
|
|
28679
28770
|
*
|
|
28680
28771
|
* @param request - ModifySslVpnServerRequest
|
|
28681
28772
|
* @returns ModifySslVpnServerResponse
|
|
@@ -29019,7 +29110,7 @@ export default class Client extends OpenApi {
|
|
|
29019
29110
|
* @remarks
|
|
29020
29111
|
* - **ModifyVcoRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID, but the weight of the destination route entry has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the destination route entry weight:
|
|
29021
29112
|
* - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
|
|
29022
|
-
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry
|
|
29113
|
+
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
|
|
29023
29114
|
* - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
|
|
29024
29115
|
*
|
|
29025
29116
|
* @param request - ModifyVcoRouteEntryWeightRequest
|
|
@@ -29096,7 +29187,7 @@ export default class Client extends OpenApi {
|
|
|
29096
29187
|
* @remarks
|
|
29097
29188
|
* - **ModifyVcoRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID, but the weight of the destination route entry has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the destination route entry weight:
|
|
29098
29189
|
* - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
|
|
29099
|
-
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry
|
|
29190
|
+
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
|
|
29100
29191
|
* - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
|
|
29101
29192
|
*
|
|
29102
29193
|
* @param request - ModifyVcoRouteEntryWeightRequest
|
|
@@ -29359,6 +29450,68 @@ export default class Client extends OpenApi {
|
|
|
29359
29450
|
return await this.modifyVpcAttributeWithOptions(request, runtime);
|
|
29360
29451
|
}
|
|
29361
29452
|
|
|
29453
|
+
/**
|
|
29454
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
29455
|
+
*
|
|
29456
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
29457
|
+
* @param runtime - runtime options for this request RuntimeOptions
|
|
29458
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
29459
|
+
*/
|
|
29460
|
+
async modifyVpcCidrBlockWithOptions(request: $_model.ModifyVpcCidrBlockRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyVpcCidrBlockResponse> {
|
|
29461
|
+
request.validate();
|
|
29462
|
+
let query = { };
|
|
29463
|
+
if (!$dara.isNull(request.clientToken)) {
|
|
29464
|
+
query["ClientToken"] = request.clientToken;
|
|
29465
|
+
}
|
|
29466
|
+
|
|
29467
|
+
if (!$dara.isNull(request.dryRun)) {
|
|
29468
|
+
query["DryRun"] = request.dryRun;
|
|
29469
|
+
}
|
|
29470
|
+
|
|
29471
|
+
if (!$dara.isNull(request.originalCidrBlock)) {
|
|
29472
|
+
query["OriginalCidrBlock"] = request.originalCidrBlock;
|
|
29473
|
+
}
|
|
29474
|
+
|
|
29475
|
+
if (!$dara.isNull(request.regionId)) {
|
|
29476
|
+
query["RegionId"] = request.regionId;
|
|
29477
|
+
}
|
|
29478
|
+
|
|
29479
|
+
if (!$dara.isNull(request.targetCidrBlock)) {
|
|
29480
|
+
query["TargetCidrBlock"] = request.targetCidrBlock;
|
|
29481
|
+
}
|
|
29482
|
+
|
|
29483
|
+
if (!$dara.isNull(request.vpcId)) {
|
|
29484
|
+
query["VpcId"] = request.vpcId;
|
|
29485
|
+
}
|
|
29486
|
+
|
|
29487
|
+
let req = new $OpenApiUtil.OpenApiRequest({
|
|
29488
|
+
query: OpenApiUtil.query(query),
|
|
29489
|
+
});
|
|
29490
|
+
let params = new $OpenApiUtil.Params({
|
|
29491
|
+
action: "ModifyVpcCidrBlock",
|
|
29492
|
+
version: "2016-04-28",
|
|
29493
|
+
protocol: "HTTPS",
|
|
29494
|
+
pathname: "/",
|
|
29495
|
+
method: "POST",
|
|
29496
|
+
authType: "AK",
|
|
29497
|
+
style: "RPC",
|
|
29498
|
+
reqBodyType: "formData",
|
|
29499
|
+
bodyType: "json",
|
|
29500
|
+
});
|
|
29501
|
+
return $dara.cast<$_model.ModifyVpcCidrBlockResponse>(await this.callApi(params, req, runtime), new $_model.ModifyVpcCidrBlockResponse({}));
|
|
29502
|
+
}
|
|
29503
|
+
|
|
29504
|
+
/**
|
|
29505
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
29506
|
+
*
|
|
29507
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
29508
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
29509
|
+
*/
|
|
29510
|
+
async modifyVpcCidrBlock(request: $_model.ModifyVpcCidrBlockRequest): Promise<$_model.ModifyVpcCidrBlockResponse> {
|
|
29511
|
+
let runtime = new $dara.RuntimeOptions({ });
|
|
29512
|
+
return await this.modifyVpcCidrBlockWithOptions(request, runtime);
|
|
29513
|
+
}
|
|
29514
|
+
|
|
29362
29515
|
/**
|
|
29363
29516
|
* Modifies the configuration of a prefix list.
|
|
29364
29517
|
*
|
|
@@ -29467,13 +29620,13 @@ export default class Client extends OpenApi {
|
|
|
29467
29620
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
29468
29621
|
*
|
|
29469
29622
|
* @remarks
|
|
29470
|
-
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
29471
|
-
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
29472
|
-
* - **ModifyVpnAttachmentAttribute** is
|
|
29623
|
+
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
29624
|
+
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
|
|
29625
|
+
* - The **ModifyVpnAttachmentAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the IPsec-VPN connection configuration has not been modified. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection configuration:
|
|
29473
29626
|
* - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
|
|
29474
29627
|
* - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
|
|
29475
|
-
* - **ModifyVpnAttachmentAttribute** does not support concurrent
|
|
29476
|
-
* - When you call **ModifyVpnAttachmentAttribute
|
|
29628
|
+
* - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
|
|
29629
|
+
* - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
|
|
29477
29630
|
*
|
|
29478
29631
|
* @param request - ModifyVpnAttachmentAttributeRequest
|
|
29479
29632
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -29598,13 +29751,13 @@ export default class Client extends OpenApi {
|
|
|
29598
29751
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
29599
29752
|
*
|
|
29600
29753
|
* @remarks
|
|
29601
|
-
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
29602
|
-
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
29603
|
-
* - **ModifyVpnAttachmentAttribute** is
|
|
29754
|
+
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, the **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
29755
|
+
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters, the following request parameters are supported: **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **CustomerGatewayId**.
|
|
29756
|
+
* - The **ModifyVpnAttachmentAttribute** operation is asynchronous. After a request is sent, the system returns a request ID. However, the IPsec-VPN connection configuration has not been modified. The modification task is still running in the background. You can call [DescribeVpnConnection](https://help.aliyun.com/document_detail/53046.html) to query the modification status of the IPsec-VPN connection configuration:
|
|
29604
29757
|
* - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
|
|
29605
29758
|
* - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
|
|
29606
|
-
* - **ModifyVpnAttachmentAttribute** does not support concurrent
|
|
29607
|
-
* - When you call **ModifyVpnAttachmentAttribute
|
|
29759
|
+
* - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
|
|
29760
|
+
* - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
|
|
29608
29761
|
*
|
|
29609
29762
|
* @param request - ModifyVpnAttachmentAttributeRequest
|
|
29610
29763
|
* @returns ModifyVpnAttachmentAttributeResponse
|
|
@@ -29618,14 +29771,11 @@ export default class Client extends OpenApi {
|
|
|
29618
29771
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
29619
29772
|
*
|
|
29620
29773
|
* @remarks
|
|
29621
|
-
* - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29774
|
+
* - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29622
29775
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
29623
|
-
* - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29776
|
+
* - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29624
29777
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
|
|
29625
|
-
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID
|
|
29626
|
-
* - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
|
|
29627
|
-
* - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
|
|
29628
|
-
* - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
|
|
29778
|
+
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID, but the configuration of the IPsec-VPN connection has not been modified yet. The modification node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
|
|
29629
29779
|
*
|
|
29630
29780
|
* @param request - ModifyVpnConnectionAttributeRequest
|
|
29631
29781
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -29746,14 +29896,11 @@ export default class Client extends OpenApi {
|
|
|
29746
29896
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
29747
29897
|
*
|
|
29748
29898
|
* @remarks
|
|
29749
|
-
* - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29899
|
+
* - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29750
29900
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
29751
|
-
* - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29901
|
+
* - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
29752
29902
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
|
|
29753
|
-
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID
|
|
29754
|
-
* - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
|
|
29755
|
-
* - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
|
|
29756
|
-
* - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
|
|
29903
|
+
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID, but the configuration of the IPsec-VPN connection has not been modified yet. The modification node is still running in the background. You can invoke [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the instance status of the VPN gateway to determine the modification status of the IPsec-VPN connection configuration:
|
|
29757
29904
|
*
|
|
29758
29905
|
* @param request - ModifyVpnConnectionAttributeRequest
|
|
29759
29906
|
* @returns ModifyVpnConnectionAttributeResponse
|
|
@@ -29767,7 +29914,7 @@ export default class Client extends OpenApi {
|
|
|
29767
29914
|
* Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
|
|
29768
29915
|
*
|
|
29769
29916
|
* @remarks
|
|
29770
|
-
* - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
|
|
29917
|
+
* - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration of the VPN gateway has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
|
|
29771
29918
|
* - If the VPN gateway is in the **updating** state, the configuration is being modified.
|
|
29772
29919
|
* - If the VPN gateway is in the **active** state, the configuration has been modified.
|
|
29773
29920
|
* - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
|
|
@@ -29840,7 +29987,7 @@ export default class Client extends OpenApi {
|
|
|
29840
29987
|
* Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
|
|
29841
29988
|
*
|
|
29842
29989
|
* @remarks
|
|
29843
|
-
* - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
|
|
29990
|
+
* - **ModifyVpnGatewayAttribute** is an asynchronous operation. After you call this operation, the system returns the VPN gateway information, but the configuration of the VPN gateway has not been modified yet. The modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the VPN gateway configuration:
|
|
29844
29991
|
* - If the VPN gateway is in the **updating** state, the configuration is being modified.
|
|
29845
29992
|
* - If the VPN gateway is in the **active** state, the configuration has been modified.
|
|
29846
29993
|
* - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
|
|
@@ -29970,13 +30117,13 @@ export default class Client extends OpenApi {
|
|
|
29970
30117
|
}
|
|
29971
30118
|
|
|
29972
30119
|
/**
|
|
29973
|
-
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing
|
|
30120
|
+
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
|
|
29974
30121
|
*
|
|
29975
30122
|
* @remarks
|
|
29976
|
-
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID,
|
|
29977
|
-
* - If the VPN gateway instance is in the **updating** state, the policy-based routing
|
|
29978
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based routing
|
|
29979
|
-
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing
|
|
30123
|
+
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID. However, the policy-based routing has not been modified yet because the modification node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway and determine the modification status of the policy-based routing:
|
|
30124
|
+
* - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
|
|
30125
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
|
|
30126
|
+
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
|
|
29980
30127
|
*
|
|
29981
30128
|
* @param request - ModifyVpnPbrRouteEntryPriorityRequest
|
|
29982
30129
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -30055,13 +30202,13 @@ export default class Client extends OpenApi {
|
|
|
30055
30202
|
}
|
|
30056
30203
|
|
|
30057
30204
|
/**
|
|
30058
|
-
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing
|
|
30205
|
+
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
|
|
30059
30206
|
*
|
|
30060
30207
|
* @remarks
|
|
30061
|
-
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID,
|
|
30062
|
-
* - If the VPN gateway instance is in the **updating** state, the policy-based routing
|
|
30063
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based routing
|
|
30064
|
-
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing
|
|
30208
|
+
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID. However, the policy-based routing has not been modified yet because the modification node is still running in the background. You can invoke the [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) operation to query the instance status of the VPN gateway and determine the modification status of the policy-based routing:
|
|
30209
|
+
* - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
|
|
30210
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
|
|
30211
|
+
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
|
|
30065
30212
|
*
|
|
30066
30213
|
* @param request - ModifyVpnPbrRouteEntryPriorityRequest
|
|
30067
30214
|
* @returns ModifyVpnPbrRouteEntryPriorityResponse
|
|
@@ -30185,12 +30332,12 @@ export default class Client extends OpenApi {
|
|
|
30185
30332
|
* Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
|
|
30186
30333
|
*
|
|
30187
30334
|
* @remarks
|
|
30188
|
-
* > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if
|
|
30335
|
+
* > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if it is modified by calling this operation.
|
|
30189
30336
|
* - If active/standby destination routes exist on a VPN gateway instance and you want to modify the weight of the active destination route, delete the standby destination route first. After the active destination route is modified, reconfigure the standby destination route. If you want to modify the weight of the standby destination route, delete the active destination route first. After the standby destination route is modified, reconfigure the active destination route. To delete a destination route, see [DeleteVpnRouteEntry](https://help.aliyun.com/document_detail/2526961.html).
|
|
30190
|
-
* -
|
|
30337
|
+
* - **ModifyVpnRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
|
|
30191
30338
|
* - If the VPN destination route is in the **updating** state, the weight is being modified.
|
|
30192
|
-
* - If the VPN destination route is in the **active** state, the weight
|
|
30193
|
-
* -
|
|
30339
|
+
* - If the VPN destination route is in the **active** state, the weight has been modified.
|
|
30340
|
+
* - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
|
|
30194
30341
|
*
|
|
30195
30342
|
* @param request - ModifyVpnRouteEntryWeightRequest
|
|
30196
30343
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -30268,12 +30415,12 @@ export default class Client extends OpenApi {
|
|
|
30268
30415
|
* Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
|
|
30269
30416
|
*
|
|
30270
30417
|
* @remarks
|
|
30271
|
-
* > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if
|
|
30418
|
+
* > This operation is applicable only to VPN gateway instances that support IPsec-VPN connections in single-tunnel mode. For VPN gateway instances that support IPsec-VPN connections in dual-tunnel mode, the weight does not take effect even if it is modified by calling this operation.
|
|
30272
30419
|
* - If active/standby destination routes exist on a VPN gateway instance and you want to modify the weight of the active destination route, delete the standby destination route first. After the active destination route is modified, reconfigure the standby destination route. If you want to modify the weight of the standby destination route, delete the active destination route first. After the standby destination route is modified, reconfigure the active destination route. To delete a destination route, see [DeleteVpnRouteEntry](https://help.aliyun.com/document_detail/2526961.html).
|
|
30273
|
-
* -
|
|
30420
|
+
* - **ModifyVpnRouteEntryWeight** is an asynchronous operation. After a request is sent, the system returns a request ID. However, the weight of the VPN destination route has not been modified yet because the modification task is still running in the background. You can call [DescribeVpnGateway](https://help.aliyun.com/document_detail/73720.html) to query the modification status of the weight:
|
|
30274
30421
|
* - If the VPN destination route is in the **updating** state, the weight is being modified.
|
|
30275
|
-
* - If the VPN destination route is in the **active** state, the weight
|
|
30276
|
-
* -
|
|
30422
|
+
* - If the VPN destination route is in the **active** state, the weight has been modified.
|
|
30423
|
+
* - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
|
|
30277
30424
|
*
|
|
30278
30425
|
* @param request - ModifyVpnRouteEntryWeightRequest
|
|
30279
30426
|
* @returns ModifyVpnRouteEntryWeightResponse
|
|
@@ -30287,7 +30434,7 @@ export default class Client extends OpenApi {
|
|
|
30287
30434
|
* Modifies the resource group to which a cloud resource belongs.
|
|
30288
30435
|
*
|
|
30289
30436
|
* @remarks
|
|
30290
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
30437
|
+
* The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
|
|
30291
30438
|
*
|
|
30292
30439
|
* @param request - MoveResourceGroupRequest
|
|
30293
30440
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -30349,7 +30496,7 @@ export default class Client extends OpenApi {
|
|
|
30349
30496
|
* Modifies the resource group to which a cloud resource belongs.
|
|
30350
30497
|
*
|
|
30351
30498
|
* @remarks
|
|
30352
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
30499
|
+
* The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
|
|
30353
30500
|
*
|
|
30354
30501
|
* @param request - MoveResourceGroupRequest
|
|
30355
30502
|
* @returns MoveResourceGroupResponse
|
|
@@ -31010,16 +31157,16 @@ export default class Client extends OpenApi {
|
|
|
31010
31157
|
}
|
|
31011
31158
|
|
|
31012
31159
|
/**
|
|
31013
|
-
* Releases a specified
|
|
31160
|
+
* Releases a specified elastic IP address (EIP).
|
|
31014
31161
|
*
|
|
31015
31162
|
* @remarks
|
|
31016
|
-
* Before you invoke this operation, take note of the following
|
|
31017
|
-
* - Before
|
|
31163
|
+
* Before you invoke this operation, take note of the following information:
|
|
31164
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
31018
31165
|
* - Only EIPs in the **Available** state can be released.
|
|
31019
31166
|
* - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
|
|
31020
|
-
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
31021
|
-
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
|
|
31022
|
-
* - If the EIP instance cannot be found, the EIP instance
|
|
31167
|
+
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP instance is not immediately released because the release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
|
|
31168
|
+
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations and cannot execute other operations.
|
|
31169
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
31023
31170
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
31024
31171
|
*
|
|
31025
31172
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -31071,16 +31218,16 @@ export default class Client extends OpenApi {
|
|
|
31071
31218
|
}
|
|
31072
31219
|
|
|
31073
31220
|
/**
|
|
31074
|
-
* Releases a specified
|
|
31221
|
+
* Releases a specified elastic IP address (EIP).
|
|
31075
31222
|
*
|
|
31076
31223
|
* @remarks
|
|
31077
|
-
* Before you invoke this operation, take note of the following
|
|
31078
|
-
* - Before
|
|
31224
|
+
* Before you invoke this operation, take note of the following information:
|
|
31225
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
31079
31226
|
* - Only EIPs in the **Available** state can be released.
|
|
31080
31227
|
* - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
|
|
31081
|
-
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
31082
|
-
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
|
|
31083
|
-
* - If the EIP instance cannot be found, the EIP instance
|
|
31228
|
+
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID. However, the EIP instance is not immediately released because the release node is still running in the background. You can invoke [DescribeEipAddresses](https://help.aliyun.com/document_detail/120193.html) to query the status of the EIP instance:
|
|
31229
|
+
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations and cannot execute other operations.
|
|
31230
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
31084
31231
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
31085
31232
|
*
|
|
31086
31233
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -33234,10 +33381,10 @@ export default class Client extends OpenApi {
|
|
|
33234
33381
|
}
|
|
33235
33382
|
|
|
33236
33383
|
/**
|
|
33237
|
-
*
|
|
33384
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
33238
33385
|
*
|
|
33239
33386
|
* @remarks
|
|
33240
|
-
* - Before
|
|
33387
|
+
* - Before deleting a secondary CIDR block from a VPC, delete the vSwitches that are created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
|
|
33241
33388
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
33242
33389
|
*
|
|
33243
33390
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -33301,10 +33448,10 @@ export default class Client extends OpenApi {
|
|
|
33301
33448
|
}
|
|
33302
33449
|
|
|
33303
33450
|
/**
|
|
33304
|
-
*
|
|
33451
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
33305
33452
|
*
|
|
33306
33453
|
* @remarks
|
|
33307
|
-
* - Before
|
|
33454
|
+
* - Before deleting a secondary CIDR block from a VPC, delete the vSwitches that are created with the secondary CIDR block. For more information, see [DeleteVSwitch](https://help.aliyun.com/document_detail/35746.html).
|
|
33308
33455
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
33309
33456
|
*
|
|
33310
33457
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -33390,7 +33537,7 @@ export default class Client extends OpenApi {
|
|
|
33390
33537
|
}
|
|
33391
33538
|
|
|
33392
33539
|
/**
|
|
33393
|
-
* Modifies the configuration of a DHCP options set
|
|
33540
|
+
* Modifies the configuration of a DHCP options set.
|
|
33394
33541
|
*
|
|
33395
33542
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
33396
33543
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -33473,7 +33620,7 @@ export default class Client extends OpenApi {
|
|
|
33473
33620
|
}
|
|
33474
33621
|
|
|
33475
33622
|
/**
|
|
33476
|
-
* Modifies the configuration of a DHCP options set
|
|
33623
|
+
* Modifies the configuration of a DHCP options set.
|
|
33477
33624
|
*
|
|
33478
33625
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
33479
33626
|
* @returns UpdateDhcpOptionsSetAttributeResponse
|
|
@@ -33764,7 +33911,7 @@ export default class Client extends OpenApi {
|
|
|
33764
33911
|
}
|
|
33765
33912
|
|
|
33766
33913
|
/**
|
|
33767
|
-
*
|
|
33914
|
+
* Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
|
|
33768
33915
|
*
|
|
33769
33916
|
* @remarks
|
|
33770
33917
|
* - If you modify only the **IpsecServerName** of the IPsec server, this operation is synchronous. If you modify configurations other than **IpsecServerName**, this operation is asynchronous.
|
|
@@ -33846,7 +33993,7 @@ export default class Client extends OpenApi {
|
|
|
33846
33993
|
}
|
|
33847
33994
|
|
|
33848
33995
|
/**
|
|
33849
|
-
*
|
|
33996
|
+
* Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
|
|
33850
33997
|
*
|
|
33851
33998
|
* @remarks
|
|
33852
33999
|
* - If you modify only the **IpsecServerName** of the IPsec server, this operation is synchronous. If you modify configurations other than **IpsecServerName**, this operation is asynchronous.
|