1 Answer
- Newest
- Most votes
- Most comments
0
Hi There If you have an existing Elastic Beanstalk environment launched using Launch Configurations, there is nothing you need to do. See this Stackoverflow article with a quote from AWS Support: https://stackoverflow.com/questions/74647624/change-elastic-beanstalk-environment-from-launch-configuration-to-launch-templat
If you are launching a new ElasticBeanstalk environment using CloudFormation, EB will automatically use a Launch Template. You do not need to specify this in your CloudFormation template. See https://docs.aws.amazon.com/elasticbeanstalk/latest/relnotes/release-2019-11-25-launchtemplates.html
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 15 days ago
We are using aws:autoscaling:launchconfiguration namespace to configure things like InstanceType, SSHSourceRestriction, etc.
When creating a NEW eb environment, A Launch configuration is still getting created. Once we add DisableIMDSv1 option to the cloudformation, a launch template is created instead of launch configuration.
Questions:
A year later I'm still seeing the same thing as @Max-85: If you create a new stack based on the latest elastic beanstalk example template, you'll still get an
AWS::AutoScaling::LaunchConfiguration
instead of a launch template.The docs for
aws:autoscaling:launchconfiguration
say:And it turns out you can use these options to configure a launch template, but you'll need to disable
IMDSv1
expliticly in your cloudformation template, as follows (in theOptionSettings
for theAWS::ElasticBeanstalk::ConfigurationTemplate
):