I have an S3 bucket configured as a static web site with public access and the standard permission policy. It’s hosted in US East (region 1). The URL for this bucket works.
I’ve created an A-record with the same domain name, as an alias, and value s3-website-us-east-1.amazonaws.com, which is the meat of the bucket URL. I can’t ping it. Any ideas?
I expected the domain name to be recognized by the internet, but it is not, despite Route53 telling me that the new record has been synced.
2
Answers
Well. The problem is not the domain or the A-record. I have another domain that fetches items from its bucket–items that were created some time ago. I created a new folder and put content into it, and came back 404.
Evidently something has changed over time–a configuration setting?
Any ideas?
I’ve never heard of anyone pinging an s3 bucket before. That requires the underlying server to accept ICMP requests.
You should curl instead of ping here to fetch the actual contents of the bucket. Or you know, just try loading the content on your browser.