docs: Update manual AWS Batch launch template scripts #993
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update the launch template userdata scripts in the manual AWS Batch compute environment documentation to match the current Batch Forge implementation. Changes include: - Add logging redirection for troubleshooting - Update CloudWatch agent download from wget to curl - Update CloudWatch config from custom-v0.1.json to config-v0.4.json - Add 5 new ECS settings (Spot draining, container timeouts) - Update miniconda tarball URL to versioned package - Update sed placeholder from custom-id to $FORGE_ID - Add section comments for better readability 🤖 Generated with [Claude Code](https://claude.com/claude-code)
adamrtalbot
requested review from
justinegeffen and
llewellyn-sl
as code owners
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
The manual AWS Batch compute environment documentation contains outdated launch template userdata scripts that don't match the current implementation in Batch Forge. This causes inconsistencies for users who manually configure their AWS Batch environments.
What
Updated the launch template scripts in both "with Fusion v2" and "without Fusion v2" tabs across 5 documentation files:
exec > >(tee /var/log/tower-forge.log|logger -t TowerForge -s 2>/dev/console) 2>&1for troubleshootingwgettocurl -s ... -ocustom-v0.1.jsontoconfig-v0.4.jsonECS_ENABLE_SPOT_INSTANCE_DRAINING=trueECS_CONTAINER_CREATE_TIMEOUT=10mECS_CONTAINER_START_TIMEOUT=10mECS_CONTAINER_STOP_TIMEOUT=10mECS_MANIFEST_PULL_TIMEOUT=10mminiconda-awscli.tar.gzto versionedminiconda-25.3.1-awscli-1.40.12.tar.gzcustom-idto$FORGE_IDFiles changed
platform-cloud/docs/enterprise/advanced-topics/manual-aws-batch-setup.mdxplatform-enterprise_docs/enterprise/advanced-topics/manual-aws-batch-setup.mdxplatform-enterprise_versioned_docs/version-25.1/enterprise/advanced-topics/manual-aws-batch-setup.mdxplatform-enterprise_versioned_docs/version-25.2/enterprise/advanced-topics/manual-aws-batch-setup.mdxplatform-enterprise_versioned_docs/version-25.3/enterprise/advanced-topics/manual-aws-batch-setup.mdx🤖 Generated with Claude Code