Comparison

Updated October 25, 2026

· ~2 min read

AWS Secrets Manager vs HashiCorp Vault vs OpenBao vs External Secrets Operator (2026)

Secrets Manager
Vault
OpenBao
External Secrets
Security
Kubernetes

HashiCorp moved Vault to the Business Source License in August 2023, and IBM completed its acquisition of HashiCorp in February 2025. The licence has not changed back. OpenBao, forked from the last MPL-licensed Vault release and now an OpenSSF project, ships regularly, 2.6.0 in July 2026, and has picked up significant adopters.

On AWS most teams never needed Vault at all: Secrets Manager stores and rotates secrets, Parameter Store holds configuration for free at standard tier, and IAM decides who reads what. On Kubernetes, the External Secrets Operator syncs from any of them into native Secrets.

At a glance

Secrets Manager

Parameter Store

HashiCorp Vault

OpenBao

External Secrets Operator

What it is

Managed secret store with rotation

Managed configuration and secret store

Secrets platform

Open-source fork of Vault

Kubernetes operator that syncs from a store

Price

$0.40 per secret-month + $0.05 per 10,000 calls

Standard tier free; advanced tier charged

Self-hosted, or HCP / Enterprise pricing

Free; you run it

Free; you run it

Licence

—

—

BSL 1.1

MPL 2.0

Apache 2.0

Dynamic secrets

Rotation via Lambda

No

Yes — databases, clouds, PKI

Yes

Generators for some sources

Operations

None

None

High — HA, unsealing, upgrades

High

Low

Where Vault and OpenBao still earn their keep

Short-lived, per-request database credentials across many systems; an internal certificate authority issuing certificates to thousands of services; encryption as a service so applications never hold keys; one secrets control plane across AWS, other clouds and data centres. If none of these describe you, running a highly available secrets cluster — with unseal keys, upgrades and its own disaster recovery — is a lot of operational weight to carry for something AWS does for a few dollars a month.

Which should you use?

Question 1 of 2

Are your workloads mostly on AWS?

Our verdict

On AWS, use Secrets Manager for credentials that rotate and Parameter Store for configuration, with IAM roles — task roles on ECS, Pod Identity on EKS — doing the access control. On Kubernetes, add the External Secrets Operator rather than a second secrets system. Reach for Vault or OpenBao when you need dynamic, short-lived credentials across many systems and clouds, PKI issuance or encryption as a service — choosing OpenBao for an open-source licence and community governance, Vault Enterprise for IBM support and its enterprise features.

Related solutions

SOC 2 Accelerator on AWS

Production-ready AWS architecture and controls designed to pass SOC 2 quickly and safely.

2–6 weeks
$15k–$35k
View

Production EKS Platform

A production-ready Kubernetes platform on EKS with Karpenter, GitOps, service mesh, full observability stack, and security hardening: built to run real workloads.

4–10 weeks
$30k–$70k
View

Get secrets and access control audit-ready

We work with startups and growing companies on AWS architecture decisions. Tell us about your situation and we will recommend the right approach.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.