diff --git a/platform-cloud/docs/compute-envs/aws-batch.md b/platform-cloud/docs/compute-envs/aws-batch.md index ae487cd2f..56c9bc263 100644 --- 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 index ecf633381..461702da5 100644 --- 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 index 8de2cf916..3a6c9fc67 100644 --- 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 index aea357d0b..c7dafe114 100644 --- 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 index bc518a7a0..201a1dd96 100644 --- 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 index c4c2b805e..00870222f 100644 --- 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 index cebd39709..88c63b734 100644 --- 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 index e9de8cc10..96911bcec 100644 --- 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 index c69182557..10dfb4f2f 100644 --- 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 index a5c1a9b2a..abab6a132 100644 --- 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 index 1c0aa9c6c..66cf3bf6b 100644 --- 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 index 78e2b9f0c..37691741f 100644 --- 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 index 7c6a94b26..681a8fd64 100644 --- 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 index a6323c4df..fffd91c05 100644 --- 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 index 98d6d466f..ed1ea0e3d 100644 --- 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 index b3e449e32..54672712a 100644 --- 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 index 185521174..797399436 100644 --- 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 index e8d63065c..200ee15c7 100644 --- 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 index 67c1415c1..561ea19cb 100644 --- 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 index be1ee983d..519e6cd17 100644 --- 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 diff --git a/platform-cloud/docs/credentials/managed_identities.md b/platform-cloud/docs/credentials/managed_identities.md index 795c08510..6f053d595 100644 --- a/platform-cloud/docs/credentials/managed_identities.md +++ b/platform-cloud/docs/credentials/managed_identities.md @@ -6,6 +6,10 @@ last updated: "2025-10-21" tags: [organizations, administration, managed identities, clusters, ssh, credentials] --- +:::info This page has moved +Documentation for this credential type now lives at [/platform-cloud/integrations/identity/managed-identities](/platform-cloud/integrations/identity/managed-identities). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks. +::: + Managed identities offer significant advantages for high performance computing (HPC) environments by enabling granular access control for individual workspace users. Unlike traditional SSH credentials that grant all workspace users access to HPC clusters using the same set of credentials, managed identities ensure each user’s activity is logged under their own credentials. This preservation of user identity is crucial as it naturally inherits the HPC system's fair usage queue policies, mitigates the noisy neighbor problem, and reduces the long wait times associated with First-In-First-Out (FIFO) queues common with shared SSH credentials. Traditional SSH credentials, while simplifying access control to computing resources, result in all user activities on the HPC cluster being logged under the same user credentials. This means all Seqera workspace users have the same access permissions on your HPC cluster, leading to indistinguishable user activities. diff --git a/platform-cloud/docs/credentials/overview.md b/platform-cloud/docs/credentials/overview.md index 39384058a..cd54554ea 100644 --- a/platform-cloud/docs/credentials/overview.md +++ b/platform-cloud/docs/credentials/overview.md @@ -6,6 +6,10 @@ last updated: "2025-10-21" tags: [credentials, git, container, registry,] --- +:::info This page has moved +Documentation for this credential type now lives at [/platform-cloud/integrations/overview](/platform-cloud/integrations/overview). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks. +::: + Seqera Platform supports secure credential management for all your infrastructure and service integrations. Configure credentials to authenticate with: - [Git hosting services][git]: Access private repositories from GitHub, GitLab, Bitbucket, and other Git providers. diff --git a/platform-cloud/docs/credentials/quay_registry_credentials.md b/platform-cloud/docs/credentials/quay_registry_credentials.md index 6fb89ecb3..4c668913f 100644 --- a/platform-cloud/docs/credentials/quay_registry_credentials.md +++ b/platform-cloud/docs/credentials/quay_registry_credentials.md @@ -6,6 +6,10 @@ last updated: "2025-10-21" tags: [quay, credentials] --- +:::info This page has moved +Documentation for this credential type now lives at [/platform-cloud/integrations/container-registries/quay](/platform-cloud/integrations/container-registries/quay). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks. +::: + Quay container registry credentials allow the Wave container service to authenticate and pull container images from your Quay repositories. Quay uses [robot accounts](https://docs.quay.io/glossary/robot-accounts.html) with read access permissions for secure programmatic authentication. :::note diff --git a/platform-cloud/docs/credentials/ssh_credentials.md b/platform-cloud/docs/credentials/ssh_credentials.md index dcc3b1873..bb841bb6f 100644 --- a/platform-cloud/docs/credentials/ssh_credentials.md +++ b/platform-cloud/docs/credentials/ssh_credentials.md @@ -6,6 +6,10 @@ last updated: "2025-10-21" tags: [ssh, credentials] --- +:::info This page has moved +Documentation for this credential type now lives at [/platform-cloud/integrations/identity/ssh-credentials](/platform-cloud/integrations/identity/ssh-credentials). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks. +::: + SSH public key authentication relies on asymmetric cryptography to generate a public and private key pair. The public key remains on the target (remote) machine, while the private key (and passphrase) is stored in Seqera Platform as a credential. The key pair is used to authenticate a connection with your SSH-enabled environment. To preserve individual user identities by using multiple user SSH credentials to access your HPC compute environments, see [Managed identities](./managed_identities). diff --git a/platform-cloud/docs/getting-started/overview.md b/platform-cloud/docs/getting-started/overview.md index b0aac9426..ddd01267f 100644 --- a/platform-cloud/docs/getting-started/overview.md +++ b/platform-cloud/docs/getting-started/overview.md @@ -18,7 +18,7 @@ The Community Showcase [Launchpad](../launch/launchpad) is an example workspace - [Datasets](../data/datasets) are collections of versioned, structured data (usually in the form of a samplesheet) in CSV or TSV format. A dataset is used as the input for a pipeline run. Sample datasets are used in pipelines with the same name, e.g., the *nf-core-rnaseq-test* dataset is used as input when you run the *nf-core-rnaseq* pipeline. - [Compute environments](../compute-envs/overview) are the platforms where workflows are executed. A compute environment consists of access credentials, configuration settings, and storage options for the environment. -- [Credentials](../credentials/overview) are the authentication keys Seqera uses to access compute environments, private code repositories, and external services. Credentials are SHA-256 encrypted before secure storage. The Community Showcase includes all the credentials you need to run pipelines in the included AWS Batch compute environments. +- [Credentials](/platform-cloud/integrations/overview) are the authentication keys Seqera uses to access compute environments, private code repositories, and external services. Credentials are SHA-256 encrypted before secure storage. The Community Showcase includes all the credentials you need to run pipelines in the included AWS Batch compute environments. - [Secrets](../secrets/overview) are retrieved and used during pipeline execution. In your private or organization workspace, you can store the access keys, licenses, or passwords required for your pipeline execution to interact with third-party services. The secrets included in the Community Showcase contain license keys to run *nf-dragen* and *nf-sentieon* pipelines in the Showcase compute environments. ## Run a pipeline with sample data diff --git a/platform-cloud/docs/getting-started/studios.md b/platform-cloud/docs/getting-started/studios.md index 3dc8d196a..1b786735c 100644 --- a/platform-cloud/docs/getting-started/studios.md +++ b/platform-cloud/docs/getting-started/studios.md @@ -14,7 +14,7 @@ You will need the following to get started: - At least the **Maintain** workspace [user role](../orgs-and-teams/roles) to create and configure Studios. - An [AWS Batch compute environment](../compute-envs/aws-batch#create-a-seqera-aws-batch-compute-environment) (**without Fargate**) with sufficient resources (minimum: 2 CPUs, 8192 MB RAM). -- Valid [credentials](../credentials/overview) for your cloud storage account and compute environment. +- Valid [credentials](/platform-cloud/integrations/overview) for your cloud storage account and compute environment. - [Data Explorer](../data/data-explorer) enabled in your workspace. ::: diff --git a/platform-cloud/docs/git/overview.md b/platform-cloud/docs/git/overview.md index 368ce5c92..3da174bb1 100644 --- a/platform-cloud/docs/git/overview.md +++ b/platform-cloud/docs/git/overview.md @@ -5,6 +5,10 @@ date: "10 Oct 2025" tags: [git] --- +:::info This page has moved +Documentation for this credential type now lives at [/platform-cloud/integrations/git-providers/overview](/platform-cloud/integrations/git-providers/overview). The old URL is preserved during the migration but will be removed in a future release. Update your bookmarks. +::: + Data pipelines are composed of many assets, including pipeline scripts, configuration files, dependency descriptors (such as for Conda or Docker), documentation, etc. When you manage complex data pipelines as Git repositories, all assets can be versioned and deployed with a specific tag, release, or commit ID. Version control and containerization are crucial to enable reproducible pipeline executions, and provide the ability to continuously test and validate pipelines as the code evolves over time. Seqera products have built-in support for [Git](https://git-scm.com) and several Git-hosting platforms. This page covers Git integration for both **Seqera Platform** and [**Seqera AI**](#seqera-ai). diff --git a/platform-cloud/docs/launch/launchpad.md b/platform-cloud/docs/launch/launchpad.md index ce19ad572..459e68e11 100644 --- a/platform-cloud/docs/launch/launchpad.md +++ b/platform-cloud/docs/launch/launchpad.md @@ -31,9 +31,9 @@ The launch form accepts URL query parameters. See [Populate launch form with URL ### General config -- **Pipeline to launch**: A Git repository name or URL. For saved pipelines, this is prefilled and cannot be edited. Private repositories require [access credentials](../credentials/overview). +- **Pipeline to launch**: A Git repository name or URL. For saved pipelines, this is prefilled and cannot be edited. Private repositories require [access credentials](/platform-cloud/integrations/overview). :::note - Nextflow pipelines are Git repositories that can reside on any public or private Git-hosting platform. See [Git integration](../git/overview) in the Seqera docs and [Pipeline sharing](https://docs.seqera.io/nextflow/sharing) in the Nextflow docs for more details. + Nextflow pipelines are Git repositories that can reside on any public or private Git-hosting platform. See [Git integration](/platform-cloud/integrations/git-providers/overview) in the Seqera docs and [Pipeline sharing](https://docs.seqera.io/nextflow/sharing) in the Nextflow docs for more details. ::: - **Revision**: A valid repository commit ID, tag, or branch name. Determines the version of the pipeline to launch. - **Commit ID**: Pin pipeline revision to the most recent HEAD commit ID. If no commit ID is pinned, the latest revision of the repository branch or tag is used. diff --git a/platform-cloud/docs/orgs-and-teams/workspace-management.md b/platform-cloud/docs/orgs-and-teams/workspace-management.md index 74dd78624..6ba70e8f3 100644 --- a/platform-cloud/docs/orgs-and-teams/workspace-management.md +++ b/platform-cloud/docs/orgs-and-teams/workspace-management.md @@ -31,7 +31,7 @@ Organization owners and admins can create a new workspace within an organization As a workspace owner, you can modify optional workspace fields after workspace creation. You can either select **Edit** on an organization's workspaces list or the **Settings** tab within the workspace page. ::: -Apart from the **Participants** tab, the _organization_ workspace is similar to the _user_ workspace. As such, the relation to [runs](../launch/launchpad), [actions](../pipeline-actions/overview), [compute environments](../compute-envs/overview), and [credentials](../credentials/overview) is the same. +Apart from the **Participants** tab, the _organization_ workspace is similar to the _user_ workspace. As such, the relation to [runs](../launch/launchpad), [actions](../pipeline-actions/overview), [compute environments](../compute-envs/overview), and [credentials](/platform-cloud/integrations/overview) is the same. ## Workspace settings