AWS Secrets Manager Alternatives

Seven secrets managers for teams leaving AWS Secrets Manager, with what each one bills and where it is weaker than AWS.

The best AWS Secrets Manager alternative depends on why you are leaving. If your secrets now live in AWS, GitHub Actions, Vercel and a second cloud, Infisical gives them one home, syncs them back into AWS, and its core is MIT-licensed if you want to host it yourself. If the problem is developer experience, Doppler is the smoothest workflow, free for 3 users. If you need dynamic database credentials and full control, HashiCorp Vault or its open source fork OpenBao. To cut the bill without leaving a cloud console, Google Cloud Secret Manager charges $0.06 per active version and Parameter Store stores standard parameters at no additional charge. Bitwarden Secrets Manager and Azure Key Vault complete the list.

For reference, AWS Secrets Manager costs $0.40 per secret per month plus $0.05 per 10,000 API calls, and every replica in another region is billed as a separate secret. Below: why teams leave, how each alternative is billed, where it is weaker than AWS, and the traps that make a cheap vault expensive.

Romain CochardCEO of Hack'celeration
Updated 20267alternatives compared5criteria each2026pricing checked

The ranking is editorial: a sponsored placement is always flagged on its card, and no affiliate link changes a score.

The honest take

Why teams are leaving AWS Secrets Manager

AWS Secrets Manager does its job: it encrypts secrets with KMS, rotates database credentials and answers every call through IAM. Teams rarely leave because it breaks. They leave because of how the bill grows with each copy of a secret, because everything outside AWS has to come and fetch from it, and because rotation beyond the managed cases is code they maintain. Here are the five reasons that come up most, each with the fact behind it.

A price per secret that multiplies with every copy

Storage costs $0.40 per secret per month, prorated by the hour, and a replica in another region is a distinct secret billed at the same $0.40. A team with 40 secrets in one region pays $16 a month; replicate them to two more regions and the same 40 values cost $48. AWS's own pricing example puts 1,500 secrets at $604.50 a month and 10,000 secrets at $4,060. In a 2026 write-up, one developer found secrets were the largest line of a side project: 12 secrets across two environments cost $4.80 a month, against $1.20 for all the compute.

Everything outside AWS has to come and fetch

Access goes through IAM. A Lambda function or an ECS task reads a secret with its role, which is the strength of the service. A GitHub Actions job, a Vercel deployment, a laptop or a workload on another cloud needs AWS credentials or a federation setup first, then a call to the AWS API. Teams that grew beyond one cloud end up with secrets in AWS, in their CI, in their hosting platform and in a .env file, with no single place that says where a value lives and who reads it. If you automate on AWS with Make, the AWS KMS secrets integration for Make shows the IAM setup involved.

Rotation outside the managed cases is code you own

Managed rotation covers secrets that AWS services handle for you, and managed external secrets cover credentials from a list of integration partners such as Salesforce; neither uses a Lambda function. For other types of secrets, rotation uses a Lambda function that updates both the secret and the database or service behind it. That function is yours to deploy, monitor and fix, and its invocations add to the bill.

API calls add up on chatty workloads

Every read costs $0.05 per 10,000 calls. A fleet that fetches its secrets on every request instead of caching them can turn the call line into the larger one.

Parameter Store already covers the simple cases

Many teams discover that a large share of their secrets never rotate: API keys, webhook tokens, configuration flags. AWS Systems Manager Parameter Store keeps standard parameters at no additional charge, up to 10,000 per account and region, with SecureString encryption through KMS. A common view among AWS developers follows: pay for Secrets Manager only when you need replication, very large secrets or cross-account sharing, and keep the rest as parameters.
1
Best all-round replacement

Infisical

4.4/5

Infisical is a secrets platform built around projects and environments: each project holds environments such as development, staging and production, and every secret has a value per environment. Developers pull them with the CLI into a local process, CI jobs read them through a machine identity, and secret syncs push them to the places that still expect them, including AWS Secrets Manager itself. That last point is why it ranks first: you can move the source of truth without rewriting the Lambda functions that read from AWS today.

