← Back to Skills Marketplace
shimotsuk1-rei

AWS Health Monitor

by Shimotsuk1-Rei · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
307
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install aws-health-monitor
Description
Monitor AWS Health Dashboard for active incidents and notify via configurable channels (Feishu, Telegram, Slack, Discord, etc.). Activate when user wants to...
README (SKILL.md)

AWS Health Monitor

监控 AWS Health Dashboard 活跃故障,变更时推送通知(支持飞书、Telegram、Slack、Discord 等)。

部署路径

  • 脚本:scripts/aws-health-monitor.py(部署到 workspace/scripts/)
  • 忽略配置:references/aws-health-ignore.example.json(部署为 workspace/scripts/aws-health-ignore.json)
  • 状态文件(运行时自动生成):workspace/scripts/.aws-health-state.json
  • 日志:workspace/logs/aws-health-monitor.log

关键配置(环境变量)

脚本所有关键参数通过环境变量注入,不硬编码:

环境变量 说明 默认值
HTTPS_PROXY / HTTP_PROXY 出口代理 不使用代理
AWS_HEALTH_NOTIFY_CHANNEL 通知渠道(feishu/telegram/slack/discord 等) feishu
AWS_HEALTH_NOTIFY_TARGET 通知目标(open_id / chat_id / @username 等) 必填
AWS_HEALTH_WATCH_REGIONS 监控的 region 白名单,逗号分隔 空(监控全部)
AWS_HEALTH_WATCH_SERVICES 监控的服务名白名单,逗号分隔 空(监控全部)

示例:只监控法兰克福和东京的 EC2、RDS

export AWS_HEALTH_WATCH_REGIONS=eu-central-1,ap-northeast-1
export AWS_HEALTH_WATCH_SERVICES="Amazon EC2,Amazon RDS"

挂 Cron

*/5 * * * * export http_proxy=http://\x3Cproxy>:\x3Cport> https_proxy=http://\x3Cproxy>:\x3Cport> AWS_HEALTH_NOTIFY_CHANNEL=\x3Cchannel> AWS_HEALTH_NOTIFY_TARGET=\x3Ctarget>; cd /path/to/workspace && /usr/bin/python3 scripts/aws-health-monitor.py >> logs/aws-health-monitor.log 2>&1

忽略配置(aws-health-ignore.json)

参考 references/aws-health-ignore.example.json,支持两种忽略方式:

{
  "arns": ["arn:aws:health:me-central-1::event/..."],  // 精确忽略单个 issue
  "services": ["Amazon WorkSpaces", "AWS IoT Core"]    // 按服务名模糊忽略
}

修改后保存即生效,下次轮询自动跳过。

通知触发条件

  • 新 issue 出现
  • 已知 issue 有最新更新(message 变化)
  • issue 从 Dashboard 消失(视为已解决)

通知格式示例

[新故障] | AWS Health Dashboard

Region:UAE
服务:Multiple services
状态:调查中(Increased Error Rates)
首发:2026-03-01 20:51 CST
更新:2026-03-02 13:59 CST

根因:电源故障、数据中心火灾/物理损坏
We are investigating issues with AWS services in the ME-CENTRAL-1 Region

最新进展:
We are investigating additional connectivity issues and error rates...

https://health.aws.amazon.com/health/status

根因提炼逻辑

脚本通过正则匹配 event_log 所有消息文本,识别以下根因类型: 电源故障、数据中心物理损坏、网络故障、连通性问题、硬件故障、软件 Bug、配置变更/错误、变更发布问题、容量/资源耗尽、DNS 问题、证书/TLS 问题、存储故障、内存问题、流量异常/DDoS、上游/第三方问题。

匹配到多个时用顿号拼接;未匹配则显示"暂无明确根因"。

数据来源

GET https://health.aws.amazon.com/public/currentevents(UTF-16 编码 JSON)

旧接口 https://status.aws.amazon.com/data.json 已 301 重定向至此。

