Why it matters
Builders are often left running after an image is created, and each one is billed like a streaming instance.How nOps finds it
nOps reads the last 30 complete days of AppStream billing for image builders and app block builders. A builder is flagged when it was billed on average at least 20 hours a day, with at least 24 days of 20 or more hours, it has been billed since the start of the window and is still running. The saving is the last 7 days of on-demand cost scaled to a month. Builders mostly covered by commitments and savings under $5 a month are left out.Before you start
Permission to stop image builders (appstream:StopImageBuilder, appstream:StopAppBlockBuilder).
How to implement
- Check with the image owner that no image is being built or updated on it.
- Stop it in the AppStream 2.0 console (Images → Image Builder → Actions → Stop), or run
aws appstream stop-image-builder --name NAME(orstop-app-block-builder). - Start it again only when you need to build the next image.
- If a builder is no longer needed at all, delete it.
Risks and considerations
- Unsaved work on the builder is lost when it stops. Create the image first.
- Starting a stopped builder takes several minutes.
- To roll back, start the builder again.