anchor.diff:          fog_connection: *fog_connection
       ```
   
  -1. Replace `YOUR-BUILDPACK-DIRECTORY-PREFIX`, `YOUR-DROPLET-DIRECTORY-PREFIX`, `YOUR-PACKAGE-DIRECTORY-PREFIX`, and `YOUR-RESOURCE-DIRECTORY-PREFIX` with the names of the directories you will be using.
  -   If these aren't specified, Cloud Foundry will supply usable default values.
  -
  -1. You can provide further configuration through the <code>fog_connection</code> hash, which is passed through to the Fog gem.
  -
  -1. The `nfs_mounter` job specifies how to mount a remote NFS server onto a local directory. You will need to configure the `nfs_mounter` job for the `cloud_controller_ng`, `cloud_controller_worker`, and `cloud_controller_clock` instance groups:
  +1. Replace `YOUR-BUILDPACK-DIRECTORY-PREFIX`, `YOUR-DROPLET-DIRECTORY-PREFIX`, `YOUR-PACKAGE-DIRECTORY-PREFIX`, and `YOUR-RESOURCE-DIRECTORY-PREFIX` with the names of the directories you will be using. If you do not specify these, Cloud Foundry will supply usable default values.
  +
  +1. (Optional) Provide other configuration with the `fog_connection` hash, which is passed through to the Fog gem.
  +
  +1. Configure the `nfs_mounter` job for the `cloud_controller_ng`, `cloud_controller_worker`, and `cloud_controller_clock` instance groups. The `nfs_mounter` job specifies how to mount a remote NFS server onto a local directory.
   
       ```
       name: nfs_mounter
         properties:
           nfs_server:
  -          address: NFS_ENDPOINT
  -          share: REMOTE_DIR_TO_MOUNT
  -          share_path: LOCAL_DIR_TO_MOUNT
  +          address: NFS-ENDPOINT
  +          share: REMOTE-DIR-TO-MOUNT
  +          share_path: LOCAL-DIR-TO-MOUNT
             nfsv4: false
         release: capi
      ```
   
  -Sample values:
  -
  -- `NFS_ENDPOINT`: `nfstestserver.service.cf.internal`
  -- `REMOTE_DIR_TO_MOUNT`: `/var/data/exported`
  -- `LOCAL_DIR_TO_MOUNT`: `/var/vcap/nfs`
  +Replace the placeholder text in the example above with the values you want to use. Sample values:
  +
  +- `NFS-ENDPOINT`: `nfstestserver.service.cf.internal`
  +- `REMOTE-DIR-TO-MOUNT`: `/var/data/exported`
  +- `LOCAL-DIR-TO-MOUNT`: `/var/vcap/nfs`
   
   ##<a id="webdav"></a>WebDAV
   
  
positive.code:       }]
      }
      ```
  If you are using the AWS console, an IAM Role is automatically assigned to an IAM Instance Profile with the same name, <code>cloud-controller</code>. If you are not using the AWS console, you must create an IAM Instance Profile with a single assigned IAM Role.
  
  1. In your Cloud Foundry deployment manifest, configure a resource pool to use the <code>cloud-controller</code> IAM Instance Profile:
  
  
negative.code:     ```
      blobstore:
        admin_users:
        - password: WEBDAV-BASIC-AUTH-PASSWORD
          username: WEBDAV-BASIC-AUTH-USER
        port: 8080
        secure_link:
          secret: WEBDAV-SECRET
        tls:
          cert: WEBDAV-CERT
          port: 4443
          private_key: WEBDAV-PRIVATE-KEY
          ca_cert: WEBDAV-CA-CERT-BUNDLE
      cc:
        buildpacks:
          blobstore_type: webdav
          buildpack_directory_key: cc-buildpacks
          webdav_config: &webdav_config
            public_endpoint: WEBDAV-PUBLIC-ENDPOINT
            private_endpoint: WEBDAV-PRIVATE-ENDPOINT
            username: WEBDAV_BASIC-AUTH-USER
            password: WEBDAV_BASIC-AUTH-PASSWORD
            ca_cert: WEBDAV-CA-CERT-BUNDLE
        droplets:
          blobstore_type: webdav
          droplet_directory_key: cc-droplets
  