anchor.diff:  // CONSOLE
   // TEST[skip:we don't have s3 set up while testing this]
   
  -This sets up a repository that uses all client settings from the client `my_client_named` except for the `endpoint` that is overridden
  -to `my.s3.endpoint` by the repository settings.
  +This sets up a repository that uses all client settings from the client
  +`my_client_name` except for the `endpoint` that is overridden to
  +`my.s3.endpoint` by the repository settings.
   
   [[repository-s3-permissions]]
   ===== Recommended S3 Permissions
   
  -In order to restrict the Elasticsearch snapshot process to the minimum required resources, we recommend using Amazon
  -IAM in conjunction with pre-existing S3 buckets. Here is an example policy which will allow the snapshot access to an
  - S3 bucket named "snaps.example.com". This may be configured through the AWS IAM console, by creating a Custom Policy,
  - and using a Policy Document similar to this (changing snaps.example.com to your bucket name).
  +In order to restrict the Elasticsearch snapshot process to the minimum required
  +resources, we recommend using Amazon IAM in conjunction with pre-existing S3
  +buckets. Here is an example policy which will allow the snapshot access to an S3
  +bucket named "snaps.example.com". This may be configured through the AWS IAM
  +console, by creating a Custom Policy, and using a Policy Document similar to
  +this (changing snaps.example.com to your bucket name).
   
   [source,js]
   ----
  
positive.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:
  
  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:
  
  
negative.code: ----
  // 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.
  
  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.
  