secrets-manager
Securely store, retrieve, and rotate credentials and API keys in AWS Secrets Manager.
Install
mkdir -p .claude/skills/secrets-manager && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5529" && unzip -o skill.zip -d .claude/skills/secrets-manager && rm skill.zipInstalls to .claude/skills/secrets-manager
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
AWS Secrets Manager for secure secret storage and rotation. Use when storing credentials, configuring automatic rotation, managing secret versions, retrieving secrets in applications, or integrating with RDS.Key capabilities
- →Store encrypted data like database credentials and API keys
- →Retrieve secret values using AWS CLI or boto3
- →Configure automatic rotation for secrets using Lambda functions
- →Manage multiple versions of a secret, including AWSCURRENT and AWSPREVIOUS
- →Update existing secret values
- →Integrate with AWS services like RDS for secret rotation
How it works
Secrets Manager stores encrypted data, which can be retrieved or updated, and supports automatic rotation for credentials using Lambda functions.
Inputs & outputs
When to use secrets-manager
- →Store production database credentials
- →Configure automatic rotation for RDS secrets
- →Retrieve API keys in application code
- →Manage secret versioning
About this skill
AWS Secrets Manager
AWS Secrets Manager helps protect access to applications, services, and IT resources. Store, retrieve, and automatically rotate credentials, API keys, and other secrets.
Table of Contents
Core Concepts
Secrets
Encrypted data stored in Secrets Manager. Can contain:
- Database credentials
- API keys
- OAuth tokens
- Any key-value pairs (up to 64 KB)
Versions
Each secret can have multiple versions:
- AWSCURRENT: Current active version
- AWSPENDING: Version being rotated to
- AWSPREVIOUS: Previous version
Rotation
Automatic credential rotation using Lambda functions. Built-in support for:
- Amazon RDS
- Amazon Redshift
- Amazon DocumentDB
- Custom secrets
Common Patterns
Create a Secret
AWS CLI:
# Create secret with JSON
aws secretsmanager create-secret \
--name prod/myapp/database \
--description "Production database credentials" \
--secret-string '{"username":"admin","password":"MySecurePassword123!","host":"mydb.cluster-xyz.us-east-1.rds.amazonaws.com","port":5432,"database":"myapp"}'
# Create secret with binary data
aws secretsmanager create-secret \
--name prod/myapp/certificate \
--secret-binary fileb://certificate.pem
boto3:
import boto3
import json
secrets = boto3.client('secretsmanager')
response = secrets.create_secret(
Name='prod/myapp/database',
Description='Production database credentials',
SecretString=json.dumps({
'username': 'admin',
'password': 'MySecurePassword123!',
'host': 'mydb.cluster-xyz.us-east-1.rds.amazonaws.com',
'port': 5432,
'database': 'myapp'
}),
Tags=[
{'Key': 'Environment', 'Value': 'production'},
{'Key': 'Application', 'Value': 'myapp'}
]
)
Retrieve a Secret
import boto3
import json
secrets = boto3.client('secretsmanager')
def get_secret(secret_name):
response = secrets.get_secret_value(SecretId=secret_name)
if 'SecretString' in response:
return json.loads(response['SecretString'])
else:
import base64
return base64.b64decode(response['SecretBinary'])
# Usage
credentials = get_secret('prod/myapp/database')
db_password = credentials['password']
Caching Secrets
from aws_secretsmanager_caching import SecretCache, SecretCacheConfig
# Configure cache
cache_config = SecretCacheConfig(
max_cache_size=100,
secret_refresh_interval=3600,
secret_version_stage_refresh_interval=3600
)
cache = SecretCache(config=cache_config)
def get_cached_secret(secret_name):
secret = cache.get_secret_string(secret_name)
return json.loads(secret)
Update a Secret
# Update secret value
aws secretsmanager update-secret \
--secret-id prod/myapp/database \
--secret-string '{"username":"admin","password":"NewPassword456!"}'
# Put new version with staging labels
aws secretsmanager put-secret-value \
--secret-id prod/myapp/database \
--secret-string '{"username":"admin","password":"NewPassword456!"}' \
--version-stages AWSCURRENT
Enable Rotation for RDS
aws secretsmanager rotate-secret \
--secret-id prod/myapp/database \
--rotation-lambda-arn arn:aws:lambda:us-east-1:123456789012:function:SecretsManagerRDSPostgreSQLRotation \
--rotation-rules AutomaticallyAfterDays=30
Create Secret with Rotation
# Use CloudFormation for RDS secret with rotation
aws cloudformation deploy \
--template-file rds-secret.yaml \
--stack-name rds-secret
# rds-secret.yaml
AWSTemplateFormatVersion: '2010-09-09'
Resources:
DBSecret:
Type: AWS::SecretsManager::Secret
Properties:
Name: prod/myapp/database
GenerateSecretString:
SecretStringTemplate: '{"username": "admin"}'
GenerateStringKey: password
PasswordLength: 32
ExcludeCharacters: '"@/\'
DBSecretRotation:
Type: AWS::SecretsManager::RotationSchedule
Properties:
SecretId: !Ref DBSecret
RotationLambdaARN: !GetAtt RotationLambda.Arn
RotationRules:
AutomaticallyAfterDays: 30
Use in Lambda with Extension
import json
import urllib.request
def handler(event, context):
# Use AWS Parameters and Secrets Lambda Extension
secrets_port = 2773
secret_name = 'prod/myapp/database'
url = f'http://localhost:{secrets_port}/secretsmanager/get?secretId={secret_name}'
headers = {'X-Aws-Parameters-Secrets-Token': os.environ['AWS_SESSION_TOKEN']}
request = urllib.request.Request(url, headers=headers)
response = urllib.request.urlopen(request)
secret = json.loads(response.read())['SecretString']
credentials = json.loads(secret)
return credentials
CLI Reference
Secret Management
| Command | Description |
|---|---|
aws secretsmanager create-secret | Create secret |
aws secretsmanager describe-secret | Get secret metadata |
aws secretsmanager get-secret-value | Retrieve secret value |
aws secretsmanager update-secret | Update secret |
aws secretsmanager delete-secret | Delete secret |
aws secretsmanager restore-secret | Restore deleted secret |
aws secretsmanager list-secrets | List secrets |
Versions
| Command | Description |
|---|---|
aws secretsmanager put-secret-value | Add new version |
aws secretsmanager list-secret-version-ids | List versions |
aws secretsmanager update-secret-version-stage | Move staging labels |
Rotation
| Command | Description |
|---|---|
aws secretsmanager rotate-secret | Configure/trigger rotation |
aws secretsmanager cancel-rotate-secret | Cancel rotation |
Best Practices
Secret Organization
- Use hierarchical names:
environment/application/secret-type - Tag secrets for organization and cost allocation
- Separate by environment (dev, staging, prod)
Security
- Use resource policies to control access
- Enable encryption with customer-managed KMS keys
- Rotate secrets regularly (30-90 days)
- Audit access with CloudTrail
- Use VPC endpoints for private access
Access Control
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"secretsmanager:GetSecretValue",
"secretsmanager:DescribeSecret"
],
"Resource": "arn:aws:secretsmanager:us-east-1:123456789012:secret:prod/*",
"Condition": {
"StringEquals": {
"secretsmanager:ResourceTag/Environment": "production"
}
}
}
]
}
Application Integration
- Cache secrets to reduce API calls
- Handle rotation gracefully (retry with new credentials)
- Use Lambda extension for faster access
- Never log secrets
Troubleshooting
AccessDeniedException
Causes:
- IAM policy missing
secretsmanager:GetSecretValue - Resource policy denying access
- KMS key policy missing permissions
Debug:
# Check secret resource policy
aws secretsmanager get-resource-policy --secret-id my-secret
# Check IAM permissions
aws iam simulate-principal-policy \
--policy-source-arn arn:aws:iam::123456789012:role/my-role \
--action-names secretsmanager:GetSecretValue \
--resource-arns arn:aws:secretsmanager:us-east-1:123456789012:secret:my-secret
Rotation Failed
Debug:
# Check rotation status
aws secretsmanager describe-secret --secret-id my-secret
# Check Lambda logs
aws logs filter-log-events \
--log-group-name /aws/lambda/SecretsManagerRotation \
--filter-pattern "ERROR"
Common causes:
- Lambda timeout (increase to 30+ seconds)
- Network connectivity (VPC configuration)
- Database connection issues
- Wrong secret format
Secret Not Found
# List secrets to find correct name
aws secretsmanager list-secrets \
--filters Key=name,Values=myapp
# Check if deleted (within recovery window)
aws secretsmanager list-secrets \
--include-planned-deletion
References
Limitations
- →Secrets are limited to 64 KB in size
How it compares
This skill provides a centralized, managed service for storing and rotating secrets, unlike manual credential management.
Compared to similar skills
secrets-manager side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| secrets-manager (this skill) | 1 | 7mo | Caution | Beginner |
| secrets-management | 5 | 3mo | Review | Advanced |
| equilateral-agents | 5 | 9mo | No flags | Intermediate |
| cloud-penetration-testing | 3 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by itsmostafa
View all by itsmostafa →You might also like
secrets-management
wshobson
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
equilateral-agents
Equilateral-AI
22 production-ready AI agents with database-driven orchestration for security reviews, code quality analysis, deployment validation, infrastructure checks, and compliance. Auto-activates for security concerns, deployment tasks, code reviews, quality checks, and compliance questions. Includes upgrade paths to enterprise features (GDPR, HIPAA, multi-account AWS, ML-based optimization).
cloud-penetration-testing
davila7
This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms.
iam
itsmostafa
AWS Identity and Access Management for users, roles, policies, and permissions. Use when creating IAM policies, configuring cross-account access, setting up service roles, troubleshooting permission errors, or managing access control.
checking-infrastructure-compliance
jeremylongshore
Execute use when you need to work with compliance checking. This skill provides compliance monitoring and validation with comprehensive guidance and automation. Trigger with phrases like "check compliance", "validate policies", or "audit compliance".
secure-storage
gabriellpequeno
>