Amazon Route 53 Alias โโNot Working
For some reason, I am unable to set up my static website in S3. I've been trying to resolve this for the past 2 weeks, but it doesn't work for me.
What I've done:
- Uploaded files to S3 bucket.
- Setting up a routing policy is fine.
- Target Alias โโDropdown - I can see S3 endpoints.
- Hosted zones have been created.
- Set up both an alias with and without WWW.
Result. When I type the url in the address bar, it gives an error message. None of the sites are down or DNS related errors.
I tried to follow the same steps 6-7 times, no problem at all, but domains don't work in the end. Absolutely incomprehensible where am I going wrong?
source to share
I find a solution.
I seem to have deleted my hosted zone which was first created by amazon against my domain name.
Later, when I created my hosting zone again against the same domain name, I have to update the nameservers in the hosting zone page which resolved the nameserver resolution conflict
source to share
Your zone and domain servers may not be in sync:
In Route 53, check the Name Servers (NS) created by your Hosting Zone as listed in the Registered Domains section . P>
SCREENSHOT: AWS Route 53 Top Left Menu - Hosting and Registered Domains
- Click "Hosted Zones"
- Choose your domain (example.com)
- Select "Recordset" with type NS
-
Copy each element / nameserver from the values โโfield
ns1.amazon.com
ns2.amazon.org
ns3.amazon.net
ns4.amazon.co.uk
-
Now click on "Registered Domains"
-
Choose your domain
-
Walk past each entry in the upper right corner
source to share
The basic steps to create an Amazon Route 53 that belongs to an Amazon S3 bucket are as follows -
- Create a bucket with a DNS name (e.g. images.my-company.com) - note that the Bucket Name must match the DNS you want users to enter when accessing the URL
- Activate Static Website Hosting on Amazon S3 Bucket
- In Route 53, create a Hosting Zone or use an existing Hosting Zone
- Create an entry in the guest area
- Name: Match the subdomain to your S3 bucket name
- Type: A
- Alias: Yes
- Alias: Select your S3 website from the dropdown
See: Setting up a static website using a custom domain
The most important part is that the Bucket must have the same name as the Route 53 domain name (for example, images.my-company.com).
If you are having problems, first try accessing the content via the URL of the static website. If that works, resolve the URL (e.g. via DNSLOOKUP or PING) and compare the IP address with your domain name's resolution. They should both return the same IP address.
source to share