Watadot Aws Ec2

Elastic compute management by Watadot Studio. Deployment, scaling, and state monitoring.

Security Scan

The skill is internally consistent: it's an instruction-only AWS EC2 helper that provides aws-cli commands and asks for the aws binary only; it does not request unrelated credentials or installs, but it will execute destructive AWS actions if run with credentials that allow them.

Purpose & Capability

Name/description match the content: SKILL.md is a collection of aws cli EC2 commands for discovery, lifecycle control, and security-group management. Requiring the aws binary is appropriate for this purpose.

Instruction Scope

Instructions are limited to aws-cli commands relevant to EC2. They include destructive operations (start/stop/terminate, modify security groups) which are within the stated scope but require caution. SKILL.md does not specify an AWS profile or limit scope of actions.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk install surface.

Credentials

The skill declares no env vars, which is coherent, but the aws cli requires AWS credentials from environment/config files/profiles at runtime. The skill will operate with whatever AWS identity is available — grant minimal, scoped permissions if you use it.

Persistence & Privilege

always is false and the skill does not request persistent or elevated platform privileges or attempt to modify other skills or global agent config.

Assessment

This skill just provides aws-cli command snippets for EC2 and requires an installed aws binary and configured AWS credentials to be useful. It won't install software, but if the agent runs these commands it will act with whatever AWS identity is configured on the host (including the ability to stop/terminate instances). Before installing or invoking: ensure the agent or environment uses a low-privilege AWS profile (or read-only credentials) if you only want discovery; avoid giving it credentials that allow destructive operations; and verify you trust the skill source since it will execute aws commands against your account.

AWS EC2 Skills

Management and orchestration patterns for Elastic Compute Cloud.

🚀 Core Commands

Instance Discovery

# List running instances with Name and Public IP
aws ec2 describe-instances --filters "Name=instance-state-name,Values=running" --query "Reservations[].Instances[].{Name:Tags[?Key==\`Name\`].Value | [0], IP:PublicIpAddress, ID:InstanceId}" --output table

# Find expensive instances (G or P family)
aws ec2 describe-instances --query "Reservations[].Instances[?contains(InstanceType, 'g') || contains(InstanceType, 'p')].[InstanceId, InstanceType]"

Lifecycle Control

# Start/Stop instances by ID
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>

Network & Security

# Describe security group rules
aws ec2 describe-security-groups --group-ids <sg-id> --query "SecurityGroups[].IpPermissions"

# Add ingress rule (Port 22 from specific IP)
aws ec2 authorize-security-group-ingress --group-id <sg-id> --protocol tcp --port 22 --cidr <your-ip>/32

🧠 Best Practices

1. Tag Everything: Use standard tagging (Name, Env, Owner) for billing and discovery.
2. Instance Profiles: Use IAM Roles instead of storing hard-coded credentials on instances.
3. Spot Instances: Use Spot for stateless workloads (like Remotion rendering) to save up to 90%.
4. Security Groups: Default to "Deny All" and only open specific ports for required CIDRs.