anchor.diff:  exit
   ```
   
  -Once the files are successfully uploaded, login again to your instance using the `ssh' command. You can now install the schemas:
  +Once the files are successfully uploaded, login again to your instance using the `ssh` command. You can now install the schemas:
   
   ```
   > mysql -h DB-INSTANCE-NAME -u ADMIN-NAME -p killbill < killbill.ddl
  
positive.code: 
  The next page will give several configuration options. 
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/single-ami-configuration.png[align=center]
  
  In most cases you should accept the defaults. Then click **Continue to Launch**.
  
  
negative.code: 
  [6] Add the ELB in front of the EC2 instances
  
  The last major task is to setup the Elasic 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*.
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/ELB-select-type.png[align=center]
  
  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*.
  
  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.
  == Configuration
  
  === SSL Certificates
  