What problem does it solve? Teams provisioning AWS resources manually or with inconsistent practices end up with untagged resources, over-privileged IAM policies, and no auditable infrastructure state. This Skill enforces an IaC-first discipline for AWS so every resource is defined in code, tagged for cost allocation, and secured with least-privilege access. ## Core Features & Use Cases - IaC-First Provisioning: Define VPC, EC2, EKS, RDS, Lambda, S3, Bedrock, and SageMaker resources in Terraform, CloudFormation, or AWS CDK with no manual console changes. - Least-Privilege IAM: Author IAM roles, resource policies, and SCPs that reject wildcard permissions and mandate IAM Identity Center short-lived credentials over long-lived access keys. - FinOps and Observability: Apply mandatory cost-allocation tags (team-id, service-name, budget-tier), default to Graviton4 compute, and enable CloudWatch, X-Ray, and AWS Config monitoring. - Use Case: When standing up a new EKS cluster for a checkout service, use this Skill to generate the Terraform configuration with EKS Auto Mode, Graviton4 node provisioning, FinOps tags, and a CloudWatch alarm, then emit the aws-infra-spec.json handoff for DevOps. ## Quick Start Use the aws-infrastructure skill to write Terraform for a new EKS cluster with least-privilege IAM roles, FinOps tags, and CloudWatch observability.