Auto Scaling:Troubleshoot scaling activity exceptions

Error message

Cause

Solution

DBInstanceIdentifier does not refer to an existing DB instance.(xxxx)

The ApsaraDB RDS instance attached to the scaling group does not exist.

Verify that the ApsaraDB RDS instance attached to the scaling group exists.

The current status of the load balancer xxxxx does not support this action.

The Server Load Balancer (SLB) instance is not in the Active state.

Verify that the SLB instance attached to the scaling group is in the Active state.

To execute the specified scaling rule, the total capacity will not change.

The number of instances in a scaling group must remain within the defined minimum and maximum limits. Any scaling activity that causes the instance count to exceed these limits will be rejected.

Check the current instance count and scaling rule configuration. Make sure the post-scaling count stays within the configured min and max limits.

The current status of DB instance xxxxx does not support this action.

The ApsaraDB RDS instance is in an abnormal state and cannot support scaling activities.

Log on to the ApsaraDBRDS console to check the instance status. After confirming that the instance is healthy, retry the scaling activity.

You cannot delete a scaling group or launch a new scaling activity while there is scaling activity in progress for the specified scaling group.

A scaling activity is already in progress for the scaling group.

Wait for the current scaling activity to complete before initiating a new one.

You cannot launch a new scaling activity during the cooldown period.

The scaling group is in the cooldown period.

Wait for the cooldown period to end before triggering another scaling activity. For more information, see Cooldown period.

The current status of the specified scaling group does not support this action.

The scaling group is in an unsupported state, such as Disabled or Deleting.

If the scaling group is Disabled, enable it before initiating the scaling activity.

The specified SecurityGroupId does not exist.

The security group specified in the scaling configuration does not exist.

Update the scaling configuration to reference a valid security group.

To remove the instances, the total capacity will be lesser than the min size.

Removing the instances would bring the group size below the configured minimum.

Check the current instance count and scaling rule configuration. Make sure the post-scaling count stays within the configured min and max limits.

The specified LoadBalancerId does not exist.

The SLB instance attached to the scaling group does not exist.

Verify that the SLB instance exists. For more information, see Attach or detach SLB instances to or from scaling groups.

Ess should be authorized in ram to operate user resource.

The Resource Access Management (RAM) user does not have the permissions required to operate Auto Scaling resources.

Log on to the RAM console and grant the necessary permissions.

To attach the instances, the total capacity will be greater than the max size.

Attaching the instances would bring the group size above the configured maximum.

Check the current instance count and scaling rule configuration. Make sure the post-scaling count stays within the configured min and max limits.

The current status of virtual switch does not support this operation.

The vSwitch is in the pending or modifying state.

Check the status of the vSwitch associated with the scaling group. After confirming it is working correctly, retry the scaling activity.

The specified virtual switch does not exist.

The vSwitch associated with the scaling group does not exist.

Make sure the vSwitch has not been deleted.

The specified launch template set is not found.

The launch template associated with the scaling group does not exist.

Log on to the ECS console to verify that the launch template exists. If necessary, update the launch template for the scaling group.

Instance "xxxxx" and the specified scaling group are not in the same VPC.

The ECS instance and the scaling group are in different virtual private clouds (VPCs).

Make sure the ECS instance and the scaling group are in the same VPC, or that the ECS instance uses the classic network.

The specified virtual switch and the instance in Load Balancer "xxxxx" are not in the same VPC.

The SLB instance and the vSwitch are in different VPCs.

Make sure the vSwitch and the SLB instance are in the same VPC. For more information, see Attach or detach SLB instances to or from scaling groups.

Instance "xxxx" is already attached to another scaling group.

An ECS instance can belong to only one scaling group at a time.

Make sure the instances to be added are not already part of another scaling group.

The specified image does not exist.

The image specified in the scaling configuration does not exist.

Update the scaling configuration to reference an image that exists and is accessible.

DataDiskSnapshotId "xxxx" does not exist.