The pricing counts identities, and an identity is any principal that authenticates, human or machine. Free covers 5 identities and 3 environments with unlimited projects and 10 secret syncs. Pro costs $20 per identity per month billed annually, or $23 month to month. The 5 free identities do not carry over: once you upgrade, every identity is billed, so a team of 6 developers and 4 CI identities on Pro pays $200 a month on the annual plan, not $100. The core platform is MIT-licensed and free to self-host on Docker, Kubernetes or a Linux VM, which removes the per-identity bill if you run it yourself and stay on the MIT features; Enterprise features such as SSO need a self-hosted license, priced by sales. Teams leaving Doppler for it will find the steps in our Doppler switch guide.

Read the plan grid before you commit to rotation. Dynamic secrets are only on Advanced and Enterprise, and on Pro, rotation covers public databases only. A team that leaves AWS for its rotation Lambdas should price Advanced, not Pro. Machine identities count as seats, so a fleet of 30 services each with its own identity costs more than a 5-person team.

Standout features
  • Secret syncs back into AWS Secrets Manager
  • MIT-licensed core you can self-host
  • Projects and environments out of the box
+Pros
  • ✓Keeps AWS workloads reading from AWS during the move
  • ✓Free plan large enough for a small team
  • ✓Self-hosting the MIT core removes the per-identity bill
−Cons
  • ✗Machine identities are billed like users
  • ✗Dynamic secrets only on Advanced and Enterprise
  • ✗Rotation on Pro limited to public databases
Infisical vs AWS Secrets Manager
CriterionInfisicalAWS Secrets Manager
Pricing unitPer identity (human or machine)Per secret, per replica
Free plan5 identities, 3 environmentsFree Tier credits for new AWS customers
Outside AWSCLI, CI, syncs to many platformsAWS API with IAM credentials
Self-hostingYes, MIT-licensed coreNo
Verdict

The default pick when secrets have outgrown one cloud. If every workload stays on AWS and only the bill hurts, look at Parameter Store or Google Cloud Secret Manager pricing first.

See Infisical pricing → →
2
Best developer workflow

Doppler

4.2/5

Doppler organizes secrets by project and config (development, staging, production, plus branch configs), and developers run their app through the Doppler CLI so secrets arrive as environment variables without a file on disk. Automated syncs then push each config to the platforms that run the code: AWS Secrets Manager, AWS Parameter Store, GCP Secret Manager, Azure Key Vault, GitHub Actions, Vercel, Heroku, Render and more.

The bill counts people, not secrets or machines: non-human identities and AI agents ride free. The Developer plan is free for 3 users, then $8 a month per additional user. Team costs $21 per user per month, with a 14-day trial. A 10-developer team on Team pays $210 a month, whatever the number of secrets, environments or services, which is the opposite of the AWS model.

The limits sit in the plan grid. The Developer plan keeps the activity log for 3 days only, so an audit trail worth the name starts on Team. Team includes 100 config syncs; custom roles, user groups and a higher sync limit (500 instead of 100) are add-ons at $9 per seat per month each, so a team that needs all three pays $48 per user per month, not $21. Dynamic secrets, enterprise key management and the on-premises deployment all come with the Enterprise plan.

Standout features
  • Machines and AI agents free, only people billed
  • Syncs to AWS, GCP, Azure, GitHub, Vercel
  • CLI injects secrets without a .env file
+Pros
  • ✓CLI-first workflow developers adopt quickly
  • ✓Bill does not grow with secrets or services
  • ✓Free for up to 3 users
−Cons
  • ✗Activity log kept 3 days on the free plan
  • ✗Roles, groups and syncs past 100 cost $9 per seat each
  • ✗Dynamic secrets only on Enterprise
Doppler vs AWS Secrets Manager
CriterionDopplerAWS Secrets Manager
Pricing unitPer user; machines freePer secret, per replica
Free plan3 usersFree Tier credits for new AWS customers
Local developmentCLI injects variablesAWS CLI or SDK calls
Dynamic secretsEnterprise planRotation through managed rotation or Lambda
Verdict

