Issue configuring a website using cloudfront+S3+ route 53+ google domains

0

Hey Everyone, I am exploring the platform and decided to host a couple of websites. For one, I purchased the domain from Route 53 and quickly set it up using Route 53 and S3 (HTTP only).

For the second website, I used a domain previously associated with my Shopify store (now disconnected) and registered with Google Domains. I followed a similar approach, but this time, I copied the four DNS servers provided by Route 53 to Google Domains.

The website works correctly when accessed through the S3 static website link, but when I try to open it in browsers like Safari or Chrome, it loads indefinitely and eventually fails. I used https://www.whatsmydns.net to check propagation, and most servers show green in A and NS records.

I attempted to use CloudFront on top of that, obtained the right certificates, and made modifications to S3, but the problem persists. It seems to be an issue between Google Domains and Route 53. Any feedback would be appreciated as I am trying to learn more about the platform.

Thank you for reading!

1 Answer
0

Hello.

If the domain settings are correct, please review the settings as shown below.
For S3 static website hosts, the bucket name and domain name must match.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html

In the case of CloudFront and S3, you will need to check whether the S3 bucket policy is correct.
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html

profile picture
EXPERT
answered 23 days ago
profile picture
EXPERT
reviewed 23 days ago
  • Thank you for your reply, Sadly I followed the tutorials you mentioned to the T, the website is running when accessed through the cloudFront link (******.cloudfront.net). On the google Domains side It is configured to use Custom name servers. Is there anything else to do on that end besides adding the 4 servers given by route 53?

  • Can you use something like the "dig" command to confirm that the NS records can be resolved correctly? If this cannot be confirmed, the NS record may be set incorrectly, or there may be some cache remaining due to TTL, etc.

    dig domain.com ns
    
  • @Riku when I enter my domain name and do a DNS look up for NS this is what I get :

    user-MBP:~ bruce$ dig domain.com ns

    ; <<>> DiG 9.10.6 <<>> domain.com ns ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6910 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 5

    ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;domain.com. IN NS

    ;; ANSWER SECTION: domain.com. 172800 IN NS ns-552.awsdns-05.net. domaincom. 172800 IN NS ns-8.awsdns-01.com. domain.com. 172800 IN NS ns-1258.awsdns-29.org. domain.com. 172800 IN NS ns-1771.awsdns-29.co.uk.

  • The NS record looks fine. By the way, did you set up the CloudFront document below? https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html

  • No luck, Everything in cloudfront seems to be configured properly. is there any other NS besides these 4 that could would need to be added to google domains? I'm gonna keep playing with it, I am convinced that something is off on google domains end since the other website I created works fine.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions