'Cannot connect to fresh Amazon EC2 Windows Micro Instance

I have tried a number of times to create an Amazon EC2 instance (micro, windows, with SQL Server Express), but I just cannot connect to the newly created instance. What am I doing wrong?

I try connecting using Remote Desktop, but it just doesn't connect.

The security group I have assigned to the instance is as follows : Port : 80 Source : 0.0.0.0/0 Port : 443 Source : 0.0.0.0/0 Port : 1433 Source : 0.0.0.0/0 Port : 3389 Source : 0.0.0.0/0

I presume the 0.0.0.0/0 means that that port is open to all IP addresses.

From the EC2 dashboard, I have taken the Public DNS, and this is what I have used to connect with using Remote Desktop.

I just took all other default options when creating the instance.

Can anyone help me? What might I be doing wrong?



Solution 1:[1]

I set up the same Amazon EC2 instance (micro, windows, with SQL Server Express). I used the default security group and had the same problem as you. Once I added port 3389 (RDP) to that security group and applied the rule, I was able to connect with RDP.

Solution 2:[2]

I had the same problem. It turns out that it took several minutes for the Security Group rules to actually apply to the new instance. The view rules link initially showed no applied rules. Once the rule appeared I was able to RDP successfully.

Solution 3:[3]

Can you not connect (timeout) or not login (passes fail)?

Timeout: make sure your security group is applied to the instance (not default).

Also double check your public DNS -- it updates when you apply an elastic IP so it may be a few numbers off.

Solution 4:[4]

You can set below inbound rule in the security settings and try again

enter image description here

Solution 5:[5]

I was also facing same issue while connecting to my RDP. I follow the below steps to resolve it,

  1. Delete all security group excluding default one.
  2. Create new security group with properties source - MyIp type - RDP
  3. Add newly created security group to instance.

It will start working.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Halvard
Solution 2 NathanAldenSr
Solution 3 Dan
Solution 4 Shakeer Hussain
Solution 5 Mahesh Shivaji Mane.