AWS Secrets Manager
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
0warn against
Jan 19, 2026first mention
Jun 10, 2026latest mention
Why people recommend it
“But Secrets Manager just works.”
runs LLMs on AWS Bedrockon “Ask HN: Do you trust AI agents with API keys / priva…”
“Secrets Manager + KMS handles storage correctly”
Show 2 more
“This should be solved by the vaults (hashi corp / AWS Secrets Manager).”
“pulling them declaratively from a secure backend (1Pass, AWS Secrets Manager, etc)”
Caveats and dissent
No one in these comments warned against it.
Who recommends it in their own words
Threads where it came up
- PgDog is funded and coming to a database near you 1 mention
- The Vercel breach: OAuth attack exposes risk in platform environment variables 1 mention
- Ask HN: Do you trust AI agents with API keys / private keys? 1 mention
- Show HN: Hardened OpenClaw on AWS with Terraform 1 mention
- Show HN: OneCLI – Vault for AI Agents in Rust 1 mention
- Using Proxies to Hide Secrets from Claude Code 1 mention
Data: aws-secrets-manager.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 6
“we use the AWS secrets manager flowing into External Secrets Operator”
“my secrets were in Secret Manager”
“But Secrets Manager just works.”
“Secrets Manager + KMS handles storage correctly”
“This should be solved by the vaults (hashi corp / AWS Secrets Manager).”
“pulling them declaratively from a secure backend (1Pass, AWS Secrets Manager, etc)”