Thanks for reporting this, and for the followup info in the comment. I'll look into the Security group name vs ID issue with our console team. However, I see your resources have
AWSEB in the name. This implies the resources are created through ElasticBeanstalk. You shouldn't update the ASG directly, as any update to the Beanstalk environment in the future will likely undo your changes. Instead, update the Beanstalk environment directly to migrate it to a launch template.
If you think any changes may have been made to the instance/application/ASG outside of Beanstalk, I would highly encourage taking a snapshot or otherwise backing up anything important first to prevent accidental data loss, since Beanstalk will redeploy the last known application revision when you update it.
The guidance on converting launch configs to templates isn't very clear when it comes to Elastic Beanstalk, having now done this I've found that a normal environment update or environment clone, doesn't swap the configurations to templates, however enabling spot instances under "Capacity -> Auto Scaling Group -> Fleet Composition = Combine purchase options and instances" does then force the environment to convert them to templates as expected.
I just tried the same and it worked fine for me in ap-southeast-2.
- Accepted Answerasked 2 months ago
- Accepted Answerasked a year ago
- asked 2 years ago
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 9 months ago
- EXPERTpublished a year ago
- EXPERTpublished 7 months ago