I followed quite a complicated AWS guide on setting a static hosting for my website, and it’s currently not loading, not sure why. What I have done:
- Created S3 bucket for the contents of the site
estimate.dev
- Uploaded index.html to the root of the S3 bucket
- Unblocked all access to public in the "Prermissions -> Block Public Access" tab
- Added Bucket policy for public access:
{
"Version": "2012-10-17",
"Id": "PolicyForPublicWebsiteContent",
"Statement": [
{
"Sid": "PublicReadGetObject",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::estimate.dev/*"
}
]
}
- Added “Static website hosting” feature pointing to the domain
estimate.dev
and index fileindex.html
- Added Route 53 zone for
estimate.dev
with auto-generated SOA and NS records. Set TTL of 60 seconds for each. - Added A record pointing to my S3 bucket (selected in combobox)
- Changed nameservers in my registrar's control panel to point to AWS nameservers listed in SOA record
- A day passed
Now the troubleshooting part:
- On my PC
estimate.dev
resolves to AWS IP (it was resolving Registrar IP 2 days ago) - These urls perfectly return the contents of my website (just one page, index.html): http://estimate.dev.s3-website-us-east-1.amazonaws.com/ https://s3.amazonaws.com/estimate.dev/index.html
- These urls [http://estimate.dev] & [https://estimate.dev] return
ERR_CONNECTION_TIMED_OUT
in Chrome after loading for some time
I tried to delete A record and add a CNAME but it does not allow me to select my S3 bucket there. So I reverted back to A record.
What do I miss here?