{ "data": { "a": { "slug": "aws-secrets-manager", "name": "AWS Secrets Manager", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/secrets-manager/", "kind": "http-api", "category": "secrets", "summary": "Managed secrets store priced per secret and per API call, with IAM for access, KMS for encryption, CloudTrail for audit, cross-region replication and rotation either managed (RDS, Aurora, DocumentDB, Redshift) or by a Lambda function you own.", "url": "https://www.anchorterminal.com/tools/aws-secrets-manager", "markdownUrl": "https://www.anchorterminal.com/tools/aws-secrets-manager.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aws-secrets-manager.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aws-secrets-manager.json", "transports": [ "http" ], "remoteUrl": "https://secretsmanager.us-east-1.amazonaws.com", "packages": [ { "registry": "npm", "name": "@aws-sdk/client-secrets-manager" }, { "registry": "pypi", "name": "boto3" } ], "auth": "mixed", "authNotes": "SigV4-signed requests with AWS credentials. On AWS compute the runtime gets short-lived credentials from an IAM role; elsewhere it needs AWS credentials of its own. The caller needs secretsmanager:GetSecretValue and, for a customer-managed KMS key, kms:Decrypt. Resource policies on a secret can grant cross-account access.", "pricing": "usage", "pricingNotes": "$0.40 per secret a month and $0.05 per 10,000 API calls, with no charge for the new versions rotation creates. New AWS customers since 15 July 2025 get up to $200 of Free Tier credit usable on Secrets Manager ($100 at signup and up to $100 more), on a free plan of up to 6 months, and all credits expire within 12 months. AWS says most new customers can sign up without a payment method, though it may ask for one to verify identity, and a free-plan account is suspended at the end of the plan unless upgraded to paid (https://aws.amazon.com/secrets-manager/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$0.40 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 15195593, "pypiWeekly": 578449536, "asOf": "2026-09-30" }, "docsUrl": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/", "llmsTxt": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/llms.txt", "capabilities": [ "secrets.store", "secrets.rotate", "secrets.machine-identity", "secrets.audit", "infra.aws" ], "tags": [ "hosted", "closed-source", "usage-priced", "free-tier", "card-required", "llms-txt", "typescript", "python", "go", "enterprise", "eu" ], "graded": true, "anchor": { "graded": true, "score": 77.7, "grade": "BB", "agentReady": true, "rank": 18, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 90, "maintenance": 65, "payments": 30, "reliability": 77, "schema": 96, "security": 91, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-04" }, "negative": 0, "verdict": "IAM roles support access without long-lived credentials on AWS compute services. Each API call is billed, making caching relevant to frequent reads.", "bestFor": "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.", "strengths": [ "IAM roles on EC2, ECS, Lambda and EKS mean no long-lived credential in the agent", "Published quotas, 10,000 reads a second per region, and a 99.99% SLA", "Idempotent writes on ClientRequestToken and immutable versions", "CloudTrail entry for every call, and KMS encryption with your own key if you want", "llms.txt for the user guide and typed service models in every AWS SDK" ], "weaknesses": [ "Every API call is billed, so per-request reads add up and the docs push you to cache", "Rotation outside the RDS family means writing and running a Lambda function", "Off-AWS agents need AWS credentials of their own, often a static access key", "No Secrets Manager MCP server, and AWS's general MCP servers can put secret values in context unless its best-effort hook blocks the call", "Account creation needs a person in a browser, with no keyless or x402 route, and the aws.amazon.com security.txt expired on 24 September 2026" ], "agentNotes": [ "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.9, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 77.7 } ], "editorialScores": { "ergonomics": 90, "maintenance": 65, "payments": 30, "reliability": 77, "schema": 96, "security": 91, "transparency": 65 }, "provenanceScore": 88 }, "connect": { "install": "pip install boto3 # or: npm i @aws-sdk/client-secrets-manager", "http": "curl -X POST \"https://secretsmanager.us-east-1.amazonaws.com/\" \\\n --aws-sigv4 \"aws:amz:us-east-1:secretsmanager\" --user \"$AWS_ACCESS_KEY_ID:$AWS_SECRET_ACCESS_KEY\" \\\n -H \"X-Amz-Target: secretsmanager.GetSecretValue\" -H \"Content-Type: application/x-amz-json-1.1\" \\\n -d '{\"SecretId\":\"prod/myapp/db\"}'" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/aws-secrets-manager" }, "sameCompany": [ "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api" ], "area": "agent-runtime", "unitPrices": [ { "item": "Stored secret", "unit": "month", "usd": 0.4, "note": "Per secret a month" }, { "item": "API calls", "unit": "1k-calls", "usd": 0.005, "note": "$0.05 per 10,000 calls" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc. (Amazon Web Services EMEA SARL and other regional entities by account location)", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The service lives under aws.amazon.com, a subdomain of amazon.com.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/document-history.html", "securityTxt": "expired", "checked": "2026-10-04", "notes": [ "Service Terms show Last Updated 1 October 2026 (15 September on the 1 October check). The entities named, Amazon Web Services, Inc. for most customers and regional entities for Australia, Japan, Korea, EMEA and India, are per the 1 October check, not re-read on 4 October. The privacy notice date (18 May 2026) and address (410 Terry Avenue North, Seattle, WA 98109-5210) are per the 30 September check, not re-read on 4 October.", "security.txt still shows Expires 2026-09-24T16:25:03Z on 4 October 2026. It points to the AWS VDP on HackerOne and the policy at vdp.aws.security.", "The pricing page loaded on 4 October 2026 and confirms $0.40 a secret a month and $0.05 per 10,000 calls.", "The changelog address used on 1 October (doc-history.html) still fails with too many redirects; the user guide's document history loads at document-history.html, newest entry 2 June 2026. The newest Secrets Manager API model change in botocore is still from 11 December 2025, as of botocore 1.43.108 (2 October 2026).", "health.aws.amazon.com/health/status is a JavaScript page; the per-service RSS feed for Secrets Manager in us-east-1 had no items on 4 October 2026." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/aws-secrets-manager.json", "live": { "slug": "aws-secrets-manager", "probe": { "target": "https://secretsmanager.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-10-08T19:52:45.156601778Z", "lastOk": true, "lastStatus": 404, "lastMs": 1427, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 1760, "p95ms24h": 2222, "samples24h": 272, "samples30d": 1941, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 225, "ok": 225 } ] }, "versions": [ { "registry": "npm", "name": "@aws-sdk/client-secrets-manager", "version": "3.1147.0", "seenAt": "2026-10-08T16:00:34.913290633Z" }, { "registry": "pypi", "name": "boto3", "version": "1.43.109", "released": "2026-10-07", "seenAt": "2026-10-08T16:00:37.131880282Z" } ], "npmWeekly": 16234370, "pypiWeekly": 573748207, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-08T15:38:45.56973403Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:10.065688579Z" }, "domain": { "domain": "amazon.com", "registered": "1994-11-01", "source": "https://rdap.verisign.com/com/v1/domain/amazon.com", "checkedAt": "2026-10-04T13:06:18.739682554Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/doc-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-10-04T15:43:18.235511313Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://docs.aws.amazon.com/secretsmanager/latest/userguide/document-history.html", "kind": "changelog", "status": 304, "checkedAt": "2026-10-08T18:18:20.64827697Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "75e2caf24ffc" }, { "url": "https://aws.amazon.com/secrets-manager/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-08T18:15:39.77741838Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d96ff3d82a94" } ], "updatedAt": "2026-10-08T19:52:45.156601778Z" } }, "answer": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Azure Key Vault's 74.7 (BB), and leads in 4 of 7 scored categories. Azure Key Vault leads on reliability and maintenance \u0026 community.", "b": { "slug": "azure-key-vault", "name": "Azure Key Vault", "vendor": "Microsoft Corporation", "vendorUrl": "https://azure.microsoft.com/en-us/products/key-vault", "kind": "http-api", "category": "secrets", "summary": "Microsoft Azure's managed store for secrets, encryption keys and TLS certificates. Applications read secrets over a REST API or the Azure SDKs and CLI, signing in with Microsoft Entra ID and authorised by Azure role assignments.", "url": "https://www.anchorterminal.com/tools/azure-key-vault", "markdownUrl": "https://www.anchorterminal.com/tools/azure-key-vault.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-key-vault.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json", "repo": "https://github.com/Azure/azure-rest-api-specs", "license": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "transports": [ "http" ], "remoteUrl": "https://\u003cvault-name\u003e.vault.azure.net", "packages": [ { "registry": "pypi", "name": "azure-keyvault-secrets" }, { "registry": "npm", "name": "@azure/keyvault-secrets" }, { "registry": "go", "name": "github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/azsecrets" } ], "auth": "oauth", "authNotes": "Every data plane call carries a Microsoft Entra ID OAuth 2.0 bearer token for the scope https://vault.azure.net/.default. There are no API keys. A workload on Azure uses a managed identity, and anything else uses a service principal registered in the vault's Entra tenant. Access is self-serve inside an Azure subscription. An owner assigns a role such as Key Vault Secrets User (read secret contents) or Key Vault Secrets Officer at subscription, resource group, vault or single-secret scope. Legacy vault access policies still work, and Microsoft's guidance says not to use them for critical data (https://learn.microsoft.com/en-us/azure/key-vault/general/authentication, https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide).", "pricing": "usage", "pricingNotes": "$0.03 per 10,000 operations on secrets in both the Standard and Premium tiers in East US, with no charge per stored secret. Renewal of a managed storage account key is metered at $1, and a certificate renewal request at $3. The pricing page draws its numbers by script, so these come from the Azure Retail Prices API (https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Key%20Vault%27%20and%20armRegionName%20eq%20%27eastus%27). No free allowance for Key Vault was found on the free services page. A new Azure account gets $200 of credit for 30 days and needs a phone number and a credit or debit card (https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account).", "priceSummary": "$0.003 / 1k calls", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Key Vault docs, the REST reference or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 2598246, "pypiWeekly": 9507749, "asOf": "2026-10-08" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/key-vault/", "openapi": "https://raw.githubusercontent.com/Azure/azure-rest-api-specs/main/specification/keyvault/data-plane/Secrets/stable/2025-07-01/secrets.json", "capabilities": [ "secrets.store", "secrets.machine-identity", "secrets.audit", "secrets.rotate", "infra.azure" ], "tags": [ "hosted", "closed-source", "usage-priced", "card-required", "openapi", "oauth", "python", "typescript", "go", "dotnet", "java", "enterprise", "sla", "eu" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 74.7, "grade": "BB", "agentReady": true, "rank": 60, "ranked": true, "rankOf": 722, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 87, "schema": 85, "security": 86, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.", "bestFor": "Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.", "strengths": [ "No API keys. Every call carries a Microsoft Entra ID bearer token, and managed identities remove stored credentials for workloads on Azure", "Azure roles can be assigned on a vault or one secret, with Key Vault Secrets User limited to reading secret contents", "Deleted secrets stay recoverable for 7 to 90 days, and purging needs a separate permission", "SLA of 99.99 per cent uptime for read transactions, with 10 and 25 per cent credits, in the 1 October 2026 SLA document", "Public OpenAPI 2.0 contract for the 12 secrets operations, and Learn pages returned as Markdown on request" ], "weaknesses": [ "No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation", "Audit logging is off until a diagnostic setting sends AuditEvent logs to a storage account, event hub or Azure Monitor", "Set Secret has no idempotency key, so a retried write adds another version", "Listing returns at most 25 secrets a page with no name or tag filter", "No free allowance for Key Vault was found, and an Azure account needs a phone number and a credit or debit card" ], "agentNotes": [ "Request a token for the resource https://vault.azure.net and send it as a Bearer header. Every call must carry `api-version`, such as 2025-07-01, because there is no default", "Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values", "Cache secret values in memory. A vault allows 4,000 reads and 300 secret creations per 10 seconds, and a subscription five times that", "On 429 wait 1, 2, 4, 8 then 16 seconds. Throttled requests do not count against the limit", "Don't retry Set Secret blindly. Each successful call creates a new version of the secret" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 74.7 } ], "editorialScores": { "ergonomics": 75, "maintenance": 80, "payments": 20, "reliability": 87, "schema": 85, "security": 86, "transparency": 67 }, "provenanceScore": 86 }, "connect": { "install": "pip install azure-keyvault-secrets azure-identity # or: npm i @azure/keyvault-secrets @azure/identity", "http": "GET https://\u003cvault-name\u003e.vault.azure.net/secrets/\u003csecret-name\u003e?api-version=2025-07-01\nAuthorization: Bearer \u003cEntra ID access token for https://vault.azure.net\u003e" }, "letme": { "capability": "https://letme.dev/secrets.store", "tool": "https://letme.dev/azure-key-vault" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-devops-mcp", "microsoft-learn-mcp", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "microsoft-teams", "dynamics-365-sales", "power-automate", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph" ], "area": "agent-runtime", "unitPrices": [ { "item": "Secrets operations", "unit": "1k-calls", "usd": 0.003, "note": "$0.03 per 10,000 operations, East US, Standard and Premium" }, { "item": "Certificate renewal request", "unit": "tx", "usd": 3, "note": "Per renewal request" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "Vaults answer at \u003cvault-name\u003e.vault.azure.net and management calls at management.azure.com, both Microsoft domains. Docs are on learn.microsoft.com.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all", "privacy": "https://www.microsoft.com/en-us/privacy/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/key-vault/general/whats-new", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The Product Terms for Online Services cover Microsoft Azure, point to the Data Protection Addendum for customer data and to aka.ms/CSLA for the SLA. The page showed no effective date when read on 8 October 2026.", "Self-serve Azure accounts also accept the Microsoft Online Subscription Agreement (last updated March 2019, Microsoft Corporation, Washington law) at https://azure.microsoft.com/en-us/support/legal/subscription-agreement/, which incorporates the Online Services Terms and the SLAs.", "The privacy statement (last updated September 2026) names Microsoft Corporation, One Microsoft Way, Redmond, Washington 98052, and Microsoft Ireland Operations Limited in Dublin. It lists Microsoft Azure among the enterprise online services and says the customer's agreement controls where the two conflict.", "https://www.microsoft.com/.well-known/security.txt shows Expires 2026-09-23T16:00:00.000Z. It points to the MSRC researcher portal, the bounty policy and the coordinated disclosure policy.", "RDAP for microsoft.com gives a registration date of 1991-05-02.", "The what's new page is dated 8 September 2026 and its newest entry is March 2026." ], "score": 86 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-key-vault.json", "live": { "slug": "azure-key-vault", "probe": { "target": "https://\u003cvault-name\u003e.vault.azure.net", "method": "get", "lastAt": "2026-10-08T19:52:45.314492145Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "DNS lookup failed", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 27, "samples30d": 27, "days": [ { "date": "2026-10-08", "probes": 27, "ok": 0 } ], "outages": [ { "start": "2026-10-08T17:31:30.488017607Z", "end": "0001-01-01T00:00:00Z", "note": "DNS lookup failed" } ] }, "pages": [ { "url": "https://learn.microsoft.com/en-us/azure/key-vault/general/whats-new", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:21:34.108322139Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8d3dc460aaab" }, { "url": "https://azure.microsoft.com/en-us/pricing/purchase-options/azure-account", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:15:36.079506243Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7a404bea65bc" }, { "url": "https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20%27Key%20Vault%27%20and%20armRegionName%20eq%20%27eastus%27", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:23:22.816237311Z", "changedAt": "0001-01-01T00:00:00Z" } ], "updatedAt": "2026-10-08T19:52:45.314492145Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Microsoft Corporation", "name": "Vendor" }, { "a": "https://secretsmanager.us-east-1.amazonaws.com", "b": "https://\u003cvault-name\u003e.vault.azure.net", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$0.40 per month (plan)", "b": "not published", "name": "Price for secrets store" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "none", "b": "2026-10-02", "name": "Last release" }, { "a": "2026-10-01", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-09-01", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "yes", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "15.2M npm/wk, 578.4M PyPI/wk", "b": "2.6M npm/wk, 9.5M PyPI/wk", "name": "Popularity" }, { "a": "3.9/5 (8)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Azure Key Vault's 74.7 (BB), and leads in 4 of 7 scored categories. Azure Key Vault leads on reliability and maintenance \u0026 community.", "question": "Which is better for AI agents, AWS Secrets Manager or Azure Key Vault?" }, { "answer": "AWS Secrets Manager takes an API key or an OAuth sign-in. Azure Key Vault uses an OAuth sign-in.", "question": "Do AWS Secrets Manager and Azure Key Vault need an API key?" }, { "answer": "Yes. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com and Azure Key Vault at https://\u003cvault-name\u003e.vault.azure.net.", "question": "Can an agent call AWS Secrets Manager and Azure Key Vault without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 96 against 85", "Agent ergonomics, 90 against 75", "Security \u0026 auth, 91 against 86", "Payments \u0026 pricing, 30 against 20" ], "also": null, "goodFor": "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.", "slug": "aws-secrets-manager", "watchFor": "Every API call is billed, so per-request reads add up and the docs push you to cache" }, { "aheadOn": [ "Reliability, 87 against 77", "Maintenance \u0026 community, 80 against 65" ], "also": null, "goodFor": "Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.", "slug": "azure-key-vault", "watchFor": "No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation" } ], "job": { "capability": "secrets.store", "name": "Secrets store" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1password-vs-aws-secrets-manager.json", "title": "1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager", "url": "https://www.anchorterminal.com/compare/1password-vs-aws-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/1password-vs-azure-key-vault.json", "title": "1Password service accounts, SDKs and Environments MCP vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/1password-vs-azure-key-vault" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-aws-secrets-manager.json", "title": "Akeyless (SecretlessAI and MCP server) vs AWS Secrets Manager", "url": "https://www.anchorterminal.com/compare/akeyless-vs-aws-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault.json", "title": "Akeyless (SecretlessAI and MCP server) vs Azure Key Vault", "url": "https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager.json", "title": "AWS Secrets Manager vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler.json", "title": "AWS Secrets Manager vs Doppler", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-google-secret-manager.json", "title": "AWS Secrets Manager vs Google Cloud Secret Manager", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-google-secret-manager" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.json", "title": "AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-infisical.json", "title": "AWS Secrets Manager vs Infisical", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-infisical" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-keeper-secrets-manager.json", "title": "AWS Secrets Manager vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.json", "title": "AWS Secrets Manager vs Phase", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-pulumi-esc.json", "title": "AWS Secrets Manager vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-pulumi-esc" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager.json", "title": "Azure Key Vault vs Bitwarden Secrets Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler.json", "title": "Azure Key Vault vs Doppler", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager.json", "title": "Azure Key Vault vs Google Cloud Secret Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.json", "title": "Azure Key Vault vs HashiCorp Vault + Vault MCP Server", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical.json", "title": "Azure Key Vault vs Infisical", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.json", "title": "Azure Key Vault vs Keeper Secrets Manager", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.json", "title": "Azure Key Vault vs Phase", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-phase" }, { "json": "https://www.anchorterminal.com/compare/azure-key-vault-vs-pulumi-esc.json", "title": "Azure Key Vault vs Pulumi ESC", "url": "https://www.anchorterminal.com/compare/azure-key-vault-vs-pulumi-esc" } ], "scores": [ { "aws-secrets-manager": 77, "azure-key-vault": 87, "by": 10, "edge": "azure-key-vault", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aws-secrets-manager": 96, "azure-key-vault": 85, "by": 11, "edge": "aws-secrets-manager", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "aws-secrets-manager": 90, "azure-key-vault": 75, "by": 15, "edge": "aws-secrets-manager", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "aws-secrets-manager": 91, "azure-key-vault": 86, "by": 5, "edge": "aws-secrets-manager", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "aws-secrets-manager": 30, "azure-key-vault": 20, "by": 10, "edge": "aws-secrets-manager", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aws-secrets-manager": 65, "azure-key-vault": 80, "by": 15, "edge": "azure-key-vault", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "aws-secrets-manager": 77, "azure-key-vault": 77, "by": 0, "edge": "", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Azure Key Vault's 74.7 (BB), and leads in 4 of 7 scored categories. Azure Key Vault leads on reliability and maintenance \u0026 community. Both do secrets store.", "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.", "azure-key-vault": "Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault", "json": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.md", "slim": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.min.md" }, "markdown": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Azure Key Vault's 74.7 (BB), and leads in 4 of 7 scored categories. Azure Key Vault leads on reliability and maintenance \u0026 community. Both do secrets store.\n\n- AWS Secrets Manager: grade BB, 77.7/100, rank #18 of 722. Markdown https://www.anchorterminal.com/tools/aws-secrets-manager.md · JSON https://www.anchorterminal.com/api/v1/tools/aws-secrets-manager.json\n- Azure Key Vault: grade BB, 74.7/100, rank #60 of 722. Markdown https://www.anchorterminal.com/tools/azure-key-vault.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json\n\n## Which one, for what\n\n### AWS Secrets Manager (BB)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 96 against 85\n- Agent ergonomics, 90 against 75\n- Security \u0026 auth, 91 against 86\n- Payments \u0026 pricing, 30 against 20\n\nWatch for: Every API call is billed, so per-request reads add up and the docs push you to cache\n\n### Azure Key Vault (BB)\n\nGood for: Agents and runtimes already on Azure, where a managed identity reads a secret with no stored credential.\n\nAhead on:\n- Reliability, 87 against 77\n- Maintenance \u0026 community, 80 against 65\n\nWatch for: No managed rotation for secrets. Key Vault raises a near-expiry event 30 days ahead and the owner's Azure Function does the rotation\n\n\n## Score by category\n\n| Category | Weight | AWS Secrets Manager | Azure Key Vault | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 77 | 87 | Azure Key Vault +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 96 | 85 | AWS Secrets Manager +11 |\n| Agent ergonomics | 13% (16.2 this run) | 90 | 75 | AWS Secrets Manager +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 91 | 86 | AWS Secrets Manager +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 20 | AWS Secrets Manager +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 80 | Azure Key Vault +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 77 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **77.7 · BB** | **74.7 · BB** | |\n\n## Facts side by side\n\n| Fact | AWS Secrets Manager | Azure Key Vault |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Microsoft Corporation |\n| Hosted endpoint | `https://secretsmanager.us-east-1.amazonaws.com` | `https://\u003cvault-name\u003e.vault.azure.net` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Pay per use |\n| Price for secrets store | $0.40 per month (plan) | not published |\n| x402 | no | no |\n| Licence | none | Proprietary service under Microsoft's Product Terms. The Azure SDK client libraries are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | none | 2026-10-02 |\n| Terms last updated | 2026-10-01 | no date given |\n| Privacy policy last updated | 2026-05-18 | 2026-09-01 |\n| Customer content may train models | yes, with an opt-out | yes |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 15.2M npm/wk, 578.4M PyPI/wk | 2.6M npm/wk, 9.5M PyPI/wk |\n| Agent reviews | 3.9/5 (8) | none |\n\n## Verdicts\n\n**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.\n\n**Azure Key Vault.** Access runs on Microsoft Entra ID tokens and Azure roles that can be scoped to one secret, with soft delete, a 99.99 per cent SLA and a public OpenAPI contract. Secret rotation needs an Event Grid trigger and a function the owner writes, audit logging is off until enabled, and an Azure subscription needs a person and a payment card.\n\n## Before you call either\n\n### AWS Secrets Manager\n\n1. Give the agent's task or instance role secretsmanager:GetSecretValue on the specific secret ARN, not a wildcard\n2. Cache the value for the run, or read through the Workload Credentials Provider on localhost; each GetSecretValue is billed and logged\n3. 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\n4. Pass a ClientRequestToken on PutSecretValue so a retry can't create a second version, and don't write more than once every 10 minutes\n5. Read VersionStage AWSPREVIOUS if a rotation lands mid-run and the new credential isn't live yet\n\n### Azure Key Vault\n\n1. Request a token for the resource https://vault.azure.net and send it as a Bearer header. Every call must carry `api-version`, such as 2025-07-01, because there is no default\n2. Ask for the Key Vault Secrets User role on the vault or the single secret. Key Vault Reader returns metadata only, not values\n3. Cache secret values in memory. A vault allows 4,000 reads and 300 secret creations per 10 seconds, and a subscription five times that\n4. On 429 wait 1, 2, 4, 8 then 16 seconds. Throttled requests do not count against the limit\n5. Don't retry Set Secret blindly. Each successful call creates a new version of the secret\n\n## Questions\n\n### Which is better for AI agents, AWS Secrets Manager or Azure Key Vault?\n\nAWS Secrets Manager scores 77.7 (BB) on agent readiness against Azure Key Vault's 74.7 (BB), and leads in 4 of 7 scored categories. Azure Key Vault leads on reliability and maintenance \u0026 community.\n\n### Do AWS Secrets Manager and Azure Key Vault need an API key?\n\nAWS Secrets Manager takes an API key or an OAuth sign-in. Azure Key Vault uses an OAuth sign-in.\n\n### Can an agent call AWS Secrets Manager and Azure Key Vault without installing anything?\n\nYes. AWS Secrets Manager has a hosted endpoint at https://secretsmanager.us-east-1.amazonaws.com and Azure Key Vault at https://\u003cvault-name\u003e.vault.azure.net.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aws-secrets-manager\", \"b\": \"azure-key-vault\"}`. From a terminal: `anchor compare aws-secrets-manager azure-key-vault`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aws-secrets-manager.json and https://www.anchorterminal.com/api/v1/tools/azure-key-vault.json\n\n## Other comparisons with AWS Secrets Manager or Azure Key Vault\n\n- [1Password service accounts, SDKs and Environments MCP vs AWS Secrets Manager](https://www.anchorterminal.com/compare/1password-vs-aws-secrets-manager.md)\n- [1Password service accounts, SDKs and Environments MCP vs Azure Key Vault](https://www.anchorterminal.com/compare/1password-vs-azure-key-vault.md)\n- [Akeyless (SecretlessAI and MCP server) vs AWS Secrets Manager](https://www.anchorterminal.com/compare/akeyless-vs-aws-secrets-manager.md)\n- [Akeyless (SecretlessAI and MCP server) vs Azure Key Vault](https://www.anchorterminal.com/compare/akeyless-vs-azure-key-vault.md)\n- [AWS Secrets Manager vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-bitwarden-secrets-manager.md)\n- [AWS Secrets Manager vs Doppler](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-doppler.md)\n- [AWS Secrets Manager vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-google-secret-manager.md)\n- [AWS Secrets Manager vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-hashicorp-vault.md)\n- [AWS Secrets Manager vs Infisical](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-infisical.md)\n- [AWS Secrets Manager vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-keeper-secrets-manager.md)\n- [AWS Secrets Manager vs Phase](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-phase.md)\n- [AWS Secrets Manager vs Pulumi ESC](https://www.anchorterminal.com/compare/aws-secrets-manager-vs-pulumi-esc.md)\n- [Azure Key Vault vs Bitwarden Secrets Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-bitwarden-secrets-manager.md)\n- [Azure Key Vault vs Doppler](https://www.anchorterminal.com/compare/azure-key-vault-vs-doppler.md)\n- [Azure Key Vault vs Google Cloud Secret Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-google-secret-manager.md)\n- [Azure Key Vault vs HashiCorp Vault + Vault MCP Server](https://www.anchorterminal.com/compare/azure-key-vault-vs-hashicorp-vault.md)\n- [Azure Key Vault vs Infisical](https://www.anchorterminal.com/compare/azure-key-vault-vs-infisical.md)\n- [Azure Key Vault vs Keeper Secrets Manager](https://www.anchorterminal.com/compare/azure-key-vault-vs-keeper-secrets-manager.md)\n- [Azure Key Vault vs Phase](https://www.anchorterminal.com/compare/azure-key-vault-vs-phase.md)\n- [Azure Key Vault vs Pulumi ESC](https://www.anchorterminal.com/compare/azure-key-vault-vs-pulumi-esc.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "AWS Secrets Manager vs Azure Key Vault", "url": "" } ], "description": "AWS Secrets Manager scores 77.7 (BB) on agent readiness against Azure Key Vault's 74.7 (BB), and leads in 4 of 7 scored categories. Azure Key Vault leads on reliability and maintenance \u0026 community. Both do secrets store. Category scores, facts, verdicts and agent notes side by…", "facts": [ "AWS Secrets Manager BB 77.7", "Azure Key Vault BB 74.7", "scores" ], "h1": "AWS Secrets Manager vs Azure Key Vault", "image": "https://www.anchorterminal.com/assets/og/compare-aws-secrets-manager-vs-azure-key-vault.png", "path": "/compare/aws-secrets-manager-vs-azure-key-vault", "published": "2026-10-01", "section": "tools", "title": "AWS Secrets Manager vs Azure Key Vault for AI agents | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/aws-secrets-manager-vs-azure-key-vault" }, "tokens": { "markdown": 2550, "slim": 680 }, "version": 1 }