anchor.diff:  
   Before you deploy BOSH (including MicroBOSH), make sure that your IaaS is properly set up as described below.
   
  -## <a id="hardware"></a> Hardware ##
  +## <a id="hardware"></a> Choosing Suitable Hardware ##
   
   Whichever IaaS you use, your need to choose hardware that adequately supports the _describe characteristics of BOSH_.
   
  
positive.code:   <tr><td>TCP</td><td>25777</td><td>25777</td><td>0.0.0.0/0 (CIDR)</td><td>BOSH Registry</td></tr>
    </table>
  
  
  ### <a id='vsphere'></a> vSphere ###
  
  _describe multiple network configuration for vSphere_
  
  ## <a id="network"></a> Networking and Services ##
  
  In this section we describe remaining IaaS-specific setup requirements.
  
  ### <a id='aws'></a> AWS ###
  
  
negative.code: 
  ### <a id='openstack'></a> OpenStack ###
  
  OpenStack describes hardware in terms of [flavors](http://docs.openstack.org/trunk/openstack-ops/content/flavors.html).
  _insert comment here_
  
  ### <a id='vsphere'></a> vSphere ###
  
  vSphere describes hardware in terms of RAM, CPU, virtual disk, and the other typical specs.
  As a starting point for deciding what hardware to use, see the documented [hardware requirements for Cloud Foundry](../deploying/vsphere/hardware_spec.html).
  
  ## <a id="inbound"></a> Restricting Inbound Network Traffic ##
  
  When setting up your IaaS for BOSH, configuring Security Groups is required for AWS or OpenStack.
  Configuring multiple networks is recommended for vSphere.
  