seqeralabs · gavinelder · Apr 27, 2026
diff --git a/platform-cloud/docs/compute-envs/aws-batch.md b/platform-cloud/docs/compute-envs/aws-batch.md
@@ -69,6 +69,10 @@ Make sure the [Lustre client](https://docs.aws.amazon.com/fsx/latest/LustreGuide
 
 ## Required Platform IAM permissions
 
+:::tip Canonical reference moved
+The IAM permissions, IAM user/role creation steps, and credential options for AWS Batch are now consolidated in [AWS integration > IAM policies](/platform-cloud/integrations/cloud-providers/aws/iam-policies) and [AWS integration > Credentials](/platform-cloud/integrations/cloud-providers/aws/credentials). The same content remains here for now and will be removed in a future release.
+:::
+
 To create and launch pipelines, explore buckets with Data Explorer or run Studio sessions with the AWS Batch compute environment, an IAM user with specific permissions must be provided. Some permissions are mandatory for the compute environment to be created and function correctly, while others are optional and used for example to provide list of values to pick from in the Platform UI.
 
 Permissions can be attached directly to an [IAM user](#iam-user-creation), or to an [IAM role](#iam-role-creation-optional) that the IAM user can assume when accessing AWS resources.
@@ -741,7 +745,7 @@ Depending on the provided configuration in the UI, Seqera might also create IAM
 1. Select **AWS Batch** as the target platform.
 1. From the **Credentials** drop-down, select existing AWS credentials, or select **+** to add new credentials. If you're using existing credentials, skip to step 9.
     :::note
-    You can create multiple credentials in your Seqera environment. See [Credentials](../credentials/overview).
+    You can create multiple credentials in your Seqera environment. See [Credentials](/platform-cloud/integrations/overview).
     :::
 1. Enter a name, e.g., _AWS Credentials_.
 1. Under **AWS credential mode**, select **Keys** or **Role**.
@@ -981,7 +985,7 @@ AWS Batch creates resources that you may be charged for in your AWS account. See
 1. Select **AWS Batch** as the target platform.
 1. From the **Credentials** drop-down, select existing AWS credentials, or select **+** to add new credentials. If you're using existing credentials, skip to step 9.
     :::note
-    You can create multiple credentials in your Seqera environment. See [Credentials](../credentials/overview).
+    You can create multiple credentials in your Seqera environment. See [Credentials](/platform-cloud/integrations/overview).
     :::
 1. Enter a name, e.g., _AWS Credentials_.
 1. Under **AWS credential mode**, select **Keys** or **Role**.

diff --git a/platform-cloud/docs/compute-envs/aws-cloud.md b/platform-cloud/docs/compute-envs/aws-cloud.md
@@ -60,6 +60,10 @@ The following regions are currently supported:
 
 ## Required Platform IAM permissions
 
+:::tip Canonical reference moved
+The IAM permissions, IAM user/role creation steps, and credential options for AWS Cloud are now consolidated in [AWS integration > IAM policies](/platform-cloud/integrations/cloud-providers/aws/iam-policies) (select the **AWS Cloud** tab) and [AWS integration > Credentials](/platform-cloud/integrations/cloud-providers/aws/credentials). The same content remains here for now and will be removed in a future release.
+:::
+
 To create and launch pipelines, explore buckets with Data Explorer or run Studio sessions with the AWS Cloud compute environment, an IAM user with specific permissions must be provided. Some permissions are mandatory for the compute environment to be created and function correctly, while others are optional and used for example to provide list of values to pick from in the Platform UI.
 
 Permissions can be attached directly to an [IAM user](#iam-user-creation), or to an [IAM role](#iam-role-creation-optional) that the IAM user can assume when accessing AWS resources.

diff --git a/platform-cloud/docs/compute-envs/azure-batch.md b/platform-cloud/docs/compute-envs/azure-batch.md
@@ -32,6 +32,10 @@ An Azure service principal is an identity created specifically for applications,
 
 ## Create Azure resources
 
+:::tip Canonical reference moved
+Storage and Batch account setup, role assignments, service principal registration, and credential setup for Azure are now consolidated in [Azure integration](/platform-cloud/integrations/cloud-providers/azure/overview) — see [Storage access](/platform-cloud/integrations/cloud-providers/azure/storage-access), [Roles & service principals](/platform-cloud/integrations/cloud-providers/azure/roles-and-service-principals), and [Credentials](/platform-cloud/integrations/cloud-providers/azure/credentials). The same content remains here for now and will be removed in a future release.
+:::
+
 ### Resource group
 
 Create a resource group to link your Azure Batch and Azure Storage account:
@@ -318,7 +322,7 @@ Create a Batch Forge Azure Batch compute environment:
 Batch Forge creates separate Azure Batch pools for the Nextflow head job and compute tasks by default (named `tower-pool-{envId}-head` and `tower-pool-{envId}-worker`). This prevents the head node from competing for resources with compute tasks and allows independent sizing of each pool.
 :::
 
-1. Select or create [**Container registry credentials**](../credentials/azure_registry_credentials) to authenticate a registry (used by the [Wave containers](https://docs.seqera.io/nextflow/wave) service). It is recommended to use an [Azure Container registry](https://azure.microsoft.com/en-gb/products/container-registry) within the same region for maximum performance.
+1. Select or create [**Container registry credentials**](/platform-cloud/integrations/container-registries/azure) to authenticate a registry (used by the [Wave containers](https://docs.seqera.io/nextflow/wave) service). It is recommended to use an [Azure Container registry](https://azure.microsoft.com/en-gb/products/container-registry) within the same region for maximum performance.
 1. Apply [**Resource labels**](../resource-labels/overview). This will populate the **Metadata** fields of the Azure Batch pools and jobs.
 1. Expand **Staging options** to include:
     - Optional [pre- or post-run Bash scripts](../launch/advanced#pre-and-post-run-scripts) that execute before or after the Nextflow pipeline execution in your environment.

diff --git a/platform-cloud/docs/compute-envs/azure-cloud.md b/platform-cloud/docs/compute-envs/azure-cloud.md
@@ -63,6 +63,10 @@ See [Register an application in Microsoft Entra ID](https://learn.microsoft.com/
 
 ### Required permissions
 
+:::tip Canonical reference moved
+The custom role JSON, app registration steps, and credential setup for Azure Cloud are now consolidated in [Azure integration > Roles & service principals](/platform-cloud/integrations/cloud-providers/azure/roles-and-service-principals) and [Azure integration > Credentials](/platform-cloud/integrations/cloud-providers/azure/credentials). The same content remains here for now and will be removed in a future release.
+:::
+
 For granular control over the permissions granted to Seqera, use [Azure custom roles](https://learn.microsoft.com/en-us/azure/role-based-access-control/custom-roles) and [assign](https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal) them to the service principal. The full role JSON definition is:
 
 ```json

diff --git a/platform-cloud/docs/compute-envs/eks.md b/platform-cloud/docs/compute-envs/eks.md
@@ -22,6 +22,10 @@ Once you meet all the prerequisites, configure an [Amazon EKS Compute Environmen
 
 ## Required Platform IAM permissions
 
+:::tip Canonical reference moved
+The IAM permissions, IAM user/role creation, and EKS-specific setup (Service Account IAM role for Fusion v2, `aws-auth` ConfigMap) are now consolidated in [AWS integration > IAM policies](/platform-cloud/integrations/cloud-providers/aws/iam-policies) (select the **Amazon EKS** tab), [AWS integration > Credentials](/platform-cloud/integrations/cloud-providers/aws/credentials), and [AWS integration > EKS additions](/platform-cloud/integrations/cloud-providers/aws/eks-additions). The same content remains here for now and will be removed in a future release.
+:::
+
 Seqera Platform requires an IAM user with specific permissions to launch pipelines, explore buckets with Data Explorer, and run Studio sessions on the AWS EKS compute environment. Some permissions are mandatory for the compute environment to function correctly, while others are optional and enable features like populating dropdown lists in the Platform UI.
 
 Attach permissions directly to an [IAM user](#iam-user-creation), or to an [IAM role](#iam-role-creation-optional) that the IAM user can assume.
@@ -405,7 +409,7 @@ Once all prerequisites are met, create a Seqera EKS compute environment:
 1. From the **Credentials** drop-down, select existing AWS credentials, or select **+** to add new credentials. If you're using existing credentials, skip to step 9. The user must have the IAM permissions required to describe and list EKS clusters, per Service Account role requirements.
 
     :::note
-    You can create multiple credentials in your Seqera environment. See [Credentials](../credentials/overview).
+    You can create multiple credentials in your Seqera environment. See [Credentials](/platform-cloud/integrations/overview).
     :::
 
 1. Enter a name, e.g., `EKS Credentials`.

diff --git a/platform-cloud/docs/compute-envs/gke.md b/platform-cloud/docs/compute-envs/gke.md
@@ -58,7 +58,7 @@ After you've prepared your Kubernetes cluster and granted cluster access to your
 1. Enter a name for the credentials, e.g., _GKE Credentials_.
 1. Enter the **Service account key** for your Google service account.
     :::tip
-    You can create multiple credentials in your Seqera environment. See [Credentials](../credentials/overview).
+    You can create multiple credentials in your Seqera environment. See [Credentials](/platform-cloud/integrations/overview).
     :::
 1. Select the **Location** of your GKE cluster.
     :::caution

diff --git a/platform-cloud/docs/compute-envs/google-cloud-batch.md b/platform-cloud/docs/compute-envs/google-cloud-batch.md
@@ -16,6 +16,10 @@ The guide is split into two parts:
 
 ## Configure Google Cloud
 
+:::tip Canonical reference moved
+Project setup, IAM roles, service account JSON keys, and Cloud Storage bucket setup for Google Cloud are now consolidated in [Google Cloud integration](/platform-cloud/integrations/cloud-providers/google/overview) — see [IAM](/platform-cloud/integrations/cloud-providers/google/iam), [Credentials](/platform-cloud/integrations/cloud-providers/google/credentials), and [Storage access](/platform-cloud/integrations/cloud-providers/google/storage-access). The same content remains here for now and will be removed in a future release.
+:::
+
 ### Create a project
 
 Go to the [Google Project Selector page](https://console.cloud.google.com/projectselector2) and select an existing project, or select **Create project**.

diff --git a/platform-cloud/docs/compute-envs/google-cloud.md b/platform-cloud/docs/compute-envs/google-cloud.md
@@ -79,6 +79,10 @@ To create and launch pipelines or Studio sessions with this compute environment
 
 ### Required permissions
 
+:::tip Canonical reference moved
+Service account permissions for the Google Cloud compute environment are now consolidated in [Google Cloud integration > IAM](/platform-cloud/integrations/cloud-providers/google/iam). The same content remains here for now and will be removed in a future release.
+:::
+
 #### Service account permissions
 
 [Create a custom service account](https://cloud.google.com/iam/docs/service-accounts-create#creating) with at least the following permissions:

diff --git a/platform-cloud/docs/compute-envs/hpc.md b/platform-cloud/docs/compute-envs/hpc.md
@@ -23,9 +23,9 @@ To launch pipelines into an **HPC** cluster from Seqera, the following requireme
 
 ## Credentials
 
-Seqera requires SSH access to your HPC cluster to run pipelines. Use [managed identities](../credentials/managed_identities) to enable granular access control and preserve individual cluster user identities.
+Seqera requires SSH access to your HPC cluster to run pipelines. Use [managed identities](/platform-cloud/integrations/identity/managed-identities) to enable granular access control and preserve individual cluster user identities.
 
-You can also use workspace [SSH credentials](../credentials/ssh_credentials) for cluster login, but this provides service account access to your HPC to all Platform users. This means that all users will be granted the same file system access, and all activity is logged under the same user account on your HPC cluster.
+You can also use workspace [SSH credentials](/platform-cloud/integrations/identity/ssh-credentials) for cluster login, but this provides service account access to your HPC to all Platform users. This means that all users will be granted the same file system access, and all activity is logged under the same user account on your HPC cluster.
 
 For HPC clusters that do not allow direct access through an SSH client, a secure connection can be authenticated with [Tower Agent](../supported_software/agent/overview).
 

diff --git a/platform-cloud/docs/compute-envs/k8s.md b/platform-cloud/docs/compute-envs/k8s.md
@@ -82,7 +82,7 @@ After you've prepared your Kubernetes cluster for Seqera integration, create a c
 1. From the **Credentials** drop-down, select existing Kubernetes credentials, or select **+** to add new credentials. If you choose to use existing credentials, skip to step 7.
 
     :::tip
-    You can create multiple credentials in your Seqera workspace. See [Credentials](../credentials/overview).
+    You can create multiple credentials in your Seqera workspace. See [Credentials](/platform-cloud/integrations/overview).
     :::
 
 1. Enter a name, such as _K8s Credentials_.

diff --git a/platform-cloud/docs/credentials/agent_credentials.md b/platform-cloud/docs/credentials/agent_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [agent, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/agent/credentials](/platform-cloud/integrations/agent/credentials). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 [Tower Agent](../supported_software/agent/overview) enables Seqera Platform to launch pipelines on HPC clusters that do not allow direct access through an SSH client. Tower Agent authenticates a secure connection with Seqera using a Tower Agent credential.
 
 ## Tower Agent sharing

diff --git a/platform-cloud/docs/credentials/aws_registry_credentials.md b/platform-cloud/docs/credentials/aws_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [aws, ecr, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/aws](/platform-cloud/integrations/container-registries/aws). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 AWS Elastic Container Registry (ECR) credentials allow the Wave container service to authenticate and pull container images from your private ECR repositories. Wave requires IAM user credentials with long-term access keys and appropriate ECR read permissions.
 
 :::note

diff --git a/platform-cloud/docs/credentials/azure_registry_credentials.md b/platform-cloud/docs/credentials/azure_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [azure, registry, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/azure](/platform-cloud/integrations/container-registries/azure). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 Azure Container Registry credentials allow the Wave container service to authenticate and pull container images from your private Azure registries. Azure uses Role-Based Access Control (RBAC) to manage registry access.
 
 :::note

diff --git a/platform-cloud/docs/credentials/container_registry_credentials.md b/platform-cloud/docs/credentials/container_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [credentials, container-registry, wave, docker, authentication]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/overview](/platform-cloud/integrations/container-registries/overview). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 Seqera Platform supports the configuration of credentials for the Wave container service to authenticate to private and public container registries. For more information about Wave, see [Wave containers](https://docs.seqera.io/wave).
 
 :::note

diff --git a/platform-cloud/docs/credentials/data_repositories.md b/platform-cloud/docs/credentials/data_repositories.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [data explorer, aws, azure, gcp, s3-compatible, api, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/data-sources/overview](/platform-cloud/integrations/data-sources/overview). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 Data Explorer requires programmatic access via valid credentials to browse and interact with remotely hosted private data repositories.
 
 To automatically connect to one or more data repositories, create a new credential that includes **Name** and **Provider**. Specific data repositories require additional information to connect.

diff --git a/platform-cloud/docs/credentials/docker_hub_registry_credentials.md b/platform-cloud/docs/credentials/docker_hub_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [docker, registry, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/docker-hub](/platform-cloud/integrations/container-registries/docker-hub). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 Docker Hub credentials allow the Wave container service to authenticate and pull container images from your Docker Hub repositories. Docker Hub uses personal access tokens (PATs) with read-only permissions for secure programmatic access.
 
 :::note

diff --git a/platform-cloud/docs/credentials/gitea_registry_credentials.md b/platform-cloud/docs/credentials/gitea_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [gitea, registry, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/gitea](/platform-cloud/integrations/container-registries/gitea). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 Gitea Container Registry credentials allow the Wave container service to authenticate and pull container images from your Gitea repositories. Gitea registries support [authentication][gitea-auth] using personal access tokens for programmatic access.
 
 :::note

diff --git a/platform-cloud/docs/credentials/github_registry_credentials.md b/platform-cloud/docs/credentials/github_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [github, registry, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/github](/platform-cloud/integrations/container-registries/github). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 GitHub Container Registry credentials allow the Wave container service to authenticate and pull container images from GitHub Packages. GitHub Packages only supports [authentication][github-pat] using a personal access token (classic) for programmatic access.
 
 :::note

diff --git a/platform-cloud/docs/credentials/gitlab_registry_credentials.md b/platform-cloud/docs/credentials/gitlab_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [gitlab, registry, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/gitlab](/platform-cloud/integrations/container-registries/gitlab). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 GitLab Container Registry credentials allow the Wave container service to authenticate and pull container images from your GitLab repositories. If your organization has enabled two-factor authentication (2FA), you must use a [personal access token][gitlab-pat] for [GitLab container registry authentication][gitlab-cr].
 
 :::note

diff --git a/platform-cloud/docs/credentials/google_registry_credentials.md b/platform-cloud/docs/credentials/google_registry_credentials.md
@@ -6,6 +6,10 @@ last updated: "2025-10-21"
 tags: [google, container, registry, artifact, credentials]
 ---
 
+:::info This page has moved
+Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/google](/platform-cloud/integrations/container-registries/google). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks.
+:::
+
 Google Cloud registry credentials allow the Wave container service to authenticate and pull container images from Google Artifact Registry. Google Cloud registries require programmatic access using service account keys with appropriate read permissions.
 
 :::note