The data disk snapshot specified in the scaling configuration does not exist.

Update the scaling configuration to reference a snapshot that exists and is accessible.

Error message

Cause

Solution

Fail to scale instances for scaling group("Ignore to remove N instances("instances in standby/protected status")").

The target instance is in the Standby or Protected state.

Manually remove or release the instance.

Fail to remove Instances "i-xxx1, i-xxx2"("The current status of the specified scaling group does not support this action.").

The scaling group is in a state that does not support instance removal.

Make sure the scaling group is in the Enabled state. For more information, see RemoveInstances.

Fail to create Instances into scaling group("The specified InstanceType has been offline.").

The instance type specified in the scaling configuration is no longer available for purchase.

Update the scaling configuration to use an available instance type. For more information, see Overview of instance families.

Fail to create Instances into scaling group("The specified ImageId does not exist.").

The image ID specified in the scaling configuration is invalid or the image no longer exists.

Update the scaling configuration to reference an image that exists and is accessible.

Fail to create Instances into scaling group("Your account has been in arrears.").

The account has overdue payments.

Make sure your account balance is sufficient. Check your balance in Expenses and Costs.

Fail to create Instances into scaling group("Your account does not have enough balance.").

The account balance is insufficient to create new instances.

Make sure your account balance is sufficient.Check your balance in Expenses and Costs.

Fail to create Instances into scaling group("Your account has not passed the real-name authentication yet.").

The account has not completed real-name authentication.

Complete real-name authenticationbefore retrying.

Fail to create Instances into scaling group("The specified parameter "spotPriceLimit" can't be lower than current public price.").

The maximum hourly price for spot instances is below the current market price.

Update the scaling configuration to set a higher maximum hourly price or adjust the bidding policy. For more information, see Overview.

Fail to create Instances into scaling group("Living afterpay instances quota exceeded.").

The pay-as-you-go instance quota for the account has been reached.

Contact Alibaba Cloud support or submit a service ticket to request a quota increase. For more information, see Manage ECS quotas.

Fail to create Instances into scaling group("The specified parameter "KeyPairName" does not exist in our records.").

The key pair specified in the scaling configuration does not exist.

Verify that the key pair is valid. If necessary, update the scaling configuration to use a different key pair.

Fail to create Instances into scaling group("The specified parameter 'SystemDisk.Category' is not support IoOptimized Instance. Valid Values: cloud_efficiency;cloud_ssd. ").

The system disk type is not compatible with I/O-optimized instances.

Update the scaling configuration to use a supported system disk type: cloud_efficiency or cloud_ssd.

Fail to create Instances into scaling group("The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones.").

The requested resource is out of stock in the specified zone.

Update the scaling configuration or scaling group to use a different instance type or zone.

Fail to create Instances into scaling group("The RAM user does not have the privilege to pass a RAM role.").

The RAM role specified in the scaling configuration does not exist or is invalid.

Update the scaling configuration to assign a valid RAM role.

Fail to create Instances into scaling group("No payment method has been registered on the account.").

The account has no default payment method on file.

Set a default payment method in Billing Management.

Fail to create Instances into scaling group("Exceeding the allowed amount of instances of a security group.").

The number of instances in the security group has reached its limit.

Distribute instances across multiple scaling groups, each associated with a separate security group.

Fail to create Instance into scaling group("The current status of instance "pending" does not support this action.").

The instance is not in a state that supports the requested operation.

Check the instance state to ensure it is in the Running state and retry the operation.

Fail to create Instances into scaling group("Abandon lifecycleActionResult parameter caused the instance to rollback.").

A lifecycle hook with Scaling Activity set to Scale-out Event and Default Execution Policy set to Reject triggered a rollback after the timeout expired.

Review the lifecycle hook configuration and adjust the execution policy as needed.

Fail to create instance into scaling group("The specified SecurityGroupId is invalid or does not exist.")

The security group specified in the scaling configuration does not exist.

Update the scaling configuration to reference a valid security group.

