[EC2] What to do when restarting instance Tomcat fails

Z CARE Modified on: Thu, Jun 12, 2025 at 4:01 PM

Environment
1. Tomcat is installed and operated separately on an EC2 instance.
2. Remote access to the EC2 instance running Tomcat is made from an on-premise VDI, not through a Bastion host.
3. When attempting to restart Tomcat after remotely connecting to the EC2 instance from the on-premise VDI, a Tomcat shutdown error occurs.
Action
1. Add Tomcat port to the Security Group of the EC2 instance running Tomcat as a loopback
  - Source: Security Group of the EC2 instance running Tomcat (Loopback)
  - Registered ports: Inbound rule: TCP / 8005, 8009, Outbound rule: TCP / 8009