Watadot Aws Ec2
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only AWS EC2 helper, but it includes high-impact AWS CLI commands that should be used only with explicit intent and least-privilege AWS access.
Before installing or using this skill, make sure the AWS CLI profile available to the agent is least-privileged and points to the intended account and region. Treat instance termination and security-group changes as high-impact actions that should require explicit confirmation.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used with real AWS permissions, these commands can start, stop, or permanently terminate EC2 instances, affecting uptime and costs.
The skill documents AWS CLI lifecycle operations, including instance termination. This is aligned with EC2 management and is marked as dangerous, but it can still disrupt workloads if run unintentionally.
aws ec2 start-instances --instance-ids <id1> <id2> aws ec2 stop-instances --instance-ids <id> # Terminate instance (DANGER) aws ec2 terminate-instances --instance-ids <id>
Use explicit user approval for lifecycle changes, verify the AWS account and region first, and prefer least-privilege IAM permissions.
The agent may act with the same AWS privileges as the configured CLI profile, including changing network access rules if that profile allows it.
The skill relies on the local AWS CLI and includes account-mutating EC2 and security-group operations. Those commands will use whatever AWS credentials and permissions are configured locally.
requires: anyBins: [aws] ... aws ec2 authorize-security-group-ingress --group-id <sg-id> --protocol tcp --port 22 --cidr <your-ip>/32
Run this only with a dedicated AWS profile or role scoped to the needed EC2 actions, and confirm the target account, region, instance IDs, and CIDR ranges before execution.