anchor.diff:  
   ### <a id="ha-proxy"></a>Using HAProxy
   
  -If you are using the HAproxy job from cf-release as the gorouter load balancer and you set the `cc.allow_app_ssh_access` property in your Cloud Foundry manifest to true, HAproxy will also serve as the load balancer for Diego's SSH proxies. This configuration relies on the presence of the same consul server cluster that Diego components use for service discovery. This configuration also works well for deployments where all traffic on the system domain and its subdomains is directed towards the HAproxy job, as is the case for a BOSH-Lite CF deployment on the default `bosh-lite.com` domain.
  +If you are using the HAproxy job as the gorouter load balancer and you set the `cc.allow_app_ssh_access` property in your Cloud Foundry manifest to `true`, HAproxy serves as the load balancer for Diego's SSH proxies. This configuration relies on the presence of the same consul server cluster that Diego components use for service discovery. Use this configuration for deployments where all traffic on the system domain and its subdomains is directed towards the HAproxy job, as is the case for a BOSH-Lite Cloud Foundry deployment on the default `bosh-lite.com` domain.
   
  -### <a id="aws"></a>Using ELBs on Amazon Web Services
  +### <a id="aws"></a>Using Elastic Load Balancers (ELBs) on Amazon Web Services (AWS)
   
  -For AWS deployments, where the infrastructure offers load-balancing as a service through ELBs, the deployment operator can provision an ELB to balance load across the Diego SSH proxy instances. This ELB should be configured to listen to TCP traffic on the port given by the `app_ssh.port` property in the Cloud Foundry manifest and to send it to port 2222. 
  +For AWS deployments, where the infrastructure offers load-balancing as a service through ELBs, the deployment operator can provision an ELB to load balance across the Diego SSH proxy instances. This ELB should be configured to listen to TCP traffic on the port given by the `app_ssh.port` property in the Cloud Foundry manifest and to send it to port 2222. 
   
   In the Diego manifest, register the SSH proxies with your ELB by editing the `cloud_properties` values.
   
  
positive.code: 
  1. Delete your `ssh-proxy` client.
  <pre class="terminal">$ uaac token client delete ssh-proxy</pre>
  
  1. Redeploy Cloud Foundry.
  
  ## <a id="troubleshooting"></a>Troubleshooting
  
  
negative.code: <p class="note"><strong>Note</strong>: You should generate a unique key pair for each deployment.</p>
  
  1. Generate your key pair, entering an empty string for the passphrase when prompted.
  <pre class="terminal">$ ssh-keygen -f ssh-proxy-host-key.pem
  $ ssh-keygen -lf ssh-proxy-host-key.pem.pub | cut -d ' ' -f2 > ssh-proxy-host-key-fingerprint
  </pre>
  1. Locate your PEM-encoded private key in `ssh-proxy-host-key.pem` and your public key fingerprint in `ssh-proxy-host-key-fingerprint`. You will need to copy the contents of these files into your Cloud Foundry and Diego manifests.
  
  ### <a id='cf-manifest'></a> Configure Your Cloud Foundry Manifest
  
  Your manifest for Cloud Foundry should include the following properties:
  
    <pre><code>properties:
      app\_ssh:
  