Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Problem Connecting to an AWS SQL 2012 Standard Server Instance using 2012 SQL Express instance Expand / Collapse
Author
Message
Posted Thursday, February 21, 2013 6:52 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 5, 2013 2:47 PM
Points: 2, Visits: 15
Hello all.

I am a SQL newbie, and I am having trouble connecting to a AWS SQL Server 2012 Standard instance I set up a couple of days ago. I can connect fine on my computer at work (an Apple Mac running parallels, SQL version 2012 standard), but from home I am having problems connecting the AWS instance. I am getting error 53, and my computer at home is an Apple, running parallels, SQL Server 2012 Express.

I have tried to change my IP/TCP settings (enabled) through SQL configuration manager, setting up port 1433, but no luck. I am not sure what the settings should be, and how to ping the AWS server instance. This is very frustrating because I want to continue testing and learning how to use SQl with my company's data at night but I can't login.

Any help would be appreciated, I just can't figure this out.

dflaherty
Post #1422840
Posted Monday, February 25, 2013 4:53 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 9:58 AM
Points: 1,225, Visits: 9,646
AWS meaning Amazon Web Services? In an EC2 instance, or through Amazon RDS?

Are you connecting to your work network via VPN, or trying to access directly via the internet?

By default you're prompted to setup inbound IP restrictions when setting up resources in Amazon (you wouldn't want your SQL Instance directly exposed to the big bad web), so it's probably that your home IP address isn't allowed access, but your work IP address is.

I doubt you'd really want to be adding people's home (dynamic) IP addresses into the AWS firewall configs, so you would need to hop via your corporate network, either via VPN, with the correct config so the AWS address is routed via your corporate external IP, or another secure access method, e.g. Citrix/RDP to a computer on the corporate network with SSMS installed.

You can use telnet to check whether the basic network access is there, e.g. from a cmd/shell prompt "telnet <aws URL> 1433"
Post #1423545
Posted Wednesday, February 27, 2013 5:20 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 5, 2013 2:47 PM
Points: 2, Visits: 15
I got it figured out, I just needed some more time to understand how AWS sets up it's instances and the security groups.

Thank you for your time!

Post #1424820
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse