anchor.diff:  
   Your application should now be up and running on AWS.
   
  -There's a blog on https://boxfuse.com/blog/spring-boot-ec2.html[deploying Spring Boot apps
  -on EC2] as well as https://boxfuse.com/docs/payloads/springboot.html[documentation
  -for the Boxfuse Spring Boot integration] on their website that will get you started with a
  -Maven build to run the app.
  +See the blog post on https://boxfuse.com/blog/spring-boot-ec2.html[deploying Spring Boot
  +apps on EC2] as well as the
  +https://boxfuse.com/docs/payloads/springboot.html[documentation for the Boxfuse Spring
  +Boot integration] to get started with a Maven build to run the app.
   
   
   
   [[cloud-deployment-gae]]
   === Google Cloud
  -Google Cloud has several options that could be used to launch Spring Boot applications.
  +Google Cloud has several options that can be used to launch Spring Boot applications.
   The easiest to get started with is probably App Engine, but you could also find ways to
  -run Spring Boot in a container with Container Engine, or on a virtual machine using
  +run Spring Boot in a container with Container Engine or on a virtual machine with
   Compute Engine.
   
  -To run in App Engine you can create a project in the UI first, which sets up a unique
  -identifier for you and also HTTP routes. Add a Java app to the project and leave it empty,
  -then use the https://cloud.google.com/sdk/downloads[Google Cloud SDK] to push your
  -Spring Boot app into that slot from the command line or CI build.
  +To run in App Engine, you can create a project in the UI first, which sets up a unique
  +identifier for you and also sets up HTTP routes. Add a Java app to the project and leave
  +it empty and then use the https://cloud.google.com/sdk/downloads[Google Cloud SDK] to
  +push your Spring Boot app into that slot from the command line or CI build.
   
   App Engine needs you to create an `app.yaml` file to describe the resources your app
  -requires. Normally you put this in `src/main/appengine`, and it looks something like this:
  +requires. Normally you put this file in `src/main/appengine`, and it should resemble the
  +following file:
   
   [source,yaml,indent=0]
   ----
  
positive.code: ----
  
  Once Cloud Foundry acknowledges that your application has been deployed, you should be
  able to hit the application at the URI given, in this case
  `\http://acloudyspringtime.cfapps.io/`.
  
  
  
  [[cloud-deployment-cloud-foundry-services]]
  ==== Binding to services
  By default, metadata about the running application as well as service connection
  information is exposed to the application as environment variables (for example:
  `$VCAP_SERVICES`). This architecture decision is due to Cloud Foundry's polyglot
  (any language and platform can be supported as a buildpack) nature; process-scoped
  environment variables are language agnostic.
  
  Environment variables don't always make for the easiest API so Spring Boot automatically
  extracts them and flattens the data into properties that can be accessed through
  Spring's `Environment` abstraction:
  
  [source,java,indent=0]
  ----
  
negative.code: 
  
  [[deployment-script-customization]]
  ==== Customizing the Startup Script
  The default embedded startup script written by the Maven or Gradle plugin can be
  customized in a number of ways. For most people, using the default script along with
  a few customizations is usually enough. If you find you cannot customize something that
  you need to, you can always use the `embeddedLaunchScript` option to write your own
  file entirely.
  
  
  
  [[deployment-script-customization-when-it-written]]
  ===== Customizing the Start Script when It Is Written
  It often makes sense to customize elements of the start script as it is written into the
  jar file. For example, init.d scripts can provide a "`description`". Since you know
  the description up front (and it need not change), you may as well provide it when the
  jar is generated.
  
  To customize written elements, use the `embeddedLaunchScriptProperties` option of the
  Spring Boot Maven or Gradle plugins.
  