I did not say he hosted a static site making simple http requests, I said he made several bad architectural design decisions. This is the only real point of reference I have, so I was asking if any one else had similar experiences.
That explains, than. EC2 should be used for dynamic processing. Static data should be in S3 and CloudFront, ideally. Even for dynamic needs, I'd recommend using Lambda, if technically possible.
As the math shows, it's darn cheap for small and mid-sized needs. If you ever get to hundreds of millions or billions of requests/month (or really large files), than it's worth looking at cheaper alternatives to AWS.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I did not say he hosted a static site making simple http requests, I said he made several bad architectural design decisions. This is the only real point of reference I have, so I was asking if any one else had similar experiences.
I don't see how one could make such bad architectural decisions in S3 and CloudFront that would make a regular Joe website hosting cost $hundreds.
He's probably using EC2, renting fancy servers with multi-region high availability, load balancer, etc, perhaps?
He was using EC2 and allowing users to upload images and videos, he did zero compression and simply re-served the content full-size images and videos.
That explains, than. EC2 should be used for dynamic processing. Static data should be in S3 and CloudFront, ideally. Even for dynamic needs, I'd recommend using Lambda, if technically possible.
As the math shows, it's darn cheap for small and mid-sized needs. If you ever get to hundreds of millions or billions of requests/month (or really large files), than it's worth looking at cheaper alternatives to AWS.