Since last week, all our systems on Elastic Beanstalk suddenly failed to install the latest platform update, 4.2.7 to 4.3.0, as part of a weekly managed update process. This came as an unwelcome surprise, as platform updates have been working without any issues for at least the last 36 months.

I have an AWS-EB environment (Java on Tomcat) that won’t success to deploy any app. The only way I CAN successfuly deploy a version, is by stopping the EC2 instance of the environment, restart it and then to deploy. Then, the version will successfuly be deployed (but a “502 bad gateway” will be shown, and the only way to solve THAT is by switching from load balancer to single instance and back to load balancer) but the next deployment will fail. When I request app logs, it fails too.

I am new to AWS and have a couple of questions regarding the different deployment options for Elastic BeanStalk.

This question already has answers here: Error with not existing instance profile while trying to get a django project running on AWS Beanstalk (8 answers) Closed 2 days ago. I understand that it requires you to create a role from the IAM dashboard which is exactly what I did. Basically My IAM role isn’t visible […]

Iam trying to deploy my application in aws beanstalk which i have dockerized properly and i created an environment for it’s deployment but when i try to deploy my application i get the following logs and deployment fails, when i try to request logs it says failed to retrieve logs.

Hi i am trying to revert back to the old application verison that i have but when i try to i get this message”Failed to deploy application version
Environment named ****** is in an invalid state for this operation. Must be Ready..
so not exactly sure what to do
thanks
-I have tired to restart the app service and it doesnt do anything
-I have tired to upload the pervious version manually but that did not work either
-nothing is building at the moment
-restarted the tomcat server