Skip to content
This repository has been archived by the owner on Sep 11, 2023. It is now read-only.

Commit

Permalink
add aws secret engine example
Browse files Browse the repository at this point in the history
  • Loading branch information
bonifaido committed Jun 13, 2019
1 parent 664c12c commit 7551720
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions vault-config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,23 @@ secrets:
generate_lease: true
ttl: 30m

# The AWS secrets engine generates AWS access credentials dynamically based on IAM policies.
# See https://www.vaultproject.io/docs/secrets/aws/index.html for more information
- type: aws
description: AWS secret engine.
configuration:
config/root:
- access_key: "${env "AWS_ACCESS_KEY_ID"}" # or you can put the credential literals directly here
secret_key: "${env "AWS_SECRET_ACCESS_KEY"}"
# Uncomment for root credential rotation
# see: https://www.vaultproject.io/api/secret/aws/index.html#rotate-root-iam-credentials
# rotate: true
roles:
- name: simple-user
credential_type: iam_user
policy_arns:
- arn:aws:iam::123456789012:policy/UsersManageOwnCredentials

# Registers a new plugin in Vault's plugin catalog. "plugin_directory" setting should be set it Vault server configuration
# and plugin binary should be present in plugin directory. Also, for some plugins readOnlyRootFilesystem Pod Security Policy
# should be disabled to allow RPC communication between plugin and Vault server via Unix socket
Expand Down

0 comments on commit 7551720

Please sign in to comment.