aws-terraform-dev

Define AWS infrastructure with direct Terraform resources in a single main.tf.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mporenta/airflow --skill aws-terraform-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-terraform-dev
Source: https://github.com/mporenta/airflow/tree/main/.claude/skills/aws-terraform-dev
Command: npx skills add https://github.com/mporenta/airflow --skill aws-terraform-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patterns for simple Terraform infrastructure using "direct resources first, modularize later." Targets 150-250 lines per environment in a single main.tf with 3-5 variables. Covers DynamoDB (PAY_PER_REQUEST), Lambda with CI/CD packaging, API Gateway, IAM policies, and S3 conventions for event logs and Snowflake staging. Create modules only after 3+ reuses of the same pattern. Includes staging/prod differentiation and essential CloudWatch alarms. Use when creating AWS infrastructure, deploying serverless applications, or setting up event processing systems.

Core Features & Use Cases

  • Direct resources-first approach: single main.tf per environment (staging and prod) with 150-250 lines.
  • Essential components: DynamoDB (PAY_PER_REQUEST), Lambda with CI/CD packaging, API Gateway, IAM policies, and S3 conventions for event logs and Snowflake staging.
  • Use Case: Review or build simple AWS infrastructure quickly, deploying serverless apps and event processing pipelines with minimal churn.

Quick Start

Start by implementing a staging environment with a single main.tf (150-250 lines) and then replicate to prod with environment-specific variables.

Frequently Asked Questions about aws-terraform-dev

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

FAQPage Schema
What is the best way to structure simple AWS infrastructure with Terraform without premature modularization?

Use a direct resources-first approach in Terraform by maintaining a single main.tf per environment with 150-250 lines and 3-5 variables. Modularize only after reusing the same pattern three or more times to keep simple AWS infra lean.

How do I deploy serverless applications using Terraform for DynamoDB, Lambda, and API Gateway?

Deploy serverless apps by defining DynamoDB with PAY_PER_REQUEST, Lambda with CI/CD packaging, and API Gateway directly in Terraform. This covers IAM policies and S3 conventions for event logs within a single staging or production configuration.

Can I use this lean Terraform approach for small to mid-sized AWS deployments across staging and production?

Yes, this lean Terraform approach targets small to mid-sized AWS deployments by using a single main.tf per environment with environment-specific variables. It supports staging and production differentiation alongside essential CloudWatch alarms.

When should I not use direct resources and instead modularize my Terraform AWS configuration?

You should avoid direct resources and modularize your Terraform AWS configuration only after identifying 3 or more reuses of the same pattern. Premature modularization adds unnecessary churn for simple infrastructures under 250 lines.

How do I set up CloudWatch alarms and S3 event logging for AWS Lambda using Terraform?

Set up CloudWatch alarms and S3 event logging by defining essential alarms and S3 conventions for event logs directly in Terraform. This includes establishing S3 paths for Snowflake staging alongside DynamoDB and IAM policies.