Docs: Update autoscale AWS documentation that still uses deprecated docker+machine executor

Problem to solve

The documentation page "Autoscale GitLab Runner on AWS" at:

https://docs.gitlab.com/runner/configuration/runner_autoscale_aws/

is outdated and still instructs users to use the docker+machine executor.

However:

This creates confusion for users because the linked doc appears to describe a recommended autoscaling method, but in reality it relies entirely on deprecated and unsupported components.

Further details

Users following this document will attempt to configure autoscaling runners with docker+machine. This leads to:

  • Compatibility errors (for example Docker API mismatches such as client version 1.43 is too old)
  • Instability when creating AWS instances
  • Unsupported docker-machine behaviors
  • An autoscaling method that GitLab no longer recommends or maintains

GitLab now has a modern and fully supported solution for autoscaling runners on AWS:
the GitLab Runner Autoscaler (Instance Group Autoscaler).

Updating the documentation will prevent new users from adopting a deprecated architecture and guide them toward the supported solution.

Target audience:

  • DevOps engineers deploying autoscaled GitLab Runners on AWS
  • Cloud infrastructure teams following GitLab documentation

Proposal

Who can address the issue

A technical writer in collaboration with the Runner team or compute/infra specialists familiar with autoscaling architecture.

Other links/references

Edited by 🤖 GitLab Bot 🤖