anchor.diff:  
   export SSH_AUTH_SOCK="/var/lib/buildkite-agent/.ssh/ssh-agent.sock"
   ```
  -
  -## Using multiple keys by adding pipeline-specific environments  
  -
  -There is yet another way to use multiple SSH keys.  
  -
  -1. Add a pipeline-specific environment (for example, by using [Elastic Stack's secrets support](https://github.com/buildkite/elastic-ci-stack-for-aws#build-secrets) or by having an Agent environment hook that switches on the repository URL or the pipeline slug):  
  -```bash
  -GIT_SSH_COMMAND="ssh -i ~/.ssh/id_rsa_mypipeline"
  -```
  -2. Create an identity file at that location:
  -```bash
  -~/.ssh/id_rsa_mypipeline
  -```
  -3. Add the public key for that identity file to `mypipeline` on the git repository provider
  -
  -If you are using Elastic Stack, this approach is redundant as [secrets support](https://github.com/buildkite/elastic-ci-stack-for-aws#build-secrets) allows you to specify an SSH key per pipeline as `/{pipeline-slug}/private_ssh_key`. 
  
positive.code: 
  If you need to use multiple SSH keys for different pipelines, we support a special repository hostname format which you can use with your `~/.ssh/config`.
  
  To use a different key for a given pipeline, first change the repository hostname in your Buildkite pipeline settings from `server.com` to `server.com-mypipeline`, and then add an entry to the SSH config file on your agent machine for the host `server.com-mypipeline` and specify your custom SSH key.
  
  For example, if you had a pipeline repository URL of `git@github.com:org/pipeline-1.git` you would change it in your Buildkite repository settings to `git@github.com-pipeline-1:org/pipeline-1.git` and create the following SSH config file:
  
  
negative.code: id_rsa.pipeline-1  id_rsa.pipeline-1.pub
  ```
  
  Alternatively, you can use a shorter approach to creating multiple SSH keys (described below) by adding pipeline-specific environments.  
  
  <section class="Docs__note">
    <p>Note that if you are using Elastic Stack, the following approach is redundant as [secrets support](https://github.com/buildkite/elastic-ci-stack-for-aws#build-secrets) allows you to specify an SSH key per pipeline as `/{pipeline-slug}/private_ssh_key`.</p>
  </section>
  
  1. Add a pipeline-specific environment (for example, by using [Elastic Stack's secrets support](https://github.com/buildkite/elastic-ci-stack-for-aws#build-secrets) or by having an Agent environment hook that switches on the repository URL or the pipeline slug):  
  ```bash
  GIT_SSH_COMMAND="ssh -i ~/.ssh/id_rsa_mypipeline"
  ```
  2. Create an identity file at that location:
  ```bash
  ~/.ssh/id_rsa_mypipeline
  ```
  3. Add the public key for that identity file to `mypipeline` on the git repository provider.  
  
  ## Using multiple keys with ssh-agent
  
  If you need to use multiple keys, or want to use keys with pass-phrases, an alternative to the above hostname method is to use `ssh-agent`.
  