RDS - SQL Server Express - Connectivity
Sorry, I've been working at this for the past 4 hours...
Created an RDS SQL Server Express DB via "Easy Create" options.
I modified config after to allow public access.
I'm not able to connect via Visual Studio Code "mssql for Visual Studio Code" extension.
"mssql: Error: Unable to connect using the connection information provided."
I'm also not able to ping, telnet et cetera the endpoint plus 1433 port. That bit doesn't completely surprise me - I've seen posts stating Amazon blocks that type of traffic.
Database is associated with default VPC which is wide open - no defaults changed.
Under "Security Groups" for database I see "Security group rules (2)" which leads me to believe there are 2 groups associated but the list below is completely blank and I cannot edit - add, delete, modify. My thought it those groups are hidden since it's managed.
Any ideas?
Thank you!
there could be multiple reasons for which you are not able to connect to the db instance. If you are connecting from visualstudio running outside of aws (could be your laptop) you need to make sure that the instance is public
you can refer to https://aws.amazon.com/getting-started/hands-on/visualize-data-amazon-rds-sql-server-using-amazon-quicksight/ which explains about how to connect using ssms and you can ignore the quicksight connectivity.
Relevant questions
RDS SQL Server upgrade downtime
Accepted Answerasked 2 years agoError while connecting to SQL Server Express Edition from SCT
asked a year agoRDS - SQL Server Express - Connectivity
Accepted Answerasked a month agoCan't connect to SQL Server 2014 Express AMI
Accepted Answerasked 3 years agoRDS SQL Server backup options
Accepted AnswerAWS RDS - Microsoft SQL Express Server - Cannot add users with permissions
asked 5 years agoRDS SQL Server - Using MSDN licenses
Accepted Answerasked 5 years agoHow is RDS for SQL Server Express charged?
Accepted Answerasked 6 months agoAnnouncement: Amazon RDS for SQL Server ending support for Microsoft SQL Server 2012
asked 3 months agoSQL Server on RDS Issue With Linked Server
Accepted Answer
Thanks so much for your help and pointing out that page. My issue was in the inbound messages per step J - adding an inbound rule for traffic from my machine. I mistakenly thought the existing rule allowed all traffic regardless of source - it was only from an existing Security Group.
Thank you again!