anchor.diff:  ----
   // NOTCONSOLE
   
  -You may further restrict the permissions by specifying a prefix within the bucket, in this example, named "foo".
  +You may further restrict the permissions by specifying a prefix within the
  +bucket, in this example, named "foo".
   
   [source,js]
   ----
  
positive.code: 
  `client`::
  
      The name of the s3 client to use to connect to S3. Defaults to `default`.
  
  `base_path`::
  
      Specifies the path within bucket to repository data. Defaults to
      value of `repositories.s3.base_path` or to root directory if not set.
      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 `/`.
  
  `chunk_size`::
  
      Big files can be broken down into chunks during snapshotting if needed.
      The chunk size can be specified in bytes or by using size value notation,
      i.e. `1gb`, `10mb`, `5kb`. Defaults to `1gb`.
  
  `compress`::
  
  
negative.code: 
  `buffer_size`::
  
      Minimum threshold below which the chunk is uploaded using a single request.
      Beyond this threshold, the S3 repository will use the
      http://docs.aws.amazon.com/AmazonS3/latest/dev/uploadobjusingmpu.html[AWS
      Multipart Upload API] to split the chunk into several parts, each of
      `buffer_size` length, and to upload each part in its own request. Note that
      setting a buffer size lower than `5mb` is not allowed since it will prevent
      the use of the Multipart API and may result in upload errors. It is also not
      possible to set a buffer size greater than `5gb` as it is the maximum upload
      size allowed by S3. Defaults to the minimum between `100mb` and `5%` of the
      heap size.
  
  `canned_acl`::
  
      The S3 repository supports all
      http://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl[S3
      canned ACLs] : `private`, `public-read`, `public-read-write`,
      `authenticated-read`, `log-delivery-write`, `bucket-owner-read`,
      `bucket-owner-full-control`. Defaults to `private`.  You could specify a
      canned ACL using the `canned_acl` setting. When the S3 repository creates
      buckets and objects, it adds the canned ACL into the buckets and objects.
  
  `storage_class`::
  
      Sets the S3 storage class for objects stored in the snapshot repository.
      Values may be `standard`, `reduced_redundancy`, `standard_ia`.  Defaults to
      `standard`. Changing this setting on an existing repository only affects the
      storage class for newly created objects, resulting in a mixed usage of
      storage classes. Additionally, S3 Lifecycle Policies can be used to manage
      the storage class of existing objects.  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]
  
  NOTE: The option of defining client settings in the repository settings as
  documented below is considered deprecated, and will be removed in a future
  version.
  
  In addition to the above settings, you may also specify all non-secure client
  settings in the repository settings.  In this case, the client settings found in
  the repository settings will be merged with those of the named client used by
  the repository.  Conflicts between client and repository settings are resolved
  by the repository settings taking precedence over client settings.
  
  For example:
  
  