[Sgoettschkes]

If you are running on Heroku or Google App Engine, you don't have a server as well. AWS Lambda abstracts the concept of a server even more, but yeah...

I also think the costs are pretty high. Of course I have no idea how much traffic and requests where calculated, so I am just guessing. As cloudfront and S3 do the heavy lifting, a cheap server or two for actual editing of the content should be enough. And they don't need to scale on the same level as there won't be that much changing for customers, so paying more than 10,000$ for that with 100.000 customers seems pretty high.

But I get what the idea behind it was, and it seems to work pretty good. Also nice to have really low costs in the beginning :)

[neogenix]

If you would have the same setup, but with EC2 instead of lambda, you would still have the same CloudFront pricing, so you should compare the $410 lambda costs for 100.000 customers with the costs of some EC2 servers plus ELB. Of course, then, you will miss the benefits of 1. no server-maintenance, 2. no down-time or scaling issues and 3. initial startup costs - without customers.