anchor.diff:  
   su -l -c "cd /var/lib/tomcat/bin && /var/lib/tomcat/bin/updateProperties.sh $DB_PROPS $KB_PROPS" tomcat
   ```
  -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). DB_USER and DB_PASSWORD should be set to the administrator credentials you have chosen for the RDS instance.
  +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 Kill Bill properties that you need to change from the standard defaults.
   
  
positive.code: 
  [1] Setup the Database
  
  The first step is to setup the RDS instance. This process begins with the RDS dashboard, which is distinct from the EC2 dashboard. Open the dashboard, select `Databases` from the left menu, and click the red button at the top right that reads `Create Database`:
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/create-database.png[align=center]
  
  You will be taken to the `Create Database` page. The first choice you will have is between `Standard Create`, which allows you to set a full range of configuration parametera, or `Easy Create`, which sets most of these parameters to defaults. We recommend `Easy Create` in most cases.
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/standard-or-easy.png[align=center]
  
  The next section offers you a choice of several database types. Kill Bill can work with any database type that is `mysql` or `postgres` compatible. For robust production use, Amazon Aurora is probably a good choice. Here we will illustrate the simpler steps setting up a MariaDB database.
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/database-types.png[align=center]
  
  The next choice determines the instance size. We suggest the `Production` option as this will provide the most robust configuration.
  
  image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/instance-sizes.png[align=center]
  
  The last section asks you to:
  
  
negative.code: image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/aws/userdata.png[align=center]
  
  
  [4] Create the 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:
  
  `ssh -i PRIVATE_KEY.pem ubuntu@INSTANCE_IP`
  
  Here PRIVATE_KEY is the pathname where you have stored the private key that was downloaded when you generated your key pair, and INSTANCE_IP is the IPV4 address described earlier. The private key will not work unless its access controls are set to readable by the owner only.
  
  On Windows versions before Windows 10, you may need to download a program called PuTTY to enable `ssh`. On Windows 10 `ssh` is available but may need to be activated through the Settings screen.
  
  The first time you login, you will see a warning message asking if you want to add this host to your list of hosts. You should answer `yes`.
  
  
  Once you are logged in, you can use the `mysql` command to create the two databases `killbill` and `kaui`. The credentials for this command are the same ones you set up for the database and copied to the configuration file. The password will not be echoed when it is typed.
  
  ```
  > mysql -h DB-INSTANCE-NAME -u ADMIN-NAME -p
  Enter Password: 
  mysql> create database killbill;
  mysql> create database kaui;
  mysql> exit
  ```
  The next step is to install the schemas. These can be found at:
  
  * killbill schema: `http://docs.killbill.io/latest/ddl.sql`
  * kaui schema: `https://github.com/killbill/killbill-admin-ui/blob/master/db/ddl.sql`
  
  One easy way to do this is to return to your local computer (type `exit`) and use the `sftp` command. Then upload them to your EC2 instance home directory with the commands:
  
  ```
  sftp -i PRIVATE_KEY.pem ubuntu@INSTANCE_IP
  put killbill.ddl
  put kaui.ddl
  exit
  ```
  
  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
  Enter Password:
  > 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:
  
  ```
  > mysql -h DB-INSTANCE-NAME -u ADMIN-NAME -p
  Enter Password:
  use killbill
  show tables;
  use kaui
  show tables;
  exit
  ```
  
  Each `show tables` command should display a list of table names for the database. 
  
  
  
  [5] Stop and Restart the KillBill Service
  
  IS THIS NECESSARY? IF SO SHOULD IT BE DONE ON ALL INSTANCES?
  
  ```
  > sudo service killbill stop
  