luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Update the S3 storage backend docs to reflect capabilities.

This commit is contained in:
Jeremy Voorhis 2017-05-10 20:00:59 -07:00
parent 26ed13af91
commit 3407a033ba
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/configuration/storage/s3.html.md
View File

@ -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: <required>)` – 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: <required>)` – 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`.