buildkite/elastic-ci-stack-for-aws v7.5.0 on GitHub

v7.5.0 (2026-10-13)

Full Changelog

Changed

Bump s3 secrets helper to 2.9.0 #1922 (@scadu)
Update module golang.org/x/sys to v0.49.0 #1920 (@renovate[bot])
Update go toolchain directive to v1.27.2 #1917 (@renovate[bot])
Update golang Docker tag to v1.27 #1918 (@renovate[bot])
Update buildkite/buildkite-agent-scaler to v1.16.0 #1916 (@renovate[bot])
Update buildkite-agent to v4.4.0 #1915 (@renovate[bot])

Internal

Add v7 support policy banner to README #1913 (@petetomasik)
Fix release steps being skipped by change filtering #1887 (@scadu)

Agent Changelog (v4.4.0)

v4.4.0

What's Changed

🐛 Fixed

Stop leaking BUILDKITE_JOB_LOG_TMPFILE between jobs when enable-job-log-tmpfile is set and the agent runs with --spawn by @isaacsu in buildkite/agent#4484
Treat Windows paths such as C:\tools\runner.exe as absolute when resolving commands by @tomowatt in buildkite/agent#4382

🔧 Changed

Redact Buildkite tokens by prefix in errors reported by the experimental buildkite-agent job capture-error by @123sarahj123 in buildkite/agent#4468
Show the buildkite-agent cache exec restore report inside the replay or run group, instead of in a separate group by @ss1909 in buildkite/agent#4483
Explain how to fix buildkite-agent cache save and cache restore on hosted agents when they run inside a Docker plugin container by @buildkate in buildkite/agent#4492

🏠 Internal

Remove repository docs that duplicate the public docs site by @zhming0 in buildkite/agent#4467
Move Git LFS fetch and checkout helpers into git_lfs.go by @zhming0 in buildkite/agent#4493
Move finishMirrorUpdate into checkout_mirror.go by @zhming0 in buildkite/agent#4494

Full Changelog: buildkite/agent@v4.3.0...v4.4.0

Full Changelog: v7.4.0...v7.5.0

Upgrading

Follow the v7 upgrade guide before updating. Remove or replace retired parameters in parameter files and deployment automation. If you use a custom AMI through ImageId or ImageIdParameter, rebuild it from the v7 base AMI and update it in the same stack update; a v6-based AMI might not boot under the v7 template depending on the configuration.

Perform a CloudFormation stack update with the following URL:

https://s3.amazonaws.com/buildkite-aws-stack/v7.5.0/aws-stack.yml

If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):