anchor.diff:      - 10.1.200.15
       static:
       - 10.1.200.11-10.1.200.15
  -    <strong>az: z4</strong>
  +    **az: z4**
       cloud_properties:
         ephemeral_external_ip: true
  -      <strong>network_name: sample-network</strong>
  -      <strong>subnetwork_name: sample-subnet-is1-az2</strong>
  +      **network_name: sample-network**
  +      **subnetwork_name: sample-subnet-is1-az2**
         tags:
  -      - <strong>sample-is1</strong>
  -</code>
  -</pre>
  +      - **sample-is1**
  +```
   
   ### AWS Cloud Config
   
   <p class="note"><strong>Note:</strong> AWS networking requires security groups, which need to be created separately. In the below example, the operator must create the <strong>sample-<%= vars.app_runtime_abbr_lc %>-is</strong> and <strong>sample-is1</strong> security groups.</p>
   
  -<pre>
  -<code>
  +```
   azs:
   - name: z1
     cloud_properties:
  
positive.code:     - 10.1.31.255
      static:
      - 10.1.31.190-10.1.31.254
      <strong>az: z2</strong>
      cloud_properties:
        security_groups:
        - <strong>sample-<%= vars.app_runtime_abbr_lc %>-is</strong>
        # with bbl, there will also be a cf internal security group
        subnet: <strong>sample-subnet-<%= vars.app_runtime_abbr_lc %>-az2</strong>
    - range: 10.0.200.0/28
      gateway: 10.0.200.1
      reserved:
  
negative.code: 
  <p class="note"><strong>Note:</strong> When deploying with a BOSH v2-style manifest that leverages <code>instance_groups</code>, you must enable UAA to differentiate between links exported by the Gorouters, as it only accepts connections from one instance group of Gorouters. As you may have multiple isolation segments, <%= vars.recommended_by %> recommends renaming the instance group used for the system domain. You must also to specify the name of the link from which UAA consumes the link.</p>
  
  ```
  instance_groups:
  - name: router
    instances: 2
  