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.
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.
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.
edit: refreshing that they highlight baked in ddos protection right up front on their marketing site: https://docs.render.com/ddos-protection
its like 10 minutes of setup tops to host on s3
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