Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

How to get passed this error on EBS?

0

Creating Auto Scaling launch configuration failed Reason: Resource handler returned message: "The Launch Configuration creation operation is not available in your account. Use launch templates to create configuration templates for your Auto Scaling groups.

This is the error I get when I try to launch my new environment. Even worse, the AWS EBS web dashboard won't let me change the environment configuration, saying that the environment "is in an invalid state for this operation. Must be Ready." I can't do anything, even as root.

Topics
Management & GovernanceCompute
Tags
AWS Auto ScalingAWS Elastic Beanstalk
Language
English
asked a year ago369 views
1 Answer
3

Hello.

AWS has deprecated the use of launch configurations.
Therefore, you must configure AutoScaling using launch templates in ElasticBeanstalk as well.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-launch-templates.html

Starting on October 1, 2024, the Amazon EC2 Auto Scaling service will no longer support the creation of launch configurations for new accounts. This change is due to launch configurations being phased out and replaced by launch templates by the Amazon EC2 Auto Scaling service. For more information, see Auto Scaling launch configurations in the Amazon EC2 Auto Scaling User Guide.

To use the launch template, you should be able to use it by setting "RootVolumeType" to "gp3" or "DisableIMDSv1" to "true" as described in the following document.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-autoscaling-launch-templates.html#environments-cfg-autoscaling-launch-templates-options

EXPERT
answered a year ago
EXPERT
reviewed a year ago
  • Mickael
    a year ago

    That worked. Thank you. Still, I had to terminate the environment and recreate it because the EBS wouldn't let me change even that part of the configuration. To be honest I find it quite absurd that the GUI would give me a default configuration option that is deprecated and creates an unrecoverable error. It shouldn't even allow me to do this, let alone be the default option. But after using AWS for a few years this barely even surprises me. In general, when talking UI/UX design with my colleagues, I often use the most absurd parts of AWS as an example of what not to do.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content