anchor.diff:  
       <pre class='terminal'>
       $ bosh micro deploy ami-03223a6a
  -    Deploying new micro BOSH instance ~/workspace/my-deployments/micro_bosh.yml     to 'https://54.86.66.111:25555' (type 'yes' to continue): yes
  +    Deploying new micro BOSH instance ~/workspace/my-deployments/micro_bosh.yml to 'https://54.86.66.111:25555' (type 'yes' to continue): yes
         Started deploy micro bosh
         ...
         Done deploy micro bosh
  
positive.code: 
  ## <a id="troubleshooting"></a>Basic Troubleshooting ##
  
  If the deployment failed, run `bosh micro delete`, then deploy again.
  
  If you see error messages that refer to your `access key signature`, check the
  accuracy of the ACCESS-KEY-ID and SECRET-ACCESS-KEY in the deployment manifest.
  
  If you see other error messages:
  
  * Check your `micro_bosh.yml` for errors.
  * Review your AWS configuration to verify you did not miss any steps.
negative.code:   architecture: x86_64
    root_device_name: /dev/sda1
    ami:
      us-east-1: ami-03223a6a  # This is the Amazon Machine Image (AMI) identifier
  </pre>
  
  ## <a id="deploy"></a>Step 4: Deploy MicroBOSH ##
  
  1. Use `bosh micro deployment PATH-TO-micro_bosh.yml` to set MicroBOSH to use your manifest file.
  
      In the following example, `micro_bosh.yml` is located in `~/workspace/my-deployment`:
  
      <pre class='terminal'>
      $ bosh micro deployment ~/workspace/my-deployment/micro\_bosh.yml
  