anchor.diff:  
   
   ==== Summary
  -This is one of the easiest ways to get to AWS, but there are more things
  -to cover, such as how to integrate Elastic Beanstalk into any CI / CD tool, use the
  -Elastic Beanstalk maven plugin instead of the CLI, and others. There is a
  -https://exampledriven.wordpress.com/2017/01/09/spring-boot-aws-elastic-beanstalk-example/[blog post]
  -covering these topics more in detail.
  +This is one of the easiest ways to get to AWS, but there are more things to cover, such as
  +how to integrate Elastic Beanstalk into any CI / CD tool, use the Elastic Beanstalk Maven
  +plugin instead of the CLI, and others. There is a
  +https://exampledriven.wordpress.com/2017/01/09/spring-boot-aws-elastic-beanstalk-example/
  +[blog post] covering these topics more in detail.
   
   
   
  
positive.code: |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`
  |The arguments to pass to the program (the Spring Boot app).
  
negative.code: 
  
  ==== 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 that produce a war file. There is no any
  special configuration required. You need only follow the official guide.
  
  
  
  