Update redirecting links

Ravlen · Roshni Sarangadharan · commit e9582e04da66 · 2026-01-28T23:03:10.000+05:30
diff --git a/docs/configuration/advanced-configuration.md b/docs/configuration/advanced-configuration.md
@@ -1637,7 +1637,7 @@ Example `config.toml`:
 
 The following parameters define native support for Google Cloud Storage. For more information
 about these values, see the
-[Google Cloud Storage (GCS) authentication documentation](https://cloud.google.com/storage/docs/authentication#service_accounts).
+[Google Cloud Storage (GCS) authentication documentation](https://docs.cloud.google.com/storage/docs/authentication#service_accounts).
 
 | Parameter         | Type   | Description |
 |-------------------|--------|-------------|
@@ -1686,7 +1686,7 @@ When you use GitLab Runner with Google Cloud ADC, you typically use the default
     BucketName = "runners-cache"
 ```
 
-If you use ADC, be sure that the service account that you use has the `iam.serviceAccounts.signBlob` permission. Typically this is done by granting the [Service Account Token Creator role](https://cloud.google.com/iam/docs/service-account-permissions#token-creator-role) to the service account.
+If you use ADC, be sure that the service account that you use has the `iam.serviceAccounts.signBlob` permission. Typically this is done by granting the [Service Account Token Creator role](https://docs.cloud.google.com/iam/docs/service-account-permissions#token-creator-role) to the service account.
 
 #### Workload Identity Federation for GKE
 
diff --git a/docs/configuration/runner_autoscale_aws/_index.md b/docs/configuration/runner_autoscale_aws/_index.md
@@ -59,7 +59,7 @@ You have to make sure that ports `2376` and `22` are accessible by the [Runner M
 
 ### AWS credentials
 
-You'll need an [AWS Access Key](https://docs.aws.amazon.com/general/latest/gr/managing-aws-access-keys.html)
+You'll need an [AWS Access Key](https://docs.aws.amazon.com/IAM/latest/UserGuide/security-creds.html)
 tied to a user with permission to scale (EC2) and update the cache (via S3).
 Create a new user with [policies](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-policies-for-amazon-ec2.html)
 for EC2 (AmazonEC2FullAccess) and S3. For more information about the
@@ -477,5 +477,5 @@ be an issue.
 You can read the following use cases from which this tutorial was (heavily)
 influenced:
 
-- [HumanGeo switched from Jenkins to GitLab](https://about.gitlab.com/blog/2017/11/14/humangeo-switches-jenkins-gitlab-ci/)
-- [Substrakt Health - Autoscale GitLab CI/CD runners and save 90% on EC2 costs](https://about.gitlab.com/blog/2017/11/23/autoscale-ci-runners/)
+- [HumanGeo switched from Jenkins to GitLab](https://about.gitlab.com/blog/humangeo-switches-jenkins-gitlab-ci/)
+- [Substrakt Health - Autoscale GitLab CI/CD runners and save 90% on EC2 costs](https://about.gitlab.com/blog/autoscale-ci-runners/)
diff --git a/docs/configuration/runner_autoscale_aws_fargate/_index.md b/docs/configuration/runner_autoscale_aws_fargate/_index.md
@@ -56,7 +56,7 @@ To work around this limitation, you can:
 - Create multiple ECS task definitions with different images and specify the ARN in the `FARGATE_TASK_DEFINITION` CI/CD variable.
 - Consider creating an EKS cluster by following the official [AWS EKS Blueprints](https://aws-ia.github.io/terraform-aws-eks-blueprints/).
 
-For more information, see [Get started with GitLab EKS Fargate runners in 1 hour and zero code](https://about.gitlab.com/blog/2023/05/24/eks-fargate-runner/).
+For more information, see [Get started with GitLab EKS Fargate runners in 1 hour and zero code](https://about.gitlab.com/blog/eks-fargate-runner/).
 
 {{< /alert >}}
 
@@ -283,7 +283,7 @@ An Amazon ECS cluster is a grouping of ECS container instances.
 1. Select **Update Cluster**.
 1. Next to `Default capacity provider strategy`, select **Add another provider** and choose `FARGATE`. Select **Update**.
 
-Refer to the AWS [documentation](https://docs.aws.amazon.com/AmazonECS/latest/userguide/create_cluster.html)
+Refer to the AWS [documentation](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html)
 for detailed instructions on setting up and working with a cluster on ECS Fargate.
 
 ## Step 6: Create an ECS task definition
@@ -380,7 +380,7 @@ the private subnet:
       with the same configuration as the VPC you deleted and update the `cird` address, for example `10.0.0.0/23`.
    1. [Create a public subnet](https://docs.aws.amazon.com/vpc/latest/privatelink/interface-endpoints.html) with the same configuration as the subnet you deleted. Use a `cird` address that is a subset
       of the VPC address range, for example `10.0.0.0/24`.
-1. [Create a private subnet](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-subnets.html#create-subnets) with the same
+1. [Create a private subnet](https://docs.aws.amazon.com/vpc/latest/userguide/create-subnet.html#create-subnets) with the same
    configuration as the public subnet. Use a `cird` address range that does not overlap the public subnet range, for
    example `10.0.1.0/24`.
 1. [Create a NAT gateway](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html), and place it inside
@@ -434,7 +434,7 @@ For more information, see the following AWS documentation:
 - [Amazon ECS task execution IAM role](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_execution_IAM_role.html)
 - [Amazon ECR interface VPC endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/AmazonECR/latest/userguide/vpc-endpoints.html)
 - [Amazon ECS interface VPC endpoints](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/vpc-endpoints.html)
-- [VPC with public and private subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Scenario2.html)
+- [VPC with public and private subnets](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-example-private-subnets-nat.html)
 
 ## Troubleshooting
 
diff --git a/docs/development/_index.md b/docs/development/_index.md
@@ -519,4 +519,4 @@ you can use `cd $Env:RUNNER_SRC`.
 
 1. [Reviewing GitLab Runner merge requests](reviewing-gitlab-runner.md)
 1. [Add support for new Windows Version](add-windows-version.md)
-1. [Runner Group - Team Resources](https://handbook.gitlab.com/handbook/engineering/devops/ops/verify/runner/team-resources/#overview)
+1. [Runner Group - Team Resources](https://handbook.gitlab.com/handbook/engineering/devops/runner/team-resources/#overview)
diff --git a/docs/executors/_index.md b/docs/executors/_index.md
@@ -38,7 +38,7 @@ new ones. For more information, see [Contributing new executors](https://gitlab.
 ## Prerequisites for non-Docker executors
 
 Executors that do not [rely on a helper image](../configuration/advanced-configuration.md#helper-image) require a Git
-installation on the target machine and in the `PATH`. Always use the [latest available version of Git](https://git-scm.com/downloads).
+installation on the target machine and in the `PATH`. Always use the [latest available version of Git](https://git-scm.com/downloads/).
 
 GitLab Runner uses the `git lfs` command if [Git LFS](https://git-lfs.com/) is installed
 on the target machine. Ensure Git LFS is up to date on any systems where GitLab Runner uses these executors.
diff --git a/docs/executors/custom_examples/libvirt.md b/docs/executors/custom_examples/libvirt.md
@@ -18,9 +18,9 @@ and VM will be deleted.
 
 This document does not try to explain how to set up libvirt, since it's
 out of scope. However, this driver was tested using
-[GCP Nested Virtualization](https://cloud.google.com/compute/docs/instances/nested-virtualization/overview),
+[GCP Nested Virtualization](https://docs.cloud.google.com/compute/docs/instances/nested-virtualization/overview),
 which also has
-[details on how to set up libvirt](https://cloud.google.com/compute/docs/instances/nested-virtualization/overview#starting_a_private_bridge_between_the_host_and_nested_vms)
+[details on how to set up libvirt](https://docs.cloud.google.com/compute/docs/instances/nested-virtualization/overview#starting_a_private_bridge_between_the_host_and_nested_vms)
 with bridge networking. This example will use the `default` network that
 comes with when installing libvirt so make sure it's running.
 
diff --git a/docs/executors/docker_autoscaler.md b/docs/executors/docker_autoscaler.md
@@ -139,7 +139,7 @@ concurrent = 10
 
 Prerequisites:
 
-- A VM image with [Docker Engine](https://docs.docker.com/engine/) installed, such as [`COS`](https://cloud.google.com/container-optimized-os/docs).
+- A VM image with [Docker Engine](https://docs.docker.com/engine/) installed, such as [`COS`](https://docs.cloud.google.com/container-optimized-os/docs).
 
   {{< alert type="note" >}}
 
diff --git a/docs/executors/docker_machine.md b/docs/executors/docker_machine.md
@@ -159,7 +159,7 @@ You can also use the [Kubernetes executor](kubernetes/_index.md) for this purpos
 {{< /alert >}}
 
 You can use the Docker Machine [fork](#forked-version-of-docker-machine) to create
-[Google Compute Engine instances with graphics processing units (GPUs)](https://cloud.google.com/compute/docs/gpus/).
+[Google Compute Engine instances with graphics processing units (GPUs)](https://docs.cloud.google.com/compute/docs/gpus).
 
 #### Docker Machine GPU options
 
@@ -168,12 +168,12 @@ To create an instance with GPUs, use these Docker Machine options:
 | Option                        | Example                        | Description |
 |-------------------------------|--------------------------------|-------------|
 | `--google-accelerator`        | `type=nvidia-tesla-p4,count=1` | Specifies the type and number of GPU accelerators to attach to the instance (`type=TYPE,count=N` format) |
-| `--google-maintenance-policy` | `TERMINATE`                    | Always use `TERMINATE` because [Google Cloud does not allow live migration of GPU instances](https://cloud.google.com/compute/docs/instances/live-migration-process). |
-| `--google-machine-image`      | `https://www.googleapis.com/compute/v1/projects/deeplearning-platform-release/global/images/family/tf2-ent-2-3-cu110` | The URL of a GPU-enabled operating system. See the [list of available images](https://cloud.google.com/deep-learning-vm/docs/images). |
+| `--google-maintenance-policy` | `TERMINATE`                    | Always use `TERMINATE` because [Google Cloud does not allow live migration of GPU instances](https://docs.cloud.google.com/compute/docs/instances/live-migration-process). |
+| `--google-machine-image`      | `https://www.googleapis.com/compute/v1/projects/deeplearning-platform-release/global/images/family/tf2-ent-2-3-cu110` | The URL of a GPU-enabled operating system. See the [list of available images](https://docs.cloud.google.com/deep-learning-vm/docs/images). |
 | `--google-metadata`           | `install-nvidia-driver=True`   | This flag tells the image to install the NVIDIA GPU driver. |
 
-These arguments map to [command-line arguments for `gcloud compute`](https://cloud.google.com/compute/docs/gpus/create-vm-with-gpus#gcloud_1).
-See the [Google documentation on creating VMs with attached GPUs](https://cloud.google.com/compute/docs/gpus/create-vm-with-gpus)
+These arguments map to [command-line arguments for `gcloud compute`](https://docs.cloud.google.com/compute/docs/gcloud-compute).
+See the [Google documentation on creating VMs with attached GPUs](https://docs.cloud.google.com/compute/docs/gpus/create-vm-with-gpus)
 for more details.
 
 #### Verifying Docker Machine options
diff --git a/docs/executors/virtualbox.md b/docs/executors/virtualbox.md
@@ -109,7 +109,7 @@ To use VirtualBox with Windows, you can install Cygwin or PowerShell.
 
 ### Use native OpenSSH and PowerShell
 
-- Install [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.4)
+- Install [PowerShell](https://learn.microsoft.com/en-us/powershell/scripting/install/install-powershell-on-windows?view=powershell-7.4)
 - Install and configure [OpenSSH](https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse?tabs=powershell#install-openssh-for-windows)
 - Install [Git for Windows](https://git-scm.com/)
 - Configure the [default shell as `pwsh`](https://learn.microsoft.com/en-us/windows-server/administration/OpenSSH/openssh-server-configuration#configuring-the-default-shell-for-openssh-in-windows). Update example with the correct full path:
diff --git a/docs/fleet_scaling/fleeting.md b/docs/fleet_scaling/fleeting.md
@@ -18,7 +18,7 @@ GitLab maintains these official plugins:
 
 | Cloud provider                                                             | Notes |
 |----------------------------------------------------------------------------|-------|
-| [Google Cloud](https://gitlab.com/gitlab-org/fleeting/plugins/googlecloud) | Uses [Google Cloud instance groups](https://cloud.google.com/compute/docs/instance-groups) |
+| [Google Cloud](https://gitlab.com/gitlab-org/fleeting/plugins/googlecloud) | Uses [Google Cloud instance groups](https://docs.cloud.google.com/compute/docs/instance-groups) |
 | [AWS](https://gitlab.com/gitlab-org/fleeting/plugins/aws)                  | Uses [AWS Auto Scaling groups](https://docs.aws.amazon.com/autoscaling/ec2/userguide/auto-scaling-groups.html) |
 | [Azure](https://gitlab.com/gitlab-org/fleeting/plugins/azure)              | Uses Azure [Virtual Machine Scale Sets](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview). Only [Uniform orchestration](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes#scale-sets-with-uniform-orchestration) mode is supported. |
 
diff --git a/docs/grit/_index.md b/docs/grit/_index.md
@@ -194,7 +194,7 @@ GRIT follows the GitLab Code of Conduct, which is adapted from the [Contributor
 When contributing to GRIT, follow these guidelines:
 
 - Review the [GORP Guidelines](https://gitlab.com/gitlab-org/ci-cd/runner-tools/grit/-/blob/main/GORP.md) for overall architectural design.
-- Adhere to [Google's best practices for using Terraform](https://cloud.google.com/docs/terraform/best-practices/general-style-structure).
+- Adhere to [Google's best practices for using Terraform](https://docs.cloud.google.com/docs/terraform/best-practices/general-style-structure).
 - Follow the composable module approach to reduce complexity and repetition.
 - Include appropriate Go tests for your contributions.
 
