Hacker News Reader

This is my go to stack these days for personal projects. (That said, I'm a former AWS dev, so I'm super familiar with these moving parts.)

It's easy to develop for, it's easy to automate deployments, I don't have to worry about keeping anything up to date, and I can just focus on the small amount of code I want to write.

The most expensive thing is the Route 53 configuration at $0.50/month/domain.

View on HN

I love this stack. I recently added AWS SAM to the mix as well so that I can automate deployments. I have always wondered why Route 53 was so expensive relative to the other services. I have a collection of low traffic sites that I run for local businesses and this is always the most expensive part. I guess it's hard to complain about $0.50. But, given I could probably run them all on $5 DO droplet, it ends up costing a little more.

It's my goto stack as well. However, I haven't been able to get both www->root redirect and http->https redirect working. Do you happen to know if it's possible?

www->root should be handled on DNS, therefore Route53. http->https can be done using CloudFront and Lambda@Edge

Reply on news.ycombinator.com