integrating-secrets-managers

name	integrating-secrets-managers
description	Manage this skill enables AI assistant to seamlessly integrate with various secrets managers like hashicorp vault and aws secrets manager. it generates configurations and setup code, ensuring best practices for secure credential management. use this skill when... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(cmd:*)
version	1.0.0
author	Jeremy Longshore <[e-mail]>
license	MIT
compatible-with	claude-code, codex, openclaw
tags	["devops","aws","integrating-secrets"]

Integrating Secrets Managers

Overview

Integrate secrets management platforms (HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager, Azure Key Vault) into applications and infrastructure. Generate authentication configurations, access policies, secret rotation schedules, and application code patterns for secure credential retrieval at runtime.

Prerequisites

• Secrets manager instance running and accessible (Vault server, AWS Secrets Manager enabled)
• Cloud provider CLI authenticated or Vault CLI installed (vault, aws, gcloud, az)
• IAM/policy permissions to create secrets and access policies
• Understanding of which application components need which secrets
• Network connectivity between application workloads and the secrets manager endpoint

Instructions

1. Inventory all secrets currently in use: database credentials, API keys, TLS certificates, OAuth tokens
2. Select the secrets manager based on infrastructure: Vault for multi-cloud, AWS Secrets Manager for AWS-native, GCP Secret Manager for GCP
3. Create the secrets store structure: organize by application, environment, and secret type (e.g., apps/myapp/prod/database)
4. Generate access policies with least-privilege: each application identity gets read access only to its own secrets
5. Configure authentication method: Kubernetes service account (Vault K8s auth), IAM role (AWS), Workload Identity (GCP)
6. Implement secret retrieval in the application: SDK call at startup, sidecar injection (Vault Agent), or CSI driver mount
7. Set up automatic secret rotation: define rotation lambda/function, rotation interval, and notification on rotation events
8. Remove hardcoded secrets from code and configuration files; replace with secret references
9. Add monitoring: alert on secret access failures, rotation failures, and unauthorized access attempts

Output

• Vault policies (HCL) or IAM policies (JSON) for secret access
• Authentication configuration (Vault K8s auth, AWS IAM role, GCP Workload Identity)
• Application code snippets for secret retrieval (SDK-based or environment variable injection)
• Secret rotation configuration (AWS rotation Lambda, Vault dynamic secrets)
• Kubernetes External Secrets Operator or CSI SecretProviderClass manifests

Error Handling

Error	Cause	Solution
on secret read