amazon-ec2-image-builder

Creates and automates custom AMI and container image builds with EC2 Image Builder.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building and maintaining custom AMIs and container images by hand is error-prone and hard to keep patched. This Skill guides the full EC2 Image Builder workflow — build IAM role, components, recipes, infrastructure, distribution, and pipelines — so images stay current automatically and failed builds can be diagnosed quickly. ## Core Features & Use Cases - End-to-end image creation: Build Linux, Windows, and macOS AMIs or Docker container images to ECR, from the build IAM role through recipes, infrastructure configuration, and verification. - Golden AMI automation: Set up recurring scheduled pipelines that pick up base-image updates and patches, with launch template and SSM parameter distribution so Auto Scaling groups roll onto new AMIs automatically. - Build troubleshooting: Diagnose failed or hung builds using stage-aware failure mapping, CloudWatch log analysis, and live debugging on kept build instances. - Use Case: A platform team needs a hardened Amazon Linux 2023 golden AMI rebuilt every Monday with the latest patches and published to a launch template. This Skill walks through creating the pipeline with a cron schedule, dependency-update triggers, and launch template distribution. ## Quick Start Use the amazon-ec2-image-builder skill to create a scheduled pipeline that builds a patched Amazon Linux 2023 AMI every week and updates my launch template.

Frequently Asked Questions about amazon-ec2-image-builder

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

FAQPage Schema
How do I create a custom AMI with EC2 Image Builder?

Create a build IAM role with an instance profile, choose Amazon-managed or custom components, create an image recipe with a parent image, then run create-image with an infrastructure configuration. For recurring builds, create an image pipeline with a cron schedule instead.

How do I automate golden AMI patching with Image Builder?

Create an image pipeline with a cron schedule and the EXPRESSION_MATCH_AND_DEPENDENCY_UPDATES_AVAILABLE start condition, referencing the base image with the x.x.x wildcard. Each scheduled run picks up new base-image releases, and launch template distribution rolls Auto Scaling groups onto the new AMI.

Can EC2 Image Builder build Windows, macOS, and container images?

Yes. Windows uses ExecutePowerShell components and exit code 3010 for reboots, macOS requires EC2 Mac Dedicated Hosts with host tenancy placement, and container images use container recipes targeting an ECR repository with an extra build-role managed policy.

Why did my Image Builder build fail and where are the logs?

Check image.state.status and state.reason from get-image to identify the failed stage. Component failures are only detailed in the CloudWatch log group /aws/imagebuilder/<image-name>, which contains full command stdout and stderr for each build.

Why does my scheduled Image Builder pipeline never run?

Pipelines only run at cron times, and the dependency-updates condition requires update-detectable references like wildcard versions or readable ssm: parameters. A recipe pinned to an AMI ID never registers an update, and pipelines auto-disable after consecutive failed scheduled builds.

When should I not use EC2 Image Builder?

Image Builder is not for launching instances from existing AMIs, AMI lifecycle and retirement management, or VM/ISO image import and export. Use direct EC2 launch workflows or AMI lifecycle tools for those tasks instead.