Skip to content

Comments

ec2: Enhance fleet creation with LaunchTemplateAndOverrides in responses#115

Open
nik-localstack wants to merge 1 commit intolocalstack:localstackfrom
nik-localstack:nikos/unc-263
Open

ec2: Enhance fleet creation with LaunchTemplateAndOverrides in responses#115
nik-localstack wants to merge 1 commit intolocalstack:localstackfrom
nik-localstack:nikos/unc-263

Conversation

@nik-localstack
Copy link

Motivation

When creating an EC2 Fleet with Type=instant, the response was missing the LaunchTemplateAndOverrides field for each instance. This field is present in real AWS responses and contains important information about which launch template and overrides were used to launch each instance.
Note: this field is necessary for Karpenter, otherwise it fails to parse the response.

Changes

  • The 'Instancesarray in thecreate_fleetresponse now includesLaunchTemplateAndOverrides` with:
    • LaunchTemplateSpecification - Launch template ID and version used
    • Overrides - Any overrides applied (instance type, subnet, AZ, etc.)
  • Version resolution: $Latest is now resolved to the actual version number (e.g., "1") in responses, matching AWS
  • Template ID normalization: When LaunchTemplateName is used in the request, the response always includes LaunchTemplateId (AWS behavior)

@nik-localstack nik-localstack self-assigned this Feb 20, 2026
@nik-localstack nik-localstack marked this pull request as ready for review February 20, 2026 14:17
@nik-localstack nik-localstack changed the title ec2: Enhance fleet creation to with LaunchTemplateAndOverrides in responses ec2: Enhance fleet creation with LaunchTemplateAndOverrides in responses Feb 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant