AWS administration

Install AWS CLI and propagate IAM credentials across development containers.

3|2|Updated May 12, 2026

Search Tags:#automation #security #aws #infrastructure #iam #credential management

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill aws-administration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: AWS administration
Source: https://github.com/kriscendobot/garden/tree/main/skills/aws-administration
Command: npx skills add https://github.com/kriscendobot/garden --skill aws-administration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the complexity of managing AWS credentials across multiple containerized development environments by centralizing identity management and ensuring consistent, secure access without manual configuration drift.

Core Features & Use Cases

Credential Propagation: Uses hard-linking to share a single AWS credential inode across multiple checkout directories, ensuring all environments stay in sync.
Automated Rotation: Safely rotates IAM access keys using a create-before-delete workflow to prevent downtime.
Verification: Provides automated health checks to ensure every environment resolves to the correct IAM identity, account, and region.

Quick Start

Run the verification script to confirm that all garden checkout environments are correctly authenticated with the expected AWS identity.

Frequently Asked Questions about AWS administration

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

FAQPage Schema

How do I manage AWS CLI credentials across multiple containerized development environments?▼

You can manage AWS CLI credentials across multiple containerized environments by propagating a single shared credential inode via hard links to all checkout directories, ensuring consistent identity resolution without manual configuration drift.

What is the best way to automate IAM access key rotation without causing downtime?▼

Automating IAM access key rotation without downtime requires a create-before-delete workflow, which safely provisions new keys before invalidating the old ones to maintain continuous access across all environments.

How do I verify that isolated checkout environments resolve to the correct AWS identity?▼

You can verify isolated checkout environments resolve to the correct AWS identity by running an automated health check script that validates the expected IAM user, account, and region configuration across the fleet.

Does hard-linking credential files work for synchronizing AWS access across containers?▼

Hard-linking credential files works for synchronizing AWS access across containers by mapping multiple directory paths to a single inode, ensuring any credential updates instantly reflect across all linked checkout environments.

Can I use this to enforce consistent region configuration across a fleet of development containers?▼

Yes, you can use this to enforce consistent region configuration across a fleet of development containers, as it centralizes identity management and automatically applies uniform region settings to all isolated checkouts.

Why does configuration drift happen when manually setting up AWS credentials in isolated checkouts?▼

Configuration drift happens when manually setting up AWS credentials in isolated checkouts because individual environments update keys independently, causing identity and region mismatches that hard-linked credential propagation prevents.