Port 8080 is still closed after adding a TCP custom rule to AWS Security Group

Question

I have been dealing with a very messy problem which is that I need a new open port in my EC2 instance.

I have a node.js application running in this instance. To make that happen I had to open the port 3000 through adding a new inbound rule in the security groups, which worked perfectly.

Now, I need another port opened so I can send data from an external IP to that port.

I tried opening the port adding a new inbound rule as well, but with not success. The port gets opened but just in the localhost, not in the public or private IP, so I can not telnet to the port.

I have tried adding it to the firewall iptables as well using the Ubuntu shell but I have no success on it.

I would really appreciate any help, any response. Thank you!!

Answer 1

I should do comment to get something clear from you but due to low reputation i can't. So, just ignore reputation or scoring lets consider learning.
Here are complete tutorial to add new ports in an AWS instance:

1. Open the Amazon EC2 console at EC2 Console
2. In the navigation pane, choose Security Groups. Select the security group for your instance.
3. Choose Inbound, Edit, Add Rule.
4. For Type, choose choose accordingly.
5. Now it comes "Secure Filed" it decides that which system can access this port. So, if you want that only your or some other specific systems could access this machine give their IPs e.g. in IPV-6 format. Or you want this port open publicly just enter 0.0.0.0 as IP here.
6. Choose Save.

Please follow this tutorial, I am sure it would work, in your case I think you are missing "Secure Field" thing.