anchor.diff:  ----
   // NOTCONSOLE
   
  -The bucket needs to exist to register a repository for snapshots. If you did not create the bucket then the repository
  -registration will fail.
  +The bucket needs to exist to register a repository for snapshots. If you did not
  +create the bucket then the repository registration will fail.
  +
  +Note: Starting in version 7.0, all bucket operations are using the path style
  +access pattern. In previous versions the decision to use virtual hosted style or
  +path style access was made by the AWS Java SDK.
   
   [[repository-s3-aws-vpc]]
   [float]
   ==== AWS VPC Bandwidth Settings
   
  -AWS instances resolve S3 endpoints to a public IP. If the Elasticsearch instances reside in a private subnet in an AWS VPC then all traffic to S3 will go through that VPC's NAT instance. If your VPC's NAT instance is a smaller instance size (e.g. a t1.micro) or is handling a high volume of network traffic your bandwidth to S3 may be limited by that NAT instance's networking bandwidth limitations.
  -
  -Instances residing in a public subnet in an AWS VPC will connect to S3 via the VPC's internet gateway and not be bandwidth limited by the VPC's NAT instance.
  +AWS instances resolve S3 endpoints to a public IP. If the Elasticsearch
  +instances reside in a private subnet in an AWS VPC then all traffic to S3 will
  +go through that VPC's NAT instance. If your VPC's NAT instance is a smaller
  +instance size (e.g. a t1.micro) or is handling a high volume of network traffic
  +your bandwidth to S3 may be limited by that NAT instance's networking bandwidth
  +limitations.
  +
  +Instances residing in a public subnet in an AWS VPC will connect to S3 via the
  +VPC's internet gateway and not be bandwidth limited by the VPC's NAT instance.
  
positive.code: repositories, as well as any newly created ones, will pick up the new values
  stored in the keystore.
  
  NOTE: In progress snapshot/restore tasks will not be preempted by a *reload*
  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
  
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:
  
  