amazon web services - why are my non www https url not working?

Question

I created a static s3 bucket site that works. I created a certificate for:

• www.example.com

with additional names:

• *.example.com
• example.com

In my DNS I successfully attached all 2 certificates. Yes, all 2 because the wildcard and the blank subdomain were the same CNAME values.

In the DNS I have www.example.com CNAME going to the cloudfront url.

I figured maybe this was the issue and I should use no www and also try a wildcard, but both simply didn't work and nothing loaded.

I then created a CloudFront and attached the certificate to it with Alternate Domain Names (CNAMEs)

• www.example.com
• *.example.com
• example.com

In CloudFront my Viewer Protocol Policy is REDIRECT TO HTTPS

The behavior:

• https://www.example.com works

• http://www.example.com works (redirects to https://www.example.com)

• www.example.com works (redirects to https://www.example.com)

• example.com works (redirects to https://www.example.com)

• https://example.com breaks with a (fail) and then auto attempts with (failed)net::ERR_NAME_NOT_RESOLVED

• http://example.com breaks with a (fail)

One other thing is, I do have a separate certificate for a separate website on a subdomain sub.example.com. Would this possibly affect it?

Is there anything that stands out that would be doing this?

question from:https://stackoverflow.com/questions/66056309/why-are-my-non-www-https-url-not-working

Answer 1

Based on the comments.

Resolution of example.com did not work because the DNS host (name.com) was set to resolve only www.example.com into CloudFront distro url.

The solution was to add ANAME record to point example.com into CloudFront distro url.