aws-iam-best-practices

Audit AWS IAM policies and generate least privilege hardening reports.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/BAIZ1D/macbookM1_rice --skill aws-iam-best-practices-baiz1d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-iam-best-practices
Source: https://github.com/BAIZ1D/macbookM1_rice/tree/main/agent/skills/security/aws-iam-best-practices
Command: npx skills add https://github.com/BAIZ1D/macbookM1_rice --skill aws-iam-best-practices-baiz1d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unsecure, overly permissive AWS IAM configurations create significant risk of unauthorized access, privilege escalation, and compliance violations for cloud workloads, requiring manual, time-intensive audits to identify and remediate gaps.

Core Features & Use Cases

  • IAM Policy Auditing: Scan existing IAM policies for overly permissive wildcard permissions, unused inline policies, and risky trust relationships.
  • Least Privilege Policy Generation: Create production-ready IAM policies for services like S3 with built-in security conditions for MFA enforcement, IP restrictions, and time-based access.
  • Automated Hardening Checks: Run pre-built checks to identify users without MFA, stale access keys older than 90 days, and unused IAM roles. A cloud security administrator can use this skill to complete a full IAM security audit and generate a compliance-ready hardening report in minutes instead of hours of manual review.

Quick Start

Use the aws-iam-best-practices skill to audit your AWS account's IAM configuration for security gaps and generate a prioritized least privilege hardening report.

Frequently Asked Questions about aws-iam-best-practices

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

FAQPage Schema
How do I audit AWS IAM policies for overly permissive wildcard permissions?

To audit AWS IAM policies for overly permissive wildcard permissions, run a security hardening workflow that scans existing configurations to identify risky trust relationships and unused inline policies. This generates a compliance-ready hardening report.

What is the best way to implement least privilege access control in AWS IAM?

The best way to implement least privilege access control in AWS IAM is by generating production-ready policy templates with built-in security conditions for MFA enforcement, IP restrictions, and time-based access to eliminate insecure configurations.

How do I check my AWS account for users without MFA and stale access keys?

You can check your AWS account for users without MFA and stale access keys older than 90 days by running automated hardening checks. This identifies unused IAM roles and mitigates privilege escalation risks.

Does AWS IAM least privilege hardening work for S3 service policies?

Yes, AWS IAM least privilege hardening works for S3 service policies by creating production-ready templates with built-in security conditions. This enforces MFA and IP restrictions for secure cloud access control.

Why do I need to review risky trust relationships in my AWS IAM configuration?

You need to review risky trust relationships in your AWS IAM configuration because insecure setups create significant risks of unauthorized access, privilege escalation, and compliance violations for cloud workloads requiring immediate remediation.