Update to AWS Batch docs

changelog/seqera-enterprise/v25.3.md

@@ -10,7 +10,7 @@ Seqera Platform Enterprise version 25.3 introduces a series of new features and
 
 #### Custom roles and fine-grained authorization (RBAC)
 
-- Added support for custom roles with fine-grained permissions, to define specific access controls beyond the predefined Owner, Admin, Maintain, Launch, View, and Connect roles.
+- Added support for [custom roles](https://docs.seqera.io/platform-enterprise/orgs-and-teams/custom-roles) with fine-grained permissions, to define specific access controls beyond the predefined Owner, Admin, Maintain, Launch, View, and Connect roles.
 
 #### Studios
 
@@ -20,7 +20,7 @@ Seqera Platform Enterprise version 25.3 introduces a series of new features and
 - Added ability to clone content from a Git repository to a Studio at startup time.
 - Added ability to create Studios from Docker images, built from a repository Dockerfile using Wave.
 - Added ability to stop a Studio session that is stuck starting without needing AWS console access.
-- Added **Save as data link** action when mounting data to a Studio.
+- Added **Save as data-link** action when mounting data to a Studio.
 - Added support for custom environment variables to Studio configuration.
 
 #### Pipelines

platform-enterprise_versioned_docs/version-25.3/compute-envs/aws-batch.md

@@ -88,10 +88,16 @@ S3 is used by Nextflow for the storage of intermediate files. In production pipe
 
 Batch Forge automates the configuration of an [AWS Batch](https://aws.amazon.com/batch/) compute environment and the queues required to deploy Nextflow pipelines. After your IAM user and S3 bucket have been set up, create a new **AWS Batch** compute environment in Seqera.
 
+#### Created resources
+
 :::caution
 Batch Forge automatically 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.
 :::
 
+Batch Forge 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, Forge might also create IAM roles for Nextflow head job execution, EFS or FSx filesystems, and CloudWatch log groups.
+
 **Create a Batch Forge AWS Batch compute environment**
 
 1. In a workspace, select **Compute environments > New environment**.