Migrate batch jobs from AL2 to AL2023#66
Merged
Conversation
victorlin
force-pushed
the
victorlin/upgrade-batch
branch
from
9817ef4 to
ed25aab
Compare
victorlin
changed the title
Follow-up to "Add new compute environment with Amazon Linux 2023" (19c0444) after successful testing. The migration guide¹ does not seem to contain anything noteworthy for our usage. Keeping the test job queue around for future testing, and the old compute environment around in case we need to revert back to it for any reason. ¹ https://docs.aws.amazon.com/batch/latest/userguide/ecs-migration-2023.html
victorlin
force-pushed
the
victorlin/upgrade-batch
branch
from
ed25aab to
7d14448
Compare
joverlee521
approved these changes
May 21, 2026
joverlee521
left a comment
joverlee521
left a comment
Contributor
There was a problem hiding this comment.
Thanks for testing this!
This was referenced May 21, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of proposed changes
Follow-up to #64 after successful testing. The migration guide does not seem to contain anything noteworthy for our usage.
Keeping the test job queue around for future testing, and the old compute environment around in case we need to revert back to it for any reason.
Related issue(s)
Closes #62
Checklist
NEXTSTRAIN_AWS_BATCH_QUEUE=nextstrain-job-queue-test nextstrain build --aws-batch zika-tutorial(link to batch job)terraform apply planand monitor