anchor.diff:  
   The final page gives you a chance to review. If everything seems OK, read and check any warnings at the bottom, then click *Create Stack*. you are off!
   
  -image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/img/aws/cf-creating.png[align=center]
  +image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/cf-creating.png[align=center]
   
   If there are any errors, you will see a message and the Create will not begin. You will need to go back and fix the errors. Common errors may include using an invalid password form (which may gove a misleading message), or not choosing subnets in at least two availability zones.
   
  
positive.code: 
  If you don't have SSL certificates in ACM nor IAM, you can import a new one right away on this page.
  
  Tip: you can upload a self-signed certificate:
  
  ```
  openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout privateKey.key -out certificate.crt
  
negative.code:   * RDS Cluster failed to come up
    * ...
  
  Make sure to check the discussion above to ensure you have setup a valid VPC with valid subnets. Fow AWS specific issues, please refer to the https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html[AWS troubleshooting documentation]
      
  **Service Unavailable**
  
  We suggest to check the following:
  
  1. Are there any issues reported in the CFN logs?
  2. Is the database up and running and accessible from the Kill Bill/Kaui EC2 instances?
  3. Is the database schema correctly installed?
  4. Is the Kill Bill/Kaui server correctly started and listening on port 8080?
  5. Are the Kill Bill/Kaui servers accessible from the LB, respectively on port 80 and 9090?
  6. Are there any errors or stack traces in our logs?
  
  === Practical Tips
  
  