So we have a production EC2 instance running Amazon Linux 2013.03 and apache Tomcat 7. Sadly due to the configuration of the web application in question, the server cannot be updated except for specific packages to keep security concerns down. There is a plan to completely rebuild the application but we need the current system to keep working till that can be done.<\/p>\n
Advertisement
That said, after November 30th 2022 the instance mentioned shutdown and could not be started up again. It was a C1.Medium instance size and running in the US-West-2b availability zone, the error given was that AWS did not have the capacity to start the instance type specified. So I started a new instance as a C3.Large from an AMI that had recently been used (and worked) but this time, the application seemed to stop working immediately no matter how I started it up. It behaved as though updates had been applied although there is no reason for them to occur. The CloudWatch log pulled from the instance showed that something had been updated but we don’t know how or why, this occurs no matter what AMI we spin up going back for years. Currently I am trying to get the application to either work despite the updates, even if this requires updating code or components. \nI am not a developer, so I am not sure how to do that. The application is built on Java 7. I have been able to confirm that Tomcat itself is working fine, it seems to be something within the application. \nIf you are a Java and/or Tomcat expert, I could definitely use assistance on this ASAP. I have plenty more details but for security reasons and privacy of data within the application I cannot reveal too much here.<\/p>\n
