amazon web services - Unable to connect on AWS - RDS DB : SQL Server 2012 Express -


i'm new in aws world. have issue access instance of microsoft sql server 2012 express (11.00.5058) on rds (us-east-1a).

when have created db instance, able access it, create tables, transfer data, etc.. worked fine !

i didn't change , few hours after inactivity, try access sql server instance using microsoft sql server enterprise manager not able connect anymore. got following message:

cannot connect m3instance.cqbvdcpcgye3.us-east-1.rds.amazonaws.com,1433.

a network-related or instance-specific error occurred while establishing connection sql server. server not found or not accessible. verify instance name correct , sql server configured allow remote connections. (provider: tcp provider, error: 0 - wait operation timed out.) (microsoft sql server, error: 258)

currently, instance appears available, security group 'rds-launch-wizard (sg-be4afcc6)'.

i have try connect 1433 port on via telnet , no success.

instance name m3instance.cqbvdcpcgye3.us-east-1.rds.amazonaws.com.

do have idea append ?

thank lot help.

updated

telnet command return :

telnet m3instance.cqbvdcpcgye3.us-east-1.rds.amazonaws.com 1433  connecting m3instance.cqbvdcpcgye3.us-east-1.rds.amazonaws.com... not open connection host, on port 1433: connect failed 

db settings :

enter image description here

security group :

enter image description here enter image description here

vpc :

enter image description here

i have tried connect using home connection, or coffee shop wifi without success. didn't check ip address @ moment strange thing able connect sql server when have created db instance (create sql table, transfer data, etc...) after few hours (and without change), not able access it.

may if add new rule in security group / inbound rule this,it fix issue : (i didn't try yet because i'm @ work right , have firewall block sql access)

enter image description here

at point, data not sensitive , security not big issue.

thank again guys !!!

this because maybe choose default group , edit security group , in (inbound) add rule , allow connection (anywhere)


Comments

Popular posts from this blog

java - Run spring boot application error: Cannot instantiate interface org.springframework.context.ApplicationListener -

reactjs - React router and this.props.children - how to pass state to this.props.children -

Excel VBA "Microsoft Windows Common Controls 6.0 (SP6)" Location Changes -