mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-29 00:33:38 +00:00
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
64 lines
2.4 KiB
Markdown
64 lines
2.4 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Vault Agent Auto-Auth AliCloud Method"
|
|
sidebar_title: "AliCloud"
|
|
sidebar_current: "docs-agent-autoauth-methods-alicloud"
|
|
description: |-
|
|
AliCloud Method for Vault Agent Auto-Auth
|
|
---
|
|
|
|
# Vault Agent Auto-Auth AliCloud Method
|
|
|
|
The `alicloud` method performs authentication against the [AliCloud Auth
|
|
method](https://www.vaultproject.io/docs/auth/alicloud.html).
|
|
|
|
## Credentials
|
|
|
|
The Vault agent will use the first credential it can successfully obtain in the following order:
|
|
|
|
1. [Environment variables](https://github.com/aliyun/alibaba-cloud-sdk-go/blob/master/sdk/auth/credentials/providers/env.go)
|
|
2. A static credential configuration
|
|
3. Instance metadata (recommended)
|
|
|
|
Wherever possible, we recommend using instance metadata for credentials. These rotate every hour
|
|
and require no effort on your part to provision, making instance metadata the most secure of the three methods. If
|
|
using instance metadata _and_ a custom `credential_poll_interval`, be sure the frequency is set for
|
|
less than an hour, because instance metadata credentials expire every hour.
|
|
|
|
Environment variables are given first precedence to provide the ability to quickly override your
|
|
configuration.
|
|
|
|
## Configuration
|
|
|
|
### General
|
|
|
|
- `role` `(string: required)` - The role to authenticate against on Vault.
|
|
|
|
- `region` `(string: required)` - The AliCloud region in which the Vault agent resides. Example: "us-west-1".
|
|
|
|
- `credential_poll_interval` `(integer: optional)` - In seconds, how frequently the Vault agent should check for new credentials.
|
|
|
|
### Optional Static Credential Configuration (Not Preferred)
|
|
|
|
If instance metadata is not available, you may provide credential information through the parameters below.
|
|
|
|
- `access_key` `(string: optional)` - The access key to use.
|
|
|
|
- `secret_key` `(string: optional)` - The secret key to use.
|
|
|
|
- `access_token` `(string: optional)` - The access token to use.
|
|
|
|
- `role_arn` `(string: optional)` - The role ARN to use.
|
|
|
|
- `role_session_name` `(string: optional)` - The role session name to use.
|
|
|
|
- `role_session_expiration` `(string: optional)` - The role session expiration to use.
|
|
|
|
- `private_key` `(string: optional)` - The private key to use.
|
|
|
|
- `public_key_id` `(string: optional)` - The public key ID to use.
|
|
|
|
- `session_expiration` `(string: optional)` - The session expiration to use.
|
|
|
|
- `role_name` `(string: optional)` - The role name to use.
|