Comment by apsurd
1 year ago
https://render.com/ is free for static sites with custom domain support and SSL included. been happy so far!
used to use s3 for the longest time, but aside from costing a nominal fee, it's so unnecessarily complicated in this day and age.
Keep in mind that according to their forum you'll be charged $30/100GB for bandwidth over free allowance of 100GB:
https://community.render.com/t/confused-about-the-free-tier/...
> Exceeding allotted Bandwidth does result in automatic overage charges. $30 for additional 100 GB blocks.
So the same shady pracrice as on Netlify.
wow, thanks for mentioning that, though I'm wondering how this would work, since they didn't ask for any name/billing information at signup...
Just something to keep in mind: this also has about half of additional bandwidth costs (above 100GB) of the reddit post, so in your case you'd be billed for ~$57k or so with similar DDOS. At least they seem to provide monitoring/alerts based on their Security page.
thanks for the heads up, need to do my due diligence here.
edit: refreshing that they highlight baked in ddos protection right up front on their marketing site: https://docs.render.com/ddos-protection
> used to use s3 for the longest time, but aside from costing a nominal fee, it's so unnecessarily complicated in this day and age
its like 10 minutes of setup tops to host on s3
Not for me. It's always configuration voodoo. i've done it dozens of times and i used to think it's normal developer workflow. now i realize I was putting thumbtacks in my eyes for no good reason.
Creating an s3 bucket is easy enough. but you need to add the policy Json config to allow public access, and it has various versions across time and space. the one that works for me is like 15 years old iono. object resource "//*" something or other.
ok so now you have an s3-east-mybucket.com/index.html, ok custom domain that's route 53 yet more configuration vooodoo to point an s3 website enabled bucket blah blah.
wait! need SSL? oops actually that's cloudfront. need a cloudfront config voodo to point to an s3 config voodoo to your hopefully correctly configured route 53.
are you kidding me, 10 mins? You're a wizard. Now i do git push origin main and my sites up on render.com
yes, you need to spend the time to learn about the environment you are hosting your app in and then suddenly it won't seem like "voodoo" as much. you absolutely can set this up in 10 minutes (probably much quicker if you are adept with various infra tooling). theres even wizard dialogs for most of the things you've described right in the AWS UI nowadays.
That depends on what level of knowledge you are based on. The UX of AWS offers even leading experienced admins and developers some surprising stumbling blocks.