@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/dist/client.d.ts
CHANGED
|
@@ -12,7 +12,8 @@ export default class Client extends OpenApi {
|
|
|
12
12
|
* Activates a router interface that is in the Inactive state.
|
|
13
13
|
*
|
|
14
14
|
* @remarks
|
|
15
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the
|
|
15
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
|
|
16
|
+
* 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.
|
|
16
17
|
* > You cannot activate a router interface that has an overdue payment.
|
|
17
18
|
*
|
|
18
19
|
* @param request - ActivateRouterInterfaceRequest
|
|
@@ -24,7 +25,8 @@ export default class Client extends OpenApi {
|
|
|
24
25
|
* Activates a router interface that is in the Inactive state.
|
|
25
26
|
*
|
|
26
27
|
* @remarks
|
|
27
|
-
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the
|
|
28
|
+
* After you call the ActivateRouterInterface operation, the router interface enters the **Activating** state. After the activation succeeds, the router interface enters the **Active** state.
|
|
29
|
+
* 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.
|
|
28
30
|
* > You cannot activate a router interface that has an overdue payment.
|
|
29
31
|
*
|
|
30
32
|
* @param request - ActivateRouterInterfaceRequest
|
|
@@ -241,8 +243,8 @@ export default class Client extends OpenApi {
|
|
|
241
243
|
* Applies for an elastic IP address (EIP).
|
|
242
244
|
*
|
|
243
245
|
* @remarks
|
|
244
|
-
*
|
|
245
|
-
* 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.
|
|
246
|
+
* 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).
|
|
247
|
+
* 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.
|
|
246
248
|
*
|
|
247
249
|
* @param request - AllocateEipAddressRequest
|
|
248
250
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -253,8 +255,8 @@ export default class Client extends OpenApi {
|
|
|
253
255
|
* Applies for an elastic IP address (EIP).
|
|
254
256
|
*
|
|
255
257
|
* @remarks
|
|
256
|
-
*
|
|
257
|
-
* 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.
|
|
258
|
+
* 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).
|
|
259
|
+
* 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.
|
|
258
260
|
*
|
|
259
261
|
* @param request - AllocateEipAddressRequest
|
|
260
262
|
* @returns AllocateEipAddressResponse
|
|
@@ -506,7 +508,7 @@ export default class Client extends OpenApi {
|
|
|
506
508
|
*/
|
|
507
509
|
associateHaVip(request: $_model.AssociateHaVipRequest): Promise<$_model.AssociateHaVipResponse>;
|
|
508
510
|
/**
|
|
509
|
-
* 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
|
|
511
|
+
* 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.
|
|
510
512
|
*
|
|
511
513
|
* @remarks
|
|
512
514
|
* To use this feature, the following conditions must be met:
|
|
@@ -515,7 +517,7 @@ export default class Client extends OpenApi {
|
|
|
515
517
|
* - Only dedicated Express Connect circuits are supported.
|
|
516
518
|
* Other notes:
|
|
517
519
|
* - A maximum of three CKN and CAK pairs can be configured.
|
|
518
|
-
* - Associating a key that is currently in the Disassociated state
|
|
520
|
+
* - Associating a key that is currently in the Disassociated state disassociates the previously active key.
|
|
519
521
|
* - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
|
|
520
522
|
*
|
|
521
523
|
* @param request - AssociateMacSecKeyRequest
|
|
@@ -524,7 +526,7 @@ export default class Client extends OpenApi {
|
|
|
524
526
|
*/
|
|
525
527
|
associateMacSecKeyWithOptions(request: $_model.AssociateMacSecKeyRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AssociateMacSecKeyResponse>;
|
|
526
528
|
/**
|
|
527
|
-
* 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
|
|
529
|
+
* 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.
|
|
528
530
|
*
|
|
529
531
|
* @remarks
|
|
530
532
|
* To use this feature, the following conditions must be met:
|
|
@@ -533,7 +535,7 @@ export default class Client extends OpenApi {
|
|
|
533
535
|
* - Only dedicated Express Connect circuits are supported.
|
|
534
536
|
* Other notes:
|
|
535
537
|
* - A maximum of three CKN and CAK pairs can be configured.
|
|
536
|
-
* - Associating a key that is currently in the Disassociated state
|
|
538
|
+
* - Associating a key that is currently in the Disassociated state disassociates the previously active key.
|
|
537
539
|
* - Associating a key that is currently in the AssociatedFailed state triggers the device to renegotiate the session.
|
|
538
540
|
*
|
|
539
541
|
* @param request - AssociateMacSecKeyRequest
|
|
@@ -694,18 +696,18 @@ export default class Client extends OpenApi {
|
|
|
694
696
|
* Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
|
|
695
697
|
*
|
|
696
698
|
* @remarks
|
|
697
|
-
* Before you
|
|
698
|
-
* - Only
|
|
699
|
-
* - The SSL certificates must use
|
|
699
|
+
* Before you associate a VPN gateway with an SSL certificate, take note of the following information:
|
|
700
|
+
* - 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.
|
|
701
|
+
* - The SSL certificates must use SM algorithms.
|
|
700
702
|
* - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
|
|
701
703
|
* <props="china">
|
|
702
|
-
* - 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).
|
|
703
|
-
* - 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
|
|
704
|
+
* - 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).
|
|
705
|
+
* - 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:
|
|
704
706
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
|
|
705
707
|
* - If the VPN gateway is in the **active** state, the SSL certificate is attached.
|
|
706
|
-
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate
|
|
708
|
+
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
|
|
707
709
|
* ### Before you begin
|
|
708
|
-
* Make sure that you have two SSL certificates that use
|
|
710
|
+
* 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).
|
|
709
711
|
*
|
|
710
712
|
* @param request - AssociateVpnGatewayWithCertificateRequest
|
|
711
713
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -716,18 +718,18 @@ export default class Client extends OpenApi {
|
|
|
716
718
|
* Associates a certificate with a VPN gateway by calling the AssociateVpnGatewayWithCertificate operation.
|
|
717
719
|
*
|
|
718
720
|
* @remarks
|
|
719
|
-
* Before you
|
|
720
|
-
* - Only
|
|
721
|
-
* - The SSL certificates must use
|
|
721
|
+
* Before you associate a VPN gateway with an SSL certificate, take note of the following information:
|
|
722
|
+
* - 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.
|
|
723
|
+
* - The SSL certificates must use SM algorithms.
|
|
722
724
|
* - You cannot specify the same SSL certificate as both the encryption certificate and the signing certificate for the same VPN gateway instance.
|
|
723
725
|
* <props="china">
|
|
724
|
-
* - 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).
|
|
725
|
-
* - 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
|
|
726
|
+
* - 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).
|
|
727
|
+
* - 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:
|
|
726
728
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being attached.
|
|
727
729
|
* - If the VPN gateway is in the **active** state, the SSL certificate is attached.
|
|
728
|
-
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate
|
|
730
|
+
* - The **AssociateVpnGatewayWithCertificate** operation does not support concurrent SSL certificate binding requests for the same VPN gateway.
|
|
729
731
|
* ### Before you begin
|
|
730
|
-
* Make sure that you have two SSL certificates that use
|
|
732
|
+
* 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).
|
|
731
733
|
*
|
|
732
734
|
* @param request - AssociateVpnGatewayWithCertificateRequest
|
|
733
735
|
* @returns AssociateVpnGatewayWithCertificateResponse
|
|
@@ -761,7 +763,7 @@ export default class Client extends OpenApi {
|
|
|
761
763
|
*/
|
|
762
764
|
attachDhcpOptionsSetToVpc(request: $_model.AttachDhcpOptionsSetToVpcRequest): Promise<$_model.AttachDhcpOptionsSetToVpcResponse>;
|
|
763
765
|
/**
|
|
764
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
766
|
+
* 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.
|
|
765
767
|
*
|
|
766
768
|
* @param request - AttachVbrToVpconnRequest
|
|
767
769
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -769,7 +771,7 @@ export default class Client extends OpenApi {
|
|
|
769
771
|
*/
|
|
770
772
|
attachVbrToVpconnWithOptions(request: $_model.AttachVbrToVpconnRequest, runtime: $dara.RuntimeOptions): Promise<$_model.AttachVbrToVpconnResponse>;
|
|
771
773
|
/**
|
|
772
|
-
* Associates a Virtual Border Router (VBR) instance with shared Express Connect circuits.
|
|
774
|
+
* 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.
|
|
773
775
|
*
|
|
774
776
|
* @param request - AttachVbrToVpconnRequest
|
|
775
777
|
* @returns AttachVbrToVpconnResponse
|
|
@@ -801,10 +803,10 @@ export default class Client extends OpenApi {
|
|
|
801
803
|
*/
|
|
802
804
|
cancelCommonBandwidthPackageIpBandwidth(request: $_model.CancelCommonBandwidthPackageIpBandwidthRequest): Promise<$_model.CancelCommonBandwidthPackageIpBandwidthResponse>;
|
|
803
805
|
/**
|
|
804
|
-
* Cancels access
|
|
806
|
+
* Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
|
|
805
807
|
*
|
|
806
808
|
* @remarks
|
|
807
|
-
* You can cancel access
|
|
809
|
+
* 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**.
|
|
808
810
|
*
|
|
809
811
|
* @param request - CancelPhysicalConnectionRequest
|
|
810
812
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -812,10 +814,10 @@ export default class Client extends OpenApi {
|
|
|
812
814
|
*/
|
|
813
815
|
cancelPhysicalConnectionWithOptions(request: $_model.CancelPhysicalConnectionRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CancelPhysicalConnectionResponse>;
|
|
814
816
|
/**
|
|
815
|
-
* Cancels access
|
|
817
|
+
* Cancels the access of an Express Connect circuit. After the cancellation, the Express Connect circuit enters the Canceled state.
|
|
816
818
|
*
|
|
817
819
|
* @remarks
|
|
818
|
-
* You can cancel access
|
|
820
|
+
* 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**.
|
|
819
821
|
*
|
|
820
822
|
* @param request - CancelPhysicalConnectionRequest
|
|
821
823
|
* @returns CancelPhysicalConnectionResponse
|
|
@@ -864,7 +866,7 @@ export default class Client extends OpenApi {
|
|
|
864
866
|
*/
|
|
865
867
|
checkCanAllocateVpcPrivateIpAddress(request: $_model.CheckCanAllocateVpcPrivateIpAddressRequest): Promise<$_model.CheckCanAllocateVpcPrivateIpAddressResponse>;
|
|
866
868
|
/**
|
|
867
|
-
* Calls the CheckVpnBgpEnabled operation to query whether the region
|
|
869
|
+
* Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
|
|
868
870
|
*
|
|
869
871
|
* @param request - CheckVpnBgpEnabledRequest
|
|
870
872
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -872,14 +874,19 @@ export default class Client extends OpenApi {
|
|
|
872
874
|
*/
|
|
873
875
|
checkVpnBgpEnabledWithOptions(request: $_model.CheckVpnBgpEnabledRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CheckVpnBgpEnabledResponse>;
|
|
874
876
|
/**
|
|
875
|
-
* Calls the CheckVpnBgpEnabled operation to query whether the region
|
|
877
|
+
* Calls the CheckVpnBgpEnabled operation to query whether the region to which an IPsec-VPN connection belongs supports the BGP feature.
|
|
876
878
|
*
|
|
877
879
|
* @param request - CheckVpnBgpEnabledRequest
|
|
878
880
|
* @returns CheckVpnBgpEnabledResponse
|
|
879
881
|
*/
|
|
880
882
|
checkVpnBgpEnabled(request: $_model.CheckVpnBgpEnabledRequest): Promise<$_model.CheckVpnBgpEnabledResponse>;
|
|
881
883
|
/**
|
|
882
|
-
* Calls CompletePhysicalConnectionLOA to complete the construction.
|
|
884
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
885
|
+
*
|
|
886
|
+
* @remarks
|
|
887
|
+
* 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**.
|
|
888
|
+
* Complete call chain:
|
|
889
|
+
* 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).
|
|
883
890
|
*
|
|
884
891
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
885
892
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -887,7 +894,12 @@ export default class Client extends OpenApi {
|
|
|
887
894
|
*/
|
|
888
895
|
completePhysicalConnectionLOAWithOptions(request: $_model.CompletePhysicalConnectionLOARequest, runtime: $dara.RuntimeOptions): Promise<$_model.CompletePhysicalConnectionLOAResponse>;
|
|
889
896
|
/**
|
|
890
|
-
* Calls CompletePhysicalConnectionLOA to complete the construction.
|
|
897
|
+
* Calls CompletePhysicalConnectionLOA to complete the construction and backfill the completion information after the LOA is approved and the line construction is finished.
|
|
898
|
+
*
|
|
899
|
+
* @remarks
|
|
900
|
+
* 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**.
|
|
901
|
+
* Complete call chain:
|
|
902
|
+
* 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).
|
|
891
903
|
*
|
|
892
904
|
* @param request - CompletePhysicalConnectionLOARequest
|
|
893
905
|
* @returns CompletePhysicalConnectionLOAResponse
|
|
@@ -909,11 +921,11 @@ export default class Client extends OpenApi {
|
|
|
909
921
|
*/
|
|
910
922
|
confirmPhysicalConnection(request: $_model.ConfirmPhysicalConnectionRequest): Promise<$_model.ConfirmPhysicalConnectionResponse>;
|
|
911
923
|
/**
|
|
912
|
-
*
|
|
924
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
913
925
|
*
|
|
914
926
|
* @remarks
|
|
915
|
-
* After you
|
|
916
|
-
* When you
|
|
927
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
928
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
917
929
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
918
930
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
919
931
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -924,11 +936,11 @@ export default class Client extends OpenApi {
|
|
|
924
936
|
*/
|
|
925
937
|
connectRouterInterfaceWithOptions(request: $_model.ConnectRouterInterfaceRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ConnectRouterInterfaceResponse>;
|
|
926
938
|
/**
|
|
927
|
-
*
|
|
939
|
+
* Calls the ConnectRouterInterface operation to initiate a connection from the requester VPC router interface to the accepter.
|
|
928
940
|
*
|
|
929
941
|
* @remarks
|
|
930
|
-
* After you
|
|
931
|
-
* When you
|
|
942
|
+
* After you invoke this operation, the router interface enters the **Connecting** state and transitions to the **Active** state after the connection is established.
|
|
943
|
+
* When you invoke this operation to create a VPC, note the following items:
|
|
932
944
|
* - Only a requester VPC router interface in the **Idle** state can initiate a connection to the accepter VPC.
|
|
933
945
|
* - A maximum of one pair of interconnected router interfaces can exist between any two routers.
|
|
934
946
|
* - If your account has a router interface with an overdue payment, you cannot initiate a connection.
|
|
@@ -1275,18 +1287,28 @@ export default class Client extends OpenApi {
|
|
|
1275
1287
|
*/
|
|
1276
1288
|
createExpressConnectTrafficQosRule(request: $_model.CreateExpressConnectTrafficQosRuleRequest): Promise<$_model.CreateExpressConnectTrafficQosRuleResponse>;
|
|
1277
1289
|
/**
|
|
1278
|
-
*
|
|
1279
|
-
*
|
|
1280
|
-
* @remarks
|
|
1281
|
-
*
|
|
1282
|
-
* -
|
|
1290
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
1291
|
+
*
|
|
1292
|
+
* @remarks
|
|
1293
|
+
* Resource status requirements (prerequisites)
|
|
1294
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
1295
|
+
* - 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.
|
|
1296
|
+
* - 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.
|
|
1297
|
+
* - 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.
|
|
1298
|
+
* How to check and advance the Express Connect circuit status
|
|
1299
|
+
* - 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:
|
|
1300
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
1301
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
1302
|
+
* - 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.
|
|
1303
|
+
* The following scenarios do not support creating failover test jobs:
|
|
1304
|
+
* - 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.
|
|
1283
1305
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
1284
1306
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
1285
1307
|
*
|
|
1286
1308
|
* - The Express Connect circuit instance has more than one shared Express Connect circuit.
|
|
1287
|
-
* - The Express Connect circuit instance has more than one cross-account
|
|
1309
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
1288
1310
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
1289
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
1311
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
1290
1312
|
*
|
|
1291
1313
|
* @param request - CreateFailoverTestJobRequest
|
|
1292
1314
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -1294,18 +1316,28 @@ export default class Client extends OpenApi {
|
|
|
1294
1316
|
*/
|
|
1295
1317
|
createFailoverTestJobWithOptions(request: $_model.CreateFailoverTestJobRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateFailoverTestJobResponse>;
|
|
1296
1318
|
/**
|
|
1297
|
-
*
|
|
1298
|
-
*
|
|
1299
|
-
* @remarks
|
|
1300
|
-
*
|
|
1301
|
-
* -
|
|
1319
|
+
* Calls the CreateFailoverTestJob operation to create a failover test job for Express Connect.
|
|
1320
|
+
*
|
|
1321
|
+
* @remarks
|
|
1322
|
+
* Resource status requirements (prerequisites)
|
|
1323
|
+
* - Before creating a failover test job, ensure that the test resources and their associated resources are in the following states. Otherwise, the creation fails:
|
|
1324
|
+
* - 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.
|
|
1325
|
+
* - 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.
|
|
1326
|
+
* - 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.
|
|
1327
|
+
* How to check and advance the Express Connect circuit status
|
|
1328
|
+
* - 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:
|
|
1329
|
+
* - Allocated (port reserved, pending confirmation) → Call ConfirmPhysicalConnection to confirm → Confirmed → Call EnablePhysicalConnection to activate (asynchronous; poll DescribePhysicalConnections after activation to confirm) → Enabled.
|
|
1330
|
+
* - Note: EnablePhysicalConnection only supports activating Express Connect circuits in the Confirmed state. If the circuit is in the Allocated state, call ConfirmPhysicalConnection first.
|
|
1331
|
+
* - 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.
|
|
1332
|
+
* The following scenarios do not support creating failover test jobs:
|
|
1333
|
+
* - 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.
|
|
1302
1334
|
* - The Express Connect circuit instance or shared Express Connect circuit instance has not been paid for or has an overdue payment.
|
|
1303
1335
|
* - The Express Connect circuit instance or shared Express Connect circuit instance is already in another running failover test job.
|
|
1304
1336
|
*
|
|
1305
1337
|
* - The Express Connect circuit instance has more than one shared Express Connect circuit.
|
|
1306
|
-
* - The Express Connect circuit instance has more than one cross-account
|
|
1338
|
+
* - The Express Connect circuit instance has more than one cross-account VBR.
|
|
1307
1339
|
* - The shared Express Connect circuit instance is not associated with a VBR.
|
|
1308
|
-
* - The VLAN of the shared Express Connect circuit instance is
|
|
1340
|
+
* - The VLAN configuration of the shared Express Connect circuit instance is 0.
|
|
1309
1341
|
*
|
|
1310
1342
|
* @param request - CreateFailoverTestJobRequest
|
|
1311
1343
|
* @returns CreateFailoverTestJobResponse
|
|
@@ -2015,8 +2047,8 @@ export default class Client extends OpenApi {
|
|
|
2015
2047
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
2016
2048
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
2017
2049
|
* - **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.
|
|
2018
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
2019
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
2050
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
2051
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
2020
2052
|
*
|
|
2021
2053
|
* @param request - CreateRouteTargetGroupRequest
|
|
2022
2054
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2031,8 +2063,8 @@ export default class Client extends OpenApi {
|
|
|
2031
2063
|
* - If the routing target group is in the **Pending** state, the routing target group is being created.
|
|
2032
2064
|
* - If the routing target group is in the **Available**, **Unavailable**, **Switched**, or **Abnormal** state, the routing target group is created.
|
|
2033
2065
|
* - **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.
|
|
2034
|
-
* - **Primary instance**: The weight is 100. The primary instance
|
|
2035
|
-
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic
|
|
2066
|
+
* - **Primary instance**: The weight is 100. The primary instance carries all traffic under normal conditions and takes effect when health checks are successful.
|
|
2067
|
+
* - **Secondary instance**: The weight is 0. The secondary instance takes over traffic after the primary instance fails and serves as disaster recovery and backup.
|
|
2036
2068
|
*
|
|
2037
2069
|
* @param request - CreateRouteTargetGroupRequest
|
|
2038
2070
|
* @returns CreateRouteTargetGroupResponse
|
|
@@ -2135,7 +2167,7 @@ export default class Client extends OpenApi {
|
|
|
2135
2167
|
* Creates an SSL-VPN server.
|
|
2136
2168
|
*
|
|
2137
2169
|
* @remarks
|
|
2138
|
-
* - **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
|
|
2170
|
+
* - **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:
|
|
2139
2171
|
* - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
|
|
2140
2172
|
* - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
|
|
2141
2173
|
* - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
|
|
@@ -2152,7 +2184,7 @@ export default class Client extends OpenApi {
|
|
|
2152
2184
|
* Creates an SSL-VPN server.
|
|
2153
2185
|
*
|
|
2154
2186
|
* @remarks
|
|
2155
|
-
* - **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
|
|
2187
|
+
* - **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:
|
|
2156
2188
|
* - If the VPN gateway instance is in the **updating** state, the SSL-VPN server is being created.
|
|
2157
2189
|
* - If the VPN gateway instance is in the **active** state, the SSL-VPN server is created.
|
|
2158
2190
|
* - **CreateSslVpnServer** does not support concurrent creation of SSL-VPN servers under the same VPN gateway.
|
|
@@ -2245,18 +2277,18 @@ export default class Client extends OpenApi {
|
|
|
2245
2277
|
* Creates a vSwitch.
|
|
2246
2278
|
*
|
|
2247
2279
|
* @remarks
|
|
2248
|
-
*
|
|
2280
|
+
* When you call this operation to create a vSwitch, take note of the following items:
|
|
2249
2281
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
2250
|
-
* - 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.
|
|
2282
|
+
* - 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.
|
|
2251
2283
|
* - 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).
|
|
2252
2284
|
* - A cloud service instance can belong to only one vSwitch.
|
|
2253
2285
|
* - vSwitches do not support multicast or broadcast.
|
|
2254
2286
|
* - After a vSwitch is created, you cannot modify its CIDR block.
|
|
2255
|
-
* - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID
|
|
2256
|
-
* -
|
|
2257
|
-
* -
|
|
2287
|
+
* - 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:
|
|
2288
|
+
* - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
|
|
2289
|
+
* - When the vSwitch is in the **Available** state, the vSwitch is available.
|
|
2258
2290
|
* - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
|
|
2259
|
-
* -
|
|
2291
|
+
* - 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.
|
|
2260
2292
|
*
|
|
2261
2293
|
* @param request - CreateVSwitchRequest
|
|
2262
2294
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2267,18 +2299,18 @@ export default class Client extends OpenApi {
|
|
|
2267
2299
|
* Creates a vSwitch.
|
|
2268
2300
|
*
|
|
2269
2301
|
* @remarks
|
|
2270
|
-
*
|
|
2302
|
+
* When you call this operation to create a vSwitch, take note of the following items:
|
|
2271
2303
|
* - The number of vSwitches in each VPC cannot exceed 150.
|
|
2272
|
-
* - 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.
|
|
2304
|
+
* - 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.
|
|
2273
2305
|
* - 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).
|
|
2274
2306
|
* - A cloud service instance can belong to only one vSwitch.
|
|
2275
2307
|
* - vSwitches do not support multicast or broadcast.
|
|
2276
2308
|
* - After a vSwitch is created, you cannot modify its CIDR block.
|
|
2277
|
-
* - The **CreateVSwitch** operation is asynchronous. After you send a request, the system returns an instance ID
|
|
2278
|
-
* -
|
|
2279
|
-
* -
|
|
2309
|
+
* - 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:
|
|
2310
|
+
* - When the vSwitch is in the **Pending** state, the vSwitch is being configured.
|
|
2311
|
+
* - When the vSwitch is in the **Available** state, the vSwitch is available.
|
|
2280
2312
|
* - The **CreateVSwitch** operation does not support concurrent creation of vSwitches in the same VPC.
|
|
2281
|
-
* -
|
|
2313
|
+
* - 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.
|
|
2282
2314
|
*
|
|
2283
2315
|
* @param request - CreateVSwitchRequest
|
|
2284
2316
|
* @returns CreateVSwitchResponse
|
|
@@ -2293,7 +2325,7 @@ export default class Client extends OpenApi {
|
|
|
2293
2325
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
2294
2326
|
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
2295
2327
|
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
2296
|
-
* - 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
|
|
2328
|
+
* - 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:
|
|
2297
2329
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
2298
2330
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
2299
2331
|
*
|
|
@@ -2311,7 +2343,7 @@ export default class Client extends OpenApi {
|
|
|
2311
2343
|
* - A reserved CIDR block cannot contain the system reserved IP addresses of the vSwitch to which it belongs.
|
|
2312
2344
|
* - IPv4 CIDR block: The first and last three IP addresses of the vSwitch are system reserved IP addresses.
|
|
2313
2345
|
* - IPv6 CIDR block: The first and last nine IP addresses of the vSwitch are system reserved IP addresses.
|
|
2314
|
-
* - 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
|
|
2346
|
+
* - 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:
|
|
2315
2347
|
* - If the reserved CIDR block for a vSwitch is in the **Assigning** state, the reserved CIDR block for a vSwitch is being allocated.
|
|
2316
2348
|
* - If the reserved CIDR block for a vSwitch is in the **Assigned** state, the reserved CIDR block for a vSwitch has been allocated.
|
|
2317
2349
|
*
|
|
@@ -2320,7 +2352,7 @@ export default class Client extends OpenApi {
|
|
|
2320
2352
|
*/
|
|
2321
2353
|
createVSwitchCidrReservation(request: $_model.CreateVSwitchCidrReservationRequest): Promise<$_model.CreateVSwitchCidrReservationResponse>;
|
|
2322
2354
|
/**
|
|
2323
|
-
* Creates a VBR failover group
|
|
2355
|
+
* Creates a VBR failover group.
|
|
2324
2356
|
*
|
|
2325
2357
|
* @param request - CreateVbrHaRequest
|
|
2326
2358
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2328,7 +2360,7 @@ export default class Client extends OpenApi {
|
|
|
2328
2360
|
*/
|
|
2329
2361
|
createVbrHaWithOptions(request: $_model.CreateVbrHaRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVbrHaResponse>;
|
|
2330
2362
|
/**
|
|
2331
|
-
* Creates a VBR failover group
|
|
2363
|
+
* Creates a VBR failover group.
|
|
2332
2364
|
*
|
|
2333
2365
|
* @param request - CreateVbrHaRequest
|
|
2334
2366
|
* @returns CreateVbrHaResponse
|
|
@@ -2340,11 +2372,11 @@ export default class Client extends OpenApi {
|
|
|
2340
2372
|
* @remarks
|
|
2341
2373
|
* - 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).
|
|
2342
2374
|
* - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
|
|
2343
|
-
* - Do not add a destination route
|
|
2375
|
+
* - 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.
|
|
2344
2376
|
* - **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:
|
|
2345
2377
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
|
|
2346
2378
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
|
|
2347
|
-
* - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2379
|
+
* - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2348
2380
|
*
|
|
2349
2381
|
* @param request - CreateVcoRouteEntryRequest
|
|
2350
2382
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2357,11 +2389,11 @@ export default class Client extends OpenApi {
|
|
|
2357
2389
|
* @remarks
|
|
2358
2390
|
* - 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).
|
|
2359
2391
|
* - Adding a destination route with a destination CIDR block of 0.0.0.0/0 is not supported.
|
|
2360
|
-
* - Do not add a destination route
|
|
2392
|
+
* - 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.
|
|
2361
2393
|
* - **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:
|
|
2362
2394
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being created.
|
|
2363
2395
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is created.
|
|
2364
|
-
* - **CreateVcoRouteEntry** does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2396
|
+
* - The **CreateVcoRouteEntry** operation does not support concurrent creation of destination route entries for the same IPsec-VPN connection.
|
|
2365
2397
|
*
|
|
2366
2398
|
* @param request - CreateVcoRouteEntryRequest
|
|
2367
2399
|
* @returns CreateVcoRouteEntryResponse
|
|
@@ -2392,7 +2424,18 @@ export default class Client extends OpenApi {
|
|
|
2392
2424
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
2393
2425
|
*
|
|
2394
2426
|
* @remarks
|
|
2395
|
-
* Before
|
|
2427
|
+
* 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).
|
|
2428
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
2429
|
+
* - 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:
|
|
2430
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
2431
|
+
* - 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.
|
|
2432
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
2433
|
+
* - 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.
|
|
2434
|
+
* - 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).
|
|
2435
|
+
* - 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.
|
|
2436
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
2437
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
2438
|
+
* - 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.
|
|
2396
2439
|
*
|
|
2397
2440
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
2398
2441
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2403,7 +2446,18 @@ export default class Client extends OpenApi {
|
|
|
2403
2446
|
* Invokes the CreateVirtualPhysicalConnection operation to create shared Express Connect circuits.
|
|
2404
2447
|
*
|
|
2405
2448
|
* @remarks
|
|
2406
|
-
* Before
|
|
2449
|
+
* 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).
|
|
2450
|
+
* Before you call this operation, make sure the following conditions are met:
|
|
2451
|
+
* - 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:
|
|
2452
|
+
* - CreatePhysicalConnection: Creates an Express Connect circuit.
|
|
2453
|
+
* - 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.
|
|
2454
|
+
* - ConfirmPhysicalConnection: Reports construction completion. The circuit must be in the Allocated state. After success, it enters the Confirmed state.
|
|
2455
|
+
* - 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.
|
|
2456
|
+
* - 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).
|
|
2457
|
+
* - 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.
|
|
2458
|
+
* - VpconnAliUid is the tenant\\"s Alibaba Cloud account (RAM users or partner accounts are not supported). Cross-site pushing is not allowed by default.
|
|
2459
|
+
* - The number of shared Express Connect circuits on a single Express Connect circuit has not exceeded the quota.
|
|
2460
|
+
* - 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.
|
|
2407
2461
|
*
|
|
2408
2462
|
* @param request - CreateVirtualPhysicalConnectionRequest
|
|
2409
2463
|
* @returns CreateVirtualPhysicalConnectionResponse
|
|
@@ -2501,13 +2555,13 @@ export default class Client extends OpenApi {
|
|
|
2501
2555
|
*/
|
|
2502
2556
|
createVpcPrefixList(request: $_model.CreateVpcPrefixListRequest): Promise<$_model.CreateVpcPrefixListResponse>;
|
|
2503
2557
|
/**
|
|
2504
|
-
* Transforms the
|
|
2558
|
+
* Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
|
|
2505
2559
|
*
|
|
2506
2560
|
* @remarks
|
|
2507
|
-
* By invoking the CreateVpconnFromVbr operation, a partner can transform the
|
|
2508
|
-
* Before you execute the transform:
|
|
2561
|
+
* 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.
|
|
2562
|
+
* Before you execute the transform procedure:
|
|
2509
2563
|
* 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).
|
|
2510
|
-
* After the transform is complete:
|
|
2564
|
+
* After the transform procedure is complete:
|
|
2511
2565
|
* 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.
|
|
2512
2566
|
* 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.
|
|
2513
2567
|
*
|
|
@@ -2517,13 +2571,13 @@ export default class Client extends OpenApi {
|
|
|
2517
2571
|
*/
|
|
2518
2572
|
createVpconnFromVbrWithOptions(request: $_model.CreateVpconnFromVbrRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpconnFromVbrResponse>;
|
|
2519
2573
|
/**
|
|
2520
|
-
* Transforms the
|
|
2574
|
+
* Transforms the routing mode of shared Express Connect circuits from cross-account Virtual Border Router (VBR) push to cross-account shared port push.
|
|
2521
2575
|
*
|
|
2522
2576
|
* @remarks
|
|
2523
|
-
* By invoking the CreateVpconnFromVbr operation, a partner can transform the
|
|
2524
|
-
* Before you execute the transform:
|
|
2577
|
+
* 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.
|
|
2578
|
+
* Before you execute the transform procedure:
|
|
2525
2579
|
* 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).
|
|
2526
|
-
* After the transform is complete:
|
|
2580
|
+
* After the transform procedure is complete:
|
|
2527
2581
|
* 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.
|
|
2528
2582
|
* 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.
|
|
2529
2583
|
*
|
|
@@ -2532,16 +2586,11 @@ export default class Client extends OpenApi {
|
|
|
2532
2586
|
*/
|
|
2533
2587
|
createVpconnFromVbr(request: $_model.CreateVpconnFromVbrRequest): Promise<$_model.CreateVpconnFromVbrResponse>;
|
|
2534
2588
|
/**
|
|
2535
|
-
* Creates an IPsec-VPN connection
|
|
2589
|
+
* Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
|
|
2536
2590
|
*
|
|
2537
2591
|
* @remarks
|
|
2538
2592
|
* >Notice:
|
|
2539
|
-
*
|
|
2540
|
-
* - 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.
|
|
2541
|
-
* ### Before you begin
|
|
2542
|
-
* 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).
|
|
2543
|
-
*
|
|
2544
|
-
* 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.
|
|
2593
|
+
* ### Before you begin.
|
|
2545
2594
|
*
|
|
2546
2595
|
* @param request - CreateVpnAttachmentRequest
|
|
2547
2596
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2549,16 +2598,11 @@ export default class Client extends OpenApi {
|
|
|
2549
2598
|
*/
|
|
2550
2599
|
createVpnAttachmentWithOptions(request: $_model.CreateVpnAttachmentRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpnAttachmentResponse>;
|
|
2551
2600
|
/**
|
|
2552
|
-
* Creates an IPsec-VPN connection
|
|
2601
|
+
* Creates an IPsec-VPN connection to be associated with a transit router instance by calling the CreateVpnAttachment operation.
|
|
2553
2602
|
*
|
|
2554
2603
|
* @remarks
|
|
2555
2604
|
* >Notice:
|
|
2556
|
-
*
|
|
2557
|
-
* - 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.
|
|
2558
|
-
* ### Before you begin
|
|
2559
|
-
* 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).
|
|
2560
|
-
*
|
|
2561
|
-
* 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.
|
|
2605
|
+
* ### Before you begin.
|
|
2562
2606
|
*
|
|
2563
2607
|
* @param request - CreateVpnAttachmentRequest
|
|
2564
2608
|
* @returns CreateVpnAttachmentResponse
|
|
@@ -2571,11 +2615,8 @@ export default class Client extends OpenApi {
|
|
|
2571
2615
|
* - 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:
|
|
2572
2616
|
* **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
2573
2617
|
* 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).
|
|
2574
|
-
* - 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:
|
|
2575
2618
|
* **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
|
|
2576
|
-
* - 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
|
|
2577
|
-
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
|
|
2578
|
-
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
|
|
2619
|
+
* - 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.
|
|
2579
2620
|
* - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
|
|
2580
2621
|
*
|
|
2581
2622
|
* @param request - CreateVpnConnectionRequest
|
|
@@ -2590,11 +2631,8 @@ export default class Client extends OpenApi {
|
|
|
2590
2631
|
* - 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:
|
|
2591
2632
|
* **ClientToken**, **Name**, **EffectImmediately**, **AutoConfigRoute**, **Tags** array, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
2592
2633
|
* 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).
|
|
2593
|
-
* - 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:
|
|
2594
2634
|
* **ClientToken**, **CustomerGatewayId**, **Name**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, **RemoteCaCertificate**, and **Tags** array.
|
|
2595
|
-
* - 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
|
|
2596
|
-
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being created.
|
|
2597
|
-
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is created.
|
|
2635
|
+
* - 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.
|
|
2598
2636
|
* - The **CreateVpnConnection** operation does not support concurrent creation of IPsec-VPN connections under the same VPN gateway.
|
|
2599
2637
|
*
|
|
2600
2638
|
* @param request - CreateVpnConnectionRequest
|
|
@@ -2605,8 +2643,8 @@ export default class Client extends OpenApi {
|
|
|
2605
2643
|
* Creates a VPN gateway.
|
|
2606
2644
|
*
|
|
2607
2645
|
* @remarks
|
|
2608
|
-
* - 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).
|
|
2609
|
-
* - 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).
|
|
2646
|
+
* - 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).
|
|
2647
|
+
* - 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).
|
|
2610
2648
|
* - 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:
|
|
2611
2649
|
*
|
|
2612
2650
|
* - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
|
|
@@ -2621,8 +2659,8 @@ export default class Client extends OpenApi {
|
|
|
2621
2659
|
* Creates a VPN gateway.
|
|
2622
2660
|
*
|
|
2623
2661
|
* @remarks
|
|
2624
|
-
* - 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).
|
|
2625
|
-
* - 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).
|
|
2662
|
+
* - 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).
|
|
2663
|
+
* - 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).
|
|
2626
2664
|
* - 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:
|
|
2627
2665
|
*
|
|
2628
2666
|
* - If the VPN gateway is in the **provisioning** state, the VPN gateway is being created.
|
|
@@ -2633,18 +2671,18 @@ export default class Client extends OpenApi {
|
|
|
2633
2671
|
*/
|
|
2634
2672
|
createVpnGateway(request: $_model.CreateVpnGatewayRequest): Promise<$_model.CreateVpnGatewayResponse>;
|
|
2635
2673
|
/**
|
|
2636
|
-
* Creates a policy-based route
|
|
2674
|
+
* Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
|
|
2637
2675
|
*
|
|
2638
2676
|
* @remarks
|
|
2639
2677
|
* ### Before you begin
|
|
2640
|
-
* - Before
|
|
2641
|
-
* - Before
|
|
2678
|
+
* - 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).
|
|
2679
|
+
* - 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).
|
|
2642
2680
|
* ### Limits
|
|
2643
|
-
* -
|
|
2644
|
-
* - Do not add
|
|
2645
|
-
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you
|
|
2681
|
+
* - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
|
|
2682
|
+
* - 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.
|
|
2683
|
+
* - 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:
|
|
2646
2684
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
2647
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based route
|
|
2685
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
2648
2686
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
2649
2687
|
*
|
|
2650
2688
|
* @param request - CreateVpnPbrRouteEntryRequest
|
|
@@ -2653,18 +2691,18 @@ export default class Client extends OpenApi {
|
|
|
2653
2691
|
*/
|
|
2654
2692
|
createVpnPbrRouteEntryWithOptions(request: $_model.CreateVpnPbrRouteEntryRequest, runtime: $dara.RuntimeOptions): Promise<$_model.CreateVpnPbrRouteEntryResponse>;
|
|
2655
2693
|
/**
|
|
2656
|
-
* Creates a policy-based route
|
|
2694
|
+
* Creates a VPN policy-based route by calling the CreateVpnPbrRouteEntry operation.
|
|
2657
2695
|
*
|
|
2658
2696
|
* @remarks
|
|
2659
2697
|
* ### Before you begin
|
|
2660
|
-
* - Before
|
|
2661
|
-
* - Before
|
|
2698
|
+
* - 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).
|
|
2699
|
+
* - 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).
|
|
2662
2700
|
* ### Limits
|
|
2663
|
-
* -
|
|
2664
|
-
* - Do not add
|
|
2665
|
-
* - The **CreateVpnPbrRouteEntry** operation is asynchronous. After you
|
|
2701
|
+
* - Policy-based routes whose destination CIDR block is 0.0.0.0/0 are not supported.
|
|
2702
|
+
* - 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.
|
|
2703
|
+
* - 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:
|
|
2666
2704
|
* - If the VPN gateway instance is in the **updating** state, the policy-based route is being created.
|
|
2667
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based route
|
|
2705
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based route is created.
|
|
2668
2706
|
* - The **CreateVpnPbrRouteEntry** operation does not support concurrent creation of policy-based routes for the same VPN gateway instance.
|
|
2669
2707
|
*
|
|
2670
2708
|
* @param request - CreateVpnPbrRouteEntryRequest
|
|
@@ -2753,7 +2791,7 @@ export default class Client extends OpenApi {
|
|
|
2753
2791
|
*/
|
|
2754
2792
|
deactiveFlowLog(request: $_model.DeactiveFlowLogRequest): Promise<$_model.DeactiveFlowLogResponse>;
|
|
2755
2793
|
/**
|
|
2756
|
-
* Deletes a specified
|
|
2794
|
+
* Deletes a specified BGP group.
|
|
2757
2795
|
*
|
|
2758
2796
|
* @param request - DeleteBgpGroupRequest
|
|
2759
2797
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2761,7 +2799,7 @@ export default class Client extends OpenApi {
|
|
|
2761
2799
|
*/
|
|
2762
2800
|
deleteBgpGroupWithOptions(request: $_model.DeleteBgpGroupRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteBgpGroupResponse>;
|
|
2763
2801
|
/**
|
|
2764
|
-
* Deletes a specified
|
|
2802
|
+
* Deletes a specified BGP group.
|
|
2765
2803
|
*
|
|
2766
2804
|
* @param request - DeleteBgpGroupRequest
|
|
2767
2805
|
* @returns DeleteBgpGroupResponse
|
|
@@ -2770,6 +2808,9 @@ export default class Client extends OpenApi {
|
|
|
2770
2808
|
/**
|
|
2771
2809
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
2772
2810
|
*
|
|
2811
|
+
* @remarks
|
|
2812
|
+
* 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.
|
|
2813
|
+
*
|
|
2773
2814
|
* @param request - DeleteBgpNetworkRequest
|
|
2774
2815
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
2775
2816
|
* @returns DeleteBgpNetworkResponse
|
|
@@ -2778,6 +2819,9 @@ export default class Client extends OpenApi {
|
|
|
2778
2819
|
/**
|
|
2779
2820
|
* Deletes an advertised Border Gateway Protocol (BGP) network.
|
|
2780
2821
|
*
|
|
2822
|
+
* @remarks
|
|
2823
|
+
* 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.
|
|
2824
|
+
*
|
|
2781
2825
|
* @param request - DeleteBgpNetworkRequest
|
|
2782
2826
|
* @returns DeleteBgpNetworkResponse
|
|
2783
2827
|
*/
|
|
@@ -2954,10 +2998,10 @@ export default class Client extends OpenApi {
|
|
|
2954
2998
|
*/
|
|
2955
2999
|
deleteExpressConnectTrafficQosRule(request: $_model.DeleteExpressConnectTrafficQosRuleRequest): Promise<$_model.DeleteExpressConnectTrafficQosRuleResponse>;
|
|
2956
3000
|
/**
|
|
2957
|
-
* Deletes an Express Connect failover test job.
|
|
3001
|
+
* Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
|
|
2958
3002
|
*
|
|
2959
3003
|
* @remarks
|
|
2960
|
-
* Only failover test jobs in the **Pending** or **Completed** state can be deleted.
|
|
3004
|
+
* 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**.
|
|
2961
3005
|
*
|
|
2962
3006
|
* @param request - DeleteFailoverTestJobRequest
|
|
2963
3007
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -2965,10 +3009,10 @@ export default class Client extends OpenApi {
|
|
|
2965
3009
|
*/
|
|
2966
3010
|
deleteFailoverTestJobWithOptions(request: $_model.DeleteFailoverTestJobRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteFailoverTestJobResponse>;
|
|
2967
3011
|
/**
|
|
2968
|
-
* Deletes an Express Connect failover test job.
|
|
3012
|
+
* Deletes an Express Connect failover test job by calling the DeleteFailoverTestJob operation.
|
|
2969
3013
|
*
|
|
2970
3014
|
* @remarks
|
|
2971
|
-
* Only failover test jobs in the **Pending** or **Completed** state can be deleted.
|
|
3015
|
+
* 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**.
|
|
2972
3016
|
*
|
|
2973
3017
|
* @param request - DeleteFailoverTestJobRequest
|
|
2974
3018
|
* @returns DeleteFailoverTestJobResponse
|
|
@@ -3172,7 +3216,7 @@ export default class Client extends OpenApi {
|
|
|
3172
3216
|
* Deletes an IPsec server.
|
|
3173
3217
|
*
|
|
3174
3218
|
* @remarks
|
|
3175
|
-
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID
|
|
3219
|
+
* - **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:
|
|
3176
3220
|
* - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
|
|
3177
3221
|
* - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
|
|
3178
3222
|
* - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
|
|
@@ -3186,7 +3230,7 @@ export default class Client extends OpenApi {
|
|
|
3186
3230
|
* Deletes an IPsec server.
|
|
3187
3231
|
*
|
|
3188
3232
|
* @remarks
|
|
3189
|
-
* - **DeleteIpsecServer** is an asynchronous operation. After you send a request, the system returns a request ID
|
|
3233
|
+
* - **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:
|
|
3190
3234
|
* - If the VPN gateway instance is in the **updating** state, the IPsec server is being deleted.
|
|
3191
3235
|
* - If the VPN gateway instance is in the **active** state, the IPsec server is deleted.
|
|
3192
3236
|
* - **DeleteIpsecServer** does not support concurrent deletion of IPsec servers under the same VPN gateway.
|
|
@@ -3305,12 +3349,12 @@ export default class Client extends OpenApi {
|
|
|
3305
3349
|
* Deletes a specified Internet NAT gateway.
|
|
3306
3350
|
*
|
|
3307
3351
|
* @remarks
|
|
3308
|
-
* *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://
|
|
3352
|
+
* *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:
|
|
3309
3353
|
*
|
|
3310
3354
|
* - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
|
|
3311
3355
|
* - If the NAT gateway cannot be found, the NAT gateway is deleted.
|
|
3312
3356
|
*
|
|
3313
|
-
* >
|
|
3357
|
+
* > Deleting a NAT gateway is irreversible. Proceed with caution.
|
|
3314
3358
|
*
|
|
3315
3359
|
* @param request - DeleteNatGatewayRequest
|
|
3316
3360
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3321,12 +3365,12 @@ export default class Client extends OpenApi {
|
|
|
3321
3365
|
* Deletes a specified Internet NAT gateway.
|
|
3322
3366
|
*
|
|
3323
3367
|
* @remarks
|
|
3324
|
-
* *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://
|
|
3368
|
+
* *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:
|
|
3325
3369
|
*
|
|
3326
3370
|
* - If the NAT gateway is in the **Deleting** state, the NAT gateway is being deleted. In this state, you can only perform query operations.
|
|
3327
3371
|
* - If the NAT gateway cannot be found, the NAT gateway is deleted.
|
|
3328
3372
|
*
|
|
3329
|
-
* >
|
|
3373
|
+
* > Deleting a NAT gateway is irreversible. Proceed with caution.
|
|
3330
3374
|
*
|
|
3331
3375
|
* @param request - DeleteNatGatewayRequest
|
|
3332
3376
|
* @returns DeleteNatGatewayResponse
|
|
@@ -3419,11 +3463,11 @@ export default class Client extends OpenApi {
|
|
|
3419
3463
|
*
|
|
3420
3464
|
* @remarks
|
|
3421
3465
|
* Before you call this operation, take note of the following items:
|
|
3422
|
-
* - Before
|
|
3466
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
3423
3467
|
* - **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.
|
|
3424
3468
|
* - 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.
|
|
3425
3469
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
3426
|
-
* - **DeletePublicIpAddressPool**
|
|
3470
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
3427
3471
|
*
|
|
3428
3472
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
3429
3473
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3435,11 +3479,11 @@ export default class Client extends OpenApi {
|
|
|
3435
3479
|
*
|
|
3436
3480
|
* @remarks
|
|
3437
3481
|
* Before you call this operation, take note of the following items:
|
|
3438
|
-
* - Before
|
|
3482
|
+
* - Before you delete an IP address pool, make sure that the IP addresses in the pool are not in use.
|
|
3439
3483
|
* - **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.
|
|
3440
3484
|
* - 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.
|
|
3441
3485
|
* - If the IP address pool cannot be found, the IP address pool is deleted.
|
|
3442
|
-
* - **DeletePublicIpAddressPool**
|
|
3486
|
+
* - You cannot call **DeletePublicIpAddressPool** to concurrently delete the same IP address pool.
|
|
3443
3487
|
*
|
|
3444
3488
|
* @param request - DeletePublicIpAddressPoolRequest
|
|
3445
3489
|
* @returns DeletePublicIpAddressPoolResponse
|
|
@@ -3451,7 +3495,7 @@ export default class Client extends OpenApi {
|
|
|
3451
3495
|
* @remarks
|
|
3452
3496
|
* Before you call this operation, take note of the following information:
|
|
3453
3497
|
* - Before deleting a CIDR block, make sure that the CIDR block is not in use.
|
|
3454
|
-
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
3498
|
+
* - **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.
|
|
3455
3499
|
* - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
|
|
3456
3500
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
3457
3501
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -3467,7 +3511,7 @@ export default class Client extends OpenApi {
|
|
|
3467
3511
|
* @remarks
|
|
3468
3512
|
* Before you call this operation, take note of the following information:
|
|
3469
3513
|
* - Before deleting a CIDR block, make sure that the CIDR block is not in use.
|
|
3470
|
-
* - **DeletePublicIpAddressPoolCidrBlock** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
3514
|
+
* - **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.
|
|
3471
3515
|
* - If the CIDR block is in the **Deleting** state, the CIDR block is being deleted. In this state, you can only perform query operations.
|
|
3472
3516
|
* - If the CIDR block cannot be found, the CIDR block is deleted.
|
|
3473
3517
|
* - The **DeletePublicIpAddressPoolCidrBlock** operation does not support concurrent deletion of the same CIDR block.
|
|
@@ -3477,16 +3521,16 @@ export default class Client extends OpenApi {
|
|
|
3477
3521
|
*/
|
|
3478
3522
|
deletePublicIpAddressPoolCidrBlock(request: $_model.DeletePublicIpAddressPoolCidrBlockRequest): Promise<$_model.DeletePublicIpAddressPoolCidrBlockResponse>;
|
|
3479
3523
|
/**
|
|
3480
|
-
*
|
|
3524
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
3481
3525
|
*
|
|
3482
3526
|
* @remarks
|
|
3483
3527
|
* When you call this operation to delete routing entries, note the following items:
|
|
3484
3528
|
* - Only routing entries in the **Available** state can be deleted.
|
|
3485
|
-
* - Routing entries cannot be deleted if the VPC
|
|
3486
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
3487
|
-
* - If the
|
|
3488
|
-
* - If the specified
|
|
3489
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
3529
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
3530
|
+
* - 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:
|
|
3531
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
3532
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
3533
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
3490
3534
|
*
|
|
3491
3535
|
* @param request - DeleteRouteEntriesRequest
|
|
3492
3536
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3494,16 +3538,16 @@ export default class Client extends OpenApi {
|
|
|
3494
3538
|
*/
|
|
3495
3539
|
deleteRouteEntriesWithOptions(request: $_model.DeleteRouteEntriesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteRouteEntriesResponse>;
|
|
3496
3540
|
/**
|
|
3497
|
-
*
|
|
3541
|
+
* Calls DeleteRouteEntries to batch delete custom route entries.
|
|
3498
3542
|
*
|
|
3499
3543
|
* @remarks
|
|
3500
3544
|
* When you call this operation to delete routing entries, note the following items:
|
|
3501
3545
|
* - Only routing entries in the **Available** state can be deleted.
|
|
3502
|
-
* - Routing entries cannot be deleted if the VPC
|
|
3503
|
-
* - The **DeleteRouteEntries** operation is asynchronous. After you send a request, the system returns a request ID, but the
|
|
3504
|
-
* - If the
|
|
3505
|
-
* - If the specified
|
|
3506
|
-
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries
|
|
3546
|
+
* - Routing entries cannot be deleted if the VPC that contains the route table is creating or deleting a vSwitch or routing entry.
|
|
3547
|
+
* - 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:
|
|
3548
|
+
* - If the routing entry is in the **Deleting** state, the routing entry is being deleted.
|
|
3549
|
+
* - If the specified routing entry cannot be found, the routing entry is deleted.
|
|
3550
|
+
* - The **DeleteRouteEntries** operation does not support concurrent batch deletion of routing entries in route tables within the same VPC.
|
|
3507
3551
|
*
|
|
3508
3552
|
* @param request - DeleteRouteEntriesRequest
|
|
3509
3553
|
* @returns DeleteRouteEntriesResponse
|
|
@@ -3687,10 +3731,10 @@ export default class Client extends OpenApi {
|
|
|
3687
3731
|
* 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.
|
|
3688
3732
|
*
|
|
3689
3733
|
* @remarks
|
|
3690
|
-
* - **DeleteSslVpnServer** is
|
|
3734
|
+
* - 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:
|
|
3691
3735
|
* - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
|
|
3692
3736
|
* - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
|
|
3693
|
-
* - **DeleteSslVpnServer** does not support concurrent deletion of SSL
|
|
3737
|
+
* - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
|
|
3694
3738
|
*
|
|
3695
3739
|
* @param request - DeleteSslVpnServerRequest
|
|
3696
3740
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3701,10 +3745,10 @@ export default class Client extends OpenApi {
|
|
|
3701
3745
|
* 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.
|
|
3702
3746
|
*
|
|
3703
3747
|
* @remarks
|
|
3704
|
-
* - **DeleteSslVpnServer** is
|
|
3748
|
+
* - 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:
|
|
3705
3749
|
* - If the VPN gateway instance is in the **updating** state, the SSL server is being deleted.
|
|
3706
3750
|
* - If the VPN gateway instance is in the **active** state, the SSL server is deleted.
|
|
3707
|
-
* - **DeleteSslVpnServer** does not support concurrent deletion of SSL
|
|
3751
|
+
* - The **DeleteSslVpnServer** operation does not support concurrent deletion of SSL servers under the same VPN gateway.
|
|
3708
3752
|
*
|
|
3709
3753
|
* @param request - DeleteSslVpnServerRequest
|
|
3710
3754
|
* @returns DeleteSslVpnServerResponse
|
|
@@ -3854,7 +3898,7 @@ export default class Client extends OpenApi {
|
|
|
3854
3898
|
*/
|
|
3855
3899
|
deleteVSwitchCidrReservation(request: $_model.DeleteVSwitchCidrReservationRequest): Promise<$_model.DeleteVSwitchCidrReservationResponse>;
|
|
3856
3900
|
/**
|
|
3857
|
-
*
|
|
3901
|
+
* Calls DeleteVbrHa to delete a VBR failover group.
|
|
3858
3902
|
*
|
|
3859
3903
|
* @param request - DeleteVbrHaRequest
|
|
3860
3904
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -3862,7 +3906,7 @@ export default class Client extends OpenApi {
|
|
|
3862
3906
|
*/
|
|
3863
3907
|
deleteVbrHaWithOptions(request: $_model.DeleteVbrHaRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteVbrHaResponse>;
|
|
3864
3908
|
/**
|
|
3865
|
-
*
|
|
3909
|
+
* Calls DeleteVbrHa to delete a VBR failover group.
|
|
3866
3910
|
*
|
|
3867
3911
|
* @param request - DeleteVbrHaRequest
|
|
3868
3912
|
* @returns DeleteVbrHaResponse
|
|
@@ -3872,7 +3916,7 @@ export default class Client extends OpenApi {
|
|
|
3872
3916
|
* Deletes a destination route entry from an IPsec-VPN connection.
|
|
3873
3917
|
*
|
|
3874
3918
|
* @remarks
|
|
3875
|
-
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry
|
|
3919
|
+
* - **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:
|
|
3876
3920
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
|
|
3877
3921
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
|
|
3878
3922
|
* - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
|
|
@@ -3886,7 +3930,7 @@ export default class Client extends OpenApi {
|
|
|
3886
3930
|
* Deletes a destination route entry from an IPsec-VPN connection.
|
|
3887
3931
|
*
|
|
3888
3932
|
* @remarks
|
|
3889
|
-
* - **DeleteVcoRouteEntry** is an asynchronous operation. After you send a request, the system returns a request ID, but the destination route entry
|
|
3933
|
+
* - **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:
|
|
3890
3934
|
* - If the IPsec-VPN connection is in the **updating** state, the destination route entry is being deleted.
|
|
3891
3935
|
* - If the IPsec-VPN connection is in the **attached** state, the destination route entry is deleted.
|
|
3892
3936
|
* - **DeleteVcoRouteEntry** does not support concurrent deletion of destination route entries for the same IPsec-VPN connection.
|
|
@@ -3994,11 +4038,11 @@ export default class Client extends OpenApi {
|
|
|
3994
4038
|
*/
|
|
3995
4039
|
deleteVpcPrefixList(request: $_model.DeleteVpcPrefixListRequest): Promise<$_model.DeleteVpcPrefixListResponse>;
|
|
3996
4040
|
/**
|
|
3997
|
-
* Deletes an IPsec-VPN connection
|
|
4041
|
+
* Deletes an IPsec-VPN connection.
|
|
3998
4042
|
*
|
|
3999
4043
|
* @remarks
|
|
4000
|
-
* - If the IPsec-VPN connection is
|
|
4001
|
-
* - If the IPsec-VPN connection is not
|
|
4044
|
+
* - 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).
|
|
4045
|
+
* - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
|
|
4002
4046
|
*
|
|
4003
4047
|
* @param request - DeleteVpnAttachmentRequest
|
|
4004
4048
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4006,11 +4050,11 @@ export default class Client extends OpenApi {
|
|
|
4006
4050
|
*/
|
|
4007
4051
|
deleteVpnAttachmentWithOptions(request: $_model.DeleteVpnAttachmentRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DeleteVpnAttachmentResponse>;
|
|
4008
4052
|
/**
|
|
4009
|
-
* Deletes an IPsec-VPN connection
|
|
4053
|
+
* Deletes an IPsec-VPN connection.
|
|
4010
4054
|
*
|
|
4011
4055
|
* @remarks
|
|
4012
|
-
* - If the IPsec-VPN connection is
|
|
4013
|
-
* - If the IPsec-VPN connection is not
|
|
4056
|
+
* - 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).
|
|
4057
|
+
* - If the IPsec-VPN connection is not bindded to any resource, you can call the `DeleteVpnAttachment` operation to directly delete the IPsec-VPN connection.
|
|
4014
4058
|
*
|
|
4015
4059
|
* @param request - DeleteVpnAttachmentRequest
|
|
4016
4060
|
* @returns DeleteVpnAttachmentResponse
|
|
@@ -4020,7 +4064,7 @@ export default class Client extends OpenApi {
|
|
|
4020
4064
|
* Deletes a specified IPsec-VPN connection.
|
|
4021
4065
|
*
|
|
4022
4066
|
* @remarks
|
|
4023
|
-
* - **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
|
|
4067
|
+
* - **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:
|
|
4024
4068
|
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
|
|
4025
4069
|
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
|
|
4026
4070
|
* - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
|
|
@@ -4035,7 +4079,7 @@ export default class Client extends OpenApi {
|
|
|
4035
4079
|
* Deletes a specified IPsec-VPN connection.
|
|
4036
4080
|
*
|
|
4037
4081
|
* @remarks
|
|
4038
|
-
* - **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
|
|
4082
|
+
* - **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:
|
|
4039
4083
|
* - If the VPN gateway instance is in the **updating** state, the IPsec-VPN connection is being deleted.
|
|
4040
4084
|
* - If the VPN gateway instance is in the **active** state, the IPsec-VPN connection is deleted.
|
|
4041
4085
|
* - **DeleteVpnConnection** does not support concurrent deletion of IPsec-VPN connections under the same VPN gateway.
|
|
@@ -4049,7 +4093,7 @@ export default class Client extends OpenApi {
|
|
|
4049
4093
|
* Deletes a specified VPN gateway.
|
|
4050
4094
|
*
|
|
4051
4095
|
* @remarks
|
|
4052
|
-
* > You cannot delete a VPN gateway that has
|
|
4096
|
+
* > You cannot delete a VPN gateway that has IPsec-VPN connections.
|
|
4053
4097
|
*
|
|
4054
4098
|
* @param request - DeleteVpnGatewayRequest
|
|
4055
4099
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4060,7 +4104,7 @@ export default class Client extends OpenApi {
|
|
|
4060
4104
|
* Deletes a specified VPN gateway.
|
|
4061
4105
|
*
|
|
4062
4106
|
* @remarks
|
|
4063
|
-
* > You cannot delete a VPN gateway that has
|
|
4107
|
+
* > You cannot delete a VPN gateway that has IPsec-VPN connections.
|
|
4064
4108
|
*
|
|
4065
4109
|
* @param request - DeleteVpnGatewayRequest
|
|
4066
4110
|
* @returns DeleteVpnGatewayResponse
|
|
@@ -4097,7 +4141,7 @@ export default class Client extends OpenApi {
|
|
|
4097
4141
|
* Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
|
|
4098
4142
|
*
|
|
4099
4143
|
* @remarks
|
|
4100
|
-
* - **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:
|
|
4144
|
+
* - **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:
|
|
4101
4145
|
* - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
|
|
4102
4146
|
* - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
|
|
4103
4147
|
* - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
|
|
@@ -4111,7 +4155,7 @@ export default class Client extends OpenApi {
|
|
|
4111
4155
|
* Deletes a VPN destination route by calling the DeleteVpnRouteEntry operation.
|
|
4112
4156
|
*
|
|
4113
4157
|
* @remarks
|
|
4114
|
-
* - **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:
|
|
4158
|
+
* - **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:
|
|
4115
4159
|
* - If the VPN gateway instance is in the **updating** state, the VPN destination route is being deleted.
|
|
4116
4160
|
* - If the VPN gateway instance is in the **active** state, the VPN destination route is deleted.
|
|
4117
4161
|
* - **DeleteVpnRouteEntry** does not support concurrent deletion of VPN destination routes for the same VPN gateway.
|
|
@@ -4279,10 +4323,10 @@ export default class Client extends OpenApi {
|
|
|
4279
4323
|
*/
|
|
4280
4324
|
describeEcGrantRelation(request: $_model.DescribeEcGrantRelationRequest): Promise<$_model.DescribeEcGrantRelationResponse>;
|
|
4281
4325
|
/**
|
|
4282
|
-
* Queries
|
|
4326
|
+
* Queries elastic IP addresses (EIPs) created in a specified region.
|
|
4283
4327
|
*
|
|
4284
4328
|
* @remarks
|
|
4285
|
-
*
|
|
4329
|
+
* 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.
|
|
4286
4330
|
*
|
|
4287
4331
|
* @param request - DescribeEipAddressesRequest
|
|
4288
4332
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4290,10 +4334,10 @@ export default class Client extends OpenApi {
|
|
|
4290
4334
|
*/
|
|
4291
4335
|
describeEipAddressesWithOptions(request: $_model.DescribeEipAddressesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeEipAddressesResponse>;
|
|
4292
4336
|
/**
|
|
4293
|
-
* Queries
|
|
4337
|
+
* Queries elastic IP addresses (EIPs) created in a specified region.
|
|
4294
4338
|
*
|
|
4295
4339
|
* @remarks
|
|
4296
|
-
*
|
|
4340
|
+
* 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.
|
|
4297
4341
|
*
|
|
4298
4342
|
* @param request - DescribeEipAddressesRequest
|
|
4299
4343
|
* @returns DescribeEipAddressesResponse
|
|
@@ -4374,6 +4418,9 @@ export default class Client extends OpenApi {
|
|
|
4374
4418
|
/**
|
|
4375
4419
|
* Queries Express Connect QoS queues.
|
|
4376
4420
|
*
|
|
4421
|
+
* @remarks
|
|
4422
|
+
* Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
|
|
4423
|
+
*
|
|
4377
4424
|
* @param request - DescribeExpressConnectTrafficQosQueueRequest
|
|
4378
4425
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
4379
4426
|
* @returns DescribeExpressConnectTrafficQosQueueResponse
|
|
@@ -4382,6 +4429,9 @@ export default class Client extends OpenApi {
|
|
|
4382
4429
|
/**
|
|
4383
4430
|
* Queries Express Connect QoS queues.
|
|
4384
4431
|
*
|
|
4432
|
+
* @remarks
|
|
4433
|
+
* Before you call this operation, call CreateExpressConnectTrafficQos to create a QoS policy and obtain the **QosId**.
|
|
4434
|
+
*
|
|
4385
4435
|
* @param request - DescribeExpressConnectTrafficQosQueueRequest
|
|
4386
4436
|
* @returns DescribeExpressConnectTrafficQosQueueResponse
|
|
4387
4437
|
*/
|
|
@@ -4402,7 +4452,7 @@ export default class Client extends OpenApi {
|
|
|
4402
4452
|
*/
|
|
4403
4453
|
describeExpressConnectTrafficQosRule(request: $_model.DescribeExpressConnectTrafficQosRuleRequest): Promise<$_model.DescribeExpressConnectTrafficQosRuleResponse>;
|
|
4404
4454
|
/**
|
|
4405
|
-
* Queries the details of an Express Connect failover test job
|
|
4455
|
+
* Queries the details of an Express Connect failover test job.
|
|
4406
4456
|
*
|
|
4407
4457
|
* @param request - DescribeFailoverTestJobRequest
|
|
4408
4458
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4410,14 +4460,14 @@ export default class Client extends OpenApi {
|
|
|
4410
4460
|
*/
|
|
4411
4461
|
describeFailoverTestJobWithOptions(request: $_model.DescribeFailoverTestJobRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeFailoverTestJobResponse>;
|
|
4412
4462
|
/**
|
|
4413
|
-
* Queries the details of an Express Connect failover test job
|
|
4463
|
+
* Queries the details of an Express Connect failover test job.
|
|
4414
4464
|
*
|
|
4415
4465
|
* @param request - DescribeFailoverTestJobRequest
|
|
4416
4466
|
* @returns DescribeFailoverTestJobResponse
|
|
4417
4467
|
*/
|
|
4418
4468
|
describeFailoverTestJob(request: $_model.DescribeFailoverTestJobRequest): Promise<$_model.DescribeFailoverTestJobResponse>;
|
|
4419
4469
|
/**
|
|
4420
|
-
* Queries failover test jobs
|
|
4470
|
+
* Queries Express Connect failover test jobs in batches.
|
|
4421
4471
|
*
|
|
4422
4472
|
* @param request - DescribeFailoverTestJobsRequest
|
|
4423
4473
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4425,7 +4475,7 @@ export default class Client extends OpenApi {
|
|
|
4425
4475
|
*/
|
|
4426
4476
|
describeFailoverTestJobsWithOptions(request: $_model.DescribeFailoverTestJobsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeFailoverTestJobsResponse>;
|
|
4427
4477
|
/**
|
|
4428
|
-
* Queries failover test jobs
|
|
4478
|
+
* Queries Express Connect failover test jobs in batches.
|
|
4429
4479
|
*
|
|
4430
4480
|
* @param request - DescribeFailoverTestJobsRequest
|
|
4431
4481
|
* @returns DescribeFailoverTestJobsResponse
|
|
@@ -4753,7 +4803,7 @@ export default class Client extends OpenApi {
|
|
|
4753
4803
|
* Queries information about Express Connect circuits in a specified region.
|
|
4754
4804
|
*
|
|
4755
4805
|
* @remarks
|
|
4756
|
-
* 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,
|
|
4806
|
+
* 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.
|
|
4757
4807
|
*
|
|
4758
4808
|
* @param request - DescribePhysicalConnectionsRequest
|
|
4759
4809
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4764,7 +4814,7 @@ export default class Client extends OpenApi {
|
|
|
4764
4814
|
* Queries information about Express Connect circuits in a specified region.
|
|
4765
4815
|
*
|
|
4766
4816
|
* @remarks
|
|
4767
|
-
* 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,
|
|
4817
|
+
* 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.
|
|
4768
4818
|
*
|
|
4769
4819
|
* @param request - DescribePhysicalConnectionsRequest
|
|
4770
4820
|
* @returns DescribePhysicalConnectionsResponse
|
|
@@ -4877,7 +4927,7 @@ export default class Client extends OpenApi {
|
|
|
4877
4927
|
*/
|
|
4878
4928
|
describeRouterInterfaceAttribute(request: $_model.DescribeRouterInterfaceAttributeRequest): Promise<$_model.DescribeRouterInterfaceAttributeResponse>;
|
|
4879
4929
|
/**
|
|
4880
|
-
* Queries router interfaces in a specified region
|
|
4930
|
+
* Queries router interfaces in a specified region.
|
|
4881
4931
|
*
|
|
4882
4932
|
* @param request - DescribeRouterInterfacesRequest
|
|
4883
4933
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -4885,7 +4935,7 @@ export default class Client extends OpenApi {
|
|
|
4885
4935
|
*/
|
|
4886
4936
|
describeRouterInterfacesWithOptions(request: $_model.DescribeRouterInterfacesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeRouterInterfacesResponse>;
|
|
4887
4937
|
/**
|
|
4888
|
-
* Queries router interfaces in a specified region
|
|
4938
|
+
* Queries router interfaces in a specified region.
|
|
4889
4939
|
*
|
|
4890
4940
|
* @param request - DescribeRouterInterfacesRequest
|
|
4891
4941
|
* @returns DescribeRouterInterfacesResponse
|
|
@@ -5011,7 +5061,7 @@ export default class Client extends OpenApi {
|
|
|
5011
5061
|
*/
|
|
5012
5062
|
describeTagKeys(request: $_model.DescribeTagKeysRequest): Promise<$_model.DescribeTagKeysResponse>;
|
|
5013
5063
|
/**
|
|
5014
|
-
*
|
|
5064
|
+
* Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
|
|
5015
5065
|
*
|
|
5016
5066
|
* @param request - DescribeTagKeysForExpressConnectRequest
|
|
5017
5067
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5019,7 +5069,7 @@ export default class Client extends OpenApi {
|
|
|
5019
5069
|
*/
|
|
5020
5070
|
describeTagKeysForExpressConnectWithOptions(request: $_model.DescribeTagKeysForExpressConnectRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeTagKeysForExpressConnectResponse>;
|
|
5021
5071
|
/**
|
|
5022
|
-
*
|
|
5072
|
+
* Queries the tag list of Express Connect resources by calling the DescribeTagKeysForExpressConnect operation.
|
|
5023
5073
|
*
|
|
5024
5074
|
* @param request - DescribeTagKeysForExpressConnectRequest
|
|
5025
5075
|
* @returns DescribeTagKeysForExpressConnectResponse
|
|
@@ -5085,6 +5135,9 @@ export default class Client extends OpenApi {
|
|
|
5085
5135
|
/**
|
|
5086
5136
|
* Queries networkable information. Internal networking is performed by vSwitch.
|
|
5087
5137
|
*
|
|
5138
|
+
* @remarks
|
|
5139
|
+
* 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.
|
|
5140
|
+
*
|
|
5088
5141
|
* @param request - DescribeVSwitchesRequest
|
|
5089
5142
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
5090
5143
|
* @returns DescribeVSwitchesResponse
|
|
@@ -5093,6 +5146,9 @@ export default class Client extends OpenApi {
|
|
|
5093
5146
|
/**
|
|
5094
5147
|
* Queries networkable information. Internal networking is performed by vSwitch.
|
|
5095
5148
|
*
|
|
5149
|
+
* @remarks
|
|
5150
|
+
* 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.
|
|
5151
|
+
*
|
|
5096
5152
|
* @param request - DescribeVSwitchesRequest
|
|
5097
5153
|
* @returns DescribeVSwitchesResponse
|
|
5098
5154
|
*/
|
|
@@ -5128,7 +5184,7 @@ export default class Client extends OpenApi {
|
|
|
5128
5184
|
*/
|
|
5129
5185
|
describeVcoRouteEntries(request: $_model.DescribeVcoRouteEntriesRequest): Promise<$_model.DescribeVcoRouteEntriesResponse>;
|
|
5130
5186
|
/**
|
|
5131
|
-
* Queries
|
|
5187
|
+
* Queries Virtual Border Routers (VBRs) that are created.
|
|
5132
5188
|
*
|
|
5133
5189
|
* @param request - DescribeVirtualBorderRoutersRequest
|
|
5134
5190
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5136,7 +5192,7 @@ export default class Client extends OpenApi {
|
|
|
5136
5192
|
*/
|
|
5137
5193
|
describeVirtualBorderRoutersWithOptions(request: $_model.DescribeVirtualBorderRoutersRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeVirtualBorderRoutersResponse>;
|
|
5138
5194
|
/**
|
|
5139
|
-
* Queries
|
|
5195
|
+
* Queries Virtual Border Routers (VBRs) that are created.
|
|
5140
5196
|
*
|
|
5141
5197
|
* @param request - DescribeVirtualBorderRoutersRequest
|
|
5142
5198
|
* @returns DescribeVirtualBorderRoutersResponse
|
|
@@ -5190,6 +5246,9 @@ export default class Client extends OpenApi {
|
|
|
5190
5246
|
/**
|
|
5191
5247
|
* Queries created VPCs.
|
|
5192
5248
|
*
|
|
5249
|
+
* @remarks
|
|
5250
|
+
* 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.
|
|
5251
|
+
*
|
|
5193
5252
|
* @param request - DescribeVpcsRequest
|
|
5194
5253
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
5195
5254
|
* @returns DescribeVpcsResponse
|
|
@@ -5198,6 +5257,9 @@ export default class Client extends OpenApi {
|
|
|
5198
5257
|
/**
|
|
5199
5258
|
* Queries created VPCs.
|
|
5200
5259
|
*
|
|
5260
|
+
* @remarks
|
|
5261
|
+
* 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.
|
|
5262
|
+
*
|
|
5201
5263
|
* @param request - DescribeVpcsRequest
|
|
5202
5264
|
* @returns DescribeVpcsResponse
|
|
5203
5265
|
*/
|
|
@@ -5353,7 +5415,7 @@ export default class Client extends OpenApi {
|
|
|
5353
5415
|
*/
|
|
5354
5416
|
describeVpnRouteEntries(request: $_model.DescribeVpnRouteEntriesRequest): Promise<$_model.DescribeVpnRouteEntriesResponse>;
|
|
5355
5417
|
/**
|
|
5356
|
-
* Queries the logs of an SSL server
|
|
5418
|
+
* Queries the logs of an SSL server.
|
|
5357
5419
|
*
|
|
5358
5420
|
* @param request - DescribeVpnSslServerLogsRequest
|
|
5359
5421
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5361,7 +5423,7 @@ export default class Client extends OpenApi {
|
|
|
5361
5423
|
*/
|
|
5362
5424
|
describeVpnSslServerLogsWithOptions(request: $_model.DescribeVpnSslServerLogsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DescribeVpnSslServerLogsResponse>;
|
|
5363
5425
|
/**
|
|
5364
|
-
* Queries the logs of an SSL server
|
|
5426
|
+
* Queries the logs of an SSL server.
|
|
5365
5427
|
*
|
|
5366
5428
|
* @param request - DescribeVpnSslServerLogsRequest
|
|
5367
5429
|
* @returns DescribeVpnSslServerLogsResponse
|
|
@@ -5435,10 +5497,10 @@ export default class Client extends OpenApi {
|
|
|
5435
5497
|
*/
|
|
5436
5498
|
diagnoseVpnConnections(request: $_model.DiagnoseVpnConnectionsRequest): Promise<$_model.DiagnoseVpnConnectionsResponse>;
|
|
5437
5499
|
/**
|
|
5438
|
-
*
|
|
5500
|
+
* Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
|
|
5439
5501
|
*
|
|
5440
5502
|
* @remarks
|
|
5441
|
-
* Only VPN gateway instances in specific regions support the one-click
|
|
5503
|
+
* 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).
|
|
5442
5504
|
*
|
|
5443
5505
|
* @param request - DiagnoseVpnGatewayRequest
|
|
5444
5506
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5446,10 +5508,10 @@ export default class Client extends OpenApi {
|
|
|
5446
5508
|
*/
|
|
5447
5509
|
diagnoseVpnGatewayWithOptions(request: $_model.DiagnoseVpnGatewayRequest, runtime: $dara.RuntimeOptions): Promise<$_model.DiagnoseVpnGatewayResponse>;
|
|
5448
5510
|
/**
|
|
5449
|
-
*
|
|
5511
|
+
* Calls the DiagnoseVpnGateway operation to perform a one-click diagnosis on a specified VPN gateway instance.
|
|
5450
5512
|
*
|
|
5451
5513
|
* @remarks
|
|
5452
|
-
* Only VPN gateway instances in specific regions support the one-click
|
|
5514
|
+
* 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).
|
|
5453
5515
|
*
|
|
5454
5516
|
* @param request - DiagnoseVpnGatewayRequest
|
|
5455
5517
|
* @returns DiagnoseVpnGatewayResponse
|
|
@@ -5531,10 +5593,10 @@ export default class Client extends OpenApi {
|
|
|
5531
5593
|
* Dissociates a VPN gateway from a certificate.
|
|
5532
5594
|
*
|
|
5533
5595
|
* @remarks
|
|
5534
|
-
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
5596
|
+
* - **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:
|
|
5535
5597
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
|
|
5536
5598
|
* - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
|
|
5537
|
-
* - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL
|
|
5599
|
+
* - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
|
|
5538
5600
|
*
|
|
5539
5601
|
* @param request - DissociateVpnGatewayWithCertificateRequest
|
|
5540
5602
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5545,10 +5607,10 @@ export default class Client extends OpenApi {
|
|
|
5545
5607
|
* Dissociates a VPN gateway from a certificate.
|
|
5546
5608
|
*
|
|
5547
5609
|
* @remarks
|
|
5548
|
-
* - **DissociateVpnGatewayWithCertificate** is an asynchronous operation. After a request is sent, the system returns a request ID
|
|
5610
|
+
* - **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:
|
|
5549
5611
|
* - If the VPN gateway is in the **updating** state, the SSL certificate is being dissociated.
|
|
5550
5612
|
* - If the VPN gateway is in the **active** state, the SSL certificate is dissociated.
|
|
5551
|
-
* - **DissociateVpnGatewayWithCertificate** does not support concurrent SSL
|
|
5613
|
+
* - **DissociateVpnGatewayWithCertificate** does not support concurrent dissociation of SSL certificates from the same VPN gateway.
|
|
5552
5614
|
*
|
|
5553
5615
|
* @param request - DissociateVpnGatewayWithCertificateRequest
|
|
5554
5616
|
* @returns DissociateVpnGatewayWithCertificateResponse
|
|
@@ -5573,11 +5635,12 @@ export default class Client extends OpenApi {
|
|
|
5573
5635
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
5574
5636
|
*
|
|
5575
5637
|
* @remarks
|
|
5576
|
-
* When you
|
|
5577
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
5578
|
-
* -
|
|
5579
|
-
* -
|
|
5580
|
-
* -
|
|
5638
|
+
* When you invoke this operation, note the following items:
|
|
5639
|
+
* - 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).
|
|
5640
|
+
* - 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.
|
|
5641
|
+
* - 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.
|
|
5642
|
+
* - 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.
|
|
5643
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
5581
5644
|
*
|
|
5582
5645
|
* @param request - EnablePhysicalConnectionRequest
|
|
5583
5646
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5588,11 +5651,12 @@ export default class Client extends OpenApi {
|
|
|
5588
5651
|
* Enables an Express Connect circuit that is in the Confirmed state. After the circuit is enabled, it enters the Enabled state.
|
|
5589
5652
|
*
|
|
5590
5653
|
* @remarks
|
|
5591
|
-
* When you
|
|
5592
|
-
* - You can enable only an Express Connect circuit that is in the
|
|
5593
|
-
* -
|
|
5594
|
-
* -
|
|
5595
|
-
* -
|
|
5654
|
+
* When you invoke this operation, note the following items:
|
|
5655
|
+
* - 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).
|
|
5656
|
+
* - 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.
|
|
5657
|
+
* - 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.
|
|
5658
|
+
* - 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.
|
|
5659
|
+
* If the Express Connect circuit is already in the Enabled state, invoking this operation again returns a success response (idempotent).
|
|
5596
5660
|
*
|
|
5597
5661
|
* @param request - EnablePhysicalConnectionRequest
|
|
5598
5662
|
* @returns EnablePhysicalConnectionResponse
|
|
@@ -5693,7 +5757,7 @@ export default class Client extends OpenApi {
|
|
|
5693
5757
|
* Queries the information about a single NAT gateway instance.
|
|
5694
5758
|
*
|
|
5695
5759
|
* @remarks
|
|
5696
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
5760
|
+
* 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.
|
|
5697
5761
|
*
|
|
5698
5762
|
* @param request - GetNatGatewayAttributeRequest
|
|
5699
5763
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5704,7 +5768,7 @@ export default class Client extends OpenApi {
|
|
|
5704
5768
|
* Queries the information about a single NAT gateway instance.
|
|
5705
5769
|
*
|
|
5706
5770
|
* @remarks
|
|
5707
|
-
* This operation queries the information about a single Internet NAT gateway or VPC NAT gateway. The term "NAT gateway" in this topic
|
|
5771
|
+
* 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.
|
|
5708
5772
|
*
|
|
5709
5773
|
* @param request - GetNatGatewayAttributeRequest
|
|
5710
5774
|
* @returns GetNatGatewayAttributeResponse
|
|
@@ -5860,10 +5924,10 @@ export default class Client extends OpenApi {
|
|
|
5860
5924
|
*/
|
|
5861
5925
|
getVpcRouteEntrySummary(request: $_model.GetVpcRouteEntrySummaryRequest): Promise<$_model.GetVpcRouteEntrySummaryResponse>;
|
|
5862
5926
|
/**
|
|
5863
|
-
* Queries the one-click
|
|
5927
|
+
* Queries the one-click diagnosis result of a VPN gateway instance.
|
|
5864
5928
|
*
|
|
5865
5929
|
* @remarks
|
|
5866
|
-
* When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters
|
|
5930
|
+
* When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
|
|
5867
5931
|
*
|
|
5868
5932
|
* @param request - GetVpnGatewayDiagnoseResultRequest
|
|
5869
5933
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5871,10 +5935,10 @@ export default class Client extends OpenApi {
|
|
|
5871
5935
|
*/
|
|
5872
5936
|
getVpnGatewayDiagnoseResultWithOptions(request: $_model.GetVpnGatewayDiagnoseResultRequest, runtime: $dara.RuntimeOptions): Promise<$_model.GetVpnGatewayDiagnoseResultResponse>;
|
|
5873
5937
|
/**
|
|
5874
|
-
* Queries the one-click
|
|
5938
|
+
* Queries the one-click diagnosis result of a VPN gateway instance.
|
|
5875
5939
|
*
|
|
5876
5940
|
* @remarks
|
|
5877
|
-
* When you call the **GetVpnGatewayDiagnoseResult** operation, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters
|
|
5941
|
+
* When you call the **GetVpnGatewayDiagnoseResult** operation, in addition to the required parameters, you must specify at least one of the **DiagnoseId** and **VpnGatewayId** parameters.
|
|
5878
5942
|
*
|
|
5879
5943
|
* @param request - GetVpnGatewayDiagnoseResultRequest
|
|
5880
5944
|
* @returns GetVpnGatewayDiagnoseResultResponse
|
|
@@ -5909,7 +5973,18 @@ export default class Client extends OpenApi {
|
|
|
5909
5973
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
5910
5974
|
*
|
|
5911
5975
|
* @remarks
|
|
5912
|
-
*
|
|
5976
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
5977
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
5978
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
5979
|
+
* **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:
|
|
5980
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
5981
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
5982
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
5983
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
5984
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
5985
|
+
* - 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).
|
|
5986
|
+
* - 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.
|
|
5987
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
5913
5988
|
*
|
|
5914
5989
|
* @param tmpReq - GrantInstanceToVbrRequest
|
|
5915
5990
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5920,14 +5995,25 @@ export default class Client extends OpenApi {
|
|
|
5920
5995
|
* Invokes the GrantInstanceToVbr operation to grant authorization of a VPC-connected instance to a VBR instance for cross-account VBR uplink scenarios.
|
|
5921
5996
|
*
|
|
5922
5997
|
* @remarks
|
|
5923
|
-
*
|
|
5998
|
+
* This operation is used for cross-account scenarios. Before calling this operation, ensure that the following resources are ready:
|
|
5999
|
+
* **Account A (VPC owner, the caller of this operation):**
|
|
6000
|
+
* - A VPC has been created and is in the Available state (CreateVpc).
|
|
6001
|
+
* **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:
|
|
6002
|
+
* 1. Call CreatePhysicalConnection to create an Express Connect circuit.
|
|
6003
|
+
* 2. Apply for a Letter of Authorization (LOA) and complete the construction (ApplyPhysicalConnectionLOA → CompletePhysicalConnectionLOA). The Express Connect circuit enters the Confirmed state.
|
|
6004
|
+
* 3. Call EnablePhysicalConnection to enable the Express Connect circuit (the circuit must be in the Confirmed state).
|
|
6005
|
+
* 4. Call CreateVirtualBorderRouter to create a VBR (the Express Connect circuit must be in the Enabled state. Otherwise, the error InvalidPhysicalConnectionId.NotEnabled is returned).
|
|
6006
|
+
* After the preceding preparations are complete, Account A calls this operation to grant the VPC to the VBR of Account B:
|
|
6007
|
+
* - 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).
|
|
6008
|
+
* - 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.
|
|
6009
|
+
* Note: VbrOwnerUid cannot be the same as the caller\\"s account. Otherwise, the error Parameter.Illegal is returned.
|
|
5924
6010
|
*
|
|
5925
6011
|
* @param request - GrantInstanceToVbrRequest
|
|
5926
6012
|
* @returns GrantInstanceToVbrResponse
|
|
5927
6013
|
*/
|
|
5928
6014
|
grantInstanceToVbr(request: $_model.GrantInstanceToVbrRequest): Promise<$_model.GrantInstanceToVbrResponse>;
|
|
5929
6015
|
/**
|
|
5930
|
-
*
|
|
6016
|
+
* Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
|
|
5931
6017
|
*
|
|
5932
6018
|
* @param request - ListBusinessAccessPointsRequest
|
|
5933
6019
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -5935,7 +6021,7 @@ export default class Client extends OpenApi {
|
|
|
5935
6021
|
*/
|
|
5936
6022
|
listBusinessAccessPointsWithOptions(request: $_model.ListBusinessAccessPointsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListBusinessAccessPointsResponse>;
|
|
5937
6023
|
/**
|
|
5938
|
-
*
|
|
6024
|
+
* Queries the access point information of Express Connect circuits by calling the ListBusinessAccessPoints operation.
|
|
5939
6025
|
*
|
|
5940
6026
|
* @param request - ListBusinessAccessPointsRequest
|
|
5941
6027
|
* @returns ListBusinessAccessPointsResponse
|
|
@@ -6290,7 +6376,7 @@ export default class Client extends OpenApi {
|
|
|
6290
6376
|
*/
|
|
6291
6377
|
listVSwitchCidrReservations(request: $_model.ListVSwitchCidrReservationsRequest): Promise<$_model.ListVSwitchCidrReservationsResponse>;
|
|
6292
6378
|
/**
|
|
6293
|
-
* Queries information about shared Express Connect circuits
|
|
6379
|
+
* Queries information about shared Express Connect circuits.
|
|
6294
6380
|
*
|
|
6295
6381
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
6296
6382
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -6298,7 +6384,7 @@ export default class Client extends OpenApi {
|
|
|
6298
6384
|
*/
|
|
6299
6385
|
listVirtualPhysicalConnectionsWithOptions(request: $_model.ListVirtualPhysicalConnectionsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListVirtualPhysicalConnectionsResponse>;
|
|
6300
6386
|
/**
|
|
6301
|
-
* Queries information about shared Express Connect circuits
|
|
6387
|
+
* Queries information about shared Express Connect circuits.
|
|
6302
6388
|
*
|
|
6303
6389
|
* @param request - ListVirtualPhysicalConnectionsRequest
|
|
6304
6390
|
* @returns ListVirtualPhysicalConnectionsResponse
|
|
@@ -6355,7 +6441,7 @@ export default class Client extends OpenApi {
|
|
|
6355
6441
|
* @remarks
|
|
6356
6442
|
* When you call **ListVpnCertificateAssociations**:
|
|
6357
6443
|
* - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
|
|
6358
|
-
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified
|
|
6444
|
+
* - 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.
|
|
6359
6445
|
* - 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.
|
|
6360
6446
|
* - 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.
|
|
6361
6447
|
*
|
|
@@ -6370,7 +6456,7 @@ export default class Client extends OpenApi {
|
|
|
6370
6456
|
* @remarks
|
|
6371
6457
|
* When you call **ListVpnCertificateAssociations**:
|
|
6372
6458
|
* - If you specify only the **RegionId** parameter, all associations between VPN gateway instances and SSL certificates in the specified region are queried.
|
|
6373
|
-
* - If you specify the **RegionId** and **CertificateType** parameters, the associations between VPN gateway instances and SSL certificates of the specified
|
|
6459
|
+
* - 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.
|
|
6374
6460
|
* - 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.
|
|
6375
6461
|
* - 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.
|
|
6376
6462
|
*
|
|
@@ -6484,7 +6570,7 @@ export default class Client extends OpenApi {
|
|
|
6484
6570
|
*/
|
|
6485
6571
|
modifyCommonBandwidthPackageSpec(request: $_model.ModifyCommonBandwidthPackageSpecRequest): Promise<$_model.ModifyCommonBandwidthPackageSpecResponse>;
|
|
6486
6572
|
/**
|
|
6487
|
-
* Modifies the configuration of a customer gateway
|
|
6573
|
+
* Modifies the configuration of a customer gateway.
|
|
6488
6574
|
*
|
|
6489
6575
|
* @remarks
|
|
6490
6576
|
* - 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:
|
|
@@ -6499,7 +6585,7 @@ export default class Client extends OpenApi {
|
|
|
6499
6585
|
*/
|
|
6500
6586
|
modifyCustomerGatewayAttributeWithOptions(request: $_model.ModifyCustomerGatewayAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyCustomerGatewayAttributeResponse>;
|
|
6501
6587
|
/**
|
|
6502
|
-
* Modifies the configuration of a customer gateway
|
|
6588
|
+
* Modifies the configuration of a customer gateway.
|
|
6503
6589
|
*
|
|
6504
6590
|
* @remarks
|
|
6505
6591
|
* - 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:
|
|
@@ -6573,12 +6659,12 @@ export default class Client extends OpenApi {
|
|
|
6573
6659
|
*/
|
|
6574
6660
|
modifyExpressCloudConnectionBandwidth(request: $_model.ModifyExpressCloudConnectionBandwidthRequest): Promise<$_model.ModifyExpressCloudConnectionBandwidthResponse>;
|
|
6575
6661
|
/**
|
|
6576
|
-
*
|
|
6662
|
+
* Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
|
|
6577
6663
|
*
|
|
6578
6664
|
* @remarks
|
|
6579
6665
|
* - 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.
|
|
6580
|
-
* - When associating dedicated Express Connect circuits, only full
|
|
6581
|
-
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must
|
|
6666
|
+
* - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
|
|
6667
|
+
* - 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.
|
|
6582
6668
|
* - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
|
|
6583
6669
|
* - 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.
|
|
6584
6670
|
*
|
|
@@ -6588,12 +6674,12 @@ export default class Client extends OpenApi {
|
|
|
6588
6674
|
*/
|
|
6589
6675
|
modifyExpressConnectTrafficQosWithOptions(request: $_model.ModifyExpressConnectTrafficQosRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyExpressConnectTrafficQosResponse>;
|
|
6590
6676
|
/**
|
|
6591
|
-
*
|
|
6677
|
+
* Modifies an Express Connect Quality of Service (QoS) policy. You can also use this operation to associate dedicated Express Connect circuits with the policy.
|
|
6592
6678
|
*
|
|
6593
6679
|
* @remarks
|
|
6594
6680
|
* - 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.
|
|
6595
|
-
* - When associating dedicated Express Connect circuits, only full
|
|
6596
|
-
* - If a dedicated Express Connect circuit has shared Express Connect circuits or cross-account VBRs, you must
|
|
6681
|
+
* - When associating dedicated Express Connect circuits, only full replacement is supported. To disassociate all circuits, pass an empty string.
|
|
6682
|
+
* - 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.
|
|
6597
6683
|
* - The device on which the dedicated Express Connect circuit resides must support the QoS feature before association.
|
|
6598
6684
|
* - 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.
|
|
6599
6685
|
*
|
|
@@ -7021,13 +7107,13 @@ export default class Client extends OpenApi {
|
|
|
7021
7107
|
*/
|
|
7022
7108
|
modifyNetworkAclAttributes(request: $_model.ModifyNetworkAclAttributesRequest): Promise<$_model.ModifyNetworkAclAttributesResponse>;
|
|
7023
7109
|
/**
|
|
7024
|
-
* Modifies the
|
|
7110
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
7025
7111
|
*
|
|
7026
7112
|
* @remarks
|
|
7027
7113
|
* When you call this operation, note the following items:
|
|
7028
7114
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
7029
7115
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
7030
|
-
* -
|
|
7116
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
7031
7117
|
*
|
|
7032
7118
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
7033
7119
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7035,13 +7121,13 @@ export default class Client extends OpenApi {
|
|
|
7035
7121
|
*/
|
|
7036
7122
|
modifyPhysicalConnectionAttributeWithOptions(request: $_model.ModifyPhysicalConnectionAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyPhysicalConnectionAttributeResponse>;
|
|
7037
7123
|
/**
|
|
7038
|
-
* Modifies the
|
|
7124
|
+
* Modifies the configurations of an Express Connect circuit.
|
|
7039
7125
|
*
|
|
7040
7126
|
* @remarks
|
|
7041
7127
|
* When you call this operation, note the following items:
|
|
7042
7128
|
* - You can modify the specifications and redundant circuit ID only for Express Connect circuits in the **Initial**, **Enabled**, or **Rejected** state.
|
|
7043
7129
|
* - You cannot modify Express Connect circuits in the **Canceled**, **Allocating**, **AllocationFailed**, or **Terminated** state.
|
|
7044
|
-
* -
|
|
7130
|
+
* - After an Express Connect circuit in the **Rejected** state is modified, it enters the **Initial** state.
|
|
7045
7131
|
*
|
|
7046
7132
|
* @param request - ModifyPhysicalConnectionAttributeRequest
|
|
7047
7133
|
* @returns ModifyPhysicalConnectionAttributeResponse
|
|
@@ -7182,15 +7268,15 @@ export default class Client extends OpenApi {
|
|
|
7182
7268
|
*/
|
|
7183
7269
|
modifySslVpnClientCert(request: $_model.ModifySslVpnClientCertRequest): Promise<$_model.ModifySslVpnClientCertResponse>;
|
|
7184
7270
|
/**
|
|
7185
|
-
* Modifies the configuration of an SSL-VPN server.
|
|
7271
|
+
* Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
|
|
7186
7272
|
*
|
|
7187
7273
|
* @remarks
|
|
7188
|
-
* - If you want to enable two-factor
|
|
7189
|
-
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify
|
|
7190
|
-
* - When **ModifySslVpnServer** is asynchronous, the system returns a request ID
|
|
7274
|
+
* - 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).
|
|
7275
|
+
* - 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.
|
|
7276
|
+
* - 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:
|
|
7191
7277
|
* - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
|
|
7192
7278
|
* - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
|
|
7193
|
-
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the
|
|
7279
|
+
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
|
|
7194
7280
|
*
|
|
7195
7281
|
* @param request - ModifySslVpnServerRequest
|
|
7196
7282
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7198,15 +7284,15 @@ export default class Client extends OpenApi {
|
|
|
7198
7284
|
*/
|
|
7199
7285
|
modifySslVpnServerWithOptions(request: $_model.ModifySslVpnServerRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifySslVpnServerResponse>;
|
|
7200
7286
|
/**
|
|
7201
|
-
* Modifies the configuration of an SSL-VPN server.
|
|
7287
|
+
* Modifies the configuration of an SSL-VPN server by calling the ModifySslVpnServer operation.
|
|
7202
7288
|
*
|
|
7203
7289
|
* @remarks
|
|
7204
|
-
* - If you want to enable two-factor
|
|
7205
|
-
* - When you modify only the **Name** of the SSL-VPN server, this operation is synchronous. If you modify
|
|
7206
|
-
* - When **ModifySslVpnServer** is asynchronous, the system returns a request ID
|
|
7290
|
+
* - 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).
|
|
7291
|
+
* - 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.
|
|
7292
|
+
* - 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:
|
|
7207
7293
|
* - If the VPN gateway instance is in the **updating** state, the configuration of the SSL-VPN server is being modified.
|
|
7208
7294
|
* - If the VPN gateway instance is in the **active** state, the configuration of the SSL-VPN server has been modified.
|
|
7209
|
-
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the
|
|
7295
|
+
* - The **ModifySslVpnServer** operation does not support concurrent modifications to the SSL-VPN server configuration under the same VPN gateway.
|
|
7210
7296
|
*
|
|
7211
7297
|
* @param request - ModifySslVpnServerRequest
|
|
7212
7298
|
* @returns ModifySslVpnServerResponse
|
|
@@ -7302,7 +7388,7 @@ export default class Client extends OpenApi {
|
|
|
7302
7388
|
* @remarks
|
|
7303
7389
|
* - **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:
|
|
7304
7390
|
* - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
|
|
7305
|
-
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry
|
|
7391
|
+
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
|
|
7306
7392
|
* - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
|
|
7307
7393
|
*
|
|
7308
7394
|
* @param request - ModifyVcoRouteEntryWeightRequest
|
|
@@ -7316,7 +7402,7 @@ export default class Client extends OpenApi {
|
|
|
7316
7402
|
* @remarks
|
|
7317
7403
|
* - **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:
|
|
7318
7404
|
* - If the IPsec-VPN connection is in the **updating** state, the weight of the destination route entry is being modified.
|
|
7319
|
-
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry
|
|
7405
|
+
* - If the IPsec-VPN connection is in the **attached** state, the weight of the destination route entry is modified.
|
|
7320
7406
|
* - **ModifyVcoRouteEntryWeight** does not support concurrent modifications of destination route entry weights for the same IPsec-VPN connection.
|
|
7321
7407
|
*
|
|
7322
7408
|
* @param request - ModifyVcoRouteEntryWeightRequest
|
|
@@ -7377,6 +7463,21 @@ export default class Client extends OpenApi {
|
|
|
7377
7463
|
* @returns ModifyVpcAttributeResponse
|
|
7378
7464
|
*/
|
|
7379
7465
|
modifyVpcAttribute(request: $_model.ModifyVpcAttributeRequest): Promise<$_model.ModifyVpcAttributeResponse>;
|
|
7466
|
+
/**
|
|
7467
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
7468
|
+
*
|
|
7469
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
7470
|
+
* @param runtime - runtime options for this request RuntimeOptions
|
|
7471
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
7472
|
+
*/
|
|
7473
|
+
modifyVpcCidrBlockWithOptions(request: $_model.ModifyVpcCidrBlockRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyVpcCidrBlockResponse>;
|
|
7474
|
+
/**
|
|
7475
|
+
* Modifies the primary or secondary CIDR block of a VPC.
|
|
7476
|
+
*
|
|
7477
|
+
* @param request - ModifyVpcCidrBlockRequest
|
|
7478
|
+
* @returns ModifyVpcCidrBlockResponse
|
|
7479
|
+
*/
|
|
7480
|
+
modifyVpcCidrBlock(request: $_model.ModifyVpcCidrBlockRequest): Promise<$_model.ModifyVpcCidrBlockResponse>;
|
|
7380
7481
|
/**
|
|
7381
7482
|
* Modifies the configuration of a prefix list.
|
|
7382
7483
|
*
|
|
@@ -7410,13 +7511,13 @@ export default class Client extends OpenApi {
|
|
|
7410
7511
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7411
7512
|
*
|
|
7412
7513
|
* @remarks
|
|
7413
|
-
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7414
|
-
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7415
|
-
* - **ModifyVpnAttachmentAttribute** is
|
|
7514
|
+
* - 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**.
|
|
7515
|
+
* - 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**.
|
|
7516
|
+
* - 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:
|
|
7416
7517
|
* - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
|
|
7417
7518
|
* - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
|
|
7418
|
-
* - **ModifyVpnAttachmentAttribute** does not support concurrent
|
|
7419
|
-
* - When you call **ModifyVpnAttachmentAttribute
|
|
7519
|
+
* - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
|
|
7520
|
+
* - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
|
|
7420
7521
|
*
|
|
7421
7522
|
* @param request - ModifyVpnAttachmentAttributeRequest
|
|
7422
7523
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7427,13 +7528,13 @@ export default class Client extends OpenApi {
|
|
|
7427
7528
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7428
7529
|
*
|
|
7429
7530
|
* @remarks
|
|
7430
|
-
* - When you modify a dual-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7431
|
-
* - When you modify a single-tunnel IPsec-VPN connection, in addition to the required parameters,
|
|
7432
|
-
* - **ModifyVpnAttachmentAttribute** is
|
|
7531
|
+
* - 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**.
|
|
7532
|
+
* - 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**.
|
|
7533
|
+
* - 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:
|
|
7433
7534
|
* - If the IPsec-VPN connection is in the **updating** state, the configuration is being modified.
|
|
7434
7535
|
* - If the IPsec-VPN connection is in the **attached** state, the configuration has been modified.
|
|
7435
|
-
* - **ModifyVpnAttachmentAttribute** does not support concurrent
|
|
7436
|
-
* - When you call **ModifyVpnAttachmentAttribute
|
|
7536
|
+
* - The **ModifyVpnAttachmentAttribute** operation does not support concurrent modifications to the IPsec-VPN connection configuration.
|
|
7537
|
+
* - When you call the **ModifyVpnAttachmentAttribute** operation, you cannot modify the gateway type of the IPsec-VPN connection.
|
|
7437
7538
|
*
|
|
7438
7539
|
* @param request - ModifyVpnAttachmentAttributeRequest
|
|
7439
7540
|
* @returns ModifyVpnAttachmentAttributeResponse
|
|
@@ -7443,14 +7544,11 @@ export default class Client extends OpenApi {
|
|
|
7443
7544
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7444
7545
|
*
|
|
7445
7546
|
* @remarks
|
|
7446
|
-
* - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7547
|
+
* - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7447
7548
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
7448
|
-
* - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7549
|
+
* - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7449
7550
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
|
|
7450
|
-
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID
|
|
7451
|
-
* - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
|
|
7452
|
-
* - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
|
|
7453
|
-
* - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
|
|
7551
|
+
* - 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:
|
|
7454
7552
|
*
|
|
7455
7553
|
* @param request - ModifyVpnConnectionAttributeRequest
|
|
7456
7554
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7461,14 +7559,11 @@ export default class Client extends OpenApi {
|
|
|
7461
7559
|
* Modifies the configuration of an IPsec-VPN connection.
|
|
7462
7560
|
*
|
|
7463
7561
|
* @remarks
|
|
7464
|
-
* - To modify a dual-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7562
|
+
* - To modify a dual-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7465
7563
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **AutoConfigRoute**, **TunnelOptionsSpecification** array, and **EnableTunnelsBgp**.
|
|
7466
|
-
* - To modify a single-tunnel IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7564
|
+
* - To modify a single-tunnel mode IPsec-VPN connection, the `ModifyVpnConnectionAttribute` operation supports the following request parameters in addition to the required parameters:
|
|
7467
7565
|
* **ClientToken**, **Name**, **LocalSubnet**, **RemoteSubnet**, **EffectImmediately**, **IkeConfig**, **IpsecConfig**, **HealthCheckConfig**, **AutoConfigRoute**, **EnableDpd**, **EnableNatTraversal**, **BgpConfig**, and **RemoteCaCertificate**.
|
|
7468
|
-
* - The **ModifyVpnConnectionAttribute** operation is asynchronous. After a request is sent, the system returns a request ID
|
|
7469
|
-
* - If the VPN gateway instance is in the **updating** state, the configuration of the IPsec-VPN connection is being modified.
|
|
7470
|
-
* - If the VPN gateway instance is in the **active** state, the configuration of the IPsec-VPN connection is modified.
|
|
7471
|
-
* - The **ModifyVpnConnectionAttribute** operation does not support concurrent modifications to IPsec-VPN connection configurations under the same VPN gateway.
|
|
7566
|
+
* - 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:
|
|
7472
7567
|
*
|
|
7473
7568
|
* @param request - ModifyVpnConnectionAttributeRequest
|
|
7474
7569
|
* @returns ModifyVpnConnectionAttributeResponse
|
|
@@ -7478,7 +7573,7 @@ export default class Client extends OpenApi {
|
|
|
7478
7573
|
* Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
|
|
7479
7574
|
*
|
|
7480
7575
|
* @remarks
|
|
7481
|
-
* - **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:
|
|
7576
|
+
* - **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:
|
|
7482
7577
|
* - If the VPN gateway is in the **updating** state, the configuration is being modified.
|
|
7483
7578
|
* - If the VPN gateway is in the **active** state, the configuration has been modified.
|
|
7484
7579
|
* - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
|
|
@@ -7492,7 +7587,7 @@ export default class Client extends OpenApi {
|
|
|
7492
7587
|
* Invokes the ModifyVpnGatewayAttribute operation to modify the name, description, or routing automatic propagation feature of a VPN gateway.
|
|
7493
7588
|
*
|
|
7494
7589
|
* @remarks
|
|
7495
|
-
* - **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:
|
|
7590
|
+
* - **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:
|
|
7496
7591
|
* - If the VPN gateway is in the **updating** state, the configuration is being modified.
|
|
7497
7592
|
* - If the VPN gateway is in the **active** state, the configuration has been modified.
|
|
7498
7593
|
* - **ModifyVpnGatewayAttribute** does not support concurrent modifications to the configuration of the same VPN gateway.
|
|
@@ -7539,13 +7634,13 @@ export default class Client extends OpenApi {
|
|
|
7539
7634
|
*/
|
|
7540
7635
|
modifyVpnPbrRouteEntryAttribute(request: $_model.ModifyVpnPbrRouteEntryAttributeRequest): Promise<$_model.ModifyVpnPbrRouteEntryAttributeResponse>;
|
|
7541
7636
|
/**
|
|
7542
|
-
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing
|
|
7637
|
+
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
|
|
7543
7638
|
*
|
|
7544
7639
|
* @remarks
|
|
7545
|
-
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID,
|
|
7546
|
-
* - If the VPN gateway instance is in the **updating** state, the policy-based routing
|
|
7547
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based routing
|
|
7548
|
-
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing
|
|
7640
|
+
* - **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:
|
|
7641
|
+
* - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
|
|
7642
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
|
|
7643
|
+
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
|
|
7549
7644
|
*
|
|
7550
7645
|
* @param request - ModifyVpnPbrRouteEntryPriorityRequest
|
|
7551
7646
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7553,13 +7648,13 @@ export default class Client extends OpenApi {
|
|
|
7553
7648
|
*/
|
|
7554
7649
|
modifyVpnPbrRouteEntryPriorityWithOptions(request: $_model.ModifyVpnPbrRouteEntryPriorityRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ModifyVpnPbrRouteEntryPriorityResponse>;
|
|
7555
7650
|
/**
|
|
7556
|
-
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing
|
|
7651
|
+
* Invokes the ModifyVpnPbrRouteEntryPriority operation to modify the policy priority of a policy-based routing.
|
|
7557
7652
|
*
|
|
7558
7653
|
* @remarks
|
|
7559
|
-
* - **ModifyVpnPbrRouteEntryPriority** is an asynchronous operation. After you send a request, the system returns a request ID,
|
|
7560
|
-
* - If the VPN gateway instance is in the **updating** state, the policy-based routing
|
|
7561
|
-
* - If the VPN gateway instance is in the **active** state, the policy-based routing
|
|
7562
|
-
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing
|
|
7654
|
+
* - **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:
|
|
7655
|
+
* - If the VPN gateway instance is in the **updating** state, the policy-based routing is being modified.
|
|
7656
|
+
* - If the VPN gateway instance is in the **active** state, the policy-based routing has been modified.
|
|
7657
|
+
* - **ModifyVpnPbrRouteEntryPriority** does not support concurrent modifications of policy-based routing on the same VPN gateway instance.
|
|
7563
7658
|
*
|
|
7564
7659
|
* @param request - ModifyVpnPbrRouteEntryPriorityRequest
|
|
7565
7660
|
* @returns ModifyVpnPbrRouteEntryPriorityResponse
|
|
@@ -7600,12 +7695,12 @@ export default class Client extends OpenApi {
|
|
|
7600
7695
|
* Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
|
|
7601
7696
|
*
|
|
7602
7697
|
* @remarks
|
|
7603
|
-
* > 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
|
|
7698
|
+
* > 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.
|
|
7604
7699
|
* - 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).
|
|
7605
|
-
* -
|
|
7700
|
+
* - **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:
|
|
7606
7701
|
* - If the VPN destination route is in the **updating** state, the weight is being modified.
|
|
7607
|
-
* - If the VPN destination route is in the **active** state, the weight
|
|
7608
|
-
* -
|
|
7702
|
+
* - If the VPN destination route is in the **active** state, the weight has been modified.
|
|
7703
|
+
* - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
|
|
7609
7704
|
*
|
|
7610
7705
|
* @param request - ModifyVpnRouteEntryWeightRequest
|
|
7611
7706
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7616,12 +7711,12 @@ export default class Client extends OpenApi {
|
|
|
7616
7711
|
* Modifies the weight of a destination route by calling the ModifyVpnRouteEntryWeight operation.
|
|
7617
7712
|
*
|
|
7618
7713
|
* @remarks
|
|
7619
|
-
* > 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
|
|
7714
|
+
* > 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.
|
|
7620
7715
|
* - 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).
|
|
7621
|
-
* -
|
|
7716
|
+
* - **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:
|
|
7622
7717
|
* - If the VPN destination route is in the **updating** state, the weight is being modified.
|
|
7623
|
-
* - If the VPN destination route is in the **active** state, the weight
|
|
7624
|
-
* -
|
|
7718
|
+
* - If the VPN destination route is in the **active** state, the weight has been modified.
|
|
7719
|
+
* - **ModifyVpnRouteEntryWeight** does not support concurrent modification of destination route weights on the same VPN gateway.
|
|
7625
7720
|
*
|
|
7626
7721
|
* @param request - ModifyVpnRouteEntryWeightRequest
|
|
7627
7722
|
* @returns ModifyVpnRouteEntryWeightResponse
|
|
@@ -7631,7 +7726,7 @@ export default class Client extends OpenApi {
|
|
|
7631
7726
|
* Modifies the resource group to which a cloud resource belongs.
|
|
7632
7727
|
*
|
|
7633
7728
|
* @remarks
|
|
7634
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
7729
|
+
* The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
|
|
7635
7730
|
*
|
|
7636
7731
|
* @param request - MoveResourceGroupRequest
|
|
7637
7732
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -7642,7 +7737,7 @@ export default class Client extends OpenApi {
|
|
|
7642
7737
|
* Modifies the resource group to which a cloud resource belongs.
|
|
7643
7738
|
*
|
|
7644
7739
|
* @remarks
|
|
7645
|
-
* The **ChangeResourceGroup** operation does not support concurrent modifications
|
|
7740
|
+
* The **ChangeResourceGroup** operation does not support concurrent modifications of the resource group for Express Connect circuit resources within the same Express Connect circuit instance.
|
|
7646
7741
|
*
|
|
7647
7742
|
* @param request - MoveResourceGroupRequest
|
|
7648
7743
|
* @returns MoveResourceGroupResponse
|
|
@@ -7828,16 +7923,16 @@ export default class Client extends OpenApi {
|
|
|
7828
7923
|
*/
|
|
7829
7924
|
recoverVirtualBorderRouter(request: $_model.RecoverVirtualBorderRouterRequest): Promise<$_model.RecoverVirtualBorderRouterResponse>;
|
|
7830
7925
|
/**
|
|
7831
|
-
* Releases a specified
|
|
7926
|
+
* Releases a specified elastic IP address (EIP).
|
|
7832
7927
|
*
|
|
7833
7928
|
* @remarks
|
|
7834
|
-
* Before you invoke this operation, take note of the following
|
|
7835
|
-
* - Before
|
|
7929
|
+
* Before you invoke this operation, take note of the following information:
|
|
7930
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
7836
7931
|
* - Only EIPs in the **Available** state can be released.
|
|
7837
7932
|
* - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
|
|
7838
|
-
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
7839
|
-
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
|
|
7840
|
-
* - If the EIP instance cannot be found, the EIP instance
|
|
7933
|
+
* - 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:
|
|
7934
|
+
* - 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.
|
|
7935
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
7841
7936
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
7842
7937
|
*
|
|
7843
7938
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -7846,16 +7941,16 @@ export default class Client extends OpenApi {
|
|
|
7846
7941
|
*/
|
|
7847
7942
|
releaseEipAddressWithOptions(request: $_model.ReleaseEipAddressRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ReleaseEipAddressResponse>;
|
|
7848
7943
|
/**
|
|
7849
|
-
* Releases a specified
|
|
7944
|
+
* Releases a specified elastic IP address (EIP).
|
|
7850
7945
|
*
|
|
7851
7946
|
* @remarks
|
|
7852
|
-
* Before you invoke this operation, take note of the following
|
|
7853
|
-
* - Before
|
|
7947
|
+
* Before you invoke this operation, take note of the following information:
|
|
7948
|
+
* - Before you release an EIP, make sure that the following conditions are met:
|
|
7854
7949
|
* - Only EIPs in the **Available** state can be released.
|
|
7855
7950
|
* - Only EIPs that use the pay-as-you-go billing method can be released. Subscription EIPs cannot be released.
|
|
7856
|
-
* - The **ReleaseEipAddress** operation is asynchronous. After you send a request, the system returns a request ID,
|
|
7857
|
-
* - If the EIP instance is in the **Releasing** state, the EIP instance is being released. In this state, you can only execute query operations.
|
|
7858
|
-
* - If the EIP instance cannot be found, the EIP instance
|
|
7951
|
+
* - 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:
|
|
7952
|
+
* - 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.
|
|
7953
|
+
* - If the EIP instance cannot be found, the EIP instance is released.
|
|
7859
7954
|
* - The **ReleaseEipAddress** operation does not support concurrent release of the same EIP instance.
|
|
7860
7955
|
*
|
|
7861
7956
|
* @param request - ReleaseEipAddressRequest
|
|
@@ -8474,10 +8569,10 @@ export default class Client extends OpenApi {
|
|
|
8474
8569
|
*/
|
|
8475
8570
|
unassociateRouteTable(request: $_model.UnassociateRouteTableRequest): Promise<$_model.UnassociateRouteTableResponse>;
|
|
8476
8571
|
/**
|
|
8477
|
-
*
|
|
8572
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
8478
8573
|
*
|
|
8479
8574
|
* @remarks
|
|
8480
|
-
* - Before
|
|
8575
|
+
* - 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).
|
|
8481
8576
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
8482
8577
|
*
|
|
8483
8578
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -8486,10 +8581,10 @@ export default class Client extends OpenApi {
|
|
|
8486
8581
|
*/
|
|
8487
8582
|
unassociateVpcCidrBlockWithOptions(request: $_model.UnassociateVpcCidrBlockRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UnassociateVpcCidrBlockResponse>;
|
|
8488
8583
|
/**
|
|
8489
|
-
*
|
|
8584
|
+
* Invokes UnassociateVpcCidrBlock to delete a secondary CIDR block from a VPC.
|
|
8490
8585
|
*
|
|
8491
8586
|
* @remarks
|
|
8492
|
-
* - Before
|
|
8587
|
+
* - 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).
|
|
8493
8588
|
* - The **UnassociateVpcCidrBlock** operation does not support concurrently deleting secondary CIDR blocks from the same VPC.
|
|
8494
8589
|
*
|
|
8495
8590
|
* @param request - UnassociateVpcCidrBlockRequest
|
|
@@ -8512,7 +8607,7 @@ export default class Client extends OpenApi {
|
|
|
8512
8607
|
*/
|
|
8513
8608
|
untagResourcesForExpressConnect(request: $_model.UntagResourcesForExpressConnectRequest): Promise<$_model.UntagResourcesForExpressConnectResponse>;
|
|
8514
8609
|
/**
|
|
8515
|
-
* Modifies the configuration of a DHCP options set
|
|
8610
|
+
* Modifies the configuration of a DHCP options set.
|
|
8516
8611
|
*
|
|
8517
8612
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
8518
8613
|
* @param runtime - runtime options for this request RuntimeOptions
|
|
@@ -8520,7 +8615,7 @@ export default class Client extends OpenApi {
|
|
|
8520
8615
|
*/
|
|
8521
8616
|
updateDhcpOptionsSetAttributeWithOptions(request: $_model.UpdateDhcpOptionsSetAttributeRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UpdateDhcpOptionsSetAttributeResponse>;
|
|
8522
8617
|
/**
|
|
8523
|
-
* Modifies the configuration of a DHCP options set
|
|
8618
|
+
* Modifies the configuration of a DHCP options set.
|
|
8524
8619
|
*
|
|
8525
8620
|
* @param request - UpdateDhcpOptionsSetAttributeRequest
|
|
8526
8621
|
* @returns UpdateDhcpOptionsSetAttributeResponse
|
|
@@ -8590,7 +8685,7 @@ export default class Client extends OpenApi {
|
|
|
8590
8685
|
*/
|
|
8591
8686
|
updateGatewayRouteTableEntryAttribute(request: $_model.UpdateGatewayRouteTableEntryAttributeRequest): Promise<$_model.UpdateGatewayRouteTableEntryAttributeResponse>;
|
|
8592
8687
|
/**
|
|
8593
|
-
*
|
|
8688
|
+
* Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
|
|
8594
8689
|
*
|
|
8595
8690
|
* @remarks
|
|
8596
8691
|
* - 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.
|
|
@@ -8605,7 +8700,7 @@ export default class Client extends OpenApi {
|
|
|
8605
8700
|
*/
|
|
8606
8701
|
updateIpsecServerWithOptions(request: $_model.UpdateIpsecServerRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UpdateIpsecServerResponse>;
|
|
8607
8702
|
/**
|
|
8608
|
-
*
|
|
8703
|
+
* Calls the UpdateIpsecServer operation to update the configuration of an IPsec server.
|
|
8609
8704
|
*
|
|
8610
8705
|
* @remarks
|
|
8611
8706
|
* - 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.
|