vault-aws-cli-credentials-go

Vault AWS CLI/SDK Credentials Helper

The Vault AWS CLI/SDK Credential Helper (vaultcreds) implements the AWS CLI/SDK external credentials helper interface as outlined here: https://docs.aws.amazon.com/cli/v1/userguide/cli-configure-sourcing-external.html

vaultcreds retrieves short-lived AWS credentials from Vault / OpenBao and writes them to stdout in credential-process JSON format.

Installation

From source:

go install github.com/freakinhippie/vault-aws-cli-credentials-go/cmd/vaultcreds@latest

From Homebrew:

brew tap freakinhippie/homebrew-tap
brew install vaultcreds

From Chocolatey:

choco install vaultcreds

Chocolatey packages are published by a dedicated Windows GitHub Actions workflow after each GitHub release is published.

From release artifacts: download the package for your OS/architecture and place vaultcreds on your PATH.

Configuration

Configuration precedence is:

1. CLI flags
2. Environment variables
3. Config file (--config or VAULTCREDS_CONFIG)
4. Defaults

Additional Vault variables honored:

• VAULT_TOKEN
• VAULT_TOKEN_HELPER
• VAULT_NAMESPACE
• VAULT_SKIP_VERIFY

Token resolution matches Vault CLI behavior order:

1. VAULT_TOKEN
2. Token helper (VAULT_TOKEN_HELPER or ~/.vault token_helper)
3. ~/.vault-token

Credential Caching

Caching is disabled by default.

When enabled (--cache or VAULTCREDS_CACHE_CREDENTIALS=true), vaultcreds uses secure OS storage when available:

• Linux: Secret Service (libsecret-compatible keyring)
• macOS: Keychain
• Windows: Credential Manager (WinCred)

If caching is requested but a secure backend is unavailable or errors, vaultcreds prints a warning and continues in non-caching mode. vaultcreds does not write plaintext credentials to disk.

Cache Management Commands

Use these commands to inspect or clean existing cache entries:

vaultcreds --cache-list
vaultcreds --cache-purge "<cache-key>[,<cache-key>...]"
vaultcreds --cache-purge-expired
vaultcreds --cache-purge-all
vaultcreds --cache-keyring-recovery-help

Notes:

• Cache maintenance commands are mutually exclusive (run one at a time).
• --cache-keyring-recovery-help prints OS-specific instructions for recovering/resetting the underlying keyring.
• vaultcreds cannot directly reset OS keyring passwords; this must be done with OS keyring tooling.

Caching Setup Summary

For full OS-specific setup and headless/server guidance, see README_CACHING.md.

• Linux: requires a user D-Bus session and Secret Service provider.
• macOS: uses Keychain in the invoking user context.
• Windows: uses Credential Manager (WinCred) in the user logon context.
• If secure backend access is unavailable, vaultcreds falls back to non-caching mode and logs a warning.

AWS CLI example

credential_process should use the full path to vaultcreds; do not rely on PATH lookup.

[profile vault-dev]
credential_process = /usr/local/bin/vaultcreds --vault-addr=https://vault.example.com --role=dev-role
region = us-east-1

Status

Implemented:

• Config loading and validation
• Vault token resolution (env, helper, token file)
• Vault AWS credential retrieval (sts and creds)
• Credential-process JSON output
• Optional secure caching (Linux/macOS/Windows)
• Command-path tests for cache hit/miss, token errors, Vault errors, and successful output
• Integration/E2E test harness for vault -dev (build tag integration)

Planned:

• Additional release automation polish

Testing

Run unit tests:

go test ./...

Run integration/E2E tests (requires local vault binary):

go test -tags=integration ./internal/e2e -v

Make Targets

make help
make build
make test
make test-integration
make fmt
make vet
make tidy

Releasing

See RELEASING.md for one-time setup (GitHub secrets, Homebrew tap, Chocolatey account/API key) and the tag-based release workflow.

License

Licensed under the Apache License, Version 2.0. See LICENSE.