anchor.diff:  Of course, for our own purpose of providing the service, we will also create a very first tenant to invoice our merchants (e.g the Shakti business). That tenant will be called `saas` ('Subscription As A Service'), and the associated admin user will be called *admin_saas*.
   
   
  -Also, for sake of simplicity, we will setup Kill Bill to use a static http://shiro.apache.org/configuration.html[Shiro configuration file] to configure the various admin users/roles. In real life, it would be more practical to rely on LDAP rather that static configuration, which requires restarting Kill Bill when creating new users/roles. The LDAP configuartion is supported by Shiro but we will not describe the steps in that turorial to keep it simple.
  +Also, for sake of simplicity, we will setup Kill Bill to use a static http://shiro.apache.org/configuration.html[Shiro configuration file] to configure the various admin users/roles. In real life, it would be more practical to rely on LDAP rather than static configuration, which requires restarting Kill Bill when creating new users/roles. The LDAP configuration is supported by Shiro but we will not describe the steps in that tutorial to keep it simple.
   
   
   == Kill Bill Multi-tenant Deployment
  
positive.code: In particular, the port 8080 should be publicly available for Kill Bill (in that simple setup with no firewall) and the port 3000 should be publicly available for KAUI. In addition with started our EC2 zone with with a special script that configured and started `dockerd` on the zones.
  Notes:
  
  * The instructions from the http://killbill.io/tutorials/aws[tutorial] have been written after the 0.12.1 release so they will need to be slightly tweaked to change the Kill Bill version, ddl files, ... from 0.12.1 to at least 0.13.5 (The Docker image 0.13.5 has been released).
  * In addition to that, we will need an extra zone to configure the admin UI (KAUI) and create a new database called `kaui` in the RDS database instance.
  
  The deployment will rely on the 2 Docker images:
  
negative.code: * API Secret: `some_secret_for_shakti`
  * Click on the `Create tenant` to also create the tenant in Kill Bill.
  
  At this point, the tenant exists in Kill Bill and is known from KAUI as well.
  
  We can then configure the allowed users. KAUI needs to know who can access which tenant, and this information is kept in the KAUI database.
  It really means that any user known from Kill Bill (shiro.ini) will be able to make API calls against any tenant provided the user specifies the correct tenant `api_key` and `api_secret`, so the security resides behind keeping those keys secret.
  