In AWS go to EC2 and Load balancer and select our Load balancer (kimchi-elb)
There is only one Listener on port 80. Click the Add listener button
Update Protocol to HTTPS and Port to 443. Change Target group to custom target group (kimchi-tg)
In the Secure listener settings section select the Request new ACM certificate link. Click on the Request a certificate button. At the Request a certificate screen click the Next button to Request a public certificate.
In the Domain names section add domain names (kimchimenow.com, spicy.kimchimenow.com, dvwa.kimchimenow.com, splunk.kimchimenow.com). Then click the Next button at the bottom of the page.
Pending validation may take 30 or more minutes. Select the new certificate.
Click on the Create records in Route 53 button.
Click on the Create records button. These records help later auto renew the certificate if the certificate is set to auto-renew.
When the certificate is Issued can proceed with next steps
Navigate back to the Load balancers tab in the browser
In the Secure listener settings section click the Refresh button and select the certificate that was created. Click the Add button and then the View listeners button at the next screen.
Navigate to https://spicy.kimchimenow.com and should see the lock next to the url showing it is secured by certificate. Going to http will still have an unsecure url to the webpage. The other pages will not be secured because there is no listener defined with a certificate.
Go to Load balancers and then select the load balanc er (seas). Select HTTP:80 and under Actions select Delete listener
Click the Add listener button. Choose Action to Redirect, Protocol HTTPS and Port 443. Click the Add button, and then at the next screen the View listeners button
Now the url should forward from port 80 to secure port 443. Test by opening browser to http://spicy.kimchimenow.com