anchor.diff:      ephemeral_disk:
         size: 512000
         type: gp2
  -```
  -
  -While the above properties are always the same,
  -the properties below will need
  -to be figured out from your existing manifests.
  -(Note that the below continues
  -immediately from where the above left off,
  -so it starts in the `vm_extensions` section
  -of the cloud config.)
  -
  -```yaml
   - name: cf-router-network-properties
     cloud_properties:
       elbs:
  -    - FIGURE-THIS-OUT
  -    security_groups:
  -    - FIGURE-THIS-OUT
  -    - FIGURE-THIS-OUT
  +    - ELB-NAME-FROM-ROUTER-RESOURCE-POOL
   - name: diego-ssh-proxy-network-properties
     cloud_properties:
       elbs:
  -    - FIGURE-THIS-OUT
  -    security_groups:
  -    - FIGURE-THIS-OUT
  -    - FIGURE-THIS-OUT
  +    - ELB-NAME-FROM-DIEGO-MANIFEST-ACCESS-RESOURCE-POOL
  +
   azs:
   - name: z1
  -  cloud_properties: {availability_zone: FIGURE-THIS-OUT}
  +  cloud_properties:
  +    availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z1-RESOURCE-POOL
   - name: z1
  -  cloud_properties: {availability_zone: FIGURE-THIS-OUT}
  +  cloud_properties:
  +    availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z2-RESOURCE-POOL
   - name: z3
  -  cloud_properties: {availability_zone: FIGURE-THIS-OUT}
  +  cloud_properties:
  +    availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z3-RESOURCE-POOL
   
   networks:
   - name: default
  
positive.code:   - az: z1
      cloud_properties:
        security_groups:
        - FIGURE-THIS-OUT
        subnet: FIGURE-THIS-OUT
      gateway: 10.0.16.1
      range: 10.0.16.0/20
      reserved:
      - 10.0.16.2-10.0.16.3
      - 10.0.31.255
      static:
      - 10.0.31.190-10.0.31.254
    - az: z2
      cloud_properties:
        security_groups:
        - FIGURE-THIS-OUT
        subnet: FIGURE-THIS-OUT
      gateway: 10.0.32.1
      range: 10.0.32.0/20
      reserved:
      - 10.0.32.2-10.0.32.3
      - 10.0.47.255
      static:
      - 10.0.47.190-10.0.47.254
    - az: z3
      cloud_properties:
        security_groups:
        - FIGURE-THIS-OUT
        subnet: FIGURE-THIS-OUT
      gateway: 10.0.48.1
      range: 10.0.48.0/20
      reserved:
      - 10.0.48.2-10.0.48.3
      - 10.0.63.255
      static:
      - 10.0.63.190-10.0.63.254
    type: manual
  ```
  
  Here are some important takeaways from this example:
  
  * You must include compilation configuration.
  * You must include at least the VM types.
    and extensions from the example.
  * You must have a network called `default`.
  * You must configure the Availability Zones
    `z1`, `z2`, and `z3`.
  
  Once you've written a suitable cloud config,
  upload it to the BOSH Director:
  
negative.code:   value: 12
  ```
  
  ## <a id='cloud-config'></a> Step 4: Write and Upload Cloud Config
  `cf-deployment` requires that a [cloud config](https://bosh.io/docs/cloud-config.html)
  providing certain properties be available on the BOSH Director.
  
  You must write such a cloud config,
  drawing its values from your current CF and Diego manifests.
  
  The following example can be used
  as the basis for your cloud config:
  
  ```yaml
  