Deploy MS SQL to AWS - Revision history

Tom: /* Debugging */

2020-07-24T01:22:39Z

‎Debugging

Tom: /* Debugging */

2020-07-23T01:39:43Z

‎Debugging

Tom: /* Debugging */

2020-07-23T01:38:49Z

‎Debugging

Tom: /* Debugging */

2020-07-23T01:30:56Z

‎Debugging

Tom: /* Debugging */

2020-07-23T01:29:33Z

‎Debugging

Tom: /* References */

2020-07-23T00:20:54Z

‎References

Tom: /* References */

2020-07-23T00:20:31Z

‎References

Tom: /* References */

2020-07-22T22:01:52Z

‎References

Tom at 21:59, 22 July 2020

2020-07-22T21:59:19Z

Tom: Created page with "==Full Title== Deploying an instance of Microsoft SQL Server with ASP.NET core website to Amazon Web Services ==Context== *Bring up a secure web site deployment with a minimum..."

2020-07-22T21:58:07Z

Created page with "==Full Title== Deploying an instance of Microsoft SQL Server with ASP.NET core website to Amazon Web Services ==Context== *Bring up a secure web site deployment with a minimum..."

New page

==Full Title==
Deploying an instance of Microsoft SQL Server with ASP.NET core website to Amazon Web Services
==Context==
*Bring up a secure web site deployment with a minimum of fuss.
*At first the challenge is getting the [[Web Site]] working well.
*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===
*

==References==
[[Category:Best Practice]]

@@ Line 13: / Line 13: @@
+*
 ===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
 ==References==

@@ Line 16: / Line 16: @@
 * 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 enable on your computer got to control-panel > progams-and-features > features and check he box by telnet.
+** 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

@@ Line 13: / Line 13: @@
+*
 ===Debugging===
-Connecting to SQL seems like a never ending black hole, The following link speaks to this group of problems:
+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 enable on your computer got to control-panel > progams-and-features > features and check he 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, the problem is most likely permission on the db itself.
+** 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
 ==References==

@@ Line 16: / Line 16: @@
 * 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.
 ** 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, the problem is most likely permission on the db itself.

@@ Line 17: / Line 17: @@
 ==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/USER_VPC.Scenarios.html#USER_VPC.Scenario1 Scenarios for Accessing a DB Instance in a VPC]
+* [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]]

← Older revision		Revision as of 22:01, 22 July 2020
Line 16:		Line 16:

	==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]
		+
	[[Category:Best Practice]]		[[Category:Best Practice]]

@@ Line 2: / Line 2: @@
 Deploying an instance of Microsoft SQL Server with ASP.NET core website to Amazon Web Services
 ==Context==
-*Bring up a secure web site deployment with a minimum of fuss.
+*Bring up a secure SQL server for use by a web site with a minimum of fuss.
-*At first the challenge is getting the [[Web Site]] working well.
+*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.