Difference between revisions of "Deploy MS SQL to AWS"
From MgmtWiki
(→References) |
(→Debugging) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
* | * | ||
===Debugging=== | ===Debugging=== | ||
| − | * | + | Connecting to SQL seems like a never ending black hole, The following link speaks to this group of problems: https://aws.amazon.com/premiumsupport/knowledge-center/rds-cannot-connect/ |
| + | * Debugging the connection from SSMS on a Windows machine can best be tested with telnt id-addr port-number, where port-number = 1433 for SSMS. | ||
| + | ** If telnet is not enabled on your computer got to control-panel > progams-and-features > windows-features and check the box by telnet. | ||
| + | ** The most common reason for the telent error "Could not open connection to the host, on port 23: Connect failed" is observed to the firewall block telnet.exe. | ||
| + | ** If a telnet connection works, then a network connection was established, and the issue is likely caused by the user authentication to the database, such as user name and password | ||
| + | |||
| + | [https://aws.amazon.com/premiumsupport/knowledge-center/rds-connectivity-instance-subnet-vpc/ How can I troubleshoot connectivity to an Amazon RDS instance that uses a public or private subnet of a VPC?] | ||
| + | *This issue can occur when the Publicly Accessible property of the instance is set to No. | ||
==References== | ==References== | ||
* [https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.CreatingConnecting.SQLServer.html Creating a Microsoft SQL Server DB Instance and Connecting to a DB Instance] | * [https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.CreatingConnecting.SQLServer.html Creating a Microsoft SQL Server DB Instance and Connecting to a DB Instance] | ||
| + | * [https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.Scenarios.html#USER_VPC.Scenario1 Scenarios for Accessing a DB Instance in a VPC] | ||
[[Category:Best Practice]] | [[Category:Best Practice]] | ||
Latest revision as of 18:22, 23 July 2020
Full Title
Deploying an instance of Microsoft SQL Server with ASP.NET core website to Amazon Web Services
Context
- Bring up a secure SQL server for use by a web site with a minimum of fuss.
- At first the challenge is
- The assumption here is that the design is not fully fleshed out as the User Experience needs to be functional before it can be fully evaluated.
- Later the problem is to get the performance to be good while the deployment expands to multiple instances.
Problems
- The largest part of the problem is not getting the SQL server to run, but rather to ensure that it is secure and accessible where required.
Solutions
Debugging
Connecting to SQL seems like a never ending black hole, The following link speaks to this group of problems: https://aws.amazon.com/premiumsupport/knowledge-center/rds-cannot-connect/
- Debugging the connection from SSMS on a Windows machine can best be tested with telnt id-addr port-number, where port-number = 1433 for SSMS.
- If telnet is not enabled on your computer got to control-panel > progams-and-features > windows-features and check the box by telnet.
- The most common reason for the telent error "Could not open connection to the host, on port 23: Connect failed" is observed to the firewall block telnet.exe.
- If a telnet connection works, then a network connection was established, and the issue is likely caused by the user authentication to the database, such as user name and password
- This issue can occur when the Publicly Accessible property of the instance is set to No.
