Cannot connect to AWS EC2 from visual studio (or a

Question

I have an AWS server (MS SQL SERVER EXPRESS 2008 R2 with IIS), with an elastic IP of 54.214.8.111, security groups configured with HTTP, MS SQL and FTP, and I can connect to the remote virtual machine using the rdp file that amazon gives you in the console.

However when I try to connect via visual studio to test if the database is working, it gives me a "Login failed for user 'dbuser' error. I have a user called dbuser on my SQL Server (on the server side of course) with full access permissions etc. I also cannot connect to an ftp on the server, despite all guides and help doc. Something seems to be simply blocking my connection. I have tried the same thing on multiple computers.

Everything seems to be configured correctly except I suspect the server instance.

Can anyone help? PS I'm fairly new to web development, this is my first AWS EC2 server.

[UPDATE] I just tried to create a new instance in a different location, same error, maybe I don't know how to configure the SQL Server on the EC2?

Answer 1

I recently had the same connectivity issue to AWS/SQL Server, I finally have it resolved.

Connecting to SQL Server remotely on AWS involves 3 main factors: AWS --> Windows Security --> SQL Server Settings/Security.

Connections can easily fail because each area has specific requirements. I'll go through the check-list:

AWS:

1. In AWS management console, go to Security Groups, click on the group that applies to your windows server, make sure MS SQL TCP port 1433 is open to 0.0.0.0 or your specific client IP. If not, you'll need to add it.

2. Note the Public IP of your server

WINDOWS:

1. RDP to the Amazon Windows server, Start > Administrative Tools > Local Security Policy
2. Click Windows Firewall with Advanced Security, Windows Firewall Properties, Click the "Public Profile" tab, set Firewall State to "ON", Inbound to Block, Outbound to Allow (or block depending on your application). OK.
3. Expand the Windows Firewall (on the left Pane), R-Click the Inbound Rule, Click New Rule.
4. Click Port option, Next > , for TCP, enter 1433 Next >, Allow the connection, Next >, Next > , give it a name (SQL-PORT-ACCESS)

SQL-SERVER:

1. Login to SQL Server with SSMS (SQL Server Management Studio) using the default windows authentication.
2. On the left-pane, R-click the top server listing (with the database icon, the very first listing), and select "Properties"
3. Properties window, click Security on the left pane, choose the "SQL Server and Windows Auth"
4. Click Connections, check the "Allow Remote Connections" option ... Click OK.
5. Open the SQL Configuration Manager, Start > Programs > Microsoft SQL Server > Configuration Tools > SQL Server Configuration Manager
6. SQL Server Network Configuration (Expand), select Protocols for MSSQL, R-Click TCP , select Properties (TCP should be enabled)
7. Click IP Addresses tab, check that IP1 is enabled, Dynamic Ports is 0, TCP port is 1433
8. Scroll all the way down to IPAll section, Enter 0 in TCP Dynamic Ports, and 1433 in TCP Port. OK...
9. Back on the left pane, click, SQL Server Services, R-Click the SQL Server option, and select "Restart". (NOTE: SQL Browser server does not impact connectivity, browser service only lists available servers, with your specific connection parms, no need to start or worry about the browser)

TESTING: You don't have go to your remote client to test, start by trying to connect from the same SSMS window on the server. This reduces all the other things that can go wrong at first, if you can connect here, you have some confirmation that it works. If it doesn't work from your own server, the issues are related to Windows security and SQL security and setup.

1. Under the Object Explorer (SQL server Management Studio), click "Connect" > Database Engine...
2. In the Server name:, enter your PUBLIC IP, a comma, then 1433. Example, if your public IP is 54.4.4.4 , enter 54.4.4.4,1433,
3. Select the authentication as "SQL Server", enter the login user and password.
   1. If you're using "sa", remember to change the password.
   2. If your connection works locally, then you can try your remote client connection.
4. At this point you know your SQL server and user settings are correct.

Next, try using SSMS on another computer. If that fails, probably the firewall needs a 2nd look...

Good place to understand issues, is the SQL logs easily accessible from SSMS, on the left pane, expand Management, then SQL Server Logs, current log will list any problems.

So, those are all the parts involved -- miss one and you'll be frustrated, but start by reducing the pieces when testing.

I was able to connect to my database on AWS Windows Server/SQL Express from a Windows device...

Good Luck!