anchor.diff:  ```
   First, you need to edit the database properties. DB_SERVER should be set to the full name of the DB instance, as given in the `Connectivity and Security` panel (see above). The port number 3306 is required. DB_USER and DB_PASSWORD should be set to the administrator credentials you have chosen for the RDS instance.
   
  -Second, you may optionally edit any https://docs.killbill.io/latest/userguide_configuration.html [Kill Bill properties] that you need to change from the standard defaults.
  +Second, you may optionally edit any https://docs.killbill.io/latest/userguide_configuration.html[Kill Bill properties] that you need to change from the standard defaults.
   
   === Launch the EC2 Instances
   
  
positive.code: 
  On this page you need to do three things:
  
  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.
  
  
  
  
negative.code: 
  === 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. You will actually need to deploy two separate load balancers, one for access to KAUI, and one for the KB server. We will describe the procedure for one ELB, and you will need to repeat this for each one.
  
  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.
  
  