Golden image
A pre-built, approved server template that every new machine is copied from.
A golden image is a saved copy of a fully prepared server: operating system, security patches, settings, monitoring agents and often the application itself, all baked in and approved. Instead of starting each new virtual machine blank and setting it up afterward, you launch it from this template, so it is ready in minutes and identical to every other copy. On AWS the image format is called an AMI (Amazon Machine Image); other clouds and platforms like VMware have their own.
Good golden images are built by a pipeline, not by hand. A tool such as HashiCorp Packer or EC2 Image Builder starts a temporary machine, runs the setup scripts, runs tests and security scans, and saves the result as a new numbered version. The pipeline runs again whenever new patches come out, so the image does not go stale, and old versions are retired.
This fits the idea of immutable infrastructure: you do not patch running servers, you replace them with fresh ones made from the newer image. It makes autoscaling faster, since new machines do not spend minutes installing things, and it keeps fleets predictable. The trade-off is discipline: every change, even a tiny one, means building and rolling out a new image, and someone has to own the pipeline. Container images follow the same idea.
Keep in mind
- A pre-built, tested server template that new machines start from.
- On AWS it is an AMI; Packer and EC2 Image Builder build them.
- Rebuilt regularly so new patches are always included.
- Servers get replaced with fresh copies instead of patched in place.
Go deeper
- What is a golden image? (Red Hat)
- Introduction to Packer (HashiCorp)
- What is EC2 Image Builder? (AWS docs)