aws-containers

Deploys and troubleshoots containerized workloads on EKS, ECS, Fargate, ECR, and Elastic Beanstalk.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/dennisvink/yolomancer --skill aws-containers-dennisvink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-containers
Source: https://github.com/dennisvink/yolomancer/tree/main/skills/aws/core-skills/aws-containers
Command: npx skills add https://github.com/dennisvink/yolomancer --skill aws-containers-dennisvink

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying and debugging containers on AWS requires up-to-date knowledge of EKS, ECS, Fargate, ECR, and Elastic Beanstalk, whose APIs, versions, and configuration parameters change frequently. This Skill provides current reference guidance so you avoid relying on stale internal knowledge when configuring clusters, task definitions, registries, or troubleshooting control-plane failures. ## Core Features & Use Cases - EKS Guidance: Covers EKS Auto Mode, Karpenter, managed node groups, Fargate profiles, the AWS Load Balancer Controller, Provisioned Control Plane tiers, and node health monitoring and repair. - ECS and Fargate Workflows: Provides task definition patterns, execution vs task IAM roles, secrets injection, volumes (EFS/EBS/bind mounts), ECS Managed Instances, Managed Daemons, and capacity provider strategies. - ECR and Beanstalk Operations: Covers repository creation, image scanning, lifecycle policies, Beanstalk platform detection, configuration precedence, and deployment policies. - ECS Action Logs Troubleshooting: Recommends, enables, and reads ECS Action Logs to diagnose deployment rollbacks, circuit-breaker events, and task placement failures. - Use Case: When an ECS service deployment keeps rolling back, use this Skill to check whether Action Logs are enabled, enable vended log delivery to CloudWatch with proper KMS encryption, and read the control-plane entries to find the root cause. ## Quick Start Ask the assistant to help deploy a containerized application to ECS on Fargate or troubleshoot why an EKS workload is failing, and it will load the relevant reference file before responding.

Frequently Asked Questions about aws-containers

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

FAQPage Schema
How do I deploy a containerized application on AWS ECS with Fargate?

Register a Fargate task definition with task-level CPU and memory, an execution role for image pulls and logs, and awsvpc network mode, then create a service using the FARGATE capacity provider. The Skill provides a minimal task definition example and IAM permission mappings.

How do I troubleshoot an ECS deployment rollback or circuit-breaker failure?

Check whether ECS Action Logs are enabled for the cluster by verifying a delivery source with log type ACTION_LOGS plus a matching delivery. If not enabled, the Skill guides enabling vended log delivery to CloudWatch Logs, then reading entries around the failure onset.

What is the difference between EKS Auto Mode and standard EKS managed node groups?

EKS Auto Mode uses Karpenter-based managed compute with AWS-managed AMIs, networking, and load balancing, while managed node groups give you direct control over EC2 instances and AMIs. Auto Mode uses different node class CRDs and labels than standard Karpenter.

Can I use EBS volumes with Fargate tasks on ECS?

Yes, ECS Fargate supports EBS volumes provisioned per task, along with EFS volumes and ephemeral storage. This differs from EKS Fargate, where EBS volumes are not supported and only EFS via the CSI driver is available.

Why does the AWS Load Balancer Controller fail to discover region or VPC ID?

The default IMDS hop limit of 1 blocks pods from reaching instance metadata, causing startup errors. Fix it by passing region and vpcId explicitly via Helm values rather than raising the IMDS hop limit, which would weaken metadata security.

When should I not use ECS Managed Instances for my workload?

Avoid ECS Managed Instances for tasks that must run longer than 14 days, since instances have a maximum 14-day lifetime before automatic replacement. Custom AMIs and SSH access are also unsupported; use ECS Exec for debugging instead.