[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5115":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":15,"stars7d":16,"stars30d":17,"stars90d":14,"forks30d":14,"starsTrendScore":16,"compositeScore":18,"rankGlobal":9,"rankLanguage":9,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":20,"topics":22,"createdAt":9,"pushedAt":9,"updatedAt":30,"readmeContent":31,"aiSummary":32,"trendingCount":14,"starSnapshotCount":14,"syncStatus":33,"lastSyncTime":34,"discoverSource":35},5115,"aws-vault","99designs\u002Faws-vault","99designs","A vault for securely storing and accessing AWS credentials in development environments",null,"Go",8979,834,117,0,1,3,16,39.77,"MIT License",false,"master",[23,5,24,25,26,27,28,29],"aws","cli","credentials","iam","keychain","mfa","temporary-credentials","2026-06-12 02:01:08","# AWS Vault\n\n[![Downloads](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fdownloads\u002F99designs\u002Faws-vault\u002Ftotal.svg)](https:\u002F\u002Fgithub.com\u002F99designs\u002Faws-vault\u002Freleases)\n[![Continuous Integration](https:\u002F\u002Fgithub.com\u002F99designs\u002Faws-vault\u002Fworkflows\u002FContinuous%20Integration\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002F99designs\u002Faws-vault\u002Factions)\n\n> [!WARNING]\n> This project has been abandoned and it's not receiving any more updates. If you want to continue to receive updates\n> or contribute, please feel free to look at the active fork at: https:\u002F\u002Fgithub.com\u002FByteNess\u002Faws-vault\n\nAWS Vault is a tool to securely store and access AWS credentials in a development environment.\n\nAWS Vault stores IAM credentials in your operating system's secure keystore and then generates temporary credentials from those to expose to your shell and applications. It's designed to be complementary to the AWS CLI tools, and is aware of your [profiles and configuration in `~\u002F.aws\u002Fconfig`](https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Fuserguide\u002Fcli-chap-getting-started.html#cli-config-files).\n\nCheck out the [announcement blog post](https:\u002F\u002F99designs.com.au\u002Ftech-blog\u002Fblog\u002F2015\u002F10\u002F26\u002Faws-vault\u002F) for more details.\n\n## Installing\n\nYou can install AWS Vault:\n- by downloading the [latest release](https:\u002F\u002Fgithub.com\u002F99designs\u002Faws-vault\u002Freleases\u002Flatest)\n- on macOS with [Homebrew](https:\u002F\u002Fformulae.brew.sh\u002Fformula\u002Faws-vault): `brew install aws-vault`\n- on macOS with [MacPorts](https:\u002F\u002Fports.macports.org\u002Fport\u002Faws-vault\u002Fsummary): `port install aws-vault`\n- on Windows with [Chocolatey](https:\u002F\u002Fchocolatey.org\u002Fpackages\u002Faws-vault): `choco install aws-vault`\n- on Windows with [Scoop](https:\u002F\u002Fscoop.sh\u002F): `scoop install aws-vault`\n- on Linux with [Homebrew on Linux](https:\u002F\u002Fformulae.brew.sh\u002Fformula\u002Faws-vault): `brew install aws-vault`\n- on [Arch Linux](https:\u002F\u002Fwww.archlinux.org\u002Fpackages\u002Fcommunity\u002Fx86_64\u002Faws-vault\u002F): `pacman -S aws-vault`\n- on [Gentoo Linux](https:\u002F\u002Fgithub.com\u002Fgentoo\u002Fguru\u002Ftree\u002Fmaster\u002Fapp-admin\u002Faws-vault): `emerge --ask app-admin\u002Faws-vault` ([enable Guru first](https:\u002F\u002Fwiki.gentoo.org\u002Fwiki\u002FProject:GURU\u002FInformation_for_End_Users))\n- on [FreeBSD](https:\u002F\u002Fwww.freshports.org\u002Fsecurity\u002Faws-vault\u002F): `pkg install aws-vault`\n- on [OpenSUSE](https:\u002F\u002Fsoftware.opensuse.org\u002Fpackage\u002Faws-vault): enable devel:languages:go repo then `zypper install aws-vault`\n- with [Nix](https:\u002F\u002Fsearch.nixos.org\u002Fpackages?show=aws-vault&query=aws-vault): `nix-env -i aws-vault`\n- with [asdf-vm](https:\u002F\u002Fgithub.com\u002Fkarancode\u002Fasdf-aws-vault): `asdf plugin-add aws-vault https:\u002F\u002Fgithub.com\u002Fkarancode\u002Fasdf-aws-vault.git && asdf install aws-vault \u003Cversion>`\n\n## Documentation\n\nConfig, usage, tips and tricks are available in the [USAGE.md](.\u002FUSAGE.md) file.\n\n## Vaulting Backends\n\nThe supported vaulting backends are:\n\n* [macOS Keychain](https:\u002F\u002Fsupport.apple.com\u002Fen-au\u002Fguide\u002Fkeychain-access\u002Fwelcome\u002Fmac)\n* [Windows Credential Manager](https:\u002F\u002Fsupport.microsoft.com\u002Fen-au\u002Fhelp\u002F4026814\u002Fwindows-accessing-credential-manager)\n* Secret Service ([Gnome Keyring](https:\u002F\u002Fwiki.gnome.org\u002FProjects\u002FGnomeKeyring), [KWallet](https:\u002F\u002Fkde.org\u002Fapplications\u002Fsystem\u002Forg.kde.kwalletmanager5))\n* [KWallet](https:\u002F\u002Fkde.org\u002Fapplications\u002Fsystem\u002Forg.kde.kwalletmanager5)\n* [Pass](https:\u002F\u002Fwww.passwordstore.org\u002F)\n* Encrypted file\n\nUse the `--backend` flag or `AWS_VAULT_BACKEND` environment variable to specify.\n\n## Quick start\n\n```shell\n# Store AWS credentials for the \"jonsmith\" profile\n$ aws-vault add jonsmith\nEnter Access Key Id: ABDCDEFDASDASF\nEnter Secret Key: %%%\n\n# Execute a command (using temporary credentials)\n$ aws-vault exec jonsmith -- aws s3 ls\nbucket_1\nbucket_2\n\n# open a browser window and login to the AWS Console\n$ aws-vault login jonsmith\n\n# List credentials\n$ aws-vault list\nProfile                  Credentials              Sessions\n=======                  ===========              ========\njonsmith                 jonsmith                 -\n\n# Start a subshell with temporary credentials\n$ aws-vault exec jonsmith\nStarting subshell \u002Fbin\u002Fzsh, use `exit` to exit the subshell\n$ aws s3 ls\nbucket_1\nbucket_2\n```\n\n## How it works\n\n`aws-vault` uses Amazon's STS service to generate [temporary credentials](https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fid_credentials_temp.html) via the `GetSessionToken` or `AssumeRole` API calls. These expire in a short period of time, so the risk of leaking credentials is reduced.\n\nAWS Vault then exposes the temporary credentials to the sub-process in one of two ways\n\n1. **Environment variables** are written to the sub-process. Notice in the below example how the AWS credentials get written out\n   ```shell\n   $ aws-vault exec jonsmith -- env | grep AWS\n   AWS_VAULT=jonsmith\n   AWS_DEFAULT_REGION=us-east-1\n   AWS_REGION=us-east-1\n   AWS_ACCESS_KEY_ID=%%%\n   AWS_SECRET_ACCESS_KEY=%%%\n   AWS_SESSION_TOKEN=%%%\n   AWS_CREDENTIAL_EXPIRATION=2020-04-16T11:16:27Z\n   ```\n2. **Local metadata server** is started. This approach has the advantage that anything that uses Amazon's SDKs will automatically refresh credentials as needed, so session times can be as short as possible.\n   ```shell\n   $ aws-vault exec --server jonsmith -- env | grep AWS\n   AWS_VAULT=jonsmith\n   AWS_DEFAULT_REGION=us-east-1\n   AWS_REGION=us-east-1\n   AWS_CONTAINER_CREDENTIALS_FULL_URI=%%%\n   AWS_CONTAINER_AUTHORIZATION_TOKEN=%%%\n   ```\n\nThe default is to use environment variables, but you can opt-in to the local instance metadata server with the `--server` flag on the `exec` command.\n\n## Roles and MFA\n\n[Best-practice](https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002Fbest-practices.html#delegate-using-roles) is to [create Roles to delegate permissions](https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Fuserguide\u002Fcli-roles.html). For security, you should also require that users provide a one-time key generated from a multi-factor authentication (MFA) device.\n\nFirst you'll need to create the users and roles in IAM, as well as [setup an MFA device](https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002FGenerateMFAConfigAccount.html). You can then [set up IAM roles to enforce MFA](https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Fuserguide\u002Fcli-configure-role.html#cli-configure-role-mfa).\n\nHere's an example configuration using roles and MFA:\n\n```ini\n[default]\nregion = us-east-1\n\n[profile jonsmith]\nmfa_serial = arn:aws:iam::111111111111:mfa\u002Fjonsmith\n\n[profile foo-readonly]\nsource_profile = jonsmith\nrole_arn = arn:aws:iam::22222222222:role\u002FReadOnly\n\n[profile foo-admin]\nsource_profile = jonsmith\nrole_arn = arn:aws:iam::22222222222:role\u002FAdministrator\nmfa_serial = arn:aws:iam::111111111111:mfa\u002Fjonsmith\n\n[profile bar-role1]\nsource_profile = jonsmith\nrole_arn = arn:aws:iam::333333333333:role\u002FRole1\nmfa_serial = arn:aws:iam::111111111111:mfa\u002Fjonsmith\n\n[profile bar-role2]\nsource_profile = bar-role1\nrole_arn = arn:aws:iam::333333333333:role\u002FRole2\nmfa_serial = arn:aws:iam::111111111111:mfa\u002Fjonsmith\n```\n\nHere's what you can expect from aws-vault\n\n| Command                                  | Credentials                 | Cached        | MFA |\n|------------------------------------------|-----------------------------|---------------|-----|\n| `aws-vault exec jonsmith --no-session`   | Long-term credentials       | No            | No  |\n| `aws-vault exec jonsmith`                | session-token               | session-token | Yes |\n| `aws-vault exec foo-readonly`            | role                        | No            | No  |\n| `aws-vault exec foo-admin`               | session-token + role        | session-token | Yes |\n| `aws-vault exec foo-admin --duration=2h` | role                        | role          | Yes |\n| `aws-vault exec bar-role2`               | session-token + role + role | session-token | Yes |\n| `aws-vault exec bar-role2 --no-session`  | role + role                 | role          | Yes |\n\n## Development\n\nThe [macOS release builds](https:\u002F\u002Fgithub.com\u002F99designs\u002Faws-vault\u002Freleases) are code-signed to avoid extra prompts in Keychain. You can verify this with:\n```shell\n$ codesign --verify --verbose $(which aws-vault)\n```\n\nIf you are developing or compiling the aws-vault binary yourself, you can [generate a self-signed certificate](https:\u002F\u002Fsupport.apple.com\u002Fen-au\u002Fguide\u002Fkeychain-access\u002Fkyca8916\u002Fmac) by accessing Keychain Access > Certificate Assistant > Create Certificate -> Certificate Type: Code Signing. You can then sign your binary with:\n```shell\n$ go build .\n$ codesign --sign \u003CName of certificate created above> .\u002Faws-vault\n```\n\n## References and Inspiration\n\n * https:\u002F\u002Fgithub.com\u002Fpda\u002Faws-keychain\n * https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002FMFAProtectedAPI.html\n * https:\u002F\u002Fdocs.aws.amazon.com\u002FIAM\u002Flatest\u002FUserGuide\u002FIAMBestPractices.html#create-iam-users\n * https:\u002F\u002Fgithub.com\u002Fmakethunder\u002Fawsudo\n * https:\u002F\u002Fgithub.com\u002FAdRoll\u002Fhologram\n * https:\u002F\u002Fgithub.com\u002Frealestate-com-au\u002Fcredulous\n * https:\u002F\u002Fgithub.com\u002Fdump247\u002Faws-mock-metadata\n * https:\u002F\u002Fboto.readthedocs.org\u002Fen\u002Flatest\u002Fboto_config_tut.html\n","AWS Vault 是一个用于在开发环境中安全存储和访问 AWS 凭证的工具。它通过将 IAM 凭证存储在操作系统安全密钥库中，并从中生成临时凭证供 shell 和应用程序使用，从而提高了安全性。该工具支持多因素认证（MFA），并能与 AWS CLI 配置文件无缝集成，确保了用户可以轻松管理多个 AWS 账户和服务。适用于需要频繁切换 AWS 身份或希望提高本地开发环境安全性的开发者及团队。尽管原项目已不再维护，但社区活跃的 fork 依然提供更新和支持。",2,"2026-06-11 03:02:36","top_language"]