anchor.diff:  
   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.
  +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]
   
  
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: 
  1. Assign a name to you load balancer
  2. Select a protocol for your listener. For our first example we will assume this will be HTTP. However to ensure a secure connection, we recommend using HTTPS as discussed below.
  3. Scroll to the bottom and select at least *two* availability zones. *IMPORTANT: You must select all of the zones that your EC2 instances are contained in. Otherwise, the load balancer will be unable to connect to these instances.*
  
  Then choose *Next: Configure Security Settings*. You will now see a page titled *Step 2: Configure Security Settings*.
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/ELB-configure-security.png[align=center]
  
  If you have selected the HTTPS protocol, you will now be required to create or provide an X.509 SSL Certificate. There are many ways to do this. Some are discussed below. If you are using HTTP, you will see a warning message. Ignore the message and choosed *Next: Configure Security Groups*. This will take you to a page titled *Step 3: Configure Security Groups.* 
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/ELB-configure-security-groups.png[align=center]
  
  This page will show you the existing security groups and offer the choice to choose an existing group or create a new one. We advise you to create a new group at this time. The new security group should have inbound rules enabling inputs for KAUI and Kill Bill as follows: 
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/ELB-security-group.png[align=center]
  
  You will use the same security group for both load balancers.
  
  
  
  