> It’s nice to see that AWS’ supporting services are ran pretty much the same way as how outside companies will run their workload within AWS.<p>Reminds me that Heroku does (or at least did) run their slug compiler Vulcan <i>as a Heroku app</i>—when you push your app to Heroku, you're simply relying on another Heroku dyno to do the work of building yours. They don't need to do anything special to those dynos, or give them any special privileges; they're already isolated enough to serve as build-task runners, and their only output is to push something from their filesystem to S3, which they can do completely obliviously to Heroku's architecture.<p>I believe the recently-rebuilt Heroku dashboard might <i>also</i> be a Heroku app, but I'm not as sure on that one.