diff --git a/platform-enterprise_docs/compute-envs/aws-batch.md b/platform-enterprise_docs/compute-envs/aws-batch.md index 01f4b65aa..094b126d2 100644 --- a/platform-enterprise_docs/compute-envs/aws-batch.md +++ b/platform-enterprise_docs/compute-envs/aws-batch.md @@ -668,7 +668,7 @@ Seqera automates the configuration of an [AWS Batch](https://aws.amazon.com/batc Seqera will create the head and compute [job queues](https://docs.aws.amazon.com/batch/latest/userguide/job_queues.html) and their respective [compute environments](https://docs.aws.amazon.com/batch/latest/userguide/compute_environments.html) where jobs will be executed. The job queues are configured with [job state limit actions](https://docs.aws.amazon.com/batch/latest/APIReference/API_JobStateTimeLimitAction.html) to automatically purge jobs that cannot be scheduled on any node type available for the compute environment. Depending on the provided configuration in the UI, Seqera might also create IAM roles for Nextflow head job execution, CloudWatch log groups, EFS or FSx filesystems, etc. -1. After logging in to [Seqera](https://cloud.seqera.io) and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. +1. After logging in to your Platform Enterprise installation and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. 1. Select **Add compute environment**. 1. Enter a descriptive name for this environment, e.g., _AWS Batch Spot (eu-west-1)_. 1. Select **AWS Batch** as the target platform. diff --git a/platform-enterprise_versioned_docs/version-25.1/compute-envs/aws-batch.md b/platform-enterprise_versioned_docs/version-25.1/compute-envs/aws-batch.md index 8d2c7ea35..094b126d2 100644 --- a/platform-enterprise_versioned_docs/version-25.1/compute-envs/aws-batch.md +++ b/platform-enterprise_versioned_docs/version-25.1/compute-envs/aws-batch.md @@ -655,8 +655,6 @@ Multiple users can be specified in the trust policy by adding more ARNs to the ` ## Automatic configuration of Batch resources -Seqera automates the configuration of an [AWS Batch](https://aws.amazon.com/batch/) compute environment and the queues required for deploying Nextflow pipelines. - :::caution AWS Batch creates resources that you may be charged for in your AWS account. See [Cloud costs](../monitoring/cloud-costs) for guidelines to manage cloud resources effectively and prevent unexpected costs. ::: @@ -670,7 +668,7 @@ Seqera automates the configuration of an [AWS Batch](https://aws.amazon.com/batc Seqera will create the head and compute [job queues](https://docs.aws.amazon.com/batch/latest/userguide/job_queues.html) and their respective [compute environments](https://docs.aws.amazon.com/batch/latest/userguide/compute_environments.html) where jobs will be executed. The job queues are configured with [job state limit actions](https://docs.aws.amazon.com/batch/latest/APIReference/API_JobStateTimeLimitAction.html) to automatically purge jobs that cannot be scheduled on any node type available for the compute environment. Depending on the provided configuration in the UI, Seqera might also create IAM roles for Nextflow head job execution, CloudWatch log groups, EFS or FSx filesystems, etc. -1. After logging in to [Seqera](https://cloud.seqera.io) and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. +1. After logging in to your Platform Enterprise installation and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. 1. Select **Add compute environment**. 1. Enter a descriptive name for this environment, e.g., _AWS Batch Spot (eu-west-1)_. 1. Select **AWS Batch** as the target platform. diff --git a/platform-enterprise_versioned_docs/version-25.2/compute-envs/aws-batch.md b/platform-enterprise_versioned_docs/version-25.2/compute-envs/aws-batch.md index 8d2c7ea35..094b126d2 100644 --- a/platform-enterprise_versioned_docs/version-25.2/compute-envs/aws-batch.md +++ b/platform-enterprise_versioned_docs/version-25.2/compute-envs/aws-batch.md @@ -655,8 +655,6 @@ Multiple users can be specified in the trust policy by adding more ARNs to the ` ## Automatic configuration of Batch resources -Seqera automates the configuration of an [AWS Batch](https://aws.amazon.com/batch/) compute environment and the queues required for deploying Nextflow pipelines. - :::caution AWS Batch creates resources that you may be charged for in your AWS account. See [Cloud costs](../monitoring/cloud-costs) for guidelines to manage cloud resources effectively and prevent unexpected costs. ::: @@ -670,7 +668,7 @@ Seqera automates the configuration of an [AWS Batch](https://aws.amazon.com/batc Seqera will create the head and compute [job queues](https://docs.aws.amazon.com/batch/latest/userguide/job_queues.html) and their respective [compute environments](https://docs.aws.amazon.com/batch/latest/userguide/compute_environments.html) where jobs will be executed. The job queues are configured with [job state limit actions](https://docs.aws.amazon.com/batch/latest/APIReference/API_JobStateTimeLimitAction.html) to automatically purge jobs that cannot be scheduled on any node type available for the compute environment. Depending on the provided configuration in the UI, Seqera might also create IAM roles for Nextflow head job execution, CloudWatch log groups, EFS or FSx filesystems, etc. -1. After logging in to [Seqera](https://cloud.seqera.io) and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. +1. After logging in to your Platform Enterprise installation and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. 1. Select **Add compute environment**. 1. Enter a descriptive name for this environment, e.g., _AWS Batch Spot (eu-west-1)_. 1. Select **AWS Batch** as the target platform. diff --git a/platform-enterprise_versioned_docs/version-25.3/compute-envs/aws-batch.md b/platform-enterprise_versioned_docs/version-25.3/compute-envs/aws-batch.md index 01f4b65aa..094b126d2 100644 --- a/platform-enterprise_versioned_docs/version-25.3/compute-envs/aws-batch.md +++ b/platform-enterprise_versioned_docs/version-25.3/compute-envs/aws-batch.md @@ -668,7 +668,7 @@ Seqera automates the configuration of an [AWS Batch](https://aws.amazon.com/batc Seqera will create the head and compute [job queues](https://docs.aws.amazon.com/batch/latest/userguide/job_queues.html) and their respective [compute environments](https://docs.aws.amazon.com/batch/latest/userguide/compute_environments.html) where jobs will be executed. The job queues are configured with [job state limit actions](https://docs.aws.amazon.com/batch/latest/APIReference/API_JobStateTimeLimitAction.html) to automatically purge jobs that cannot be scheduled on any node type available for the compute environment. Depending on the provided configuration in the UI, Seqera might also create IAM roles for Nextflow head job execution, CloudWatch log groups, EFS or FSx filesystems, etc. -1. After logging in to [Seqera](https://cloud.seqera.io) and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. +1. After logging in to your Platform Enterprise installation and selecting a workspace from the dropdown menu at the top of the page, select **Compute environments** from the navigation menu. 1. Select **Add compute environment**. 1. Enter a descriptive name for this environment, e.g., _AWS Batch Spot (eu-west-1)_. 1. Select **AWS Batch** as the target platform.