awscdk cfnPractitioner

Streamline Your Image Management with EC2 Image Builder and AWS CDK

5 min read AWS DevOps BlogJul 29, 2026Reviewed for accuracy

Practitioner — Hands-on experience recommended

In today's fast-paced development environment, managing server images efficiently is crucial. EC2 Image Builder addresses this need by automating the creation, management, and deployment of secure and up-to-date server images. This fully managed service helps teams reduce manual overhead and ensures that they are always working with the latest versions of their images.

The real magic happens with EC2 Image Builder's native auto-versioning capabilities, introduced in November 2025. This feature allows components with the same name and semantic version to auto-increment build versions, which eliminates tedious manual updates. Pipelines can now resolve to the highest available version of components and recipes, ensuring that your infrastructure is always using the latest compatible versions without any extra steps. For example, using a wildcard placeholder like 'x' in versioning (e.g., 1.2.x) makes it easier to manage updates seamlessly.

When implementing this in production, it's essential to choose the right constructs. The AWS CDK provides both Layer 1 (L1) constructs that map directly to CloudFormation resources and Layer 2 (L2) constructs that offer best practice configurations. Using L2 constructs can save time and reduce the complexity of your code. However, be mindful of the specific configurations required for your infrastructure, such as instance profiles and logging buckets, to ensure everything works smoothly.

Key takeaways

→Leverage auto-versioning to eliminate manual updates in your image management.
→Use L2 constructs in AWS CDK for simplified and best-practice configurations.
→Implement pipelines that resolve to the highest available version of components automatically.
→Set up proper logging with S3 buckets to track your image building process.
→Utilize semantic versioning to maintain clarity in your image versions.

Why it matters

Streamlining image management can significantly reduce deployment times and minimize errors, leading to faster and more reliable releases in production environments.

Code examples

TypeScript

1// Using L1 constructs
2const instanceProfileRole = new iam.Role(stack, 'EC2InstanceProfileForImageBuilderRole', {
3  assumedBy: iam.ServicePrincipal.fromStaticServicePrincipleName('ec2.amazonaws.com'),
4  managedPolicies: [
5 
6
7 iam.ManagedPolicy.fromAwsManagedPolicyName('AmazonSSMManagedInstanceCore'),
8 
9
10 iam.ManagedPolicy.fromAwsManagedPolicyName('EC2InstanceProfileForImageBuilder'),
11  ],
12});
13
14const instanceProfile = new iam.InstanceProfile(stack, 'EC2InstanceProfileForImageBuilder', {
15  role: instanceProfileRole,
16});
17
18const bucket = new s3.Bucket(stack, 'ImageBuilderLoggingBucket', {
19 bucketName: `ec2imagebuilder-logs-${stack.region}-${stack.account}`,
20  enforceSSL: true,
21});
22
23const l1InfrastructureConfiguration = new imagebuilder.CfnInfrastructureConfiguration(stack, 'L1InfrastructureConfiguration', {
24  name: 'l1-infrastructure-configuration',
25  instanceProfileName: instanceProfile.instanceProfileName,
26
27 instanceMetadataOptions: { httpTokens: 'required' },
28  logging: {
29 
30
31 s3Bucket: bucket.bucketName,
32 
33
34 s3KeyPrefix: 'imagebuilder-logging',
35  },
36});
37const l1ImageRecipe = new imagebuilder.CfnImageRecipe(stack, 'L1ImageRecipe', {
38  name: 'l1-image-recipe',
39  version: '1.0.0',
40
41 parentImage: `arn:${stack.partition}:imagebuilder:${stack.region}:aws:image/amazon-linux-2023-x86/x.x.x`,
42  components: [
43
44
45
46 {
47 
48
49
50
51 componentArn: `arn:${stack.partition}:imagebuilder:${stack.region}:aws:component/update-linux/x.x.x`,
52 
53
54 },
55  ],
56});
57
58const l1ImagePipeline = new imagebuilder.CfnImagePipeline(stack, 'L1ImagePipeline', {
59  name: 'l1-image-pipeline',
60
61 imageRecipeArn: l1ImageRecipe.attrArn,
62  infrastructureConfigurationArn: l1InfrastructureConfiguration.attrArn,
63});