A permitting fleet must upgrade reliably. Leadership prefers images that are baked in CI over long-lived golden images patched in place. Which pattern should the architect choose?
Select an answer to reveal the explanation.
Short Explanation
Treat servers like sealed bottles from the plant, not pets you nurse with SSH. Bake the AMI in CI, launch fresh, and retire the old ones—upgrades and rollbacks stay clean.
Full Explanation
Immutable AMI pipelines produce versioned images in CI and replace instances rather than mutating long-lived golden images in place, improving upgrade reliability and rollback. Persistent SSH patching of aged golden images, unnamed mystery latest images, and hand-edited production filesystems create drift and weak rollback.