L13. Secrets Management: Secrets Manager vs Parameter Store
Video generating
Check back soon for the video lesson on Secrets Management: Secrets Manager vs Parameter Store
Course outlineLesson 13 of 18
The exam's favorite decision point: when built-in automatic rotation justifies Secrets Manager's cost, and when Parameter Store's free tier is the right call.
Secrets Manager: Rotation Built In
AWS Secrets Manager exists to solve the problem of credentials that need to change on a schedule without breaking every application that depends on them. It supports automatic rotation through AWS-provided or custom Lambda rotation functions, and ships with native rotation templates for RDS, Redshift, and DocumentDB credentials, so rotating a database password on a configured schedule can use an AWS-provided Lambda template. Secrets Manager supports same-account cross-Region secret replication and separately configured cross-account access, which matters for multi-account architectures where a shared credential needs to be available in more than one place without manual copying. Pricing reflects the extra capability: you pay per stored secret plus per API call, which is worth weighing against how many secrets you actually need this level of service for.Parameter Store: Configuration and SecureString
Systems Manager Parameter Store stores configuration data and secrets as one of three parameter types: plainString, StringList, or KMS-encrypted SecureString. Standard parameters have no additional storage charge at standard throughput. Advanced parameters add larger values, higher parameter-count limits and parameter policies, with additional charges. Throughput is configured separately from the parameter tier; higher-throughput API interactions and KMS usage can incur charges. The detail that catches people out on the exam: Parameter Store has no built-in automatic rotation. A SecureString parameter is encrypted at rest, but nothing rotates its value for you; if you want scheduled rotation, you have to build and schedule that logic yourself, typically with a Lambda function and an EventBridge rule you own end to end.
Cross-Account Access and Rotation Scope
Cross-account secret access is not cross-account replication. Configure a secret resource policy, a caller identity policy and permissions on a customer managed KMS key; the AWS managed aws/secretsmanager key cannot support cross-account access. Managed secrets can use service-managed rotation without Lambda; other secrets use supported Lambda rotation functions. Verify networking and permissions for the rotation function and target database.
The Decision Rule
| Requirement | Choose |
|---|---|
| Automatic rotation needed | Secrets Manager |
| High-value credential (database password, API key for a critical system) | Secrets Manager |
| General application configuration | Parameter Store |
| Lower-cost secret storage, rotation not required | Parameter Store |
Shared Ground
Both services integrate with IAM for fine-grained access control (you can scope a policy down to a single secret or parameter path) and with CloudTrail for audit logging of supported API operations. Neither leaves you without visibility into who accessed what and when; the services also differ in replication, version staging, parameter policies and access-sharing mechanisms. Exam tip: Choose Secrets Manager when credential-value rotation is required; KMS key-material rotation alone does not change a secret value. If a question is about generic configuration with no rotation or database-credential angle, and cost is emphasized, Parameter Store Standard tier wins on price alone.
References
- Secret rotation modes
- Secret replication
- Cross-account access
- Parameter tiers
- Parameter Store pricing
Continue Learning
- ✓Secrets Manager has built-in automatic rotation, with ready-made Lambda rotation templates for RDS, Redshift, and DocumentDB credentials
- ✓Parameter Store SecureString parameters are KMS-encrypted, but Parameter Store has no built-in rotation: you must build and schedule your own rotation logic
- ✓Parameter Store tiers govern storage size, count and policies; throughput is a separate setting and KMS charges can apply
- ✓Secrets Manager replicates secrets across Regions in the same account; cross-account access needs resource, identity and customer managed KMS key permissions
- ✓Default exam heuristic: use Secrets Manager for anything needing automatic rotation or high-value credentials like database passwords, use Parameter Store for general configuration and lower-cost secret storage
1. A team needs an RDS database password to rotate on a configured schedule using an AWS-provided rotation function. Which service should they use?
2. What is a key limitation of Systems Manager Parameter Store compared to Secrets Manager?
3. A team needs to store 200 non-sensitive application configuration flags with no rotation requirement, at minimal cost. What is the most appropriate choice?