Where should your secrets live?
Three approaches to secrets management on AWS: Secrets Manager with built-in rotation, Parameter Store with a generous free tier, and HashiCorp Vault for multi-cloud dynamic secrets. Most teams overpay - Parameter Store Standard is free for up to 10,000 parameters.
Built-in automatic rotation for RDS, Redshift, DocumentDB
Free tier, hierarchical namespacing, tight IAM integration
Dynamic secrets, multi-cloud, PKI, transit encryption
| Criteria | Secrets Manager | SSM Parameter Store | HashiCorp Vault |
|---|---|---|---|
| Automatic Rotation | Yes (RDS, Redshift, DocumentDB, Lambda) | No (manual or custom Lambda) | Yes (dynamic secrets - generated on-the-fly) |
| Free Tier | 30-day trial (new accounts) | 10,000 Standard params - free forever | Open source (self-hosted) |
| Max Size per Secret | 64 KB | 4 KB (Standard) / 8 KB (Advanced) | Unlimited |
| Cross-Account Access | Yes (resource policy) | Yes (RAM sharing, Advanced tier only, since 2024) | Yes (multi-cloud) |
| Versioning | Yes (automatic) | Yes (100 versions retained) | Yes (versioned K/V store) |
| Encryption | KMS (mandatory) | KMS (mandatory for SecureString type; String type is unencrypted) | Transit engine or external KMS |
| Audit Logging | CloudTrail | CloudTrail | Vault audit log (file/syslog/socket) |
| Operational Overhead | None (fully managed) | None (fully managed) | High (cluster management, unsealing, backups) |
If your secrets do not need automatic rotation or cross-account access, Parameter Store Standard is free and stores up to 10,000 parameters. That covers 90% of use cases.
Since the IBM acquisition, many teams are migrating from Vault to AWS-native solutions (Secrets Manager + Parameter Store) due to lower operational overhead. Only choose Vault if you genuinely need multi-cloud or dynamic secrets.
Up to 10,000 Standard parameters with no monthly cost. For non-rotating secrets (API keys, config values), Parameter Store is the most cost-effective option. Secrets Manager is worth the $0.40/secret/month only when you need automatic rotation or resource-based cross-account policies.
Regardless of which tool you choose, the worst option is hardcoded secrets. All three solutions integrate with Lambda, ECS, EKS, and EC2 to inject secrets at runtime.
These comparisons are a starting point. Every architecture is different. Contact us for tailored AWS security assessments and architectural guidance.