4 ms·
Why would you host a static website using s3? What's wrong with a traditional file system? You already have the load balancer.
by TedDoesntTalk 6y ago
Why would you host a static website using s3? What's wrong with a traditional file system? You already have the load balancer.
- GordonS 6y agoWith block storage (a disk), you are going to need some compute capability to host it. Presumably with S3 you don't need that (I know you can do this with Azure Blob Storage, hosting static content directly; assume it's the same with AWS)
- sokoloff 6y agoIt is the same. S3 alone can host a static website (albeit only over http if you want a custom domain name; you need to add CloudFront [or equivalent] to get https hosting with a valid cert under a custom domain name).
- moooo99 6y agoHosting a static website using S3 can be done dirt-cheap. We were hosting our website on S3 for a while now, with a monthly bill of 1,20€ with CloudFlare CDN in front of our bucket. Another big plus is that you do not have to worry about server administration, load balancers etc.
- ggregoire 6y agoJust curious, why CloudFlare instead of CloudFront?
- benaadams 6y agoI'd assume because CloudFlare doesn't charge anything for bandwidth; so their costs are exceptionally predictable
- abiogenesis 6y agoFor a static website isn't something like Netlify easier (and cheaper, as in free)?
- paulcarroty 6y ago100GB bandwidth/month for free, it's quite small traffic.
- kayoone 6y agowith caching (eg. cloudflare) in front of s3 hosting for static websites, you have almost zero cost hosting.
- davidgerard 6y agobecause it's super cheap and ridiculously easy hardest part is working out how to go fully-public fully-static
- ghaff 6y agoMy website is very small scale. I'm already using S3 to store some other things so hosting the static site on S3 is pretty straightforward. And it costs me literally pennies a month.