Fail to create instance into scaling group("The specified ImageId does not exist.")

The image specified in the scaling configuration does not exist.

Update the scaling configuration to reference an image that exists.

Fail to create instance into scaling group("Your account has been in arrears.")

The account balance is insufficient.

Make sure your account balance is sufficient.

Fail to scale instances for scaling group("Backend server quota exceeded in load balancer "lb-xxxxxxx".").

The quota for ECS instances that can be added to the SLB backend server group has been reached.

Request a quota increase. For more information, see Limits and Quota management.

Fail to create Instances into scaling group("The specified imageName does not exist.").

The image name specified in the scaling configuration does not exist.

Update the scaling configuration to reference a valid image name.

Fail to create Instances into scaling group("This resource type is not supported. Please try other resource types.").

The specified resource type is not available in the selected zone.

Specify multiple zones and multiple instance types in the scaling configuration to improve scale-out success rate. For more information, see Manage scaling groups and Create a scaling configuration of the ECS type.

Fail to create Instances into scaling group("The specified parameter SnapshotId is not exist.").

The disk snapshot specified in the scaling configuration does not exist.

Update the scaling configuration to reference a valid snapshot.

Fail to create Instances into scaling group("Don't have enough private IPs in this switch").

The vSwitch does not have enough available private IP addresses.

Expand the IP range of the vSwitch, or configure the scaling group to span multiple zones. For more information, see Manage scaling groups.

Fail to create Instances into scaling group("The specified parameter SystemDisk.Size is less than the image size.").

The system disk size specified in the scaling configuration is smaller than the image size.

Increase the system disk size in the scaling configuration, or use an image with a smaller size.

Fail to create Instances into scaling group("Living postPaid disks quota exceeded.").

The pay-as-you-go disk quota for the account has been reached.

Contact Alibaba Cloud support or submit a service ticket to request a quota increase. For more information, see Manage ECS quotas.

Fail to create Instances into scaling group("The specified ram role is not authorized for ecs, please check your role policy.").

The AliyunEssDefaultRole RAM role does not have permissions to use ECS resources.

Grant ECS permissions to the AliyunEssDefaultRole RAM role.

Fail to create instance into scaling group("The resource in the specified zone is no longer available for sale. Please try other regions and zones.")

The instance type is no longer available for purchase in the specified zone.

Configure the scaling group to span multiple zones. For more information, see Manage scaling groups.

Fail to create instance into scaling group("The resource is out of stock in the specified zone. Please try other types, or choose other regions and zones.")

The instance type is out of stock in the specified zone.

Specify multiple zones and multiple instance types in the scaling configuration to improve scale-out success rate. For more information, see Manage scaling groups and Create a scaling configuration of the ECS type.

Fail to create instance into scaling group("The specified parameter "KeyPairName" only support IoOptimized Instance.")

The instance type is not I/O-optimized and does not support key pairs.

Change the instance type to an I/O-optimized type, or remove the KeyPairName parameter from the scaling configuration.

Fail to create instance into scaling group("A RAM role can't be used for classic instance.")

Instances in the classic network do not support RAM roles.

Change the scaling group's network type to VPC, or remove the RamRoleName parameter from the scaling configuration.

Fail to create instance into scaling group("The specified parameter "RAMRoleName" does not exist.")

The RAM role name specified in the scaling configuration does not exist.

Log on to the RAM console to verify that the RAM role exists, or update the scaling configuration to use a different RAM role.

Fail to create instance into scaling group("The specified image does not support the specified InstanceType.")

The image and instance type are incompatible.

Go to the ECS product page to check which images are supported by the instance type, then update the scaling configuration accordingly.

Fail to create instance into scaling group("The requested resource is sold out in the specified zone; try other types of resources or other regions and zones.")

The instance type is sold out in the specified zone.

Specify multiple zones and multiple instance types in the scaling configuration to improve scale-out success rate. For more information, see Manage scaling groups and Create a scaling configuration of the ECS type.