The pick when developers, not infrastructure, are the problem. If you need to host the vault yourself or issue dynamic credentials on a budget, take Infisical or OpenBao instead.

See Doppler pricing → →
3
Best for dynamic secrets and full control

HashiCorp Vault / OpenBao

4.1/5

Vault is the reference most guides start with, and for good reason: its database secrets engine generates credentials dynamically, based on configured roles, so a service gets a username and password that expire instead of a static secret someone rotates. It runs the same way on any cloud or in your own data center, handles PKI and encryption as a service, and authenticates workloads through AWS IAM, Kubernetes and other methods. If you left AWS Secrets Manager to cut the number of long-lived secrets rather than the bill, Vault is the destination.

Licensing changed the picture. Vault 1.15.0 and later ship under the Business Source License, which allows production use but not offering it to third parties as a competing hosted service. OpenBao, a fork of Vault managed by the Linux Foundation's OpenSSF, stays under the Mozilla Public License 2.0 and is free. The managed route is HCP Vault Dedicated, now listed as IBM Vault Dedicated: a development Extra Small cluster lists at $0.61644 an hour, about $450 for a 730-hour month, and a production Small cluster at $1.57799 an hour on Essentials, about $1,152 a month, plus $72.92 per client per month.

The cost that matters is people. A self-run Vault or OpenBao cluster needs storage, unsealing, upgrades, backups and someone on call. For fewer than a few hundred secrets that never rotate, it is more machine than you need. If you want dynamic secrets without running a cluster, Akeyless, which several comparison guides add, sells them as SaaS: its free plan covers 5 clients, 500 static secrets and 5 dynamic secrets, and paid plans are quoted on an annual client count, with any overage invoiced at the end of the 12-month contract. If you run Vault today and want out, our HashiCorp Vault switch guide lists the destinations.

Standout features
  • Dynamic database credentials on demand
  • Same vault on every cloud and on-premises
  • OpenBao fork under MPL 2.0, free
+Pros
  • ✓Short-lived credentials instead of rotation code
  • ✓Widest set of auth methods and engines
  • ✓No lock-in to one cloud's IAM
−Cons
  • ✗Running a cluster is a job in itself
  • ✗Vault itself is under the Business Source License
  • ✗Managed HCP clusters start near $450 a month
HashiCorp Vault / OpenBao vs AWS Secrets Manager
CriterionHashiCorp Vault / OpenBaoAWS Secrets Manager
Pricing unitSelf-run free; HCP per cluster-hour plus clientsPer secret, per replica
Dynamic secretsDatabase secrets engineRotation through managed rotation or Lambda
Where it runsAny cloud, on-premisesAWS regions
LicenceVault BSL; OpenBao MPL 2.0Proprietary managed service
Verdict

The pick for platform teams that want dynamic credentials everywhere. Without someone to operate it, a managed tool such as Infisical or Doppler will cost less in total.

See OpenBao → →
4
Cheapest per secret on a hyperscaler

Google Cloud Secret Manager

4.0/5

Google Cloud Secret Manager is the closest like-for-like replacement on another hyperscaler: secrets with versions, IAM permissions per secret, audit logs, and rotation schedules that send a notification to Pub/Sub when a secret is due. Your own code, often a Cloud Run job or a Cloud Function, then changes the value, which is the same pattern as the AWS Lambda rotation.

The pricing is where it wins. An active secret version costs $0.06 per location per month, and the first 6 versions are free each month across the billing account. Access operations cost $0.03 per 10,000, with 10,000 free, and rotation notifications $0.05 each beyond the 3 free. The replication rule is the trap AWS users miss in reverse: an automatic replication policy is billed as a single location, while AWS bills every replica as a new secret. 40 secrets with one active version each come to $2.04 a month after the free versions, against $16 on AWS before any replica.

Two details change the count. The price is per active version, and a disabled version still counts as active: only destroying the versions you no longer read takes them off the bill. With user-managed replication, each location you choose is billed. And it is still a single-cloud service: reaching it from AWS or a CI job means Google credentials or workload identity federation, the same friction you had with IAM. Weighing Google as a whole? Read our guide to leaving Google Cloud before you commit.

