- 最新
- 投票最多
- 评论最多
First, let's ensure that the CloudFront distribution is properly associated with your domain. In the CloudFront console, make sure that you've added your domain (e.g., example.com) as an alternate domain name in the distribution settings.
Next, verify that the SSL certificate associated with the CloudFront distribution covers your custom domain. If you're using AWS Certificate Manager, ensure that the certificate includes both the domain and subdomains (e.g., *.example.com).
Additionally, check the DNS settings for your domain. Make sure that you have a CNAME record pointing to the CloudFront distribution URL. It's important to verify that the DNS settings have propagated, as this can sometimes take time.
Is your domain registered with AWS or an external registrar?
If it's an external registrar, are your domain records configured to use the Route53 nameservers? Details for the name servers are available in your Route53 hosted zone as below!
Thx for quick reply. Domain was transferred from godaddy. I think it was properly released and transferred. I've tried to validate the domain via DNS but it didn't work (pending status for days - and yes I added the record generated by AWS to the zone during this type of validation) - email validation was OK. Now domain is fully under AWS - checked WHOIS. I didn't touch the NS records in the zone - it was generated by AWS. Something somewhere is wrong because even DNS validation didn't work.
相关内容
AWS 官方已更新 1 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Thx for quick reply. CloudFront alternate domain set - if not I couldn't create A Record in zone for distribution via wizard. Certificate is set as *.example.com. I have there A Record - it enables connect CloudFront endpoint and distribution directly, but yes I've tried instead A Record CNAME too. And no change. I let it propagated for several days.