aws-idle-resource-detector

What This Skill Does

The aws-idle-resource-detector is an advanced AWS hygiene utility designed for OpenClaw agents to proactively identify and mitigate cloud infrastructure waste. By scanning your AWS accounts across multiple regions, this agent detects resources that are incurring costs while providing zero business value. The skill is engineered to flag stopped EC2 instances, unattached EBS volumes, unused Elastic IPs, idle load balancers, and stagnant RDS instances, among others. It calculates the potential monthly and annual cost savings and provides actionable runbooks to clean up your environment safely. By automating the identification of "zombie" resources, the tool empowers DevOps teams and FinOps practitioners to optimize their AWS spend without manually auditing thousands of resources.

Installation

To integrate this skill into your OpenClaw agent, execute the following command in your agent terminal: clawhub install openclaw/skills/skills/anmolnagpal/idle-resource-detector

Use Cases

• Cloud Cost Optimization: Automatically generate a monthly audit report to present to stakeholders, showcasing potential savings by removing underutilized infrastructure.
• Security Hardening: Identify and decommission orphaned resources that are not only wasting money but also increase your attack surface by remaining active in your cloud perimeter.
• Account Cleanup: Use this skill before migrating or downsizing environments to ensure no legacy "ghost" resources are accidentally carried over to the new architecture.
• Budget Compliance: Monitor non-production accounts for "sprawl" where developers may have spun up high-performance resources that were never shut down after testing.

Example Prompts

1. "Run a scan on my us-east-1 and eu-west-1 regions and list all EBS volumes and idle load balancers that have been inactive for over 30 days."
2. "Identify all resources costing more than $50/month that are considered idle and draft a cleanup plan, but exclude any resources with the tag 'Production'."
3. "Summarize my total monthly cloud waste and provide the specific AWS CLI commands required to delete the unused NAT Gateways discovered today."

Tips & Limitations

• Safety First: The agent strictly follows a safety-first protocol. Never attempt to delete resources marked with 'prod' or 'critical' flags without manual human verification.
• Read-Only Permissions: To ensure security, it is recommended to run this agent with a read-only IAM role for discovery, only escalating to delete permissions once a cleanup plan has been approved by an administrator.
• Data Freshness: The scan accuracy relies on CloudWatch metrics; ensure that your resources have enhanced monitoring enabled to get the most precise idle detection data.