Agent skill · aws
amazon-ec2-image-builder
Creates and automates custom image builds with EC2 Image Builder - Linux, Windows, and macOS AMIs, and container images to ECR. Covers the build IAM role, Amazon-managed and custom components, image recipes, infrastructure and distribution configuration (launch templates, SSM parameters, other Regions), one-off builds, recurring scheduled pipelines for golden AMI automation and OS patching, custom image workflows, and diagnosing failed builds. Applies when creating, automating, or scheduling AMI or container image builds with Image Builder, or when debugging a failed build. Not for launching instances from existing AMIs, AMI lifecycle/retirement, or general EC2 fleet management.
What it needs
About 4k tokens when loaded.
What this skill does
Amazon EC2 Image Builder Overview Domain expertise for building custom AMIs and container images with EC2 Image Builder — from the build IAM role through recipes, pipelines, distribution, and troubleshooting. Works best with the AWS MCP server — recommended for sandboxed execution and audit logging. All guidance also works with standard AWS CLI access. Guardrail — where this skill's own files live (MCP vs local install) This skill can be loaded two ways, and they resolve the skill's own bundled files from different places. Determine how the skill was loaded before reading a reference or running a script: Loaded through the AWS MCP retrieveskill tool: The skill is not installed on the local filesystem. You MUST fetch each reference or script via retrieveskill with the file parameter (e.g. file="references/creating-images.md"), and use the returned content. Do NOT fileread these paths locally — they do not exist on disk. Installed locally (e.g. .kiro/skills/amazon-ec2-image-builder/ or ~/.claude/skills/amazon-ec2-image-builder/): Read files from the local skill directory using relative paths. This distinction applies only to the skill's own packaged files. User data and session artifacts are always read from and written to the user's working directory. Never fetch or write user data through retrieveskill. First decision: one-off image or recurring pipeline Ask this before creating anything — it changes what you build. The user wants Do this --- --- One custom AMI, once Follow creating-images.md through step 7a: create-image with a recipe and infrastructure configuration — no pipeline needed. A golden AMI that stays current (scheduled rebuilds that pick up base-image updates and patches) An image pipeline: follow creating-images.md — the schedule is part of the create-image-pipeline call (step 7b). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aws/amazon-ec2-image-builder