Standout features
  • Automatic replication billed as one location
  • $0.06 per active version, 6 free
  • Rotation schedules through Pub/Sub
+Pros
  • ✓Storage price far below AWS per secret
  • ✓Free monthly allowance covers small projects
  • ✓Familiar model for AWS users
−Cons
  • ✗Disabled versions are billed until destroyed
  • ✗Rotation logic is still your code
  • ✗Reaching it from outside Google needs federation
Google Cloud Secret Manager vs AWS Secrets Manager
CriterionGoogle Cloud Secret ManagerAWS Secrets Manager
Storage price$0.06 per active version per location$0.40 per secret
ReplicasAutomatic replication billed as one locationEach replica billed as a secret
API calls$0.03 per 10,000, 10,000 free$0.05 per 10,000
RotationPub/Sub notification, your codeManaged rotation or Lambda
Verdict

The pick when your workloads are moving to Google Cloud anyway. If they stay on AWS, Parameter Store saves as much without a second cloud account.

See Secret Manager pricing → →
5
Best if you stay on AWS

AWS Systems Manager Parameter Store

3.9/5

Parameter Store is the alternative already in your AWS account. It holds configuration values and secrets as parameters, encrypted with KMS when you choose the SecureString type, and your IAM roles read them through the Systems Manager API. Standard parameters come at no additional charge, up to 10,000 per account and region with a 4 KB value. Advanced parameters cost $0.05 per parameter per month, go up to 100,000 per account and region, hold 8 KB and accept parameter policies such as an expiration date.

The saving is direct: 200 static API keys cost $80 a month in Secrets Manager and nothing as standard parameters. The higher throughput setting, which you need past the default rate, bills $0.05 per 10,000 API interactions, the same rate as Secrets Manager calls.

What you give up is everything that made Secrets Manager a secrets product. AWS lists credential rotation as none for Parameter Store, and recommends Secrets Manager when you need automatic rotation and cross-region replication. Standard values also stop at 4 KB on Standard against 65,536 bytes per secret in Secrets Manager. It is still an AWS service: GitHub Actions, Vercel or a second cloud need AWS credentials to read anything.

Standout features
  • Standard parameters at no additional charge
  • Same IAM roles and KMS keys you use today
  • Advanced tier with expiration policies
+Pros
  • ✓Biggest saving with the smallest change
  • ✓No new vendor or account
  • ✓Works next to Secrets Manager
−Cons
  • ✗Credential rotation left to you
  • ✗4 KB limit on standard parameters
  • ✗Still AWS-only for every consumer
AWS Systems Manager Parameter Store vs AWS Secrets Manager
CriterionAWS Systems Manager Parameter StoreAWS Secrets Manager
Storage priceStandard at no additional charge; Advanced $0.05$0.40 per secret
Value size4 KB (Standard), 8 KB (Advanced)65,536 bytes
RotationLeft to youManaged rotation or Lambda
Limit per region10,000 Standard, 100,000 Advanced500,000 secrets
Verdict

The pick for static secrets on an AWS-only stack. As soon as you need rotation, replication or access from outside AWS, keep Secrets Manager for those secrets or move to Infisical.

See Parameter Store pricing → →
6
Best budget pick with end-to-end encryption

Bitwarden Secrets Manager

3.8/5

Bitwarden Secrets Manager comes from the open source password manager (see our business password manager ranking) and applies the same end-to-end encryption to machine secrets. Secrets live in projects, machine accounts give a pipeline or a server scoped access, and ready-made integrations cover GitHub Actions, GitLab CI/CD and Jenkins, with a CLI and SDKs for the rest and per-namespace scoping for Kubernetes. Every access is in the event log. If you automate with n8n, the Bitwarden integration for n8n shows what can be wired, and our Bitwarden switch guide covers the reverse trip.

