AWS EC2 – Troubleshooting SSH Connection Issues

After reading the VPC documentation more closely, my first EC2 instance is connected.

Here is what i got wrong when setting up the EC2 instance and VPC.

With only a private ip, my development machine would never be able to connect to the EC2 instance unless it was a part of the VPC's network. So to talk to it from the outside, I needed to specify that for every instance created that an associated public ip address be assigned as well.

Here is what did to fix it:

1. Correct me if i am wrong, but it looks like there was not an option in the EC2 browser console to assign a public ip address to the already created instance, So i ended up deleting it.

2. I want back to the VPC console, and went to the subnets option. I then selected the public subnet that was initially created in the VPC wizard and specified in the "Modify Auto-Assign Public IP" option to enable the auto-assignment of a public ip address for every new EC2 instance created.

3. Create a new EC2 instance, and a new public ip address is assigned.

4. Followed amazon's directions for ssh and communication was successfully initiated.

I had a similar frustrating problem when I installed JetBrains YouTrack on a Windows Server 2012 ec2 instance. What worked for me was opening the Windows firewall ports that java was using specifically and disabling the World Wide Publishing service port. I also had to run the YouTrack service under the LocalSystem account instead of the default account.

Try this:

• Turn off the default website in IIS if it is in use

• Run a netstat -a -b to discover the ports the java.exe was attempting to bind to e.g:

  TCP 0.0.0.0:80 WIN-9NFIG6IEPT6:0 LISTENING [java.exe]

  TCP 127.0.0.1:49306 WIN-9NFIG6IEPT6:49307 ESTABLISHED [java.exe]

• Open the service control manager and right click on your service and open the properties dialog. On the Log On As tab select Local System Account as the account the service runs under. It's important that this user be Administrator

• I highly recommend turning the firewall back on.
• Open the firewall Inbound rules tab and disable the World Wide Web Services (HTTP-In) Rule

• Create a new rule for Tomcat with TCP Port 80 and any other port it might need.

• Save the rule and test your url from outside the server.