Hi Ovidio!

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 [1] to figure out the problem. You can enable access logs for your ALB to help you figure out the reasons for the failure [2].

For “Engine execution has encountered an error”, you can use the following document link [3] 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 [4] 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!

References:

[1] https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-troubleshooting.html [2] https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-access-logs.html#enable-access-logging [3] https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/troubleshooting.html [4] https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-health-enhanced-notifications.html