- Newest
- Most votes
- Most comments
Thanks for flagging this — I’ve seen similar issues even when the correct LaunchTemplate options are set. One thing that helped was verifying the platform version and re-deploying the environment after configuration changes. Have you checked if a new environment using the same settings defaults to the launch template correctly?
Hi Pablo, thanks for the thoughtful follow-up and link! It’s helpful to know Terraform was the provisioning layer. That subtle switch between aws:autoscaling:launchconfiguration and aws:ec2:instances definitely seems to be a trigger for this behavior, even when other settings are correctly applied.
Interesting that toggling “Combine purchasing options and instances” resolved the issue manually — definitely feels like a workaround rather than a long-term solution.
Glad my note helped surface some clarity on what was going on. Appreciate you sharing the extra context!
—TheQuietBuilder
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
Hello! Thanks for the answer, it helped me find a "reason" for what was happening.
In my case, I create the resources through terraform, so the "problem" is that, even though IMDSv1 is disabled by default using the Amazon Linux 2023 image, I needed to explicitly set the DisableIMDSv1 option to true (I don't think this should happen). Reference: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-autoscalinglaunchconfiguration
I believe that what caused this issue was using the InstanceType option in the aws:autoscaling:launchconfiguration namespace instead of InstanceTypes in aws:ec2:instances (which doesn't seem like a fair reason for this issue, since assigning an IamInstanceProfile is only possible through the aws:autoscaling:launchconfiguration namespace, unless I misunderstood (: )
Now, for the environments that were created manually with the same settings mentioned, I don't know exactly what the reason was, since they were recently created environments.
For these environments, enabling Combine purchasing options and instances and then disabling it solved my problem, but I also believe that it is not the best way to handle or solve this problem.