anchor.diff:  // CONSOLE
   // TEST[skip:we don't have s3 setup while testing this]
   
  -Most client settings are specified inside `elasticsearch.yml`, but some are
  -sensitive and must be stored in the {ref}/secure-settings.html[elasticsearch keystore].
  -
  -For example, before you start the node, run these commands to add AWS access
  -key settings to the keystore:
  +Most client settings can be added to the `elasticsearch.yml` configuration file
  +with the exception of the secure settings, which you add to the {es} keystore.
  +For more information about creating and updating the {es} keystore, see
  +{ref}/secure-settings.html[Secure settings].
  +
  +For example, before you start the node, run these commands to add AWS access key
  +settings to the keystore:
   
   [source,sh]
   ----
  
positive.code: 
      The port of a proxy to connect to s3 through.
  
  `proxy.username`::
  
      The username to connect to the `proxy.host` with. (Secure)    
  
  `proxy.password`::
  
      The password to connect to the `proxy.host` with. (Secure)    
  
  `read_timeout`::
  
  
negative.code: of the client's secure settings. The task will complete using the client as it
  was built when the operation started.
  
  The following list contains the available client settings. Those that must be
  stored in the keystore are marked as "secure" and are *reloadable*; the other
  settings belong in the `elasticsearch.yml` file.
  
  `access_key` ({ref}/secure-settings.html[Secure])::
  
      An s3 access key. The `secret_key` setting must also be specified. 
  
  `secret_key` ({ref}/secure-settings.html[Secure])::
  
      An s3 secret key. The `access_key` setting must also be specified. 
  
  `session_token`::
      An s3 session token. The `access_key` and `secret_key` settings must also
  