Teams costs $6 per user per month, against $21 for Doppler Team and $20 for Infisical Pro. Free gives 2 users, 3 projects and 3 machine accounts with unlimited secrets. Teams is billed on an annual subscription, with unlimited projects and up to 20 machine accounts, then $1 per additional machine account. Enterprise costs $12 per user per month and adds SSO, SCIM and 50 machine accounts. Self-hosting is advertised for Enterprise but still marked as coming soon for Secrets Manager, so confirm it before you plan around it. A team of 8 with 25 machine accounts on Teams pays $53 a month: $48 for users and $5 for the 5 extra machine accounts.

The trade-off is depth. Bitwarden is a store and distribution layer for static secrets: its plan comparison covers storage, sharing, projects, machine accounts and export, while the AWS rotation Lambdas you run today stay your job. Its list of platform integrations is shorter than Doppler's or Infisical's, so moving off AWS means switching each workload to the Bitwarden CLI, SDK or integration it reads from.

Standout features
  • End-to-end encrypted, open source
  • Unlimited secrets on every plan
  • GitHub Actions, GitLab and Jenkins integrations
+Pros
  • ✓$6 per user per month on Teams
  • ✓Free plan covers a two-person project
  • ✓Enterprise adds SSO, SCIM and 50 machine accounts
−Cons
  • ✗Built for static secrets, rotation stays your job
  • ✗Machine accounts capped per plan
  • ✗Each workload must switch to the Bitwarden CLI or SDK
Bitwarden Secrets Manager vs AWS Secrets Manager
CriterionBitwarden Secrets ManagerAWS Secrets Manager
Pricing unitPer user, machine accounts included up to a capPer secret, per replica
Free plan2 users, 3 projects, 3 machine accountsFree Tier credits for new AWS customers
EncryptionEnd-to-end, zero-knowledgeKMS keys in your account
Self-hostingEnterprise planNo
Verdict

The pick for a small team that wants a cheap, encrypted store for static secrets. If you rely on rotation today, choose Infisical Advanced or Vault instead.

See Bitwarden Secrets Manager → →
7
Best for Microsoft shops

Azure Key Vault

3.7/5

Azure Key Vault stores secrets, keys and certificates behind Microsoft Entra ID permissions, with Standard vaults using software-protected keys and Premium vaults adding HSM-protected keys. For a company that runs Microsoft 365, Entra ID and Azure subscriptions already, it puts application secrets under the same identity and the same audit as everything else. For the migration itself, our Azure agency page explains how we run these moves.

The billing model is the opposite of AWS: Azure bills secret operations, at $0.03 per 10,000 transactions on Standard and Premium, and the price sheet lists operations, not secrets stored. A vault holding 500 secrets read 300,000 times a month comes to $0.90. Keys and certificates carry their own lines: an HSM-protected RSA 2,048-bit key costs $1 per key per month plus transactions, a certificate renewal request $3, and an automated key rotation $1 per scheduled rotation.

The weak points are familiar. Secret rotation follows the pattern Microsoft documents: an Event Grid event fires near expiry and an Azure Function sets the new value, the same kind of code you run on AWS. And it is an Azure service, so reaching it from AWS, GitHub Actions or a laptop means Entra credentials or federation.

Standout features
  • Billed per operation, not per secret
  • Keys, secrets and certificates in one vault
  • HSM-protected keys on Premium
+Pros
  • ✓Very low cost for many rarely read secrets
  • ✓One identity model with Microsoft 365
  • ✓$200 credit to run the migration pilot
−Cons
  • ✗Secret rotation runs in your own function
  • ✗Azure-only for every consumer
  • ✗Separate charges for HSM keys and certificates
Azure Key Vault vs AWS Secrets Manager
CriterionAzure Key VaultAWS Secrets Manager
Pricing unit$0.03 per 10,000 operations$0.40 per secret plus calls
Keys and certificatesSame vault, HSM on PremiumSeparate services (KMS, ACM)
RotationEvent Grid and a functionManaged rotation or Lambda
IdentityMicrosoft Entra IDAWS IAM
Verdict

The pick when the company already runs on Microsoft. For a team that works across clouds, Infisical or Doppler will reach more places with less glue code.

See Key Vault pricing → →
At a glance

7 AWS Secrets Manager alternatives compared

