www.awsgood.com
The Metrics page in the Lightsail console shows four categories: CPU utilization, network in/out, burst capacity headroom, and status checks. Alarms also support only these items, with email and SMS as notification channels—if you want to push to WeCom or DingTalk, you have to write your own polling relay, or use a script inside the instance to call a webhook directly.
Use the CLI to fetch historical metrics. Note that Lightsail commands must explicitly include --region; omitting it causes an error. This was a small pitfall I hit at the very beginning:
aws lightsail get-instance-metric
--instance-name wp-prod-01
--metric-name CPUUtilization
--period 300
--start-time 2026-03-01T00:00:00Z
--end-time 2026-03-01T06:00:00Z
--statistics Maximum
--unit Percent
--region ap-northeast-1
The response snippet looks like this; the jump to 99.3 is the starting point of the incident I'll discuss later:
```json
{
"metricName": "CPUUtilization",