secrets-management

Design centralized secrets management with Vault, AWS Secrets Manager, rotation policies, and audit logging.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill secrets-management-kalilurrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/02-devops-infra/secrets-management
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill secrets-management-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hardcoded credentials, secrets committed to git, and unmanaged API keys create security breaches and compliance failures. This Skill designs a centralized secrets management architecture with encrypted storage, controlled access, automatic rotation, and full audit trails. ## Core Features & Use Cases - Secret Store Selection: Compare HashiCorp Vault, AWS Secrets Manager, and Kubernetes Secrets across cost, rotation, dynamic secrets, and multi-cloud support. - Rotation & Access Control: Implement automatic database password rotation, dual-key API key rotation, RBAC policies, and AppRole authentication. - Runtime Injection & Auditing: Inject secrets via environment variables, mounted volumes, or Vault Agent sidecars, and stream audit logs to a SIEM. - Use Case: A platform team migrating 45 hardcoded credentials uses this Skill to stand up Vault with dynamic PostgreSQL credentials, 90-day rotation, and audit logging to Elasticsearch. ## Quick Start Design a secrets management architecture for my Kubernetes-hosted application using Vault with automatic database password rotation and audit logging.

Frequently Asked Questions about secrets-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage secrets in Kubernetes securely?

Store secrets in an external store like Vault or AWS Secrets Manager and sync them with the External Secrets Operator, or enable encryption at rest for native Kubernetes Secrets. Inject them at runtime via environment variables or mounted volumes, never in images or git.

Vault vs AWS Secrets Manager: which should I choose?

Vault suits multi-cloud environments and supports dynamic secrets that auto-expire, while AWS Secrets Manager is simpler for AWS-only workloads at $0.40 per secret per month. Both offer automatic rotation and audit logging.

How do I rotate database passwords without downtime?

Use Vault's dynamic database secrets to generate short-lived credentials, or follow a rotation process: generate a new password, update the database and secret store, rolling-restart applications, then revoke the old password after a grace period.

Can I sync AWS Secrets Manager secrets into Kubernetes?

Yes, the External Secrets Operator syncs secrets from AWS Secrets Manager into Kubernetes Secrets on a configurable refresh interval. Define a SecretStore pointing to AWS and an ExternalSecret mapping remote keys to a Kubernetes Secret.

Why should secrets never be stored in Docker images?

Docker image layers are immutable and readable by anyone with image access, permanently exposing any baked-in secret. Inject secrets at runtime through environment variables, mounted volumes, or a Vault Agent sidecar instead.