Speaking as someone who rolled his own version of this, there were a lot of more complete solutions out there, but they all involved some technology that I felt would cause more pain down the road. Whether it&#x27;s Chef&#x2F;Ansible&#x2F;Puppet which are popular, but seem targeted at mutable infrastructure (one of our explicit goals was immutable infrastructure) or Mesos&#x2F;Kubernetes&#x2F;ECS&#x2F;CoreOS which seem targeted at a larger fleet of instances than we&#x27;re running, there didn&#x27;t seem to be any starting point beyond composing the right set of tools and writing the glue that made sense for us.<p>What we ended up with uses Terraform for provisioning instances, Docker (and a private registry) for distributing our application code, Consul for coordinating everything and HAProxy w&#x2F; consul-template for dynamic routing. There were only two pieces that we had to write. The first (which we may open source, if we&#x27;re given the time to clean it up and generalize it) is a small Go agent that runs on provisioned hosts, figures out its role based on instance meta data, pulls its configuration from Consul and handles deployment, both initial and subsequent when a new version is registered with Consul. The second piece is ensuring that CI generates Docker images as artifacts, pushes them to our private registry and updates Consul to indicate that there&#x27;s new code to deploy.<p>It took us about a week to get this working and it&#x27;s been mostly rock solid for almost a year now. Part of why it&#x27;s been solid is that we understand exactly how every component of it works. The one problem we&#x27;ve had came from not understanding how HAProxy worked (never point HAProxy and an ELB...it will cache the NS resolution and ELBs can change IPs over time). If we&#x27;d tried something off-the-shelf, we&#x27;d have a much shallower understanding and, since it&#x27;s not optimized for our use case, we would have run into many more issues than we&#x27;ve had. On the whole, I highly recommend rolling your own. The code that you will have to write is glue code that&#x27;s really just replacing what would be configuration in something pre-built. I get that it seems imposing to people without devops experience, but between the tools that are available these days and articles like the one we&#x27;re commenting about, it doesn&#x27;t take a guru to get everything working seamlessly. Also, the tools from Hashicorp are fabulous. Use them whenever possible. No disclaimer necessary since I have no affiliation with them beyond using their tools and watching their talks on the subject.