Homepage
Not present in the local metadata.
brew package intelligence
awscli
Automic Vault tracks awscli because plain text secrets matters when AI agents run command-line tools on macOS.
overview
What Automic Vault knows about awscli
Official Amazon AWS command-line interface
Commands and aliases
No executable aliases were found in the local package database.
radioisotope
Plain Text Secrets
`aws` stores credentials as plaintext at ~/.aws/credentials. Our isotope securely locks them in the macOS keychain such that only the `aws` command can access them, and approval gates explicit `aws config export-credentials` output.
Local README excerpt
Automic Vault aws-cli Isotope
The isotope now uses AWS' native credential_process protocol instead of placing AWS secrets in the aws process environment.
Implementation
Migration moves plain text keys from ~/.aws/credentials to the Keychain and installs this non-secret config in ~/.aws/config:
[default]
credential_process = /usr/local/bin/av credential-helper awsThe installed /opt/awscli/bin/aws launcher runs AWS Python in isolated mode and mints a short-lived AUTOMIC_VAULT_CREDENTIAL_HELPER_TOKEN for the AWS process. The helper only answers when that token is present and the parent process is the root-controlled AWS launcher path running under isolated Python, so unrelated processes cannot call the helper directly to retrieve credentials and cannot use PYTHONPATH/sitecustomize injection to make AWS Python call it. The isotope also disables AWS CLI legacy external plugins because those plugins run as Python code inside the credential-approved AWS process.
aws config export-credentials is approval gated before it can print the credential-process result, including invocations with AWS global options before the config command.
Detection also treats aws login cache files under ~/.aws/login/cache as plain text credentials. Migration warns when those files are present because this isotope cannot safely migrate the result of aws login.
Caveats
We assume a single profile and user. If you have more complex credential requirements you should use brew:aws-vault-binary instead. It’s more cumbersome but also more capable.
AWS CLI legacy external plugins configured under [plugins] are intentionally disabled. If your workflow depends on them, use non-isotoped brew:awscli or a dedicated credential manager.
Source: data/radioisotopes/aws-cli/README.md
Coverage source
Caveats
- We only support console allocated key/secret pairs.
- We do not support `aws login` derived creds (PR welcome!). Note that if you authenticate in this manner we will continue to (correctly) report it as a secrets-hazard.
- We do not support multiple profiles (use `brew:aws-vault-binary`)
approval gates
Human review metadata for risky commands
The local approval-gate seed includes 9 rules for awscli. Covered entrypoints: aws. Severity labels: critical, high.
Example gated actions
- Official Amazon AWS command-line interface
- Export AWS credentials to stdout or process environment formats.
- Assume an AWS role and receive temporary credentials.
- Read and print a secret from AWS Secrets Manager.
- Delete S3 objects or buckets.
- Recursively mutate S3 objects.
- Create, update, or delete IAM access keys.
install metadata
Resolver facts
| Package key | brew:awscli |
|---|---|
| Last updated | 2026-05-22T09:42:20Z |
| Pulse | updated |
source trail
Generated from repository data
This page is regenerated by scripts/generate-pkg-pages.py. Deployments refuse to publish if www/pkg/ is stale relative to local package data.
Used sources
- Nucleus package database
- approval-gate seed metadata
- local isotope README
- radioisotope security manifest