Elastic Beanstalk questions

Hello there!

Id love to provide more insights.

When I create the environment the new Auto Scaling Group is created with a launch configuration even though these are supposedly deprecated in favour of launch templates. Why is this? Is there any way to create a launch template instead?

Launch configurations are still supported by AWS Auto Scaling Groups, but they are being replaced by launch templates, which offer more flexibility and advanced features. To create an Auto Scaling Group with a launch template instead of a launch configuration, follow these steps:

1. Go to the AWS Management Console and navigate to the EC2 service. (I inserted a direct link for you but just make sure youre in the correct region.
2. Create a new launch template by providing the necessary configuration details, such as the Amazon Machine Image (AMI), instance type, key pair, and security groups.
3. Once the launch template is created, go to the Auto Scaling service and create a new Auto Scaling Group.
4. During the creation process, select the option to use a launch template instead of a launch configuration.
5. Choose the launch template you created earlier, and proceed with the remaining configuration steps.

The console create environment wizard allows me to select an existing security group but always creates a new security group anyway. Once the environment is created it seems impossible to remove this new security group from the configuration: if I edit the configuration and deselect the new security group it still remains.

Many AWS services and tools create new security groups by default to ensure that the necessary rules are in place for the resources being created. However, you can modify the security groups associated with an Auto Scaling Group after it has been created.

Here are the steps to remove or modify the security groups:

1. Open the Amazon EC2 console and navigate to the "Auto Scaling Groups" section.
2. Select the Auto Scaling Group you want to modify.
3. From the "Details" tab, scroll down to the "Instance Details" section, and click the link for the launch template or launch configuration used by the Auto Scaling Group.
4. In the launch template or launch configuration details, you can modify the security groups associated with the instances.
5. After making the desired changes, create a new version of the launch template or launch configuration.
6. Update the Auto Scaling Group to use the new launch template or launch configuration version.

It's important to note that removing a security group from an Auto Scaling Group may impact the existing instances in the group, as they will no longer have the rules defined in the removed security group. Therefore, it's important to review and update the security group rules accordingly to ensure that the necessary access is maintained.

My questions were about Elastic Beanstalk specifically - why it is using Launch Configurations? And how to do I remove the newly created security group from an existing environment?