aws-iam

Implement least-privilege IAM users, roles, and policies in AWS.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tylern91/dotfiles --skill aws-iam-tylern91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-iam
Source: https://github.com/tylern91/dotfiles/tree/main/agents/.agents/skills/aws-iam
Command: npx skills add https://github.com/tylern91/dotfiles --skill aws-iam-tylern91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing IAM users, roles, and policies securely is complex and error-prone, risking over-privileged access and inconsistent governance.

Core Features & Use Cases

  • Least-privilege policy design: craft minimal permissions for services and users.
  • Role and trust configuration: build robust trust policies for cross-account access and OIDC federation.
  • Auditing and governance: enable IAM Access Analyzer, credential reports, and change tracking to enforce compliance.

Quick Start

Configure a least-privilege IAM setup by creating roles, policies, and trust relationships according to your organization's needs.

Frequently Asked Questions about aws-iam

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

FAQPage Schema
How do I create least-privilege IAM policies for AWS users and roles?

You can build robust trust policies for cross-account access and OIDC federation by configuring role trust relationships. This ensures secure, structured identity federation across different AWS environments.

How do I configure cross-account roles and OIDC federation in AWS IAM?

You can build robust trust policies for cross-account access and OIDC federation by configuring role trust relationships. This ensures secure, structured identity federation across different AWS environments.

What is the best way to audit IAM usage and enforce compliance in AWS?

Auditing IAM usage involves enabling IAM Access Analyzer, generating credential reports, and tracking policy changes. This enforces compliance and identifies over-privileged access across your AWS environments.

When do I need permission boundaries for AWS IAM roles?

Permission boundaries are needed when you must restrict the maximum permissions an IAM role can grant. They satisfy requirements for structured policy creation and security governance by cpping delegated permissions.

Does this approach work for structuring role trust configuration across multiple AWS accounts?

Yes, this approach applies directly to cross-account roles and trust configuration. It satisfies requirements for structured policy creation and security governance across AWS environments.