Unfortunately my client is closely coupled to a venture I'm doing on the side. I won't be open sourcing it. If it's just static web pages you need without mutable data, you can do that directly off Amazon S3. There are lots of blogs and open source projects for that:

http://stout.is/

https://sysadmincasts.com/episodes/48-static-sites-using-aws...

If you sprinkle in AWS SDK for Javascript in the browser, you can handle mutations directly into various persistence services without needing EC2. I'm still very early in my exploration of this approach so I was hoping to see some case study myself. If there's no direct way to invoke lambda from a service event (e.g., an RDS mutation), you could invoke it from the client after returning from the RDS request.

I’m almost at a point where I think static websites are a solved problem. Compile your website with whatever (Jekyll, Octopress, etc), save it to GitHub for good measure, and push it to an S3 bucket with CloudFront og CloudFlare in front of it.

You can always find somewhere else to host your stuff, but I’d say I’m pretty happy with a deployment workflow that’s basically

    bundle exec jekyll build
    s3_website push

Aaand you’re done. And you can even roll those two into a pre- or post-commit hook.

Checkout Jekyll, I’m having a great time building https://github.com/anishavasandani/suchbrooklyn.com

I wrote parched and parched-tasks-web app specifically for this.