anchor.diff:      Previously, the base_path could take a leading `/` (forward slash).
       However, this has been deprecated and setting the base_path now should
       omit the leading `/`.
  -
  -`access_key`::
  -
  -    The access key to use for authentication. Defaults to value of
  -    `cloud.aws.access_key`.
  -
  -`secret_key`::
  -
  -    The secret key to use for authentication. Defaults to value of
  -    `cloud.aws.secret_key`.
   
   `chunk_size`::
   
  
positive.code:     Due to the extra complexity with the Glacier class lifecycle, it is not
      currently supported by the plugin. For more information about the
      different classes, see http://docs.aws.amazon.com/AmazonS3/latest/dev/storage-class-intro.html[AWS Storage Classes Guide]
  
  `path_style_access`::
  
      Activate path style access for http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html[virtual hosting of buckets].
      The default behaviour is to detect which access style to use based on the configured endpoint (an IP will result
      in path-style access) and the bucket being accessed (some buckets are not valid DNS names).
  
  Note that you can define S3 repository settings for all S3 repositories in `elasticsearch.yml` configuration file.
  They are all prefixed with `repositories.s3.`. For example, you can define compression for all S3 repositories
  by setting `repositories.s3.compress: true` in `elasticsearch.yml`.
  
  The S3 repositories use the same credentials as the rest of the AWS services
  provided by this plugin (`discovery`). See <<repository-s3-usage>> for details.
  
  Multiple S3 repositories can be created. If the buckets require different
  credentials, then define them as part of the repository settings.
  
  [[repository-s3-permissions]]
  ===== Recommended S3 Permissions
  
negative.code: ----
  // NOTCONSOLE
  
  [[repository-s3-aws-vpc]]
  [float]
  ==== AWS VPC Bandwidth Settings
  