You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since yesterday we got a strange behaviour on our deploy. Here, we are using launchConfiguration to set the security groups for EC2 and loadbalancers. The SG for LB works great, but looking at the Cloudformation log, it's creates a launchTemplate instead of the launchConfiguration.
We didn't had any change on our eb_deployer file.
There's any parameter we need to add to eb_deployer file to use launchConfiguration instead of the launchTemplate?
Thanks,
The text was updated successfully, but these errors were encountered:
It seems like Launch Configurations are no longer supported in new AWS regions like sa-east-1, and when you create a Beanstalk environment there, of late it has started creating environments with a Launch Template even though it is not fully supported by Beanstalk in the sense that we do not have option settings namespaces for launch templates like we have aws:autoscaling:launchconfiguration.
Does not solve anything, but might indicate that more people will eventually run into same issue
Hello,
Since yesterday we got a strange behaviour on our deploy. Here, we are using
launchConfiguration
to set the security groups for EC2 and loadbalancers. The SG for LB works great, but looking at the Cloudformation log, it's creates alaunchTemplate
instead of thelaunchConfiguration
.We didn't had any change on our eb_deployer file.
There's any parameter we need to add to eb_deployer file to use
launchConfiguration
instead of thelaunchTemplate
?Thanks,
The text was updated successfully, but these errors were encountered: