a43e292424
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
2.4 KiB
| layout | page_title | sidebar_title | sidebar_current | description |
|---|---|---|---|---|
| docs | Vault Agent Auto-Auth AWS Method | AWS | docs-agent-autoauth-methods-aws | AWS Method for Vault Agent Auto-Auth |
Vault Agent Auto-Auth AWS Method
The aws method performs authentication against the AWS Auth
method. Both ec2 and iam
authentication types are supported. If ec2 is used, the agent will store the
reauthentication value in memory and use it for reauthenticating, but will not
persist it to disk.
Due to the complexity of the Trust On First Use (TOFU) model used in the ec2
method, we recommend the iam method when possible.
Credentials
Vault will use the AWS SDK's normal credential chain behavior, which means it will use the first valid credentials it finds in the following order:
- A static credential configuration
- Environment variables
- A file containing credentials
- From any identity services available in its physical environment like container environment variables or role-based instance metadata
Wherever possible, we recommend using identity services (method 4) for credentials.
These rotate regularly and require no effort on your part to provision, making
identity services the most secure of the four methods. If using identity services and a custom
credential_poll_interval, be sure the frequency is set low enough to pick up new credentials
from the physical environment as they become available.
To use identity services, choose the iam type and leave the access_key, secret_key, and session_token
parameters unset in your configuration.
Configuration
-
type(string: required)- The type of authentication; must beec2oriam. -
role(string: required)- The role to authenticate against on Vault. -
credential_poll_interval(integer: optional)- In seconds, how frequently the Vault agent should check for new credentials if using the iam type. -
access_key(string: optional)- When using static credentials, the access key to use. -
secret_key(string: optional)- When using static credentials, the secret key to use. -
session_token(string: optional)- The session token to use for authentication, if needed. -
header_value(string: optional)- If configured in Vault, the value to use foriam_server_id_header_value.