Merge branch 'kpaizee-fix-redirects-ci-docs' into 'master'

Fix doc links that are redirecting

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/130445



Merged-by: Marcel Amirault <mamirault@gitlab.com>
Approved-by: Marcel Amirault <mamirault@gitlab.com>
Co-authored-by: Kati Paizee <kpaizee@gitlab.com>

doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md

@@ -17,7 +17,7 @@ Ensure your own [runners are configured](../../runners/index.md).
 
 ## Prerequisites
 
-- An [AWS account](https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/).
+- An [AWS account](https://repost.aws/knowledge-center/create-and-activate-aws-account).
   Sign in with an existing AWS account or create a new one.
 - In this guide, you create an infrastructure in [`us-east-2` region](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html).
   You can use any region, but do not change it after you begin.

doc/ci/cloud_services/azure/index.md

@@ -135,7 +135,7 @@ The CI/CD variables are:
 
 - `AZURE_CLIENT_ID`: The [application client ID you saved earlier](#create-azure-ad-application-and-service-principal).
 - `AZURE_TENANT_ID`: Your Azure Active Directory. You can
-  [find it by using the Azure CLI or Azure Portal](https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).
+  [find it by using the Azure CLI or Azure Portal](https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/how-to-find-tenant).
 - `GITLAB_OIDC_TOKEN`: An OIDC [ID token](../../yaml/index.md#id_tokens).
 
 ## Troubleshooting

doc/ci/cloud_services/index.md

@@ -14,7 +14,7 @@ WARNING:
 `CI_JOB_JWT` and `CI_JOB_JWT_V2` were [deprecated in GitLab 15.9](../../update/deprecations.md#old-versions-of-json-web-tokens-are-deprecated)
 and are scheduled to be removed in GitLab 16.5. Use [ID tokens](../yaml/index.md#id_tokens) instead.
 
-GitLab CI/CD supports [OpenID Connect (OIDC)](https://openid.net/connect/faq/) to
+GitLab CI/CD supports [OpenID Connect (OIDC)](https://openid.net/developers/how-connect-works/) to
 give your build and deployment jobs access to cloud credentials and services.
 Historically, teams stored secrets in projects or applied permissions on the GitLab Runner
 instance to build and deploy. OIDC capable [ID tokens](../yaml/index.md#id_tokens) are configurable

doc/ci/testing/load_performance_testing.md

@@ -59,7 +59,7 @@ Configuring your Load Performance Testing job can be broken down into several di
 
 ### Determine the test parameters
 
-The first thing you need to do is determine the [type of load test](https://k6.io/docs/test-types/introduction)
+The first thing you need to do is determine the [type of load test](https://k6.io/docs/test-types/load-test-types/)
 you want to run, and how you want it to run (for example, the number of users, throughput, and so on).
 
 Refer to the [k6 docs](https://k6.io/docs/), especially the [k6 testing guides](https://k6.io/docs/testing-guides),
@@ -79,7 +79,7 @@ We strongly recommend [not running these tests against a production environment]
 ### Write the load performance test
 
 After the environment is prepared, you can write the k6 test itself. k6 is a flexible
-tool and can be used to run [many kinds of performance tests](https://k6.io/docs/test-types/introduction).
+tool and can be used to run [many kinds of performance tests](https://k6.io/docs/test-types/load-test-types/).
 Refer to the [k6 documentation](https://k6.io/docs/) for detailed information on how to write tests.
 
 ### Configure the test in GitLab CI/CD
@@ -151,7 +151,7 @@ The CI/CD YAML configuration example above works for testing against static envi
 but it can be extended to work with [review apps](../review_apps/index.md) or
 [dynamic environments](../environments/index.md) with a few extra steps.
 
-The best approach is to capture the dynamic URL in a [`.env` file](https://docs.docker.com/compose/env-file/)
+The best approach is to capture the dynamic URL in a [`.env` file](https://docs.docker.com/compose/environment-variables/env-file/)
 as a job artifact to be shared, then use a custom CI/CD variable we've provided named `K6_DOCKER_OPTIONS`
 to configure the k6 Docker container to use the file. With this, k6 can then use any
 environment variables from the `.env` file in scripts using standard JavaScript,