aws-infrastructure

Provision and configure AWS infrastructure with Terraform, least-privilege IAM, and FinOps tagging.

Updated Feb 10, 2026
Ready to run
npx skills add https://github.com/vesviet/agent-skills --skill aws-infrastructure-vesviet
💬 Prompt for ChatGPT / Claude Chat▼
Please help me install this Agent Skill.
Skill: aws-infrastructure
Source: https://github.com/vesviet/agent-skills/tree/main/core/skills/platform/aws-infrastructure
Command: npx skills add https://github.com/vesviet/agent-skills --skill aws-infrastructure-vesviet

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about aws-infrastructure

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

FAQPage Schema
How do I provision AWS infrastructure with Terraform following best practices?▼

Define all resources in Terraform, CloudFormation, or AWS CDK rather than the console, apply mandatory FinOps tags (team-id, service-name, budget-tier), and enable CloudWatch and X-Ray observability. Validate the IaC in a staging environment before producing the aws-infra-spec.json handoff.

How do I enforce least-privilege IAM policies on AWS?▼

Author IAM roles and resource policies without wildcard Action or Resource permissions, and require Security Engineer review before deployment. Use IAM Identity Center with short-lived credentials and deny iam:CreateAccessKey via an SCP at the root OU to block long-lived access keys.

Should I use EKS Auto Mode or managed node groups for new clusters?▼

Use EKS Auto Mode for new clusters, as it eliminates manual node group management. Karpenter auto-provisions right-sized Graviton4 nodes on demand based on pending pod requirements, reducing both cost and operational overhead.

Does AWS Graviton4 require changes to container images?▼

Yes, container images must be built as multi-arch for linux/amd64 and linux/arm64 to run on Graviton4 instances like C8g, M8g, and R8g. Enforce multi-arch builds in CI so workloads can default to Graviton4 for lower cost and better performance.

What guardrails are required for Amazon Bedrock in production?▼

Production Bedrock endpoints must enable Guardrails v2 with contextual grounding and a grounding threshold of at least 0.7. This blocks responses not grounded in the provided context, reducing hallucinated output from the endpoint.

Why do untagged AWS resources cause problems?▼

Resources without team-id, service-name, and budget-tier tags break cost allocation and FinOps reporting. Enforce tag policies through AWS Config and reject untagged resources in IaC review so every provisioned resource is attributable to a team and budget.