- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Does Lightsail use a load balancer or similar?
If not used, IIS may need to be configured to use an SSL certificate.
https://learn.microsoft.com/en-us/iis/manage/configuring-security/how-to-set-up-ssl-on-iis
I thought the status was unused because there was no load balancer, etc.
Not sure what blueprint type the instance you're trying this with is but Lightsail has a bunch of tutorials for setting up SSL: https://lightsail.aws.amazon.com/ls/docs/en_us/search?s=SSL
For example, here's a tutorial on how to create and configure SSL certificated with a LAMP instance: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-using-lets-encrypt-certificates-with-lamp
I've made progress. WWW.mydomain.com is now working with SSL. Unfortunately, mydomain.com is not working with SSL. Web browser says "Not Secure" when I simply enter mydomain.com. I got www.mydomain.com working by following their directions to create a load balancer, adding an SSL certificate to the load balancer and then adding a CNAME DNS record that points www to the load balancer DNS name.
My DNS is supported by Godaddy. The A-Record points to the public IP address of the IIS Server. You can't specify a DNS name for the A-Record so mydomain.com points to my public IP address -- not the load balancer with the SSL certificate. How do I get mydomain.com to have SSL support?
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Monaten
Latest Status: Yes, the certificate I purchased and installed on the IIS running on my Lightsail instance is worthless. I had to create a load balancer and an AWS certificate, add a WWW CNAME to my DNS and WWW.MyDomain.com now has SSL working -- BUT not MyDomain.com. I can't figure out how to get SSL working for MyDomain.com. Until AWS can tell me how to get SSL for MyDomain.com, I am circumventing the problem by installing the URL Re-write module in IIS and simply change MyDomain.com to WWW.MyDomain.com -- that is working -- It's "HOKEY" but it works. I would prefer a better solution.