Usage Guidance
This script does what it says (polls the public AWS Health feed and builds messages), but verify two things before using: (1) The script calls an external CLI named 'openclaw' to send notifications — the registry did not declare that dependency. Ensure 'openclaw' exists on your system, understand what endpoints and credentials it uses, and confirm it is from a trusted source. (2) The SKILL.md expects several environment variables (notify channel/target, optional proxy, watch filters) though the registry declared none — you must set AWS_HEALTH_NOTIFY_TARGET at minimum. Also review and control the workspace paths where the script will write state and logs. If you cannot verify the origin and behavior of the 'openclaw' binary, do not install or run this skill. If you want a cleaner deployment, ask the author to update metadata to declare the 'openclaw' dependency and the required env vars (or change the notifier to use direct API calls with documented credentials).
Capability Analysis
Type: OpenClaw Skill Name: aws-health-monitor Version: 1.0.0 The skill bundle is designed to monitor AWS Health Dashboard and send notifications via OpenClaw's messaging system. The Python script (`scripts/aws-health-monitor.py`) fetches data from a legitimate AWS endpoint (`https://health.aws.amazon.com/public/currentevents`) and uses `subprocess.run` to call the `openclaw message send` command. This call is implemented securely using a list of arguments, preventing shell injection. All configurations are handled via environment variables or local files, and there is no evidence of data exfiltration to unauthorized endpoints, persistence mechanisms, or prompt injection attempts in `SKILL.md`.
Capability Assessment
Purpose & Capability
The skill claims to send notifications to Feishu/Telegram/Slack/Discord, and the Python script implements polling and message construction. However, the script invokes an external CLI 'openclaw' to deliver messages but the skill metadata did not declare any required binaries. That missing dependency is a meaningful mismatch: the notifier will silently fail or call an unexpected tool unless 'openclaw' is present and trusted.
Instruction Scope
SKILL.md instructions align with the script: place files under workspace/scripts, configure via environment variables, optionally run from Cron, and the script reads/writes only the ignore file, a local .aws-health-state.json, and writes logs. The runtime behavior stays within the stated monitoring/notification scope and only fetches the public AWS Health URL.
Install Mechanism
There is no installer or external download; this is instruction + Python script only. No remote code is fetched or extracted at install time. That lowers supply-chain risk, but users must still ensure the script file came from a trusted source.
Credentials
The SKILL.md and script rely on several environment variables (AWS_HEALTH_NOTIFY_CHANNEL, AWS_HEALTH_NOTIFY_TARGET, HTTP(S)_PROXY, AWS_HEALTH_WATCH_REGIONS, AWS_HEALTH_WATCH_SERVICES) but the registry metadata lists no required env vars or primary credential. Also, the notifier uses the external 'openclaw' CLI which likely needs its own credentials or configuration that are not declared. The skill does not request AWS credentials (none are needed because it uses the public status feed).
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide configs. It creates/updates a local state file (.aws-health-state.json) and writes logs under workspace; this is normal for a polling/notify tool.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install aws-health-monitor
  3. After installation, invoke the skill by name or use /aws-health-monitor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: monitor AWS Health Dashboard for active incidents with configurable region/service filters, root cause analysis, and multi-channel notifications (Feishu/Telegram/Slack/Discord).
Metadata
Slug aws-health-monitor
Version 1.0.0
License
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is AWS Health Monitor?

Monitor AWS Health Dashboard for active incidents and notify via configurable channels (Feishu, Telegram, Slack, Discord, etc.). Activate when user wants to... It is an AI Agent Skill for Claude Code / OpenClaw, with 307 downloads so far.

How do I install AWS Health Monitor?

Run "/install aws-health-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is AWS Health Monitor free?

Yes, AWS Health Monitor is completely free (open-source). You can download, install and use it at no cost.

Which platforms does AWS Health Monitor support?

AWS Health Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created AWS Health Monitor?

It is built and maintained by Shimotsuk1-Rei (@shimotsuk1-rei); the current version is v1.0.0.

💬 Comments