I am newish to AWS Elastic Beanstalk and this is the first time I have encountered this issue. I tried deploying a new version via zip upload of my app to an instance and the updated completed with errors:
"Completed but with Command Line Timeouts", I increased the timeout in the config file and redeployed, after which I got this message.
During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.
This repeats each time try to redeploy.
I went into the EC2 instance and noticed the the /var/app/ondeck folder was still there.
I assume this is the issue, but i doubt that simply removing this directory would be the answer - unless it is that simple.
The /var app/current version is still present and the app runs fine using the version that was deployed prior to the initial timeout.
I inherited this app it is Laravel and the composer scripts take a while to run.
Thanks for any help.
Sign in toAWS Console. Go to EC2 Services. On the left panel, click on the Load Balancing > Load Balancers. In the top panel, select the Load Balancer for which you want to change the idle timeout.
Elastic Beanstalk isn't great if you need a lot of environment variables. The simple reason is that Elastic Beanstalk has a hard limit of 4KB to store all key-value pairs. The environment had accumulated 74 environment variables — a few of them had exceedingly verbose names.
On July 18, 2022 Elastic Beanstalk set the status of all platform branches based on Amazon Linux AMI (AL1) to retired. For more information, see AL1 platform retirement FAQ in the AWS Elastic Beanstalk Developer Guide. The following sections provide information about all retiring platform versions.
I have faced same problem. When I update back previous platform version, it turns to healthy state, and I can deploy now.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With