AWS Secrets Manager
Centralized secret management service with automated credential rotation and fine-grained access control.
Centralized secret management service with automated credential rotation and fine-grained access control.
Coming from Google Cloud?
Both securely store and version API keys and database credentials, but AWS Secrets Manager features built-in automated Lambda rotation workflows for RDS and Aurora.
- Centralized encrypted storage for passwords, API tokens, and certificates.
- Automatic versioning and IAM access controls.
- Audit logging via CloudTrail / Cloud Audit Logs.
- Automated Rotation: AWS Secrets Manager includes pre-built Lambda rotation templates for RDS, Aurora, and Redshift; GCP requires custom Cloud Functions.
- Pricing: AWS charges $0.40 per secret per month + $0.05 per 10,000 API calls; GCP charges $0.06 per secret version per month + $0.03 per 10,000 calls.
What is AWS Secrets Manager?
AWS Secrets Manager helps you protect secrets needed to access your applications, services, and IT resources. The service enables you to easily rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle. Users and applications retrieve secrets with a call to Secrets Manager APIs, eliminating the need to hardcode sensitive information in plain text.
Decision Guide: When to Choose This Service
Use AWS Secrets Manager to store database credentials, API keys, and OAuth tokens with automated Lambda rotation schedules and native Amazon RDS/Aurora integration.
Do NOT use Secrets Manager for non-sensitive configuration parameters (like URLs or feature flags); use AWS Systems Manager Parameter Store Standard Tier for free string storage.
Core Architectural Pillars
Built-in Lambda functions rotate credentials on fixed schedules (e.g. every 30 days) with zero application downtime.
Multi-version secret staging (`AWSCURRENT`, `AWSPENDING`, `AWSPREVIOUS`) preventing race conditions during rotation.
Secrets are encrypted at rest with Customer Managed Keys or AWS Managed Keys.
Restrict secret retrieval based on IAM policies, resource tags, and VPC endpoints.
Local caching libraries minimize API request charges and latency.