No post body was provided.
Ask HN: Are there any drawbacks to using S3 for website assets?
1–5 of 5 posts
Re: Ask HN: Are there any drawbacks to using S3 for website assets?
#2Re: Ask HN: Are there any drawbacks to using S3 for website assets?
#3It depends on the global reach of your website, but please remember S3 is not a CDN. If you host your files in the US, clients in Europe will see a significant latency, for example. If possible place a CDN in front of your bucket.
Re: Ask HN: Are there any drawbacks to using S3 for website assets?
#4It depends on the global reach of your website, but please remember S3 is not a CDN. If you host your files in the US, clients in Europe will see a significant latency, for example. If possible place a CDN in front of your bucket.
If you use CloudFront (AWS CDN) they don't charge for the bandwidth transfer between S3 to it which is good but here's the drawback, setting up permissions and configuring access in anything but the simplest cases can be quite frustrating and even involve some trial and error in development to test it in my experience. I've had to whitelist http headers in the past that weren't clearly documented as being required to be done.
Re: Ask HN: Are there any drawbacks to using S3 for website assets?
#5What are you trying host? One drawback for websites is it makes deploys more complex as you've got to keep your S3 files and website files in sync. Maybe a website host only with a CDN in front would be enough.