Opt-in to Launch Templates even if no features requires it

stefansundin commented 4 years ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments. They generate extra noise for issue followers and do not help prioritize the request.

Tell us about your request I want a configuration option (like one of these) to opt-in to launch templates, even if I don't use a feature that requires them. This would make some of my ebextension cloudformation template overrides simpler since the launch template will always be there.

Something like this:

option_settings:
  - namespace: aws:elasticbeanstalk:application
    option_name: Use Launch Template
    value: true

Is this request specific to an Elastic Beanstalk platform? No.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Simplify ebextensions that override things in the cloudformation template.

Are you currently working around this issue? I have some things that is commented out by default, with a comment that it can only be enabled if the deployment is using a launch template.

Additional context If it matters, my app is open source and I make it easy to deploy on both Heroku and Elastic Beanstalk. Here's the repo: https://github.com/stefansundin/rssbox

pprahlad commented 4 years ago

We are looking into this request. Thank you for this feedback.

gagol14 commented 1 year ago

Is there any update or somebody have some tip to force ElasticBeanstalk to use LT instead of LC?

darin-holloway commented 3 months ago

@gagol14 use IMDSv2, stub a spot config, and/or use gp3 storage volumes

stefansundin commented 3 months ago

Starting on October 1, 2024, new AWS accounts will no longer be able to create launch configurations: https://docs.aws.amazon.com/autoscaling/ec2/userguide/launch-configurations.html

I don't know if they've migrated everything to use Launch Templates now, but I think what @darin-holloway said is probably true, enabling IMDSv2 probably opts you in. Looks like IMDSv2 support was released for Elastic Beanstalk a month after I opened this issue: https://aws.amazon.com/about-aws/whats-new/2020/06/aws-elastic-beanstalk-adds-support-for-imdsv2-and-service-linked-role-for-managed-updates/

Anyway, I will just close this issue since elastic beanstalk is a dying service and no one should really start using it in 2024. There are better options out there now.

aws / elastic-beanstalk-roadmap

Opt-in to Launch Templates even if no features requires it #51

Community Note