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: ----
  // 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.
  