anchor.diff:  	---
   	```
   
  -#### IaaS Settings Stub
  -
  -<p class="note"><strong>Note</strong>: This is an AWS specific IaaS Settings Stub. If deploying on another IaaS use the templates available with in each github release respository under the `templates` folder and fill in with the appropriate fields needed by BOSH.
  -
  -Create an `iaas.yml` stub which will be specific to your IaaS. Replace each of the below parameters in the stub:
  -
  -`<--PUBLIC-BROKER-IP-->` --> Pre-Allocated AWS Elastic IP
  -`<--SECURITY-GROUP-->` --> Security Group where the NFS Broker will be created. Ensure this security group has access to the security group your CF is deployed in.
  -`<--SUBNET-->` --> Subnet where the NFS Broker will be created. Ensure this subnet has access to the subnet your CF is deployed in.
  -`<--DNS-->` --> DNS IP address.
  -`<--GATEWAY-->` --> Gateway address.
  -`<--SUBNET-RANGE-->` --> CIDR range of the subnet where the NFS Broker will be created.
  -`<--RESERVED-IPs-->` --> Array of IPs that BOSH will not use for the NFS Broker. `E.G.: 10.10.200.0 - 10.10.200.10`
  -`<--STATIC-IPs-->` --> Array of IPs that BOSH can use for the NFS Broker. `E.G.: 10.10.200.10 - 10.10.200.100`
  +#### Create the IaaS Settings Stub
  +
  +<p class="note"><strong>Note</strong>: This is an AWS specific IaaS Settings Stub. If you want to deploy on another IaaS, use the templates available in the <code>templates</code> directory of each volume services release respository.</p>
  +
  +1. Create an `iaas.yml` stub to for IaaS-specific settings by copying the template below:
   
   	```
   	 ---
  
positive.code: 1. Deploy Diego:
  	<pre class="terminal"> $ bosh -d diego.yml deploy</pre>
  
  ###<a id="stubs"></a>Step 3: Create NFS Broker VM - Create Stub Files
  
  In order to create a NFS Service Broker we need to combine pieces of information into a single BOSH manifest that we will deploy. We will put these pieces into stubs and then utilize a script to combine them.
  
  #### Cloud Foundry Stub
  1. Run the following command to list the VMs deployed by your BOSH director:
  	<pre class="terminal">$ bosh vms </pre>
  	* Examine the output for the CF Nats VM labeled `nats_*` and note the corresponding `deployment name` for use in the next step.
  1. Run the following command using the `deployment name` from the last step to download your CF deployment manifest:
    <pre class="terminal"> $ bosh download manifest YOUR-CF-DEPLOYMENT-NAME > cf.yml</pre>
  
  #### Director Stub
  
  1. Run the following command to determine the UUID of your BOSH director:
  	<pre class="terminal"> $ bosh status --uuid</pre>
  
negative.code:      - name: nfsbroker
         networks:
         - name: public
           static_ips: [PUBLIC-BROKER-IP]
  
       networks:
       - name: nfsvolume-subnet
         subnets:
         - cloud_properties:
             security_groups:
             - SECURITY-GROUP
             subnet: SUBNET
           dns:
           - DNS
           gateway: GATEWAY
           range: SUBNET-RANGE
           reserved:
           - RESERVED-IPs
           static:
           - STATIC-IPs
  
       resource_pools:
         - name: medium
  