From 3407a033ba170d3779708b2a3afc1a268d16817e Mon Sep 17 00:00:00 2001 From: Jeremy Voorhis Date: Wed, 10 May 2017 20:00:59 -0700 Subject: [PATCH] Update the S3 storage backend docs to reflect capabilities. --- website/source/docs/configuration/storage/s3.html.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/website/source/docs/configuration/storage/s3.html.md b/website/source/docs/configuration/storage/s3.html.md index a020c660d..1cecd30e8 100644 --- a/website/source/docs/configuration/storage/s3.html.md +++ b/website/source/docs/configuration/storage/s3.html.md @@ -46,11 +46,13 @@ instance profile service to provide the credentials Vault will use to make S3 API calls. Leaving the `access_key` and `secret_key` fields empty will cause Vault to attempt to retrieve credentials from the AWS metadata service. -- `access_key` `(string: )` – Specifies the AWS access key. This can - also be provided via the environment variable `AWS_ACCESS_KEY_ID`. +- `access_key` – Specifies the AWS access key. This can also be provided via + the environment variable `AWS_ACCESS_KEY_ID`, AWS credential files, or by + IAM role. -- `secret_key` `(string: )` – Specifies the AWS secret key. This can - also be provided via the environment variable `AWS_SECRET_ACCESS_KEY`. +- `secret_key` – Specifies the AWS secret key. This can also be provided via + the environment variable `AWS_SECRET_ACCESS_KEY`, AWS credential files, or + by IAM role. - `session_token` `(string: "")` – Specifies the AWS session token. This can also be provided via the environment variable `AWS_SESSION_TOKEN`.