AWS CLI Skills Guide

This guide covers the AWS CLI Beast Mode skill for advanced cloud operations, automation, and resource management from the command line.

Overview

The AWS CLI (Command Line Interface) is a unified tool to manage your AWS services. The aws-cli-beast skill provides advanced patterns, automation scripts, and best practices for power users who need to manage AWS resources efficiently at scale.

Skill Details

When to Use This Skill

Use the AWS CLI skills when you need to:

• Perform bulk operations across thousands of AWS resources
• Create automated scripts for routine AWS operations
• Troubleshoot AWS networking, security, or compute issues
• Manage multiple AWS profiles and regions simultaneously
• Implement infrastructure-as-code workflows via CLI
• Perform security audits and compliance checks
• Work with AWS services that require waiters and polling
• Handle AWS CLI pagination for large datasets
• Deploy and manage Lambda functions from command line

Trigger Phrases

• "aws beast mode"
• "optimize aws resources via cli"
• "bulk s3 migration cli"
• "audit iam policies beast"
• "troubleshoot vpc networking cli"
• "aws cli automation"
• "lambda deployment cli beast"
• "dynamodb bulk operations"
• "ec2 fleet management cli"
• "iam policy audit cli"
• "bulk aws operations"

Service Coverage

The aws-cli-beast skill covers the following AWS services with advanced CLI patterns:

Core Capabilities

Advanced Querying with JMESPath

Use --query flag to transform and filter AWS CLI output server-side:

# Get instance IDs and private IPs in one command
aws ec2 describe-instances \
  --query 'Reservations[*].Instances[*].[InstanceId,PrivateIpAddress,State.Name]' \
  --output table

# Filter by tag and get only running instances
aws ec2 describe-instances \
  --filters "Name=tag:Environment,Values=production" \
  --query 'Reservations[].Instances[?State.Name==`running`].[InstanceId,Tags[?Key==`Name`].Value[0]]' \
  --output json

Bulk Operations

Handle thousands of resources efficiently:

# Stop all EC2 instances in a specific tag
aws ec2 describe-instances \
  --filters "Name=tag:Environment,Values=development" \
  --query 'Reservations[].Instances[].InstanceId' \
  --output text | xargs aws ec2 stop-instances --instance-ids

# Delete old CloudWatch log streams
aws logs describe-log-streams \
  --log-group-name /aws/lambda/my-function \
  --query 'logStreams[?lastIngestionTime<`${cutoff_timestamp}`].logStreamName' \
  --output text | xargs -r aws logs delete-log-stream --log-group-name /aws/lambda/my-function --log-stream-name

Waiters and Polling

Properly handle asynchronous resource provisioning:

# Wait for EC2 instance to be running
aws ec2 wait instance-running --instance-ids i-1234567890abcdef0

# Wait for Lambda function to be active
aws lambda wait function-active --function-name my-function

# Wait for RDS instance to be available
aws rds wait db-instance-available --db-instance-identifier my-db

Security-First Patterns

Always apply security best practices:

# Dry run before any destructive operation
aws s3 rm s3://my-bucket/important/ --dryrun

# Validate IAM policy before attaching
aws iam simulate-principal-policy \
  --policy-source-arn arn:aws:iam::123456789012:user/myuser \
  --action-names s3:GetObject \
  --resource-arns arn:aws:s3:::my-bucket/*

# Enable MFA for sensitive operations
aws iam create-virtual-mfa-device --virtual-mfa-device-name my-mfa

Profile and Region Management

Seamlessly switch between AWS accounts and regions:

# List all available profiles
aws configure list-profiles

# Use specific profile
aws --profile production ec2 describe-instances

# Multi-region query
for region in us-east-1 us-west-2 eu-west-1; do
  aws --region $region ec2 describe-vpcs --query 'Vpcs[].VpcId'
done

Reference Materials

The aws-cli-beast skill includes comprehensive reference guides:

Helper Scripts

Best Practices

1. Always use --output json for programmatically processable output
2. Use JMESPath to filter data server-side, reducing bandwidth
3. Implement proper error handling with exit codes and retry logic
4. Use waiters instead of manual polling for resource state changes
5. Enable CloudTrail for audit compliance on all operations
6. Use least-privilege IAM policies with iam-simulate-principal-policy
7. Tag all resources for cost allocation and automation
8. Use --dry-run for any operation that modifies state
9. Enable MFA for operations that modify security settings
10. Use profiles for separating development, staging, and production

Integration with Other Skills

The AWS CLI skill complements other AWS-related capabilities:

See Also

• CloudFormation Skills Guide - Infrastructure as Code with CloudFormation
• AWS SAM Guide - Serverless Application Model
• Cost Optimization Guide - AWS cost management
• AWS Agents Guide - AWS specialized agents