CPU usage is high on an RDS instance supported by CloudWatch Database Insights, but the responsible SQL is unknown.
Analyze database load by SQL and wait events.
Which feature is most appropriate?
Use CloudWatch Database Insights to analyze DB load by SQL and wait events. The former Performance Insights console experience has migrated to Database Insights.
Detailed explanation
Control-plane audit events do not break down the database load caused by SQL execution.
Control-plane audit events do not break down the database load caused by SQL execution.
Filter DB load by dimensions such as SQL and wait events to investigate the main contributors.
Filter DB load by dimensions such as SQL and wait events to investigate the main contributors.
OS process telemetry does not replace the required SQL- and wait-based DB load analysis.
OS process telemetry does not replace the required SQL- and wait-based DB load analysis.
CPU utilization shows the symptom but does not identify SQL or wait contributors by itself.
CPU utilization shows the symptom but does not identify SQL or wait contributors by itself.
Check official documentation
Compare the following points with the official documentation.
Review CloudWatch Database Insights DB-load analysis and supported database configurations.
Official references
What to confirm
Distinguish host CPU utilization from DB-load contributors by SQL and waits.
Key points
- Database Insights
- Database load
- Wait event
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-03.
Foundation review
CPU and DB load
CPUUtilization shows a host symptom. Database Insights breaks down DB load by SQL and waits to investigate contributing work, rather than inferring a query from CPU alone.
Current feature and support
Performance Insights users have migrated to Database Insights. Both Standard and Advanced support DB-load contributor analysis; verify engine, Region, and instance-class support.