anchor.diff:  Take a look at our http://docs.killbill.io/latest/getting_started.html#_using_kill_bill_with_kaui[Getting Started] guide for an introduction to Kaui.
   
   
  -=== Multi Nodes Deployments
  +=== Multi-Tier Deployments
   
   For production deployments, allocating a separate RDS database instance and allowing multiple nodes to handle traffic behind a load balancer is the recommended option. In this model, we rely on AWS ELB to correctly spread the traffic among the various nodes, and also to route traffic to either  Kill Server or KAUI based on the incoming port. Note that such deployment option requires a bit more setup and so we also provide an (easier) way to deploy using https://docs.killbill.io/latest//aws-cf.html[CloudFormation templates]. However, the benefits of this option is that it provides more control in the deployment.
   
  
positive.code: ```
  
  [5] Add the ELB in front of the EC2 instances
  
  TODO
  
  
  == Configuration
  
negative.code: 
  == Overview
  
  Single AMI deployments are a way to deploy the Kill Bill stack, that is both Kill Bill server and KAUI, the administrative UI, in the same EC2 instance. We provide a `Single-Tier` option that is suitable for testing and experiments, and a `Multi-Tier` option for production deployments.
  
  
  === Single-Tier Deployments
  
  In order to get started as quickly as possible we offer an AMI that also bundles the mysql database as part of the same image. This makes it very easy to get started, as this only requires the click of a button. It is perfect for test environments but we don't recommend it for production deployments.
  
  After launching the AMI you should have a setup that looks like the following:
  
  