- Newest
- Most votes
- Most comments
After going through the links you provided, I think the redirection is working fine but the page is not loading. I think it's redirecting to the https version of the website, however, note that https is not supported for S3 static website, which is probably it's not loading. For S3 website, you need to use http. If https is a must, and ideally should be for external websites, consider using cloudfront.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/how-to-page-redirect.html https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started-cloudfront-overview.html
Sounds like you're trying to do what I do with my site.
I have two buckets called mysite.net and www.mysite.net, both with Static website hosting enabled, with the bucket website endpoint of each bucket being http://mysite.net.s3-website-ap-southeast-2.amazonaws.com and http://www.mysite.net.s3-website-ap-southeast-2.amazonaws.com respectively.
Route 53 hosted zone is setup like this:
This works for me. Can you try similar (obviously using Northern California region instead of Sydney)?
The issue you're experiencing with your S3 bucket redirect not working properly could be due to several factors:
-
Bucket Configuration: When setting up a redirect bucket, make sure you've selected "Redirect requests" as the hosting type (not "Host a static website") in the static website hosting configuration. This is a common mistake that prevents redirects from working properly.
-
Protocol Setting: For the redirect configuration, ensure you've correctly specified the protocol. If your www site uses HTTPS, make sure to select "https" in the protocol dropdown rather than "http" or "none".
-
Formatting of the Host Name: Double-check that the host name is correctly formatted. It should be exactly "www.owenhamlin.com" without any extra characters, slashes, or protocol prefixes.
-
Permissions: While you mentioned that Block Public Access is turned off, you might still need a bucket policy that explicitly allows public read access. For a redirect bucket, you should have a policy that includes the s3:GetObject permission for public access.
-
Propagation Time: Changes to S3 website configurations can sometimes take time to propagate fully. Wait a few minutes after making changes before testing again.
-
Browser Cache: Your browser might be caching previous responses. Try clearing your browser cache or testing in an incognito/private browsing window.
-
Testing Method: Make sure you're testing using the S3 website endpoint URL (http://owenhamlin.com.s3-website-us-west-1.amazonaws.com) and not the S3 API endpoint. Redirects only work when accessing through the website endpoint.
If you've verified all these settings and the redirect still isn't working, there could be an issue with how the redirect is being processed. In that case, you might want to consider creating a support case with AWS for more specific assistance with your configuration.
Sources
S3 website-redirect-location not redirecting | AWS re:Post
Domain Redirect on S3 missing colon https// | AWS re:Post
CloudFront cache and S3 bucket redirect issue | AWS re:Post
answered a year ago
Relevant content
asked 4 years ago
asked a year ago
- AWS OFFICIALUpdated a year ago
thank you for your review, where would I make this adjustment?
I'm assuming you have configured the redirect in S3 website setting. There, instead of pointing to https://... change that to point http://... URL. Or did you use other method for redirect like just having an index.html and javascript redirect?