Help getting a Flask App to run on Elastic Beanstalk under new Launch Configuration

Hello.

After running "eb init", create a directory called ".ebextensions" within the directory.
Please create a file called "options.config" in the ".ebextensions" directory.
Please try creating the resource with "eb create" after changing the file as shown below.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/command-options-general.html#command-options-general-autoscalinglaunchconfiguration

option_settings:
  aws:autoscaling:launchconfiguration:
    DisableIMDSv1: True

The "eb init" command answered by AWS re:Post Agent does not have the option "--option-settings".
AI is giving an incorrect answer.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb3-init.html

The issue you're experiencing is related to recent changes in AWS Elastic Beanstalk regarding the use of launch configurations. AWS is phasing out launch configurations and replacing them with launch templates. This transition means that creating new launch configurations is no longer possible in accounts and regions where Elastic Beanstalk environments don't already exist.

To resolve this issue and successfully deploy your Flask application on Elastic Beanstalk, you need to signal to Elastic Beanstalk to use launch templates instead of launch configurations. You can do this by setting at least one of the following options in your environment configuration:

1. DisableIMDSv1
2. RootVolumeType
3. BlockDeviceMappings
4. EnableSpot

When using the EB CLI, you can set these options by adding them to your command. For example:

eb init -p "64bit Amazon Linux 2023 v4.2.0 running Python 3.11" flask_app.py --option-settings Namespace=aws:autoscaling:launchconfiguration,OptionName=RootVolumeType,Value=gp2

If you're using CloudFormation, make sure to include one of these options in your template YAML file.

For the Flask application itself, ensure that your main application file is named application.py or that you've set the appropriate environment variables for Elastic Beanstalk to find your application entry point.

Also, make sure you have a requirements.txt file in your project directory listing all the necessary dependencies, including Flask.

By implementing these changes, you should be able to successfully deploy your Flask application on Elastic Beanstalk using the new launch template system.
Sources
Creating an Elastic Beanstalk without success | AWS re:Post
Setting up your Python development environment for Elastic Beanstalk - AWS Elastic Beanstalk
Deploying a Flask application to Elastic Beanstalk - AWS Elastic Beanstalk