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: [[repository-s3-usage]]
  ==== Getting started with AWS
  
  The plugin will default to using
  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html[IAM Role]
  credentials for authentication. These can be overridden by, in increasing
  order of precedence, system properties `aws.accessKeyId` and `aws.secretKey`,
  environment variables `AWS_ACCESS_KEY_ID` and `AWS_SECRET_KEY`, or the
  elasticsearch config using `cloud.aws.access_key` and `cloud.aws.secret_key` or
  if you wish to set credentials specifically for s3 `cloud.aws.s3.access_key` and `cloud.aws.s3.secret_key`:
  
  [source,yaml]
  ----
  cloud:
      aws:
          access_key: AKVAIQBF2RECL7FJWGJQ
          secret_key: vExyMThREXeRMm/b/LRzEB8jWwvzQeXgjqMX+6br
  ----
  
  [[repository-s3-usage-security]]
  ===== Transport security
  
  By default this plugin uses HTTPS for all API calls to AWS endpoints. If you wish to configure HTTP you can set
  `cloud.aws.protocol` in the elasticsearch config. You can optionally override this setting per individual service
  via: `cloud.aws.ec2.protocol` or `cloud.aws.s3.protocol`.
  
  [source,yaml]
  ----
  cloud:
      aws:
          protocol: https
          s3:
              protocol: http
          ec2:
              protocol: https
  ----
  
  In addition, a proxy can be configured with the `proxy.host`, `proxy.port`, `proxy.username` and `proxy.password` settings
  (note that protocol can be `http` or `https`):
  
  [source,yaml]
  ----
  cloud:
      aws:
          protocol: https
          proxy:
              host: proxy1.company.com
              port: 8083
              username: myself
              password: theBestPasswordEver!
  ----
  
  You can also set different proxies for `ec2` and `s3`:
  
  [source,yaml]
  ----
  cloud:
      aws:
          s3:
              proxy:
                  host: proxy1.company.com
                  port: 8083
                  username: myself1
                  password: theBestPasswordEver1!
          ec2:
              proxy:
                  host: proxy2.company.com
                  port: 8083
                  username: myself2
                  password: theBestPasswordEver2!
  ----
  
  ===== Read timeout
  
  Read timeout determines the amount of time to wait for data to be transferred over an established,
  open connection before the connection is timed out. Defaults to AWS SDK default value (`50s`).
  It can be configured with `cloud.aws.read_timeout` (or `cloud.aws.s3.read_timeout`) setting:
  
  [source, yaml]
  ----
  cloud.aws.read_timeout: 30s
  ----
  
  [[repository-s3-repository]]
  ==== S3 Repository
  
  The S3 repository is using S3 to store snapshots. The S3 repository can be created using the following command:
  
  [source,js]
  ----
  
negative.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]
  
  [[repository-s3-permissions]]
  ===== Recommended S3 Permissions
  