## Summary Starting from GitLab Runner v18.9.0, the S3 download URLs for RPM packages using the old architecture naming convention (`amd64`, `arm64`, `arm`, `armhf`) return **403 Forbidden**. The architecture names were changed to RPM-native conventions but the old names were not kept as aliases. ## Affected URLs Any URL matching the pattern: ``` https://s3.dualstack.us-east-1.amazonaws.com/gitlab-runner-downloads/{latest,v18.9.0+}/rpm/gitlab-runner_{amd64,arm64,arm,armhf}.rpm ``` ## Verification | Architecture | v18.8.0 | v18.9.0+ / latest | |---|---|---| | `amd64` | 200 OK | **403 Forbidden** | | `arm64` | 200 OK | **403 Forbidden** | | `arm` | 200 OK | **403 Forbidden** | | `armhf` | 200 OK | **403 Forbidden** | | `x86_64` | 403 | **200 OK** | | `aarch64` | 200 OK | **200 OK** | | `armhfp` | 403 | **200 OK** | | `loongarch64` | 403 | **200 OK** | | `i686` | 200 OK | **200 OK** | | `riscv64` | 200 OK | **200 OK** | Note: `main` branch S3 uploads still include both old and new names, so bleeding-edge links work. Only tagged releases and `latest` are affected. ## Root cause Commit `781b86d1c` (Jan 6, 2026) changed `PackageFileArchs` in `magefiles/package.go` to use RPM-native naming: - `amd64` → `x86_64` - `arm64` → removed (only `aarch64`) - `arm` → removed - `armhf` → `armhfp` - `loong64` → `loongarch64` The old filenames were not preserved as S3 symlinks or copies, so existing users/scripts/docs referencing the old names get 403 errors. ## Impact - Users following the [manual install docs](https://docs.gitlab.com/runner/install/linux-manually/) who use `arm64` as the `${arch}` value (which the docs suggest) get a broken download - Any automation or scripts using the old naming convention for RPM downloads - The `packages.gitlab.com` YUM repository is **not affected** — it uses standard RPM naming and works correctly ## Documentation issues - `docs/install/linux-manually.md` line 56: RPM section comment still lists `arm64` as an example `${arch}` value - `docs/install/bleeding-edge.md` lines 72-79: Lists RPM links with old names (`amd64`, `arm`, `armhf`, `arm64`) that break when users substitute `main` with a version tag or `latest` as instructed ## Suggested fix 1. **Docs**: Update architecture examples and links to use the new RPM naming 2. **Consider**: Adding S3 aliases for the old names to avoid breaking existing automation (separate discussion)