aws-compute

Diagnose and troubleshoot EC2, ECS, EKS, and Lambda failures using decision trees and AWS CLI commands.

3|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/LiboMa/agenticops-chat --skill aws-compute-liboma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-compute
Source: https://github.com/LiboMa/agenticops-chat/tree/main/skills/aws-compute
Command: npx skills add https://github.com/LiboMa/agenticops-chat --skill aws-compute-liboma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When AWS compute workloads fail — EC2 instances unreachable, ECS tasks crashing, Lambda functions timing out, or EKS nodes not scaling — engineers lose time hunting through documentation. This Skill provides structured decision trees and ready-to-run AWS CLI commands to pinpoint root causes quickly. ## Core Features & Use Cases - EC2 Troubleshooting: Diagnose status check failures, launch errors, SSH connectivity issues, and stuck instances, with fixes for fstab errors, full disks, and capacity limits. - ECS Task Failure Analysis: Decode stopped reasons, exit codes, placement failures, and deployment stalls, including Fargate networking and capacity provider configuration. - Lambda & EKS Operations: Resolve Lambda timeouts, throttling, OOM kills, and cold starts, plus EKS Cluster Autoscaler and Karpenter scaling problems. - Use Case: An on-call engineer gets paged because ECS tasks keep stopping with exit code 137. The Skill identifies it as an OOM kill and walks through checking the stoppedReason, CloudWatch Logs, and raising the task memory definition. ## Quick Start Ask the agent to troubleshoot why my ECS service tasks keep failing to place on the cluster and list the likely causes with the CLI commands to verify each one.

Frequently Asked Questions about aws-compute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot an EC2 instance that failed its status checks?▼

Run aws ec2 describe-instance-status to identify which check failed. System status failures mean AWS hardware issues — stop and start the instance to migrate hosts. Instance status failures are OS-level; check console output for kernel panics, fstab errors, or full disks.

Why are my ECS tasks failing with CannotPullContainerError?▼

CannotPullContainerError usually means missing ECR permissions (ecr:GetDownloadUrlForLayer, ecr:BatchGetImage) or no network path to ECR. Fargate tasks need a NAT gateway or VPC endpoints for ECR, S3, and CloudWatch Logs.

What is the difference between Lambda reserved and provisioned concurrency?▼

Reserved concurrency caps and guarantees a maximum number of concurrent executions at no extra cost. Provisioned concurrency pre-warms execution environments to eliminate cold starts but incurs charges even when idle, and requires a published version or alias.

Cluster Autoscaler vs Karpenter for EKS node scaling?▼

Cluster Autoscaler manages ASG min/max sizes and suits homogeneous workloads but scales in minutes. Karpenter provisions EC2 instances directly with flexible instance selection, scaling in seconds, and fits diverse or dynamic workloads better.

Why is my Lambda function being throttled with 429 errors?▼

Throttling occurs when concurrent executions hit the account limit (default 1000) or the function's reserved concurrency is set too low. Check the Throttles and ConcurrentExecutions CloudWatch metrics, and request a quota increase or adjust reserved concurrency.

How do I fix an EC2 instance I cannot SSH into?▼

Check the security group inbound rule for port 22, NACL rules in both directions, route table entries to an IGW or NAT, and whether a public IP is assigned. Prefer SSM Session Manager as the primary access path, falling back to SSH only when SSM is unavailable.