Skip to content

Cannot link domain to hosting bucket in S3

0

Hello! I am new to this service and am trying to link up my domain in route 53 to my s3 bucket. I have no idea what the issue is after following and refollowing the instructions several times. The site is thevictorstailgate.com and nothing is coming up. I don't understand what some things exactly are doing as this is not my top expertise item, especially when applying all of the AWS-specific terms. Any help is appreciated on how to troubleshoot. My name servers were changed at one point when I didn't know what I was doing yet. Might that be the issue? No clue...

3 Answers
1

Hello.

I tried resolving the NS record for "thevictorstailgate.com" on the following site, but the name cannot be resolved in most countries.
https://www.nslookuptool.com/#NS&thevictorstailgate.com

Also, when I checked the NS record with whois, I found the following NS record.
Do the NS records below match the NS records registered in the Route53 hosted zone?
https://webwhois.verisign.com/webwhois-ui/index.jsp?language=

Name Server: NS-1419.AWSDNS-49.ORG
Name Server: NS-1589.AWSDNS-06.CO.UK
Name Server: NS-345.AWSDNS-43.COM
Name Server: NS-888.AWSDNS-47.NET

By the way, does the S3 bucket name match the domain name?
For example, S3 static hosting cannot be used unless the domain name and S3 bucket name match.
In other words, you cannot use it unless you create an S3 bucket with the bucket name "thevictorstailgate.com".
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started-s3.html

EXPERT

answered 2 years ago

EXPERT

reviewed 2 years ago

EXPERT

reviewed 2 years ago

  • The bucket and the domain do match, but those name servers are different. Should I change them in Route 53?

  • So, tried to change them and that did not work... any other things I can do? I have followed all of the steps in the link provided thoroughly.

  • The value of the NS record registered in Route53 must match the NS record that can be checked with whois.

    So, tried to change them and that did not work...

    Does this mean that an error occurred when making the change? Changes to DNS records will not take effect immediately, so you will need to wait for a while.

  • It does match now. Yes, the time lapse could be an issue. We shall see...

  • Do buckets need to know name servers?

0

Hello,

Verify Route 53 Domain Settings

  • Go to the Route 53 dashboard and ensure your domain is correctly registered and pointing to the right S3 bucket.
  • Check if your name servers (NS records) in Route 53 match the ones provided by your domain registrar (if you bought the domain elsewhere).

Check S3 Bucket Configuration

  • Make sure your S3 bucket's name exactly matches your domain name, including "www" if you're using it EX. thevictorstailgate.com
  • In the S3 bucket settings, enable Static Website Hosting:
  • Go to Properties → Static Website Hosting.
  • Ensure the correct index.html and error.html pages are specified.

Bucket Permissions

  • Your S3 bucket must be public for the website to be accessible. Ensure the bucket policy allows public access.
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "PublicReadGetObject",
      "Effect": "Allow",
      "Principal": "*",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::thevictorstailgate.com/*"
    }
  ]
}

  • Confirm that Block Public Access is disabled for the bucket.

DNS Records in Route 53

  • Create an A record (alias) in Route 53 that points to your S3 bucket:
  • Go to Route 53 → Hosted Zones → Your Domain → Create Record.
  • Select A - IPv4 address, and enable Alias.
  • In the alias target dropdown, select your S3 bucket endpoint (it should show up automatically if set up correctly).

Wait for DNS Propagation

  • DNS changes, like updating name servers or adding new records, can take some time (up to 48 hours) to propagate. You can check the status with a DNS checker tool like DNSChecker.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/RoutingToS3Bucket.html#:~:text=To%20route%20domain%20traffic%20to%20an%20S3%20bucket%2C,as%20example.com%2C%20and%20for%20subdomains%2C%20such%20as%20www.example.com.

EXPERT

answered 2 years ago

  • Thank you! I've done all of these steps previously hence why I'm perplexed. The bucket setting are correct, the index page is set (didn't do an error page). Public access is enabled. A record was created in Route 53. I've ensured the NS matches in both also.

    Some Qs: Does the endpoint in the alias record need to be the generic location (s3-website.us-east-2.amazonaws.com.) or the full string including thevictorstailgate.com? This domain was moved from register.com, is there anything that might be confusing things there?

    I will include some pictures...

0

Enter image description here Enter image description here Enter image description here

answered 2 years ago

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.