anchor.diff:  
   
   [[cloud-deployment]]
  -== Deploying to the cloud
  +== Deploying to the Cloud
   Spring Boot's executable jars are ready-made for most popular cloud PaaS
  -(platform-as-a-service) providers. These providers tend to require that you
  -"`bring your own container`"; they manage application processes (not Java applications
  +(Platform-as-a-Service) providers. These providers tend to require that you
  +"`bring your own container`". They manage application processes (not Java applications
   specifically), so they need some intermediary layer that adapts _your_ application to the
   _cloud's_ notion of a running process.
   
  
positive.code: 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:
  
  [indent=0,subs="verbatim,quotes,attributes"]
  ----
  
negative.code: 	deploy:
  		artifact: target/demo-0.0.1-SNAPSHOT.jar
  ----
  ====
  
  [TIP]
  .Reduce costs by setting the environment type
  ====
  By default an Elastic Beanstalk environment is load balanced. The load balancer has a
  significant cost. To avoid that cost, set the environment type to "`Single instance`", as
  described in
  http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-create-wizard.html#environments-create-wizard-capacity[the Amazon documentation].
  You can also create single instance environments by using the CLI and the
  following command:
  
  [indent=0]
  ----
  	eb create -s
  ----
  ====
  
  
  ==== 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.
  
  
  