Getting a blog running with Jekyll, GitHub Actions, S3, and CloudFront

Last year, my internal M.2 SSD drive stopped working. I had experienced disconnection problems over the last 2 years; however, last year, it just refused to turn on. It was also encrypted with BitLocker. I took it to a repair shop that claimed they could perform data recovery. However, after waiting for a couple of days, they informed me that...

If you have followed my Getting a blog running with Jekyll, GitHub Actions, AWS S3, and CloudFront post, among other things you will see an issue where if you manually go to the 404.html page, CloudFront will happily serve you the 404.html page with 200 OK status code. This not only is wrong, but also hurts SEO. I don’t care much about SEO...

I am scared of using AWS. In AWS, you can’t easily put a hard cap on the money that you will spend, meaning if you are the target of a DDoS attack or if something goes wrong, you might be overcharged massively. For me, this means that if my CloudFront distributions are under a DDoS attack, I might get a budget notification in my email, but...