Adds one or more load balancing instances.
Operation description
Operation description
You must meet the following conditions when you add load balancing instances to a scaling group:
-
The load balancing instances and the scaling group must belong to the same Alibaba Cloud account and region.
-
The load balancing instances must be in the
Runningstate. -
Each load balancing instance must be configured with at least one listener and have health checks enabled.
-
If the network type of both the load balancing instances and the scaling group is VPC, they must be in the same VPC.
-
If the network type of the scaling group is VPC and the network type of the load balancing instances is classic network, and the backend servers of the load balancing instances include VPC-connected instances, these VPC-connected instances must be in the same VPC as the scaling group.
-
The number of load balancing instances associated with the scaling group does not exceed the quota limit. For more information about the quota limit, see Limits.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
ess:AttachLoadBalancers |
update |
*ScalingGroup
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| ScalingGroupId |
string |
Yes |
The ID of the scaling group. |
asg-bp1avr6ensitts3w**** |
| ForceAttach |
boolean |
No |
Specifies whether to add all instances in the current scaling group as backend servers of the load balancing CLB (formerly SLB) instances. Valid values:
Default value: false. |
false |
| ClientToken |
string |
No |
Ensures the idempotence of the request. You can generate the parameter value on your client to ensure that the value is unique across different requests. The value can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see How to ensure idempotence. |
123e4567-e89b-12d3-a456-42665544**** |
| Async |
boolean |
No |
Specifies whether to use asynchronous invocation when you add load balancing CLB (formerly SLB) instances. Asynchronous invocation ensures the transactionality of operations. This means that either all operations are executed successfully, or if any operation fails, the execution results of all operations do not take effect. We recommend that you use asynchronous invocation. Valid values:
Default value: false. |
false |
| LoadBalancer |
array |
No |
The IDs of the load balancing CLB (formerly SLB) instances to be added. Valid values of N: 1 to 5. |
lb-2zeur05gfs**** |
|
string |
No |
The IDs of the load balancing CLB (formerly SLB) instances to be added. Valid values of N: 1 to 5. Note
You can add up to five load balancing instances to the scaling group at a time. |
lb-2zeur05gfs**** |
|
| LoadBalancerConfig |
array<object> |
No |
The configurations of the load balancing CLB (formerly SLB) instances. |
|
|
object |
No |
The configurations of the load balancing CLB (formerly SLB) instances. |
||
| LoadBalancerId |
string |
No |
The ID of the load balancing CLB (formerly SLB) instance. |
147b46d767c-cn-qingdao-cm5**** |
| Weight |
integer |
No |
The weight of the ECS instance or ECI instance as a backend server after Auto Scaling adds the ECS instance or ECI instance to the CLB server group. A higher weight indicates that the ECS instance or ECI instance is assigned more access requests. If the weight is 0, the ECS instance or ECI instance does not receive access requests. Valid values: 0 to 100. |
10 |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
|||
| ScalingActivityId |
string |
The ID of the scaling activity. This parameter is returned only when |
asa-bp140qd7mak8k63f**** |
| RequestId |
string |
The ID of the request. |
473469C7-AA6F-4DC5-B3DB-A3DC0DE3**** |
Examples
Success response
JSON format
{
"ScalingActivityId": "asa-bp140qd7mak8k63f****",
"RequestId": "473469C7-AA6F-4DC5-B3DB-A3DC0DE3****"
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.