Start with the "Main edge over AWS Secrets Manager" column: each tool fixes a different reason to leave. Prices are in US dollars at the smallest paid unit each vendor lists.

Best forMain edge over AWS Secrets ManagerFree planTeam sizeVisit
1InfisicalBest all-round replacementSyncs back to AWS, MIT self-hosting4.4/5Free; $20/identity/mo (annual)✓Multi-cloud teamsVisit →
2DopplerBest developer workflowMachines free, people billed4.2/5Free for 3; $21/user/mo✓Product teamsVisit →
3HashiCorp Vault / OpenBaoBest for dynamic secrets and full controlDynamic credentials on any cloud4.1/5OpenBao free; HCP from $0.61644/hr✓Platform teamsVisit →
4Google Cloud Secret ManagerCheapest per secret on a hyperscalerAutomatic replication billed as one location4.0/5$0.06/version/mo, 6 free✓Google Cloud usersVisit →
5AWS Systems Manager Parameter StoreBest if you stay on AWSStandard parameters at no additional charge3.9/5Standard: no additional charge✓AWS-only teamsVisit →
6Bitwarden Secrets ManagerBest budget pick with end-to-end encryptionEnd-to-end encrypted, $6 per user3.8/5Free; $6/user/mo (annual)✓Small teamsVisit →
7Azure Key VaultBest for Microsoft shopsBilled per operation, not per secret3.7/5$0.03/10,000 operations—Microsoft shopsVisit →

Scores are editorial and are the plain average of the five criteria on each card. Prices exclude taxes. Infisical and Bitwarden prices are for annual billing; Infisical Pro is $23 per identity month to month.

Is your tool missing from this page? Email us: hello@hackceleration.com

Buyer's guide

How to choose an AWS Secrets Manager alternative

A secrets manager stores the values your software needs to authenticate (database passwords, API keys, tokens, certificates), encrypts them at rest, and hands each one only to the people and machines allowed to read it, with a log of every access. AWS Secrets Manager does this inside AWS: IAM decides who reads, KMS encrypts, CloudTrail records. Every alternative on this page does the same job; what changes is who it can reach, how it rotates, and what it counts on the invoice.

Four units come back in every quote. A secret is one named value, sometimes a JSON document holding several keys: AWS bills per secret and per replica, so packing related keys into one JSON secret lowers the count. A version is one stored value of a secret over time: Google bills per active version, enabled or disabled, so old versions cost money until you destroy them. An identity or seat is a person or a machine that authenticates: Infisical bills both, Doppler bills people only, Bitwarden bills people and caps machine accounts. An operation or API call is one read or write: AWS charges $0.05 per 10,000 and Azure $0.03 per 10,000, which only matters if services skip caching.

Before you compare, write down three numbers: how many distinct values you store, how many copies of each exist across environments, accounts and regions, and how many people and machines read them. Then demand four things of any candidate: a way to reach every consumer you have (CI, hosting platform, other clouds, laptops), a rotation story for the credentials that rotate today, an audit log kept long enough for your auditors, and an export so you can leave.

1. Count values, not secrets

On AWS, one database password in three environments and two regions is six billed secrets. List the distinct values first, then price each candidate on its own unit. A team with 60 values, 3 environments and 2 regions pays for 360 secrets on AWS, $144 a month, before API calls.

2. Map who reads each secret

Split consumers into AWS workloads, CI jobs, hosting platforms, other clouds and people. If most are AWS workloads, Parameter Store or a sync tool keeps them unchanged. If most are outside AWS, a platform that syncs to them, such as Infisical or Doppler, removes the credentials you hand out today.

3. Price rotation honestly

List every rotation Lambda you run. Dynamic secrets on Vault or OpenBao replace them; on Infisical they need the Advanced plan; on Google and Azure rotation is still your code, triggered by Pub/Sub or Event Grid. A tool without rotation is fine for static keys only.

4. Plan the move in two steps

