docs: update redirecting documentation links

The link checker (lychee, --accept=200,403,429) rejects 3xx responses,
and several documentation links now permanently redirect:

- opensearch.org/docs/... moved to docs.opensearch.org/... (the docs
  site migrated to its own subdomain)
- opensearch.org/downloads.html#opensearch -> opensearch.org/downloads/
- opensearch.org/samples/docker-compose.yml -> the current wp-content path
- discuss.opendistrocommunity.dev/c/clients/ -> forum.opensearch.org/c/clients/60

Point each link at the final 200 target so the checker passes without
following redirects.

Signed-off-by: Sean Chittenden <sean.chittenden@crowdstrike.com>

Author: sean-

.github/workflows/links.yml

@@ -9,12 +9,58 @@ jobs:
 
     steps:
       - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v6
-      - name: lychee Link Checker
-        id: lychee
+
+      # Blocking: fail the build only on genuinely broken links (4xx/5xx,
+      # DNS failures, timeouts). Redirects are accepted here so a moved link
+      # does not break CI on its own -- the pass below surfaces those.
+      - name: Check for broken links
+        id: lychee-broken
         uses: lycheeverse/lychee-action@e7477775783ea5526144ba13e8db5eec57747ce8 # v2.9.0
         with:
-          args: --accept=200,403,429 --max-retries=3 --retry-wait-time=10 "**/*.html" "**/*.md" "**/*.txt" "**/*.json" --exclude "https://opensearch-domain.region.com/" --exclude "https://github.com/\[your*" --exclude "https://localhost:9200" --exclude "https://codecov.io/gh/opensearch-project/opensearch-go/branch/main/graph/badge.svg"
+          args: --accept=200,206,301,302,307,308,403,429 --max-retries=3 --retry-wait-time=10 "**/*.html" "**/*.md" "**/*.txt" "**/*.json" --exclude "https://opensearch-domain.region.com/" --exclude "https://github.com/\[your*" --exclude "https://localhost:9200" --exclude "https://codecov.io/gh/opensearch-project/opensearch-go/branch/main/graph/badge.svg"
+          fail: true
+          jobSummary: true
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+
+      # Non-blocking: surface permanent redirects (301/308) so their links can
+      # be updated to point at the final destination. --max-redirects=0 makes
+      # lychee report the redirect status instead of following it; 302/307 stay
+      # accepted because temporary redirects are not a signal to rewrite a link.
+      # LICENSE.txt/NOTICE.txt are excluded here: their URLs are canonical
+      # license text and standard attribution wording, not links to rewrite.
+      # fail:false + if:always() so this always reports without breaking CI.
+      - name: Check for permanently-redirecting links
+        id: lychee-redirects
+        if: always()
+        uses: lycheeverse/lychee-action@e7477775783ea5526144ba13e8db5eec57747ce8 # v2.9.0
+        with:
+          args: --accept=200,206,302,307,403,429 --max-redirects=0 --max-retries=3 --retry-wait-time=10 --exclude-path LICENSE.txt --exclude-path NOTICE.txt "**/*.html" "**/*.md" "**/*.txt" "**/*.json" --exclude "https://opensearch-domain.region.com/" --exclude "https://github.com/\[your*" --exclude "https://localhost:9200" --exclude "https://codecov.io/gh/opensearch-project/opensearch-go/branch/main/graph/badge.svg"
+          fail: false
+          jobSummary: true
+          output: lychee/redirects.md
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+
+      # Turn each redirect the pass above found into a PR annotation, so a moved
+      # link shows up inline on the PR (Files changed + checks summary) instead
+      # of only in the run's job summary. Never fails the build.
+      - name: Annotate redirecting links
+        if: always()
+        run: |
+          report="lychee/redirects.md"
+          [ -f "$report" ] || { echo "no redirect report found; nothing to annotate"; exit 0; }
+          awk '
+            /^### Errors in / { file=$0; sub(/^### Errors in /, "", file); next }
+            /^\* \[30[0-9]\]/ {
+              url=$0; sub(/^[^<]*</, "", url); sub(/>.*/, "", url)
+              code=$0; sub(/^\* \[/, "", code); sub(/\].*/, "", code)
+              line=""; col=""; tmp=$0
+              if (sub(/^.*\(at /, "", tmp) && match(tmp, /^[0-9]+:[0-9]+/)) {
+                pos=substr(tmp, 1, RLENGTH); split(pos, a, ":"); line=a[1]; col=a[2]
+              }
+              printf "::warning file=%s,line=%s,col=%s,title=Redirecting link::%s redirects (%s) -- update to its final destination\n", file, line, col, url, code
+            }
+          ' "$report"
         env:
           GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
-      - name: Fail if there were link errors
-        run: exit ${{ steps.lychee.outputs.exit_code }}

ADMINS.md

@@ -21,7 +21,7 @@ This document explains who the admins are (see below), what they do in this repo
 
 ## Admin Responsibilities
 
-As an admin you own stewartship of the repository and its settings. Admins have [admin-level permissions on a repository](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization). Use those privileges to serve the community and protect the repository as follows.
+As an admin you own stewartship of the repository and its settings. Admins have [admin-level permissions on a repository](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization). Use those privileges to serve the community and protect the repository as follows.
 
 ### Prioritize Security
 

COMPATIBILITY.md

@@ -3,7 +3,7 @@
 
 ## Compatibility with OpenSearch
 
-The below matrix shows the compatibility of the [`opensearch-go`](https://pkg.go.dev/github.com/opensearch-project/opensearch-go) with versions of [`OpenSearch`](https://opensearch.org/downloads.html#opensearch). Version ranges are inclusive of both endpoints.
+The below matrix shows the compatibility of the [`opensearch-go`](https://pkg.go.dev/github.com/opensearch-project/opensearch-go) with versions of [`OpenSearch`](https://opensearch.org/downloads/). Version ranges are inclusive of both endpoints.
 
 | Client Version | OpenSearch Version |
 | -------------- | ------------------ |
@@ -20,4 +20,4 @@ Starting with 5.x, the officially supported (CI-tested) set tracks the OpenSearc
 
 ## Upgrading
 
-Major versions of OpenSearch introduce breaking changes that require careful upgrades of the client. While `opensearch-go-client` 2.0.0 works against the latest OpenSearch 1.x, certain deprecated features removed in OpenSearch 2.0 have also been removed from the client. Please refer to the [OpenSearch documentation](https://opensearch.org/docs/latest/clients/index/) for more information.
+Major versions of OpenSearch introduce breaking changes that require careful upgrades of the client. While `opensearch-go-client` 2.0.0 works against the latest OpenSearch 1.x, certain deprecated features removed in OpenSearch 2.0 have also been removed from the client. Please refer to the [OpenSearch documentation](https://docs.opensearch.org/latest/clients/index/) for more information.

CONTRIBUTING.md

@@ -45,7 +45,7 @@ OpenSearch is an open source product released under the Apache 2.0 license (see
 
 We respect intellectual property rights of others and we want to make sure all incoming contributions are correctly attributed and licensed. A Developer Certificate of Origin (DCO) is a lightweight mechanism to do that.
 
-The DCO is a declaration attached to every contribution made by every developer. In the commit message of the contribution, the developer simply adds a `Signed-off-by` statement and thereby agrees to the DCO, which you can find below or at [DeveloperCertificate.org](http://developercertificate.org/).
+The DCO is a declaration attached to every contribution made by every developer. In the commit message of the contribution, the developer simply adds a `Signed-off-by` statement and thereby agrees to the DCO, which you can find below or at [DeveloperCertificate.org](https://developercertificate.org/).
 
 ```
 Developer's Certificate of Origin 1.1

DEVELOPER_GUIDE.md

@@ -61,7 +61,7 @@ OpenSearch Go Client builds using [Go](https://go.dev/doc/install) 1.24 at a min
 
 #### Docker
 
-[Docker](https://docs.docker.com/get-docker/) is required for building some OpenSearch artifacts and executing integration tests.
+[Docker](https://docs.docker.com/get-started/get-docker/) is required for building some OpenSearch artifacts and executing integration tests.
 
 #### Windows
 

README.md

@@ -1,4 +1,4 @@
-[![Go Reference](https://pkg.go.dev/badge/github.com/opensearch-project/opensearch-go.svg)](https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v5) [![Build](https://github.com/opensearch-project/opensearch-go/actions/workflows/lint.yml/badge.svg)](https://github.com/opensearch-project/opensearch-go/actions/workflows/lint.yml) [![Unit](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-unit.yml/badge.svg)](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-unit.yml) [![Integration](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-integration.yml/badge.svg)](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-integration.yml) [![codecov](https://codecov.io/gh/opensearch-project/opensearch-go/branch/main/graph/badge.svg?token=MI9g3KYHVx)](https://codecov.io/gh/opensearch-project/opensearch-go) [![Chat](https://img.shields.io/badge/chat-on%20forums-blue)](https://discuss.opendistrocommunity.dev/c/clients/) ![PRs welcome!](https://img.shields.io/badge/PRs-welcome!-success)
+[![Go Reference](https://pkg.go.dev/badge/github.com/opensearch-project/opensearch-go.svg)](https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v5) [![Build](https://github.com/opensearch-project/opensearch-go/actions/workflows/lint.yml/badge.svg)](https://github.com/opensearch-project/opensearch-go/actions/workflows/lint.yml) [![Unit](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-unit.yml/badge.svg)](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-unit.yml) [![Integration](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-integration.yml/badge.svg)](https://github.com/opensearch-project/opensearch-go/actions/workflows/test-integration.yml) [![codecov](https://codecov.io/gh/opensearch-project/opensearch-go/branch/main/graph/badge.svg?token=MI9g3KYHVx)](https://app.codecov.io/gh/opensearch-project/opensearch-go) [![Chat](https://img.shields.io/badge/chat-on%20forums-blue)](https://forum.opensearch.org/c/clients/60) ![PRs welcome!](https://img.shields.io/badge/PRs-welcome!-success)
 
 ![OpenSearch logo](OpenSearch.svg)
 
@@ -132,9 +132,9 @@ Next steps:
 - [Developer Guide](DEVELOPER_GUIDE.md)
 - [User Guide](USER_GUIDE.md)
 - [Upgrade Tool (`osapifix`)](cmd/osapifix/README.md)
-- [Documentation](https://opensearch.org/docs/latest/clients/go/)
+- [Documentation](https://docs.opensearch.org/latest/clients/go/)
 - [API Documentation](https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v5)
-- Need help? Try [Forums](https://discuss.opendistrocommunity.dev/c/clients/)
+- Need help? Try [Forums](https://forum.opensearch.org/c/clients/60)
 - [Project Principles](https://opensearch.org/#principles)
 - [Contributing to OpenSearch](CONTRIBUTING.md)
 - [Maintainer Responsibilities](MAINTAINERS.md)

SECURITY.md

@@ -1,3 +1,3 @@
 ## Reporting a Vulnerability
 
-If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/) or directly via email to aws-security@amazon.com. Please do **not** create a public GitHub issue.
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting/) or directly via email to aws-security@amazon.com. Please do **not** create a public GitHub issue.

USER_GUIDE.md

@@ -231,7 +231,7 @@ Before starting, we strongly recommend reading the full AWS documentation regard
 
 Import the request signer from `signer/awsv2`. It signs each request with AWS Signature Version 4 (SigV4) using AWS SDK for Go v2 and automatically discovers AWS credentials from the `~/.aws` folder or environment variables.
 
-To read more about SigV4 see [Signature Version 4 signing process](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html)
+To read more about SigV4 see [Signature Version 4 signing process](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html)
 
 The signer caches credentials so SigV4 signing does not call `Credentials.Retrieve` on every request, which matters most for STS-backed providers (assume-role, web identity, IRSA).
 

guides/indexing-index_lifecycle.md

@@ -8,7 +8,7 @@ This guide covers OpenSearch Golang Client API actions for Index Lifecycle. You'
 
 ## Setup
 
-In this guide, we will need an OpenSearch cluster with more than one node. Let's use the sample [docker-compose.yml](https://opensearch.org/samples/docker-compose.yml) to start a cluster with two nodes. The cluster's API will be available at `localhost:9200` with basic authentication enabled with default username and password of `admin:< admin password >`.
+In this guide, we will need an OpenSearch cluster with more than one node. Let's use the sample [docker-compose.yml](https://opensearch.org/wp-content/uploads/2025/02/docker-compose.yml) to start a cluster with two nodes. The cluster's API will be available at `localhost:9200` with basic authentication enabled with default username and password of `admin:< admin password >`.
 
 To start the cluster, run the following command:
 

guides/transport-observer_metrics.md

@@ -78,7 +78,7 @@ http.Handle("/metrics", promhttp.HandlerFor(promReg, promhttp.HandlerOpts{}))
 
 ### Shipped metrics
 
-`osprom` ships two sinks covering the [RED](https://grafana.com/blog/2018/08/02/the-red-method-how-to-instrument-your-services/) (Rate, Errors, Duration -- request-level health) and [USE](https://www.brendangregg.com/usemethod.html) (Utilization, Saturation, Errors -- resource health) methods. `NewRequestObserver` (RED) records request rate, errors, and duration labeled by `method`, status class (`2xx`/`3xx`/`4xx`/`5xx`, `error`, `unknown`), and `mode` (`request` for full-read, `stream` for time-to-first-byte); `NewPoolObserver` (USE) records connection-pool utilization, saturation, and errors from lifecycle events. See [`osprom/README.md`](../osprom/README.md) for the full metric list. Each sink receives the full transport event, so a custom `Observer` can label by route, index, or pool; the shipped ones stay deliberately low-cardinality. Tune the histogram buckets with `osprom.WithDurationBuckets` / `osprom.WithSizeBuckets`.
+`osprom` ships two sinks covering the [RED](https://grafana.com/blog/the-red-method-how-to-instrument-your-services/) (Rate, Errors, Duration -- request-level health) and [USE](https://www.brendangregg.com/usemethod.html) (Utilization, Saturation, Errors -- resource health) methods. `NewRequestObserver` (RED) records request rate, errors, and duration labeled by `method`, status class (`2xx`/`3xx`/`4xx`/`5xx`, `error`, `unknown`), and `mode` (`request` for full-read, `stream` for time-to-first-byte); `NewPoolObserver` (USE) records connection-pool utilization, saturation, and errors from lifecycle events. See [`osprom/README.md`](../osprom/README.md) for the full metric list. Each sink receives the full transport event, so a custom `Observer` can label by route, index, or pool; the shipped ones stay deliberately low-cardinality. Tune the histogram buckets with `osprom.WithDurationBuckets` / `osprom.WithSizeBuckets`.
 
 ### Custom sinks