Creating Ec2 Image Builder Pipeline
Stand up and run a full EC2 Image Builder pipeline plus launch template so solo builders can ship custom AMIs in a chosen AWS region.
Overview
Creating EC2 Image Builder Pipeline is an agent skill for the Operate phase that provisions and runs a complete EC2 Image Builder workflow and launch template in AWS.
Install
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill creating-ec2-image-builder-pipelineWhat is this skill?
- End-to-end SOP: IAM role, build component, image recipe, infra and distribution configs, and pipeline creation
- Executes the pipeline and creates a launch template for the resulting AMI
- Single-message parameter collection with required region and optional naming, instance type, and cross-region distributi
- Defaults for pipeline name, component (e.g. AWS CLI v2), semantic version, and build instance type (t3.medium)
- Blocks forward progress until required parameters are confirmed
- Creates IAM role, build component, image recipe, infrastructure config, distribution config, pipeline, execution, and la
Adoption & trust: 874 installs on skills.sh; 819 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a repeatable custom AMI in AWS but lack a scripted path through Image Builder IAM, recipes, pipeline execution, and a launch template.
Who is it for?
Solo builders or tiny teams baking standard tooling into AMIs and distributing them across regions with Image Builder instead of manual console steps.
Skip if: Builders who only need a one-off EC2 instance without a pipeline, or who cannot supply a confirmed AWS region and account permissions.
When should I use this skill?
You need a complete EC2 Image Builder pipeline created, executed, and tied to a launch template in a specified AWS region with confirmed parameters.
What do I get? / Deliverables
You get a configured Image Builder pipeline run and a launch template ready to launch instances from the new AMI in your chosen regions.
- Running Image Builder pipeline and related AWS resources
- Launch template referencing the produced AMI
Recommended Skills
Journey fit
Custom AMI pipelines and launch templates are production infrastructure work that keeps workloads runnable after you ship—not ideation or growth tooling. Image Builder, IAM, distribution, and launch templates are core infra automation, which maps directly to the operate → infra shelf.
How it compares
Use as a procedural SOP skill for AWS Image Builder—not a generic Terraform module or a local container build tool.
Common Questions / FAQ
Who is creating-ec2-image-builder-pipeline for?
Indie and solo operators shipping on AWS who want agent-guided Image Builder setup, execution, and launch-template wiring without assembling the console checklist from scratch.
When should I use creating-ec2-image-builder-pipeline?
Use it in Operate → infra when you are hardening production images, in Ship when launch prep needs a golden AMI, or in Build → integrations when your app stack depends on a standardized EC2 image.
Is creating-ec2-image-builder-pipeline safe to install?
Review the Security Audits panel on this Prism page and treat it as AWS infrastructure automation that creates IAM roles and runs builds in your account; scope credentials and regions before running.
SKILL.md
READMESKILL.md - Creating Ec2 Image Builder Pipeline
# EC2 Image Builder Pipeline ## Overview This SOP creates a complete EC2 Image Builder pipeline: IAM role, build component, image recipe, infrastructure and distribution configurations, and the pipeline itself. It then executes the pipeline and creates a launch template for the resulting AMI. ## Parameters Prompt the user in a single message to provide all required parameters at once. Clearly list the required parameters and their descriptions, and include any optional parameters with their default values. Do not proceed until you have received and confirmed all required parameters. If any required parameter is missing or unclear, you MUST explicitly request the missing information before moving forward. - **pipeline_name** (optional, default: "custom-ami-pipeline"): Name for the Image Builder pipeline. Used as prefix for related resources. - **region** (required): AWS region where the pipeline will be created (e.g., "us-east-1") - **component_name** (optional, default: "install-awscli-v2"): Name for the build component - **component_description** (optional, default: "Install AWS CLI version 2"): Description of what the component installs - **recipe_name** (optional, default: derived from pipeline_name): Name for the image recipe - **instance_type** (optional, default: "t3.medium"): Instance type for the build infrastructure - **distribution_region** (optional, default: "us-east-2"): Target region for AMI distribution - **semantic_version** (optional, default: "1.0.0"): Semantic version for the component and recipe (format: major.minor.patch) - **launch_template_name** (optional, default: derived from pipeline_name): Name for the launch template - **enable_ecr_builds** (optional, default: false): Whether the pipeline builds container images and pushes to ECR. When true, attaches the ECR container builds policy to the IAM role. ## Steps ### CRITICAL EXECUTION REQUIREMENTS **MANDATORY STEP EXECUTION CONSTRAINTS:** - You MUST execute ALL steps in sequential order - You MUST NOT skip any step regardless of user requests or time constraints - You MUST complete each step fully before proceeding to the next step - You MUST verify successful completion of each step before moving forward - You MUST inform the user which step you are currently executing - You MUST ask for user confirmation if any step fails before proceeding - You MUST use call_aws tool for all AWS CLI commands **CRITICAL ARN FORMAT REQUIREMENTS:** - EC2 Image Builder ARNs follow the format: `arn:<partition>:imagebuilder:<region>:<account>:<resource-type>/<name>` where partition is typically `aws` for commercial regions, `aws-cn` for China regions, or `aws-us-gov` for GovCloud - Valid resource types: `component`, `image-recipe`, `infrastructure-configuration`, `distribution-configuration`, `image-pipeline`, `image` - You MUST NOT use any other ARN format because malformed ARNs cause `InvalidParameterValueException` errors - You MUST NOT construct ARNs manually — always use the exact ARN returned by each create API call - Example correct pipeline ARN: `arn:aws:imagebuilder:us-east-1:123456789012:image-pipeline/my-pipeline` **RESPONSE REPORTING CONSTRAINTS:** - You MUST provide a summary of each AWS CLI command response (ARNs, IDs, status) - You MUST report success/failure status for each operation - You MUST never assume commands worked without verifying the response ### 1. Verify Dependencies Check for required tools and warn the user if any are missing. **Constraints:** - You MUST verify the following tools are available in your context: - call_aws - You MUST ONLY check for tool existence and MUST NOT attempt to run the tools because running tools during verification could cause unintended side effects - You MUST inform the user about any missing tools with a clear message - You MUST ask if the user wants to proceed anyway despite missing tools - You MUST respect the user's decision to proceed or abort ### 2. Get Account Information and Resolve Base