Migrating to static hosting with S3

Experience

February 3, 2020

Last week I finally decided to migrate my personal website from pythonanywhere to an AWS S3 bucket. It is a change I've been wanting to make for a long time but for some reason I could never find time to do it. In this little blog post I'll be sharing what I learnt in the process.

Transferring the domain name to Route53

I figured that if I was moving to AWS then I might go all the way and move my domain name ownership as well. The offcial Route53 docs were a little heavy on the reading side for me, but still useful. I still managed to screw up though, and I ended going offline for about 10 days: the amount of time my old registrar (namecheap) took to transfer the domain.

I had never transferred any domain names to Route53 or any other registrar for that matter, so it was kind of scary at first due to all the e-mail confirmations and codes; they take all this domain ownership very seriously, and I'm glad they do.

Creating the S3 bucket

I was impressed by how easy this was, plus, the small tutorial/doc AWS offers is beyond useful, clear, simple, and straight to the point. It was such a fun experience and I really enjoyed the whole process.

Now, I'll be listing some pros and cons (from my point of view) of migrating to a static website using S3.

Pros

Cons

Final thoughts and future

It was a fun, new experience and I'm glad I made the change. The next step is to use a CloudFront distribution so I can serve my files with https.