anchor.diff:  deployment.
   
   Example stub file:
  -
  -<%= yield_for_code_snippet from: 'cloudfoundry/docs-deploying-cf', at: 'cf-stub-aws' %>
  -
  -Replace the placeholder values in your stub files with data appropriate to your deployment.
  -
  -* `DIRECTOR-UUID`: The BOSH Director UUID. Run `bosh status` to view the BOSH Director UUID.
  -
  -- `zone_1` and `zone_2`: The `BOSH_VPC_PRIMARY_AZ` and `BOSH_VPC_SECONDARY_AZ` that you specified in the `bosh_environment` file above.
  -
  -* `AWS_ACCESS_KEY-ID` and `AWS_SECRET_ACCESS`: Your AWS Access Key ID and Secret
  -Key. You can use the keys that you specified in the `bosh_environment` file,
  -or generate new ones.
   
   <pre class="terminal">
   ---
  
positive.code: ---
  
  <table style="width: 60%;"><tr><td>
  <strong>WARNING</strong>: The command `bosh aws destroy` destroys everything in your AWS account, including all S3 buckets and all instances. Do not use this command unless you want to lose **everything** in your AWS account, including objects and files unrelated to your Cloud Foundry deployment.
  </td></tr></table>
  
  Cloud Foundry tools simplify the process of deploying a Cloud Foundry instance
  
negative.code:     skip_cert_verify: false
  </pre>
  
  Replace placeholders with the appropriate data:
  
  - `PLACEHOLDER-DIRECTOR-UUID` - the BOSH director UUID. You can get it by running `bundle exec bosh status`.
  
  - `PLACEHOLDER-ACCESS-KEY-ID` and `PLACEHOLDER-SECRET-KEY` - AWS access key id and secret key. You can use the same ones as you used in the `bosh_environment` file above, or generate new ones.
  
  - `PLACEHOLDER-AWS-AVAILABILITY-ZONE` and `PLACEHOLDER-AWS-AVAILABILITY-ZONE2` - `BOSH_VPC_PRIMARY_AZ` and `BOSH_VPC_SECONDARY_AZ` from the `bosh_environment` file above.
  
  - `PLACEHOLDER-SUBNET-FOR-AZ1` and `PLACEHOLDER-SUBNET-FOR-AZ2` - Look in `~/deployments/cf-example/aws_vpc_receipt.yml` (this file was generated when you ran `bosh aws create`).  They are under 'subnets' 'cf1' and 'cf2'.
  
  