Cannot get website running

Hello.

If you access the S3 static website directly with the URL below, the website will be displayed, so I think the S3 settings are correct.
http://thevictorstailgate.com.s3-website.us-east-2.amazonaws.com/

I think the problem is with the domain.
I tried resolving the NS record for "thevictorstailgate.com" on the following site, but it seemed that the NS record could not be resolved in any country.
https://www.nslookuptool.com/#NS&thevictorstailgate.com

When did you set up your domain?
If it hasn't been a while since you configured it, there may be a problem with domain propagation.

Your new name server records haven't propagated round the world yet https://dnschecker.org/#NS/thevictorstailgate.com

According to your screengrab of the Route 53 console this is set to 172800 seconds = 2 days. So it could take up to this long for the update to fully propagate.

You could try dropping that TTL figure and seeing if it makes a difference.

Probably too late now I know, but when you transferred the domain from your former provider to Route 53 you should have reduced the TTL on their end beforehand - see step 4 of https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html

I understand you're having trouble getting your website to show up after transferring it to AWS and setting it up as a static website in S3. Let's go through some potential issues and solutions:

1. S3 Bucket Configuration:

• Ensure your S3 bucket is configured for static website hosting.
• Verify that the index document is set correctly (usually index.html).
• Check that the bucket policy allows public read access to your files.

2. Route 53 Configuration:

• Confirm that your Route 53 hosted zone is set up correctly for your domain.
• Verify that you have created the necessary A record alias pointing to your S3 website endpoint.

3. DNS Propagation:

• DNS changes can take up to 48 hours to propagate fully. Be patient and try accessing your site from different networks.

4. CloudFront (if used):

• If you're using CloudFront, ensure your distribution is correctly configured to point to your S3 bucket.
• Check if you need to invalidate the CloudFront cache after making changes.

5. Browser Cache:

• Clear your browser cache or try accessing the site in an incognito/private browsing window.

6. File Permissions:

• Ensure all files in your S3 bucket have the correct permissions set to allow public read access.

7. Index Document:

• Verify that your index document (e.g., index.html) is present in the root of your S3 bucket.

8. HTTPS Configuration:

• If you're trying to access the site via HTTPS, ensure you have set up SSL/TLS certificates correctly.

If you've double-checked all these points and are still experiencing issues, you may want to review your AWS CloudFront settings (if used) or consider reaching out to AWS Support for more detailed troubleshooting.
Sources
Use your domain for a static website in an Amazon S3 bucket - Amazon Route 53
Use an Amazon CloudFront distribution to serve a static website - Amazon Route 53
Tutorial: Configuring a static website using a custom domain registered with Route 53 - Amazon Simple Storage Service
S3 static Website not syncing with my CloudFront | AWS re:Post