Just to close the loop. Deploying our .war in Tomcat 8.5 Correto 11 4.2.11. works just fine. We did not make any adjustments to code or configuration. Just change from Tomcat 8.5 Correto 11 4.2.8 to Tomcat 8.5 Correto 11 4.2.11.
There has been probabily issues with Tomcat 8.5 Correto 11 4.2.9 and Tomcat 8.5 Correto 11 4.2.10 since the are not available options anymore in the Elastic Beanstalk environment.
Restart Elastic Beanstalk App Server when Health is Severeasked 9 months ago
Corretto 17 for Elastic Beanstalkasked a year ago
Corretto 11 and javahasked 2 years ago
EBExtensions : Tomcat JVM Optionsasked 2 years ago
Corretto 11 with Tomcat 8.5 AL2 version 4.2.9 Updates for latest log4j hotpatch 1.1-12asked a year ago
Adjusting the ciphers accepted by a Tomcat server running in Beanstalkasked 4 years ago
Elastic Beanstalk 503 Service Unavailableasked 9 months ago
Elastic Beanstalk Tomcat 8.5 Corretto 11 4.2.9: Requests blocked by CORS policy + 404 ErrorAccepted Answerasked a year ago
Linux OS networking bug in Elastic Beanstalk AMI with Tomcat & Correttoasked 8 months ago
Upgrade platform Coretto 11asked 6 months ago