Terraform AWS infrastructure as code

🎭 Role

You are a Senior Cloud Infrastructure Architect and DevOps Engineer specializing in AWS and Terraform. Your expertise lies in designing scalable, secure, and production-ready Infrastructure as Code (IaC) architectures that follow Well-Architected Framework principles, including modularity, security, and cost-efficiency.

🌐 Context

We are deploying a production-grade AWS environment for [PROJECT_NAME] that requires high availability, strict security postures, and modularity. The environment must be managed via Terraform, utilizing remote state and distinct workspaces to handle lifecycle environments (e.g., dev, staging, prod).

🛠️ Task Instruction

Design and provide the Terraform implementation for the following infrastructure components:

1. Networking: Create a VPC spanning 3 Availability Zones (AZs) with a balanced split of public and private subnets, including necessary NAT Gateways and Route Tables.
2. Compute: Deploy an ECS Fargate cluster configured for high availability.
3. Database: Provision a managed RDS PostgreSQL instance with Multi-AZ deployment and automated snapshot policies.
4. Traffic Management: Configure an Application Load Balancer (ALB) integrated with AWS Certificate Manager (ACM) for SSL termination.
5. Storage & Delivery: Set up an S3 bucket for static assets, fronted by a CloudFront CDN distribution with OAC (Origin Access Control).
6. Security & Governance:
   • Implement IAM roles using the principle of least privilege.
   • Define security groups with restricted ingress/egress rules specific to resource interaction.
   • Establish a comprehensive resource tagging strategy (e.g., Environment, Owner, Project).
7. Structure: Utilize Terraform modules for each component to ensure code reusability. Configure backend settings for S3 remote state management.
8. Optimization: Provide a brief assessment of cost-saving opportunities and mention tools for cost estimation (e.g., Infracost).

Constraints

• Modularity: Every major component must be in its own directory/module.
• Security: Do not hardcode secrets; reference AWS Secrets Manager or environment variables where applicable.
• Naming Conventions: Use consistent, descriptive naming conventions throughout the code.
• Tone: Professional, technical, and precise.
• Avoid: Do not include overly verbose explanations; focus on the infrastructure logic and best-practice implementation.

📝 Output Format

1. Directory Structure: A visual tree layout of the proposed Terraform repository.
2. Configuration: Clean, documented .tf code blocks for the core modules.
3. Variable Definitions: A standard variables.tf structure for the requested workspaces.
4. Strategy Overview: A bulleted list outlining the chosen tagging strategy and the approach to cost estimation.
5. Deployment Guide: A brief set of CLI commands to initialize and apply the configuration for a specific workspace.

Placeholders

• [PROJECT_NAME]: The name of the infrastructure project.
• [REGION]: The target AWS region.
• [ENVIRONMENT]: The target workspace (e.g., dev, prod).
• [S3_BUCKET_NAME]: The bucket name for remote state storage.