anchor.diff:  [source, bash]
   .Kill Bill Docker Sequence:
   ----
  -killbill_ec2> sudo docker pull killbill/killbill:0.13.5
  +killbill_ec2> sudo docker pull killbill/killbill:0.13.7
   killbill_ec2> docker run -tid \
   --name killbillsaas \
   -p 8080:8080 \
  --v /home/ubuntu/killbil/etc/stripe.yml:/etc/killbill/stripe.yml \
  --v /home/ubuntu/killbil/etc/shiro.ini:/etc/killbill/shiro.ini \
  +-v /home/ubuntu/killbill/etc/stripe.yml:/etc/killbill/stripe.yml \
  +-v /home/ubuntu/killbill/etc/shiro.ini:/etc/killbill/shiro.ini \
   -e KILLBILL_PLUGIN_STRIPE=1 \
   -e KILLBILL_PLUGIN_ANALYTICS=1 \
   -e KILLBILL_CONFIG_DAO_URL=jdbc:mysql://RDS_URL/killbill \
  
positive.code: 
  === Configuration Files
  
  Kill Bill and its plugins will rely on a set of configuration files and those will be first uploaded on the docker host (that is, the EC2 instance where the docker container runs), and then we will use the docker `mapping` mechanism to make those configuration files visible into the docker data volume. The configuration files will need to be uploaded under `/home/ubuntu/killbil/etc/<config>`, and then that directory will be mapped to the `/etc/killbill/<config>` by specifying the option `-v` when we `run` the container.
  
  
  The following configurations files will be needed:
  
negative.code: -e KAUI_CONFIG_DAO_USER=RDS_USER \
  -e KAUI_CONFIG_DAO_PASSWORD=RDS_PWD \
  -e KAUI_URL=http://KILLBILL_IP:8080 \
  killbill/kaui:0.2.0
  kaui_ec2> sudo docker logs -f kaui-saas
  ----
  
  