2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hello.
Do the inbound rules of the EC2 security group allow HTTP port 80 and HTTPS port 443?
Also check the inbound and outbound rules in the subnet's network ACL.
https://repost.aws/knowledge-center/connect-http-https-ec2
0
Is the actual backed healthy? Anything from logs?
I just installed tomcat in the container, if I add custom TCP for 8080 in the inbound rule, I can access the tomcat page via public IP, will this way is valid ? can anyone pls confirm. If I remove custom TCP for 8080 am again unable to access the tomcat server page through public IP. Can anyone kindly help pls!
Ya nothing from logs
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 9 Monaten
- AWS OFFICIALAktualisiert vor 10 Monaten
Yes, it’s all done, still am facing the problem
Probably Tomcat's listening port is 8080, so even if port 80 is allowed in the security group, it cannot be accessed. If you change Tomcat's listening port to something like 80, you can connect by allowing port 80 in the security group. Of course, if you want to continue using port 8080, just allow port 8080 in your security group.