anchor.diff:  TIP: If your application fails to start, check the log file written to
   `/var/log/<appname>.log` for errors.
   
  -You can also flag the application to start automatically using your standard operating
  -system tools. For example, on Debian:
  +You can also flag the application to start automatically by using your standard operating
  +system tools. For example, on Debian, you could use the following command:
   
   [indent=0,subs="verbatim,quotes,attributes"]
   ----
  
positive.code: * AWS Cloud Formation
  * AWS Container Registry
  
  Each has different features and pricing model, here we will describe only the simplest
  option : AWS Elastic Beanstalk.
  
  
  
  ==== AWS Elastic Beanstalk
  As described in the official http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_Java.html[Elastic
  Beanstalk Java guide], there are two main options to deploy a Java application; You can
  either use the "`Tomcat Platform`" or the "`Java SE platform`".
  
  
  
  ===== Using the Tomcat platform
  This option applies to Spring Boot projects producing a war file. There is no any special
  configuration required, just follow the official guide.
  
  
  
  ===== Using the Java SE platform
  This option applies to Spring Boot projects producing a jar file and running an embedded
  web container. Elastic Beanstalk environments run an nginx instance on port 80 to proxy
  the actual application, running on port 5000. To configure it, add the following to your
  `application.properties`:
  
  [indent=0]
  ----
  
negative.code: |Variable |Description
  
  |`MODE`
  |The "`mode`" of operation. The default depends on the way the jar was built but is
   usually `auto` (meaning it tries to guess if it is an init script by checking if it
   is a symlink in a directory called `init.d`). You can explicitly set it to `service` so
   that the `stop\|start\|status\|restart` commands work or to `run` if you want to
   run the script in the foreground.
  
  |`USE_START_STOP_DAEMON`
  |Whether the `start-stop-daemon` command, when it's available, should be used to control
   the process. Defaults to `true`.
  
  |`PID_FOLDER`
  |The root name of the pid folder (`/var/run` by default).
  
  |`LOG_FOLDER`
  |The name of the folder in which to put log files (`/var/log` by default).
  
  |`CONF_FOLDER`
  |The name of the folder from which to read .conf files (same folder as jar-file by
   default).
  
  |`LOG_FILENAME`
  |The name of the log file in the `LOG_FOLDER` (`<appname>.log` by default).
  
  |`APP_NAME`
  |The name of the app. If the jar is run from a symlink, the script guesses the app name
   If it is not a symlink or you want to explicitly set the app name, this can be
   useful.
  
  |`RUN_ARGS`
  