anchor.diff:  > mysql -h DB-INSTANCE-NAME -u ADMIN-NAME -p kaui < kaui.ddl
   Enter Password:
   ```
  -To ensure that the databases are setup correctly, login to mysql again, then try the SHOW TABLES command:
  +To ensure that the databases are setup correctly, login to `mysql` again, then try the SHOW TABLES command:
   
   ```
   > mysql -h DB-INSTANCE-NAME -u ADMIN-NAME -p
  
positive.code: 
  
  
  [5] Stop and Restart the KillBill Service
  
  
  ```
  > sudo service killbill stop
  # Optionally clean existing logs
  > rm /var/lib/tomcat/logs/*
  > sudo service killbill start
  ```
  
  [6] Add the ELB in front of the EC2 instances
  
  The last major task is to setup the Elastic Load Balancer in front of the EC2 instances. To begin, from the EC2 dashboard scroll down the left-hand menu and select *Load Balancing / Load Balancers*. Then click the  *Create Load Balancer* button at the upper left.
  
  You will be given a choice of several load balancer types. The type we will use is *Application Load Balancer*.
  
  
negative.code: 
  This display shows that your database is starting. After a few minutes, the status will change to `Available` (You may need to reload the page to see this). At this time you can click on the database name to get more information, including the full name of the instance.
  
  On the page that appears you should see a panel named `Connectivity and Security`. The left side of this panel shows the full name of the endpoint, which you will need shortly, and the port number, which is normally 3306.
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/multitier-connectivity-and-security.png[align=center]
  
  