A Golden AMI Pipeline that Rebuilds on a Schedule, Tests and Scans

A pipeline with no schedule builds when somebody clicks, so the golden image ages until a person remembers it; image tests are the switch turned off to save an hour and scanning is off unless enabled; and the build instance's metadata service can hand its credentials to whatever a step downloads. Weekly rebuilds when a dependency changed, tests and scanning on, IMDSv2-only builds.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformAWSCompute & VMsv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Lightsail Instance with a Firewall that Names Its Sources, a Static IP and Snapshots A Patch Baseline, Its Patch Group and a Maintenance Window that Installs Batch Jobs that Survive a Reclaimed Host EC2 Instance EC2 Launch Template + Auto Scaling Group

The same job on other clouds

Golden Images on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

A Custom Image in a Family, Encrypted with Your Key and Shared by IAMGoogle Cloud Golden Images that Boot Trusted, Stay Private and ExpireAzure

Installing it

module "aws_image_builder" {
  source  = "www.iac-bazaar.com/iac-bazaar/aws-image-builder/aws"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.