tencent cloud

DetachLoadBalancers
Download PDF
Last updated: 2024-11-27 15:17:35
DetachLoadBalancers
Last updated: 2024-11-27 15:17:35
Download PDF

1. API Description

Domain name for API request: as.intl.tencentcloudapi.com.

This API is used to unbind one or more CLBs from a scaling group. This API will not terminate CLBs.

A maximum of 20 requests can be initiated per second for this API.

We recommend you to use API Explorer
Try it
API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

2. Input Parameters

The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

Parameter Name Required Type Description
Action Yes String Common Params. The value used for this API: DetachLoadBalancers.
Version Yes String Common Params. The value used for this API: 2018-04-19.
Region Yes String Common Params. For more information, please see the list of regions supported by the product.
AutoScalingGroupId Yes String Scaling group ID
LoadBalancerIds.N No Array of String List of classic CLB IDs. Up to 20 IDs are allowed. LoadBalancerIds and ForwardLoadBalancerIdentifications cannot be specified at the same time.
ForwardLoadBalancerIdentifications.N No Array of ForwardLoadBalancerIdentification List of application CLB IDs. Up to 100 IDs are allowed. LoadBalancerIds and ForwardLoadBalancerIdentifications cannot be specified at the same time.

3. Output Parameters

Parameter Name Type Description
ActivityId String Scaling activity ID
RequestId String The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

4. Example

Example1 Unbinding the classic CLB lb-crhgatrf from the security group

Input Example

POST / HTTP/1.1
Host: as.intl.tencentcloudapi.com
Content-Type: application/json
X-TC-Action: DetachLoadBalancers
<Common request parameters>

{
    "AutoScalingGroupId": "asg-12wjuh0s",
    "LoadBalancerIds": [
        "lb-crhgatrf"
    ]
}

Output Example

{
    "Response": {
        "ActivityId": "asa-67izy66g",
        "RequestId": "bd3c91e8-3051-4c02-ac58-54d47b9c9d63"
    }
}

Example2 Unbinding the application CLB lb-23aejgcv (listener: lbl-ncw704sn, forwarding rule ID: loc-l3hmaev9) from the security group

Input Example

POST / HTTP/1.1
Host: as.intl.tencentcloudapi.com
Content-Type: application/json
X-TC-Action: DetachLoadBalancers
<Common request parameters>

{
    "AutoScalingGroupId": "asg-12wjuh0s",
    "ForwardLoadBalancerIdentifications": [
        {
            "LocationId": "loc-l3hmaev9",
            "ListenerId": "lbl-ncw704sn",
            "LoadBalancerId": "lb-23aejgcv"
        }
    ]
}

Output Example

{
    "Response": {
        "ActivityId": "asa-9asddelc",
        "RequestId": "8d78668d-61eb-456d-855b-f34f91371089"
    }
}

5. Developer Resources

SDK

TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

Command Line Interface

6. Error Code

The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

Error Code Description
FailedOperation.NoActivityToGenerate No scaling activity is generated.
InternalError.RequestError An internal request error occurred.
InvalidParameter.ActionNotFound Invalid Action request.
InvalidParameter.Conflict Multiple parameters specified conflict and cannot co-exist.
InvalidParameter.InScenario The parameter is invalid in a specific scenario.
InvalidParameter.LoadBalancerNotInAutoScalingGroup The specified CLB does not exist in the current scaling group.
InvalidParameter.MustOneParameter A parameter is missing. One of the two parameters must be specified.
InvalidParameterValue.ClassicLb A classic CLB should be specified.
InvalidParameterValue.ForwardLb A CLB should be specified.
InvalidParameterValue.InvalidAutoScalingGroupId Invalid scaling group ID.
InvalidParameterValue.InvalidClbRegion The regions specified for CLB is invalid.
LimitExceeded.AfterAttachLbLimitExceeded Binding with the specified CLBs will make the total number of bound CLBs exceeds the upper limit.
MissingParameter.InScenario A parameter is missing in a specific scenario.
ResourceNotFound.AutoScalingGroupNotFound The scaling group does not exist.
ResourceNotFound.ListenerNotFound The specified listener does not exist.
ResourceNotFound.LoadBalancerNotFound The specified load balancer was not found.
ResourceNotFound.LoadBalancerNotInAutoScalingGroup The specified CLB does not exist in the current scaling group.
ResourceNotFound.LocationNotFound The specified location does not exist.
ResourceUnavailable.AutoScalingGroupInActivity The auto scaling group is active.
ResourceUnavailable.LbBackendRegionInconsistent The backend region of the CLB is not the same as the one for AS service.
ResourceUnavailable.LbProjectInconsistent The CLBs are not in the same project.
ResourceUnavailable.LbVpcInconsistent The CLB and scaling group should reside in the same VPC.
ResourceUnavailable.LoadBalancerInOperation CLB is active in the scaling group.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback