Table of Contents

Introduction

Protect your applications with AWS WAF rules managed by Terraform — rate limiting, IP blocking, and SQL injection prevention. This tutorial provides production-ready Terraform code you can adapt for your own infrastructure.

Prerequisites

  • Terraform >= 1.5 installed
  • AWS account with appropriate permissions
  • Basic familiarity with AWS services

Provider Configuration

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
    }
  }
}

provider "aws" {
  region = var.region
}

Resource Configuration

The following Terraform configuration creates the resources described above. Each resource includes proper tagging, security settings, and follows AWS best practices.

# Main resource configuration
# See the full example in our GitHub repository
# https://github.com/lucaberton/terraform-examples

variable "environment" {
  description = "Environment name"
  default     = "production"
}

variable "region" {
  description = "Cloud region"
  default     = "us-east-1"
}

Step-by-Step Deployment

Step 1: Initialize Terraform

terraform init

This downloads the AWS provider plugin and initializes the backend.

Step 2: Review the Plan

terraform plan -out=tfplan

Always review the plan before applying. Check that only the expected resources will be created.

Step 3: Apply the Configuration

terraform apply tfplan

Terraform will create all resources in the correct order, handling dependencies automatically.

Step 4: Verify the Deployment

After applying, verify your resources are running correctly:

terraform output
terraform show

Security Considerations

  • Encryption: Enable encryption at rest and in transit for all data
  • Access Control: Follow least-privilege principle for IAM/RBAC
  • Network Security: Use private subnets and restrict inbound access
  • Secrets Management: Never hardcode credentials in Terraform files
  • State Security: Store Terraform state in encrypted remote backends

Cost Optimization Tips

  1. Right-size resources — start small and scale based on actual usage
  2. Use spot/preemptible instances for non-critical workloads
  3. Set auto-scaling to match demand and avoid over-provisioning
  4. Implement lifecycle policies for storage to tier down cold data
  5. Tag resources for cost allocation and tracking

Monitoring and Observability

Set up monitoring from day one:

  • CPU, memory, and network metrics
  • Application-level health checks
  • Log aggregation and alerting
  • Cost anomaly detection

Troubleshooting

Common Issues

  1. Permission denied: Check IAM roles and policies
  2. Resource limits: Request quota increases before deploying
  3. Network connectivity: Verify security groups and route tables
  4. State conflicts: Use remote state with locking

Best Practices Summary

  1. Use modules for reusable infrastructure patterns
  2. Pin provider versions for reproducible builds
  3. Separate state per environment (dev/staging/prod)
  4. Enable drift detection in CI/CD pipelines
  5. Document everything with inline comments and README files

Conclusion

Managing AWS resources with Terraform brings consistency, version control, and automation to your infrastructure. The configurations in this guide follow production best practices and can be extended to match your specific requirements. Start with these foundations and iterate as your infrastructure needs evolve.