anchor.diff:  
   [4] Create the databases
   
  -Kill Bill requires two databases, with the names killbill and kaui. We provide predefined schemas for these databases.
  +Kill Bill requires two databases, with the names `killbill` and `kaui`. We provide predefined schemas for these databases.
   
   First you will need to login to *one* of your instances and create the databases. To login, use the secure shell command:
   
  
positive.code: Click on the *Create* button in the Application Load Balancer box. This will bring up the page titled *Step 1: Configure Load Balancer*:
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/ELB-basic-configuration.png[align=center]
  
  On this page you need to do three things:
  
  1. Assign a name to you load balancer
  2. Select a protocol for your listener (normally HTTPS to use SSL/TLS)
  3. Scroll to the bottom and select at least *two* availability zones. Normally it does not matter which ones.
  
  Then choose *Next: Configure Security Settings*. You will now see a page titled *Step 2: Configure Security Settings*.
  
negative.code: 
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/multitier-connectivity-and-security.png[align=center]
  
  Lastly, on the `Connectivity and Security` panel, locate and click on the link for the default VPC security group. You will need to add an inbound security rule, because the database by default does not allow external access. In the panel for this group, click on `Inbound Rules` and select `Edit Inbound Rules`. Next click on `Add rule`. In the `Type` column select `MYSQL/Aurora`. The port will be set to 3306 automatically. In the `Source` column, click on the search icon and select `0.0.0.0/0`. Finally, click on `Save Rules` in the bottom right. Your database is ready to go.
  
  [2] Edit the configuration script
  
  