What problem does it solve? Designing AWS infrastructure requires navigating hundreds of services, conflicting documentation versions, and subtle IAM/networking pitfalls. This Skill provides a read-only AWS reference that researches first-party AWS documentation and produces structured, least-privilege infrastructure recommendations with implementation snippets. ## Core Features & Use Cases - Multi-service reference: Covers IAM/IRSA/Pod Identity, S3, Route 53, VPC networking (Endpoints, PrivateLink, Transit Gateway), EKS, ECR, ECS, Elastic Beanstalk, and MSK with per-service deep-dive reference files. - Source authority hierarchy: Prioritizes AWS docs, CLI v2 reference, API reference, and Well-Architected Framework over community sources, and documents conflicts between first-party sources. - Pitfall detection: Surfaces common cross-service traps such as NAT Gateway data-processing costs, ECS task vs execution role confusion, EKS aws-auth vs Access Entries drift, and MSK Provisioned vs Serverless auth mismatches. - Use Case: Ask how to give EKS pods access to S3, and receive a Pod Identity vs IRSA comparison, a scoped IAM trust policy with Condition keys, Terraform snippets, and cost/networking considerations. ## Quick Start Ask the aws-expert skill how to configure private EKS worker nodes to pull images from ECR without a NAT Gateway.