All Products
Search
Document Center

Cloud Config:Check for idle RDS instances based on CPU utilization

Last Updated:Jun 04, 2026

Checks whether the maximum CPU utilization of an RDS instance meets or exceeds a specified threshold. The default detection period is 7 days. Not applicable to Cluster Edition, Serverless Edition, instances not connected to CloudMonitor, or instances without monitoring data.

Threat level

Default threat level: Low.

You can adjust the threat level.

Detection logic

  • An RDS instance is compliant if its maximum CPU utilization within a specified period meets or exceeds a set threshold. This rule does not apply if an RDS instance is not connected to CloudMonitor, has no monitoring data, or is a Cluster Edition or Serverless Edition instance. The default detection period is 7 days. Detection uses the CloudMonitor monitoring data API and consumes the basic CloudMonitor free quota. To improve detection quality, enable Hybrid Cloud Monitoring. For Hybrid Cloud Monitoring billing, see Billing of CloudMonitor.

Rule details

Parameter

Description

Rule name

Check for idle RDS instances based on CPU utilization

Rule identifier

rds-cpu-max-utilization-check

Tag

ECS

Automatic remediation

Not supported

Rule trigger

Periodic

Trigger frequency

24 hours

Supported resource types

ACS::RDS::DBInstance

Input parameters

relativeTime (Default: 168)
utilization (Default: 10)

Remediation

To fix non-compliant instances, use cloud service monitoring.