Golden AMIs with EC2 Image Builder

Exam alignment: DOP-C02 Domain 1 task statements for pipelines, testing, artifacts, or deployment.

Learning objective

Build, test, distribute, and retire versioned machine images.

Difficulty / Schwierigkeitsgrad	Advanced
Study time / Lernzeit	120 minutes
Prerequisites / Voraussetzungen	Previous lessons in this volume

Professional scenario

Instances install many packages at boot, launch slowly, and drift over time.

Core concepts

• Golden images contain approved baseline components.
• Image Builder uses recipes, components, tests, and distribution settings.
• Published AMIs are versioned release artifacts.
• Rollback images must remain until the recovery window closes.

Architecture flow

1. Identify the release input and immutable identity.
2. Select the managed AWS control plane and least-privilege role.
3. Execute build, test, artifact, or deployment work.
4. Collect service events, logs, reports, and runtime metrics.
5. Stop, retry, or roll back according to explicit rules.

Decision matrix

Requirement	Preferred choice	Reason
Fast consistent launch	Golden AMI	Preconfigured baseline
Multi-account baseline	Distribution settings	Controlled copy/share
Frequently changing app	Separate app deployment	Avoid needless base rebuild

Failure modes and troubleshooting

• Unpinned package version changes image.
• AMI passes build but fails boot validation.
• Old image is deleted before rollback window.

Security and operations

• Use short-lived service roles and least privilege.
• Encrypt artifacts and protect logs from secret exposure.
• Record changes and approvals for audit.

Hands-on lab

Goal / Ziel: Design a minimal image pipeline and launch-template promotion.

Tasks

1. Create the smallest safe test architecture.
2. Implement or simulate the main workflow.
3. Introduce one controlled failure.
4. Diagnose it from service evidence.
5. Document cleanup and one improvement.

Validation

• The workflow uses an immutable version.
• A required failure blocks promotion.
• The diagnosis identifies the first failed transition.

Cost control / Kostenkontrolle: Keep resources short lived; read cleanup before starting.

Cleanup

1. Delete pipeline/build/deployment resources.
2. Delete temporary artifacts, images, logs, and roles.

Exam traps

• Baking secrets into AMI.
• Using long boot scripts for immutable baseline.

Key takeaways

• Golden images contain approved baseline components.
• Rollback images must remain until the recovery window closes.
• Decisions must be justified by requirements and failure behavior.

Review questions

1. What is the immutable release identity?
2. Which evidence proves failure or success?
3. What is the safest recovery action?

Answers

1. A version, digest, or uniquely versioned artifact.
2. Service events, logs, reports, health checks, and runtime metrics.
3. Restore the known-good version using the configured rollback path.