ec2: Update launch template version handling#131
Merged
nik-localstack merged 1 commit intolocalstack:localstackfrom Mar 9, 2026
Merged
Conversation
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
nik-localstack
force-pushed
the
ec2/fleet/launch-template-version-usage
branch
from
07e0a17 to
f38f923
Compare
viren-nadkarni
approved these changes
Mar 9, 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.
When creating an EC2 Fleet with a LaunchTemplateSpecification that pins to a specific version, moto was always using the latest version's data to launch instances — ignoring the requested version entirely. This meant a fleet pinned to version "1" would silently use version "3"'s configuration instead.
Changes
Co-created with https://claude.com/claude-code.