anchor.diff:  
   [source,xml]
   ----
  -<servers>
  +<settings>
     ...
  -  <server>
  -    <id>my-auth-repo</id>
  -    <username>zango</username>
  -    <password>123</password>
  -  </server>
  +  <servers>
  +    <server>
  +      <id>my-auth-repo</id>
  +      <username>zango</username>
  +      <password>123</password>
  +    </server>
  +    ...
  +  </servers>
     ...
  -</servers>
  +</settings>
   ----
   
   Then in your deps.edn include a repo with a name matching the server id (here `my-auth-repo`):
  
positive.code: 
  [source,xml]
  ----
  <servers>
    ...
    <server>
      <id>my-private-repo</id>
      <username>AWS_ACCESS_KEY_HERE</username>
      <password>AWS_SECRET_ACCESS_KEY_HERE</password>
    </server>
    ...
  </servers>
  ----
  
  It is also possible to specify your AWS credentials using the AWS credential chain. This is NOT RECOMMENDED as the same AWS credentials will be used for all AWS repositories (unlike settings.xml, which lets you set these on a per-repository basis).
  
negative.code: 
  [source,xml]
  ----
  <settings>
    ...
    <proxies>
      <proxy>
        <id>my-proxy</id>
        <host>proxy.my.org</host>
        <port>3128</port>
        <nonProxyHosts>localhost|*.my.org</nonProxyHosts>
      </proxy>
    </proxies>
    ...
  </settings>
  ----
  
  Refer to the Maven https://maven.apache.org/guides/mini/guide-proxies.html[Guide to using proxies] for further details.
  