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. (Service: AutoScaling, Status Code: 400, Request ID: fda29516-7bad-4bbe-b68a-15b45521a474)" (RequestToken: cdaff2b4-76ea-0702-af8a-089ac04dc2d5, HandlerErrorCode: GeneralServiceException)

[arslaan5]

Description

Briefly describe the bug you are facing.

Steps to reproduce

Provide steps to replicate. This should include: exact ebcli commands, any relevant configuration files(sanitized), platform version, region, as well as any additional information you think is relevant.

Observed result

Please provide command output with --debug flag set.

Expected result

Describe what you expected.

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

1. OS:
2. EBCLI version:

[swarajkumarsingh]

Hola there!

Just found the solution!!!

The solution works if you are using awsebcli to create ENVs.

The Solution

1. head to root folder of your project --> under .ebextensions folder
2. create a file my_environment.config
3. Paste the content below into the newly created file

option_settings:
  - namespace: "aws:autoscaling:launchconfiguration"
    option_name: "RootVolumeType"
    value: "gp3"

4. Then, RuN eb create <env_name> --timeout 20

What does the solution do

The RootVolumeType option in the aws:autoscaling:launchconfiguration namespace specifies the type of the root volume for EC2 instances in an Elastic Beanstalk environment. Setting it to gp3 ensures the root volume is a general-purpose SSD that offers better performance and cost efficiency than gp2. It allows you to configure IOPS (up to 16,000) and throughput (up to 1,000 MB/s) independently of storage size, making it ideal for scalable and cost-optimized workloads.
Moreover solves the Deprecation Error

Thanks to the legend
Swaraj Kumar Singh