secrets-manager

Manage AWS Secrets Manager secrets, rotation, versioning, and cross-account sharing via AWS CLI.

3|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/david-2814/claw-aws --skill secrets-manager-david-2814
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-manager
Source: https://github.com/david-2814/claw-aws/tree/main/skills/secrets-manager
Command: npx skills add https://github.com/david-2814/claw-aws --skill secrets-manager-david-2814

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage AWS Secrets Manager secrets, rotation, versioning, and cross-account sharing via AWS CLI.

Core Features & Use Cases

  • Create, store, rotate, and version secrets centrally
  • Enable cross-account access with resource policies and audit usage
  • Integrate rotation with Lambda for automatic credential updates

Quick Start

Create a secret using AWS Secrets Manager and enable rotation with a Lambda function to start managing credentials.

Frequently Asked Questions about secrets-manager

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

FAQPage Schema
How do I rotate AWS Secrets Manager credentials automatically using Lambda?

You enable automatic credential rotation in AWS Secrets Manager by configuring a Lambda rotation function and setting a rotation schedule, allowing the service to update secret values automatically without manual intervention.

What is the best way to share secrets across multiple AWS accounts?

The best way to share secrets across AWS accounts is by attaching cross-account resource policies to your AWS Secrets Manager secrets, explicitly granting IAM permissions to principals in the target accounts for secure access.

Do I need specific IAM permissions to manage secrets and cross-account access in AWS?

Yes, managing AWS Secrets Manager requires IAM permissions for secretsmanager:* to create and rotate secrets, plus cross-account resource policies to authorize access from external AWS accounts.

How do I audit secret usage and manage versioning for credentials in development and production?

You audit secret usage and manage versioning by using AWS Secrets Manager to track secret lifecycle stages across development, staging, and production, applying versioning to maintain credential history and access logs.

Can I centralize the secret lifecycle and rotation policies across development, staging, and production environments?

Yes, you can centralize the secret lifecycle and rotation policies across development, staging, and production environments by using AWS Secrets Manager to uniformly apply rotation schedules and access controls via AWS CLI.