[codex] Clarify Batch Forge vs manual AWS Batch setup for EDU-1131

[llewellyn-sl]

Summary

This draft clarifies when AWS Batch compute environments should use manual mode instead of Batch Forge, specifically for teams that already manage their AWS Batch resources with Terraform or another infrastructure-as-code workflow.

Source context

• Slack source: https://seqera.slack.com/archives/C0APYR2A3A8/p1775859174458949
• Jira: https://seqera.atlassian.net/browse/EDU-1131
• Report: https://github.com/seqeralabs/agent-education-feedback-automation/blob/cursor/prompt-file-execution-e67a/2026-04-06/2026-04-10.md

Repo and doc targets

• Repo: seqeralabs/docs
• Docsets:
  • platform-cloud
  • platform-enterprise_versioned_docs
• Pages:
  • platform-cloud/docs/compute-envs/aws-batch.md
  • platform-enterprise_versioned_docs/version-25.3/compute-envs/aws-batch.md

Rationale

The current AWS Batch docs already describe both Batch Forge and manual setup, but they do not make the decision boundary explicit for customers whose Batch resources are managed outside Platform. This draft adds the missing guidance: if Terraform or another IaC workflow owns those resources, use manual mode so Platform attaches to existing infrastructure instead of taking over its lifecycle.

Validation

• Attempted markdownlint-cli2 on the touched files with a temporary npm cache.
• The run was not actionable because these pages already trigger a large number of pre-existing repo-level lint violations outside this change.
• Manually reviewed the inserted text against the existing Batch Forge and manual setup sections in both pages.

Follow-up

Please confirm whether docs should eventually include a deeper Terraform-specific example, or if the mode-selection guidance added here is the right scope for now.

[netlify]

❌ Deploy Preview for seqera-docs failed. Why did it fail? →

Name	Link
🔨 Latest commit	e8b25f9
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/69e626fcc6209400088ef61e