For the most recent update on ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1), refer to the AWS Health Dashboard. For information on AWS Service migration, see How do I migrate my services to another region?
Cloudfront custom SSL not installing for naked domain
EDIT: I think this is an issue with google admin settings. EDIT2: It's not a google admin setting, the naked domain redirect on that dashboard only handles http requests which im already redirecting with namecheap DNS.
I am using an S3 bucket to host my site, Cloudfront to distribute it, and namecheap for the domain, DNS, and SSL Certificate.
Below I've attached all the settings and screenshot of SSL certificate and as far as I can tell everything is correct. Certificate shows both www and naked domain in Namecheap and imported to ACM. Imported certificate is also in US-East-1 and I've defined cloudfront behavior to redirect http to https. However naked domain doesn't appear in details of ACM nor under custom SSL certificate details in Cloudfront.
And when trying to navigate via HTTPS to my naked domain (https://example.com) I get a timeout error. Navigating any other way (example.com, www.example.com, https://www.example.com, http://www.example.com, http://example.com) all work. I'm totally lost at where I went wrong or if the bug is out of my hands and I need to refactor my architecture. Thanks!
- Newest
- Most votes
- Most comments
Namecheap's URL redirect may not support redirection of HTTPS traffic thus https://example.com will result in timeout. You can create "ALIAS Record" in Namecheap with "@" as Host and "CloudFront Distribution" as Value. This will direct traffic for https://example.com to your CloudFront directly without the need to use Namecheap's URL redirect service.
Relevant content
- asked 3 years ago
- asked 2 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 9 months ago
