在打印窗口把「目标」选为「另存为 PDF」即可保存,页面已带 awsgood.com 版权水印。 返回原文

www.awsgood.com

Lightsail Daily Operations Guide: Backups, Scaling, and Incident Response — Which Tasks You Should Handle Yourself

2026-11-13 AWS Managed Operations 约 2 分钟

The Bottom Line

Monitoring and Alerting: The Dashboard Only Gives CPU and Traffic; Fill In the Rest Yourself

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",

Sources