anchor.diff:  The Kill Bill/KAUI server logs are located under `/var/lib/tomcat/logs/`, with the main 2 interesting logs being:
   * `killbill.out`: All Kill Bill server logs, configured as `INFO` by default
   * `kaui.out`: All KAUI server logs, configured as `INFO` by default
  -* `localhost_access_log...`: Access requests to the severs
  +* `localhost_access_log...`: Access requests to the servers
   
   The configuration of the logging (log rotation, log level, ...) can be found in `/var/lib/killbill/config/logback.xml`
  +
  +If you update the `logback.xml` (or any configuration file) you will need to restart the service. In order to restart the service, you can run as `root` the following command:
  +
  +```
  +# Restart  killbill server instance
  +> service killbill restart
  +# Restart  kaui server instance
  +> service kaui restart
  +```
   
   **Access to the Database**
   
  
positive.code: **AWS Errors**
  
  Typical Issues are:
    * Insufficient IAM Permissions
    * Limit Exceeded
    * Security Group Does Not Exist in VPC
    * RDS Cluster failed to come up
    * ...
  
  Make sure to check our `Pre-requisites` section to ensure you have setup a valid VPC with valid subnets. Fow AWS specific issues, please refer to the https://docs.amazonaws.cn/en_us/AWSCloudFormation/latest/UserGuide/troubleshooting.html[AWS troubleshooting documentation]
      
  **Service Unavailable**
  
  
negative.code: RDS cluster, so be patient...
  
  
  Let's start with the https://console.aws.amazon.com/cloudformation[CloudFormation console]: The stack will have a status which will be `CREATE_IN_PROGRESS` for the duration of the initialization, and will then either transition to `CREATE_COMPLETE` or `CREATE_FAILED`. In case of `CREATE_FAILED`, try to locate from the `Resources` tab which resource fail to initialize properly.
  
  ==== Possible Issues
  
  