Import secrets into the new tool, then sync them back into AWS Secrets Manager so existing Lambda and ECS code keeps reading from AWS. Switch consumers one by one, then delete the AWS copies. Our guide to leaving AWS covers the wider exit if the whole stack is moving.

  • Distinct values, copies per environment, account and region
  • Every consumer outside AWS
  • Rotation Lambdas to replace
  • Audit log retention on the plan you will buy
  • Machine identities and how they are billed
  • Export format and a sync back to AWS during the move
Before you sign

Four traps that make a cheap vault expensive

These four come from the pricing pages and from developers who made the switch.

01

Machine identities billed as seats

Infisical counts every machine identity like a person. 30 services each with its own identity, plus 6 developers, is 36 identities on Pro: $720 a month on the annual plan. Group services under fewer identities, or compare with Doppler, where machines ride free.

02

Add-ons that double a per-user price

Doppler Team is $21 per user, but custom roles, user groups and a sync limit raised from 100 to 500 are each $9 per seat per month on top. With all three, a 10-person team pays $480 a month instead of $210. Ask for the quote with the features you actually need.

03

A managed cluster that runs every hour

HCP Vault Dedicated bills per cluster-hour, whether anyone reads a secret or not. The development Extra Small cluster alone comes to about $450 a month, and production starts on a Small cluster near $1,152 a month before clients. OpenBao on your own machines removes the licence but not the on-call duty.

04

Paying twice during the migration

While consumers switch one by one, secrets live in both tools and you pay both. AWS schedules a deleted secret for deletion after a recovery window of at least seven days and stops charging for it once it is scheduled, so mark each AWS copy for deletion as soon as its last consumer has moved, instead of waiting for a cleanup sprint.

FAQ

Frequently asked questions about AWS Secrets Manager alternatives

  • Is AWS Parameter Store a replacement for Secrets Manager?
    For static secrets, often yes: standard parameters come at no additional charge, encrypted with KMS as SecureString. AWS lists credential rotation as none for Parameter Store and standard values stop at 4 KB, so most teams keep Secrets Manager for rotated database credentials and move static keys.
  • How do I reduce my AWS Secrets Manager bill without leaving?
    Store related keys of one service in a single JSON secret instead of one secret per key, since AWS bills per secret. Replicate only the secrets a second region actually reads, because each replica is billed at $0.40. Cache values in each service to cut API calls.
  • Is AWS KMS the same as Secrets Manager?
    They do different jobs. KMS creates and manages encryption keys and encrypts or decrypts data with them. Secrets Manager and Parameter Store store your passwords and API keys as values you retrieve, and use KMS keys to encrypt those values at rest.
  • How many secrets can AWS Secrets Manager store?
    Up to 500,000 secrets per AWS account and Region, a quota AWS marks as not adjustable, with GetSecretValue reads capped at 10,000 per second per Region. Each secret keeps its versions too: Secrets Manager removes unlabeled versions once there are more than 100, but never those created in the last 24 hours, so updating a value more often than every 10 minutes piles up versions.
  • Is HashiCorp Vault still open source?
    Vault 1.15.0 and later ship under the Business Source License, a source-available licence that allows production use but bars offering Vault as a competing hosted service. OpenBao, the fork managed by the Linux Foundation's OpenSSF, keeps the open source Mozilla Public License 2.0.
  • Should I store secrets in environment variables?
    Injecting them as environment variables at start-up is common and fine for most apps, which is how the Doppler and Infisical CLIs work. The risk is the .env file left on disk or committed to Git; keep the values in a manager and inject them at run time instead.
  • Can I encrypt secrets in Git instead of using a secrets manager?
    Yes, with tools such as SOPS or Sealed Secrets for Kubernetes, which store encrypted values next to your code. They cost nothing, but you still manage the encryption keys, and there is no central access log or revocation per person, so they suit small teams and GitOps setups.
  • Does AWS Secrets Manager have a free tier?
    Not as a free monthly allowance of secrets. Since 2025, new AWS customers get up to $200 in Free Tier credits that apply to eligible services, Secrets Manager included; the free plan lasts 6 months after account creation, and all credits must be used within 12 months. After that, every secret is billed at $0.40 a month.
Hack'celeration Lab

Get the next breakdown in your inbox

No spam. Unsubscribe anytime.