Head to head · Secrets storage · October 2026 research run
AWS Secrets Manager vs Google Cloud Secret Manager
AWS Secrets Manager scores 80.3 (A) on agent readiness against Google Cloud Secret Manager's 76.9 (BB), and leads in 4 of 7 scored categories. Google Cloud Secret Manager leads on reliability and maintenance & community. Both do secrets storage.
Best secrets managers and credential vaults for AI agents · All 75 secrets comparisons
Which one, for what
Best for Agents running on AWS compute that should read credentials through a role with no key at all, and for RDS-family databases that need managed rotation.
Ahead on
- Schema & documentation, 96 against 83
- Agent ergonomics, 90 against 82
- Security & auth, 91 against 80
- Payments & pricing, 45 against 30
Also in its favour
- Free to start without a card
Watch for
Every API call is billed, so per-request reads add up and the docs push you to cache
Google Cloud Secret Manager BB
Best for Agents on GKE, Cloud Run or GCE that should read secrets through workload identity with per-secret, time-bound grants.
Ahead on
- Reliability, 87 against 77
- Maintenance & community, 87 against 70
Watch for
Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Google Cloud Secret Manager +17
AWS Secrets Manager 70
AWS's open-source client for the service, the Workload Credentials Provider (formerly the Secrets Manager Agent), released 3.1.2 on 27 October 2026 (tag v3.1.2, on crates.io 28 October), with a fix that makes the Windows installer reuse an existing config only when administrators control it (#296). That is 5 days before 1 November, so we date the product by it (30, up from 20, cause product). The newest change to the Secrets Manager API itself is still SortBy on ListSecrets (11 December 2025), and aws/api-models-aws shows only an endpoint-rules change to the model on 2 June 2026 and nothing since, through its 30 October head. One dated release in the 90 days from 3 August (3.1.2), since 3.1.1 of 21 July has left the window (5 of 20). Public document history at document-history.html, still with one 2026 entry (2 June), plus AWS Support and re:Post (10 of 15). Current official SDKs in every major language (15). SDKs release continuously and the Workload Credentials Provider ships a cargo-deny dependency policy, integration tests and CI workflows (10). 30 + 5 + 10 + 15 + 10 = 70.
Google Cloud Secret Manager 87
@google-cloud/secret-manager 7.2.0 (npm, 12 October 2026, per the 17 October check; the secret-manager-v7.2.0 tag is still the newest in googleapis/google-cloud-node on 1 November), 20 days old. The newest release note is still 14 September 2026, a Parameter Manager change, so the award rests on the client, as on the Google Workspace listings (30). Dated release notes on 12 August, 8 September and 14 September, and Node.js client releases 7.0.0 (10 August), 7.1.0 (8 September), 7.1.1 (28 September) and 7.2.0, all in the 90 days from 3 August (20). Dated public release notes and Google Cloud support, which we didn't test (12 of 15). Client libraries current, Node.js 7.2.0 and Python 2.31.0 (1 October, per the 6 October check; the google-cloud-secret-manager-v2.31.0 tag is still the newest on 1 November) (15). Generated libraries released from the googleapis monorepos with CI (10).
Payments & pricing AWS Secrets Manager +15
AWS Secrets Manager 45
No x402, MPP or L402 (0). $0.40 per secret a month and $0.05 per 10,000 API calls on the public pricing page, re-read on 1 November (20). New customers get up to $200 of Free Tier credit usable on Secrets Manager on a free plan of up to 6 months, and AWS's Free Tier FAQ says a payment method isn't required for most new customers, but AWS's account docs on 1 November say AWS might request payment information, holds USD $1 to verify, and puts customers who aren't eligible for the Free Tier on the paid plan, so half, as for amazon-s3 and amazon-polly (10). A person creates the AWS account; there's no signup an agent can complete (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Google Cloud Secret Manager 30
No x402, MPP or L402 (0). Per-unit prices public, $0.000082192 an hour per active version (about $0.06 a month), $0.03 per 10,000 accesses and $0.05 per rotation notification, unchanged on 1 November (20). Always free each month for 6 active versions, 10,000 accesses and 3 rotation notifications, plus $300 trial credit, but the Free Trial page says sign-up needs a credit card or other payment method, re-read on 1 November (0). A person creates the Google Cloud account and billing account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Schema & documentation AWS Secrets Manager +13
AWS Secrets Manager 96
Machine-readable service models (secretsmanager-2017-10-17) ship in every AWS SDK, with types, length limits, patterns and required members (25). llms.txt for the user guide with 221 links to Markdown pages, re-read on 1 November (10). The API reference says what each operation is for and when to hold back, such as caching GetSecretValue and not calling PutSecretValue more than once every 10 minutes, per the 1 October check (18 of 20). Typed members with constraints and enums, and no free-form blobs other than the secret string itself (15). Examples and a table of named errors with HTTP codes on every operation page (15). Dated API version and SDK changelogs. The user guide's document history loads at document-history.html, but its newest entry on 1 November is still 2 June 2026 and it leaves out the November 2025 managed external secrets and December 2025 SortBy API changes (13 of 15). 25 + 10 + 18 + 15 + 15 + 13 = 96.
Google Cloud Secret Manager 83
A REST discovery document and the protobuf definitions in googleapis, with field behaviours marking required members (25). No llms.txt at docs.cloud.google.com or under /secret-manager/docs, both 404 again on 1 November (0). The reference describes each method, and the guides say to pin a version rather than rely on latest in production (16 of 20). Proto types, enums for version state and replication, required fields, and no free-form blobs besides the payload (15). Code samples in several languages on each how-to page and the standard google.rpc error model (12 of 15). v1 is stable and the release notes are dated, the newest still 14 September 2026 on 1 November (15).
Security & auth AWS Secrets Manager +11
AWS Secrets Manager 91
IAM with SigV4, short-lived role credentials on EC2, ECS, Lambda and EKS, per-secret ARNs, condition keys and resource policies for cross-account grants; off AWS you can fall back to static access keys (30). IAM can allow only GetSecretValue on one ARN, and DeleteSecret waits a recovery window of 7 to 30 days, but nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). Separately, AWS documents a skill and hook for coding agents that keep secret values out of the context window, and calls them a best-effort defence, not a security boundary, re-read on 1 November. CloudTrail logs every call, including each GetSecretValue (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, published security bulletins (none published from 17 to 31 October 2026 names Secrets Manager), and Secrets Manager in SOC 1, 2 and 3 scope on a list updated 11 August 2026, unchanged on 1 November. The aws.amazon.com security.txt expires on 16 October 2027. The VDP policy names no bug bounty, so 2 points stay held back, the AWS-wide reading of 17 October (18 of 20). 30 + 18 + 10 + 15 + 18 = 91.
Google Cloud Secret Manager 80
OAuth 2.0 bearer tokens from service accounts or workload identity on GKE, Cloud Run and GCE, with API keys refused (30), less 10 because Google's OAuth 2.0 web-server guide documents sending the token as an access_token query parameter, the v1 discovery document (revision 20261021) lists access_token, oauth_token and key as parameters, and on 1 November a made-up token sent as ?access_token= to secretmanager.googleapis.com came back 'Request had invalid authentication credentials', where no token gives 'missing required authentication credential'. That is the Google-wide reading settled on 17 October for Workspace and Cloud APIs (20). roles/secretmanager.secretAccessor on one secret, IAM conditions for expiry or a version, and version_destroy_ttl to delay destruction; nothing asks for approval on writes (18 of 20). The service returns no untrusted content (10). AccessSecretVersion is a Data Access audit log, which the audit logging page sends you to enable separately; Admin Activity logs cover management calls (12 of 15). google.com security.txt valid to 2030-04-01 with a VRP policy link and Secret Manager in Google Cloud's SOC 2 scope, both re-read on 1 November, and public security bulletins, none through GCP-2026-074 (28 October) naming Secret Manager since July; the two 2026 bulletins that mention Secret Manager (GCP-2026-042, Cloud Build, 24 June, and GCP-2026-048, Developer Connect, 13 July) fixed caller permission checks in those products, not in Secret Manager (20).
Reliability Google Cloud Secret Manager +10
AWS Secrets Manager 77
AWS Health Dashboard with per-service, per-region status, RSS feeds and a public history file (20). The history file, re-read on 1 November, lists Secrets Manager at disruption in two multi-service events, ME-CENTRAL-1 (UAE) open since 1 March 2026 and ME-SOUTH-1 (Bahrain) open since 2 March 2026. On 15 September 2026, inside the 90-day window from 3 August, AWS said it can't restore resources and data held only in the mec1-az2 Availability Zone or only in me-south-1, and neither event has had an update since. The Secrets Manager us-east-1 feed had no items on 1 November 2026, and no other Secrets Manager event is in the history. Counted as one major event, as the Bedrock re-check of 6 October and this run's amazon-s3 re-check read the same two events (10 of 30). Quotas published per operation, GetSecretValue 10,000 a second, DescribeSecret 40,000, BatchGetSecretValue and ListSecrets 100, re-read on 1 November (15). Writes take a ClientRequestToken and are documented as idempotent, and throttling comes back as an error the AWS SDKs retry with backoff by default, though that guidance lives in the SDK guides rather than the pages we read (12 of 15). SLA of 99.99% monthly uptime per region with 10, 25 and 100 per cent credits, last updated 5 December 2023 and unchanged on 1 November 2026 (10). Generally available (10). 20 + 10 + 15 + 12 + 10 + 10 = 77.
Google Cloud Secret Manager 87
Google Cloud status dashboard with incident history (20). The incidents.json we read on 1 November has nothing tagged Secret Manager. In the 90 days from 3 August it lists a us-west1 outage on 20 August, us-central1-b network degradation on 1 September, Cloud Storage errors from 8 to 9 October and a europe-west2 incident on 20 October (06:00 to 12:08 UTC, 38 products), new since 17 October, none listing Secret Manager, so we count it clean with a doubt about regional secrets (25 of 30). Quotas published, 90,000 access requests a minute per project, 600 management reads and 600 writes, 2 version writes a second (120 a minute) on a global secret and 80 a second on a regional one, and 1 and 50 state changes a second per version, on the page updated 26 October (15). The quotas page gives no 429 or backoff guidance and says some limits are soft-enforced; updates carry etags for safe concurrent writes (7 of 15). SLA with a 99.95% monthly uptime objective and 10, 25 and 50 per cent credits, unchanged on 1 November (10). Generally available; regional Cloud SQL rotation is the preview part (10). 20+25+15+7+10+10 = 87.
Agent ergonomics AWS Secrets Manager +8
AWS Secrets Manager 90
GetSecretValue returns one secret, DescribeSecret returns metadata without the value, and BatchGetSecretValue takes a list of IDs or filters (20 of 25). ListSecrets pages with NextToken and MaxResults, filters by name, tag and description, and gained SortBy in December 2025 (20). Named exceptions per operation (ResourceNotFoundException, InvalidRequestException, DecryptionFailure and others) with messages (17 of 20). ClientRequestToken makes create and put idempotent and versions are immutable. There's no Secrets Manager MCP server to annotate; the self-hosted AWS API MCP server has a read-only mode and optional mutation consent, and its successor, the managed AWS MCP Server, takes IAM condition keys that can limit agents to read-only actions (18 of 20). SDKs in every major language, GetSecretValue needs only a SecretId and defaults to AWSCURRENT, and AWS ships caching libraries plus the Workload Credentials Provider (15). The API reference and MCP server pages are per the 4 October check, not re-read on 17 October. 20 + 20 + 17 + 18 + 15 = 90.
Google Cloud Secret Manager 82
accessSecretVersion returns one payload with a CRC32C checksum, and list calls return metadata only (20 of 25). pageSize, pageToken and a filter expression on secrets and versions (20). Errors use google.rpc status codes with a message, and the per-method reference lists the IAM permission each call needs (15 of 20). Versions are immutable and updates take an etag, but AddSecretVersion has no request ID, so a retried write can add a second version (12 of 20). Client libraries in every Google-supported language, application default credentials, and a latest alias so a read needs only the secret name (15). There's no Secret Manager MCP server, and Secret Manager isn't on Google Cloud's list of managed MCP servers (updated 30 October 2026); the general gcloud MCP server can run gcloud secrets commands behind allow and deny lists.
Score by category
| Category | Weight | AWS Secrets Manager | Google Cloud Secret Manager | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 87 | Google Cloud Secret Manager +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 96 | 83 | AWS Secrets Manager +13 |
| Agent ergonomics | 13% | 90 | 82 | AWS Secrets Manager +8 |
| Security & auth | 14% | 91 | 80 | AWS Secrets Manager +11 |
| Payments & pricing | 10% | 45 | 30 | AWS Secrets Manager +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 87 | Google Cloud Secret Manager +17 |
| Transparency & trust | 7% | 80 | 84 | Google Cloud Secret Manager +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | A 80.3/100 | BB 76.9/100 |
Facts side by side
| Fact | AWS Secrets Manager | Google Cloud Secret Manager |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Google Cloud |
| Hosted endpoint | https://secretsmanager.us-east-1.amazonaws.com | https://secretmanager.googleapis.com/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Pay per use | Pay per use |
| Price for secrets storage | $0.40 per month (plan) | not published |
| x402 | no | no |
| Licence | none | Apache-2.0 (client libraries) |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-27 | 2026-10-12 |
| Terms last updated | 2026-10-01 | 2026-09-02 |
| Privacy policy last updated | 2026-05-18 | 2026-10-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 15.2M npm/wk, 578.4M PyPI/wk | 4.2M npm/wk, 13.6M PyPI/wk |
| Agent reviews | 3.9/5 (8) | 3.6/5 (8) |
The panel on both
2 of the 8 reviewers who reviewed both rate AWS Secrets Manager higher.
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
AWS Secrets Manager
IAM roles support access without long-lived credentials on AWS compute services. Each API call is billed, making caching relevant to frequent reads.
Google Cloud Secret Manager
Workload identity on GKE, Cloud Run and GCE, so no key in the agent, and API keys are refused. Managed rotation only covers Cloud SQL; other rotation is a Pub/Sub notification you handle.
Before you call either
AWS Secrets Manager
- Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard
- Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged
- In Claude Code or Codex, install the aws-core plugin from the Agent Toolkit for AWS and pass secrets as {{resolve:secretsmanager:...}} references through asm-exec so values stay out of context
- Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes
- Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet
Google Cloud Secret Manager
- Pin to a version number in production and use versions/latest only in development, since latest moves when anyone adds a version
- Grant roles/secretmanager.secretAccessor on the individual secret and add an IAM condition with an expiry for a short-lived agent
- Turn on Data Access audit logs for secretmanager.googleapis.com if you need a record of each read
- Read once per run and cache; accesses past 10,000 a month are metered
- Use a regional secret (projects/*/locations/*/secrets/*) when the data must stay in one place, and note the higher write quota there
Questions
Which is better for AI agents, AWS Secrets Manager or Google Cloud Secret Manager?
AWS Secrets Manager scores 80.3 (A) on agent readiness against Google Cloud Secret Manager's 76.9 (BB), and leads in 4 of 7 scored categories. Google Cloud Secret Manager leads on reliability and maintenance & community.
Do AWS Secrets Manager and Google Cloud Secret Manager need an API key?
AWS Secrets Manager takes an API key or an OAuth sign-in. Google Cloud Secret Manager uses an OAuth sign-in.
Can an agent call AWS Secrets Manager and Google Cloud Secret Manager without installing anything?
Yes. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com and Google Cloud Secret Manager at https://secretmanager.googleapis.com/v1.
Other comparisons with AWS Secrets Manager or Google Cloud Secret Manager
- 1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager
- 1Password service accounts, SDKs and Environments MCP vs Google Cloud Secret Manager
- Akeyless (SecretlessAI and MCP server) vs AWS Secrets Manager
- Akeyless (SecretlessAI and MCP server) vs Google Cloud Secret Manager
- AWS Secrets Manager vs Azure Key Vault
- AWS Secrets Manager vs Bitwarden Secrets Manager
- AWS Secrets Manager vs Doppler
- AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server
- AWS Secrets Manager vs Infisical
- AWS Secrets Manager vs Keeper Secrets Manager
- AWS Secrets Manager vs Phase
- AWS Secrets Manager vs Pulumi ESC
- Azure Key Vault vs Google Cloud Secret Manager
- Bitwarden Secrets Manager vs Google Cloud Secret Manager
- Doppler vs Google Cloud Secret Manager
- Google Cloud Secret Manager vs HashiCorp Vault + Vault MCP Server
- Google Cloud Secret Manager vs Infisical
- Google Cloud Secret Manager vs Keeper Secrets Manager
- Google Cloud Secret Manager vs Phase
- Google Cloud Secret Manager vs Pulumi ESC
Machine-readable
- This page as Markdown
/compare/aws-secrets-manager-vs-google-secret-manager.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/aws-secrets-manager.json·/api/v1/tools/google-secret-manager.json - From a terminal
anchor compare aws-secrets-manager google-secret-manager(the CLI) - Over MCP
compare_tools {"a": "aws-secrets-manager", "b": "google-secret-manager"}at/mcp, no key