Evaluates whether subscription SLB instances are actively in use based on their running state, listener configuration, and backend server setup. Instances that do not meet all conditions are considered idle.
Scenarios
Identifying and managing idle instances helps reduce unnecessary costs.
Risk level
Default risk level: high.
You can change the risk level when you apply this rule.
Compliance evaluation logic
-
The evaluation result is Compliant if subscription SLB instances meet all of the following conditions:
-
No subscription SLB instances are in the Stopped state.
-
Listeners are configured for each subscription SLB instance.
-
Not all listeners are stopped.
-
Backend servers are added for each subscription SLB instance, and the weight of any backend server is not 0.
-
-
The evaluation result is Non-compliant if a subscription SLB instance meets any of the following conditions:
-
The subscription SLB instance is in the Stopped state.
-
No listeners are configured for the subscription SLB instance.
-
All listeners are stopped.
-
No backend servers are added for the subscription SLB instance.
-
The weights of all backend servers are 0.
-
-
If SLB instances are pay-as-you-go instances, the evaluation result is Not Applicable.
Rule details
|
Item |
Description |
|
Rule name |
clb-prepaid-instance-idle-check |
|
Rule ID |
|
|
Tag |
SLB and LoadBalancer |
|
Automatic remediation |
Not supported |
|
Trigger type |
Configuration change |
|
Supported resource type |
SLB instance |
|
Input parameter |
allocateDays. Default value: 7, in days |
Non-compliance remediation
Ensure that subscription SLB instances are running, have active listeners configured, and have backend servers with non-zero weights. For more information, see SLB overview.