Deploy .NET to AWS - Revision history

Tom: /* References */

2020-07-22T22:00:26Z

‎References

Tom: /* Debugging */

2020-07-05T21:06:54Z

‎Debugging

Tom: /* Solutions */

2019-05-15T02:55:52Z

‎Solutions

Tom: /* Solutions */

2019-05-15T02:55:08Z

‎Solutions

Tom: /* Solutions */

2019-05-15T02:52:46Z

‎Solutions

Tom: /* Solutions */

2019-05-15T02:51:33Z

‎Solutions

Tom: /* Solutions */

2019-05-15T02:49:49Z

‎Solutions

Tom: /* Debugging */

2019-05-14T21:32:03Z

‎Debugging

Tom: /* Debugging */

2019-05-14T21:07:18Z

‎Debugging

Tom: /* Debugging */

2019-05-14T21:05:22Z

‎Debugging

← Older revision		Revision as of 22:00, 22 July 2020
Line 54:		Line 54:

	==References==		==References==
−	[[Category:~~Profile~~]]	+	[[Category:Best Practice]]

@@ Line 17: / Line 17: @@
 ** [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_server-certs.html#upload-server-certificate pushing the private key to an S3 bucket.]
 ===Debugging===
 * It is possible to install and run [https://aws.amazon.com/powershell/ AWS PowerShell tools] on your local computer to see what EC2 instances look like. (An instance is one server running the site.)
 ** [https://docs.aws.amazon.com/powershell/latest/userguide/pstools-getting-set-up-windows.html Setting up the AWS Tools for PowerShell on a Windows-based Computer]

@@ Line 14: / Line 14: @@
 * Elastic Beanstalk (EB) automates some of the deployment and expansion services for EC2. [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.html Creating and Deploying Elastic Beanstalk Applications in .NET Using AWS Toolkit for Visual Studio.]
 * [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/SSLNET.SingleInstance.html Terminating HTTPS on Amazon EC2 Instances Running .NET] on single instances (not behind a load balancer for this use case.)
-** On the EC2 instance you need to open HTTPS port (443). To do that, you go to https://console.aws.amazon.com/ec2/ and click on the Security Groups link on the left, then change the existing or create a new security group with to include HTTPS availability. It is best to select the HTTPS type in the drop-down menu to add to a security group as it will create entries for both IPV4 and IPV6 address ranges. After accepting the change, be sure that 0.0.0.0/0 is enabled for port 443.
+** On the EC2 instance you need to open HTTPS port (443). To do that, you go to https://console.aws.amazon.com/ec2/ and click on the Security Groups link on the left, then change the existing or create a new security group to include HTTPS availability. It is best to select the HTTPS type in the drop-down menu to add to a security group as it will create entries for both IPV4 and IPV6 address ranges. After accepting the change, be sure that 0.0.0.0/0 is enabled for port 443.
 ** [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_server-certs.html#upload-server-certificate pushing the private key to an S3 bucket.]
 ===Debugging===

@@ Line 13: / Line 13: @@
 * Elastic Compute Cloud (EC2) was selected as the resource for its ease of deployment and expansion to handle volume.
 * Elastic Beanstalk (EB) automates some of the deployment and expansion services for EC2. [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.html Creating and Deploying Elastic Beanstalk Applications in .NET Using AWS Toolkit for Visual Studio.]
-* [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/SSLNET.SingleInstance.html Terminating HTTPS on Amazon EC2 Instances Running .NET] on single instances (not behind a load balancer.)
+* [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/SSLNET.SingleInstance.html Terminating HTTPS on Amazon EC2 Instances Running .NET] on single instances (not behind a load balancer for this use case.)
-** On the EC2 instance you need to open HTTPS port (443). To do that, you go to https://console.aws.amazon.com/ec2/ and click on the Security Groups link on the left, then change the existing or create a new security group with to include HTTPS availablity. It is best to select the HTTPS type to add to a security group as it will create entries for both IPV4 and IPV6 address ranges. After accepting the change, be sure that 0.0.0.0/0 is enabled for port 443.
+** On the EC2 instance you need to open HTTPS port (443). To do that, you go to https://console.aws.amazon.com/ec2/ and click on the Security Groups link on the left, then change the existing or create a new security group with to include HTTPS availability. It is best to select the HTTPS type in the drop-down menu to add to a security group as it will create entries for both IPV4 and IPV6 address ranges. After accepting the change, be sure that 0.0.0.0/0 is enabled for port 443.
 ** [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_server-certs.html#upload-server-certificate pushing the private key to an S3 bucket.]
 ===Debugging===

@@ Line 14: / Line 14: @@
 * Elastic Beanstalk (EB) automates some of the deployment and expansion services for EC2. [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.html Creating and Deploying Elastic Beanstalk Applications in .NET Using AWS Toolkit for Visual Studio.]
 * [https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/SSLNET.SingleInstance.html Terminating HTTPS on Amazon EC2 Instances Running .NET] on single instances (not behind a load balancer.)
-** On the EC2 instance you need to open HTTPS port (443). To do that, you go to https://console.aws.amazon.com/ec2/ and click on the Security Groups link on the left, then change the existing or create a new security group with also HTTPS available. It is best to select the HTTPS type to add to a security group as it will create entries for both IPV4 and IPV6 address ranges. After accepting the change, but sure that 0.0.0.0/0 is enabled for port 443.
+** On the EC2 instance you need to open HTTPS port (443). To do that, you go to https://console.aws.amazon.com/ec2/ and click on the Security Groups link on the left, then change the existing or create a new security group with to include HTTPS availablity. It is best to select the HTTPS type to add to a security group as it will create entries for both IPV4 and IPV6 address ranges. After accepting the change, be sure that 0.0.0.0/0 is enabled for port 443.
 ** [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_server-certs.html#upload-server-certificate pushing the private key to an S3 bucket.]
 ===Debugging===

@@ Line 31: / Line 31: @@
 ** Navigate to cert store "cd Cert:\LocalMachine\my" and list certificates to be sure the SSL cert is loaded and has a key "(dir)[0] | fl *" where the index "[0]" matches the https cert.
 ** Examine firewall WebServerRole rules: Show-NetFirewallRule -PolicyStore ActiveStore | % {If($_.Name -match "WebServerRole") {$_}}
 ** Try to restore an existing key and certificate:
   PS Cert:\LocalMachine\my> certutil –repairstore my "EF96A6EDFE748ADA67CEFEEE6CF49DE46707EEF4"