503 Service Temporarily Unavailable
I got this page after deploying a version which was previously running successfully. There's only one instance in my application and I'm getting a "degraded" integrity. As for the causes, it is stated that "Application deployment failed [...] with exit status 1 and error: Engine excution has encountered an error. Incorrect application version 'app-....' (deployment 67). Expected version 'app-...' (deployment 66)."
It's my first time AWS and I'm a overall newbie... What am I missing, since the website was running smoothly before this last attemped deployment?
I appreciate any help....
Ovidio (from Brazil)
From the notes, I understand that you got an error 503 Service Temporarily unavailable, with application deployment failed, engine execution has encountered an error and incorrect application version, after deploying your app. Please correct me if my understanding is wrong.
Please note that the 503 Service temporarily unavailable error response code indicates that the server is not ready to handle the request. This could mean that the targets behind the Application Load Balancer (ALB) are either not responding to the requests, or the ALB does not have registered targets. You can follow the document link  to figure out the problem. You can enable access logs for your ALB to help you figure out the reasons for the failure .
For “Engine execution has encountered an error”, you can use the following document link  for the steps to troubleshoot.
Please note that Elastic Beanstalk monitors your environment for consistency following deployments. If a rolling deployment fails, the version of your application running on the instances in your environment may vary. You can check the document in link  on notifications and troubleshooting. This will help you solve the issue, by giving you steps on how to redeploy a previous version which you know works and configuring your environment to ignore health checks during deployment and redeployment of the new version to force the deployment to complete.
I hope you find the above information helpful.
Have a great day ahead!
 https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-troubleshooting.html  https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-access-logs.html#enable-access-logging  https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/troubleshooting.html  https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-health-enhanced-notifications.html
loading and deploying a previously trained sagemaker xgboost modelasked 3 years ago
Cannot start EC2 instance after changing its typeasked 3 years ago
503 Service Temporarily Unavailableasked 2 months ago
503 Service Temporarily UnavailableAccepted Answerasked 3 months ago
AWS EC2: restarted instance, got assigned a new IP, now IP is redirecting to old IP via response headers Location.asked 2 days ago
Why am I getting a 503 Service Temporarily Unavailable error?asked a year ago
Unable to resolve host ip-XX: Resource temporarily unavailableasked 2 years ago
A new EC2 instance is created after termination of the only instanceAccepted Answerasked 2 years ago
EB instance Degraded after Platform updateasked 2 years ago
EC2 site down after php update.asked 2 years ago