aws-vault7.2.0

aws-vault stores AWS IAM credentials in the operating system’s secure keystore and uses them to supply short-lived credentials to development shells and applications. It is designed to work alongside the AWS CLI, reading named profiles and settings from ~/.aws/config instead of treating long-lived keys as ordinary project data. Developers run a profile through commands such as aws-vault exec jonsmith -- env to launch a subprocess with AWS variables set.

The temporary credentials come from Amazon STS through GetSessionToken or AssumeRole calls, and their brief expiration reduces the risk of exposed keys remaining useful. aws-vault can pass credentials through environment variables or start a local metadata server for software that uses Amazon SDKs. Its supported vaulting backend is Secret Service, including GNOME Keyring and KWallet, selected with the --backend option or AWS_VAULT_BACKEND environment variable.

This suits developers and teams working with multiple AWS profiles, role assumptions, and local command-line tools that need controlled access to cloud accounts. The 7.2.0 release fixes credential-type detection during login and gives source_profile priority over SSO configuration, while also correcting INI output to match the credentials file.

Published by 99designs, aws-vault is open-source System Tools software for Windows on x86 architecture. The project has been abandoned and receives no further updates; continued maintenance and contributions are directed to the active ByteNess/aws-vault fork.