Publish Project to AWS - Revision history

Tom: /* Deploying MSSQL on AWS */

2020-07-20T05:42:48Z

‎Deploying MSSQL on AWS

Tom: /* Deploying MSSQL on AWS */

2020-07-20T05:20:10Z

‎Deploying MSSQL on AWS

Tom: /* Deploying MSSQL on AWS */

2020-07-20T05:18:51Z

‎Deploying MSSQL on AWS

Tom: /* Deploying MSSQL on AWS */

2020-07-20T05:16:52Z

‎Deploying MSSQL on AWS

Tom: /* Deploying MSSQL on AWS */

2020-07-20T05:07:36Z

‎Deploying MSSQL on AWS

Tom: /* Deploying MSSQL on AWS */

2020-07-20T05:06:57Z

‎Deploying MSSQL on AWS

Tom: /* References */

2020-07-20T05:03:30Z

‎References

Tom: /* Problems */

2020-06-15T00:12:58Z

‎Problems

Tom: /* References */

2020-06-11T01:42:58Z

‎References

Tom: /* References */

2020-06-10T22:28:04Z

‎References

@@ Line 67: / Line 67: @@
 The security consideration is that the SQL db should not be present on a publically accessible front-end server. As with a file system, front-end could read some tables and write different tables, but not be directly involved in updates or getting executable code from any writable memory.  See the wiki page [[Web Site Security]] for more details.
 * [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19 mostly addresses the high-level architectural choices. A major component is running the SQL server on an AWS VPN with the business logic on the same VPN. In no case should SQL commands come from the front-end server, but only from well-protcted micro-services running on the VPN with SQL. See the document for details on reliable configurations which are application dependent. When user private information is on the SQL db, the location of the SQL server may be important.
 ==References==

@@ Line 66: / Line 66: @@
 ===Deploying MSSQL on AWS===
 The security consideration is that the SQL db should not be present on a publically accessible front-end server. As with a file system, front-end could read some tables and write different tables, but not be directly involved in updates or getting executable code from any writable memory.  See the wiki page [[Web Site Security]] for more details.
-* [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19 mostly addresses the high-level architectural choices. A major component is running the SQL server on an AWS VPN with the business logic on the same VPN. In no case should SQL commands come from the front-end server, but only from well-protcted micro-services running on the VPN with SQL. See the document for details on reliable configurations which are application dependent.
+* [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19 mostly addresses the high-level architectural choices. A major component is running the SQL server on an AWS VPN with the business logic on the same VPN. In no case should SQL commands come from the front-end server, but only from well-protcted micro-services running on the VPN with SQL. See the document for details on reliable configurations which are application dependent. When user private information is on the SQL db, the location of the SQL server may be important.
 ==References==

@@ Line 66: / Line 66: @@
 ===Deploying MSSQL on AWS===
 The security consideration is that the SQL db should not be present on a publically accessible front-end server. As with a file system, front-end could read some tables and write different tables, but not be directly involved in updates or getting executable code from any writable memory.  See the wiki page [[Web Site Security]] for more details.
-* [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19 mostly addresses the high-level architectural choices. A major component is running the SQL server on an AWS VPN with the business logic on the same VPN. In no case should SQL commands come from the front-end server, but only from well-protcted micro-services running on the VPN with SQL.
+* [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19 mostly addresses the high-level architectural choices. A major component is running the SQL server on an AWS VPN with the business logic on the same VPN. In no case should SQL commands come from the front-end server, but only from well-protcted micro-services running on the VPN with SQL. See the document for details on reliable configurations which are application dependent.
 ==References==

@@ Line 66: / Line 66: @@
 ===Deploying MSSQL on AWS===
 The security consideration is that the SQL db should not be present on a publically accessible front-end server. As with a file system, front-end could read some tables and write different tables, but not be directly involved in updates or getting executable code from any writable memory.  See the wiki page [[Web Site Security]] for more details.
-* [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19.
+* [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19 mostly addresses the high-level architectural choices. A major component is running the SQL server on an AWS VPN with the business logic on the same VPN. In no case should SQL commands come from the front-end server, but only from well-protcted micro-services running on the VPN with SQL.
 ==References==

@@ Line 65: / Line 65: @@
 ===Deploying MSSQL on AWS===
-The security consideration is that the SQL db should not be present on a publically accessible front-end server. As with a file system, front-end could read some tables and write different tables, but not be directly involved in updates or getting executable code from any writable memory.  See the wiki page [[Web Site Security]]'
+The security consideration is that the SQL db should not be present on a publically accessible front-end server. As with a file system, front-end could read some tables and write different tables, but not be directly involved in updates or getting executable code from any writable memory.  See the wiki page [[Web Site Security]] for more details.
 * [https://d1.awsstatic.com/whitepapers/best-practices-for-deploying-microsoft-sql-server-on-aws.pdf Best Practices for Deploying Microsoft SQL Server on AWS]. Most recent version of 2020-05 captured on 2020-07-19.

@@ Line 63: / Line 63: @@
 PS C:\Users\rp_to_000\Documents\TopCat\Repos\TrustRegistry3\RegistryServer>
 </pre>
 ==References==

@@ Line 4: / Line 4: @@
 ==Context==
 ==Problems==
 ==Solution==
 From the website [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/dotnet-core-tutorial.html Deploying an ASP.NET core application with Elastic Beanstalk].

@@ Line 65: / Line 65: @@
 * [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_server-certs.html AWS working with Server Certificates.]
 * [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https-elb.html Configuring your Elastic Beanstalk environment's load balancer to terminate HTTPS]
 * Also see wiki page [[Best Practice and Example Trust Registry]]
 [[Category:Best Practice]]