Properly redirecting is something that is easy to say (or request in a ticket) but not always easy to do. It just so happens that its really important for proper site behavior, particularly if you are concerned with SEO.
Here’s how you 301 redirect a site with AWS S3 in the simplest manner possible.
Sal January 19th, 2020
Posted In: AWS
Amazon Web Services is an intimidating thing. After all, some of the largest, most active websites in the world are hosted there. But that doesn’t mean hosting a website there needs to be difficult. In fact, as AWS has matured over time and now it’s at the point where anyone with a minimum level of technical understanding can host a site using AWS.
Sal September 16th, 2019
Posted In: AWS
Tags: Amazon S3, AWS, Hosting, Route 53, Static Website
So you have an Amazon S3 hosted site with CloudFront caching in front of it? Nice work — it’s an affordable and highly scalable solution. One downside with this is that the cache, which helps makes your site so fast and cheap to run, is designed to hold on to files, possibly serving an old version to visitors.
That’s normally not a problem (it’s literally the point of a cache), but if you are making a lot of changes to the site and you want visitors to see them as soon as possible, then you will need to invalidate the cache and tell CloudFront to serve the most recent files.
Here is how you can do that…
Sal August 6th, 2018
Posted In: AWS
Tags: Amazon S3, Cache Invalidation, CloudFront, TTL
In my previous article about hosting a static website on S3, I realize that I may have rushed past the section on DNS. The AWS Static Site Quickstart tool does most of what you need, but upon further review, I can say that it doesn’t do everything and it doesn’t do DNS particularly well. So let’s revisit Route 53 and run through some of what I’ve managed to piece together.
Sal December 18th, 2017
Posted In: AWS
Tags: Amazon S3, DNS, Hosted Zone, Hosting, Static Website