Write a Reusable Terraform Module for AWS Infrastructure

Create a reusable Terraform module for provisioning [AWS_SERVICE] (e.g., ECS Fargate cluster, RDS PostgreSQL instance, VPC with subnets, S3 + CloudFront static site) on AWS. The module should follow Terraform best practices and be ready for use in [ENVIRONMENT_TYPES] (e.g., dev, staging, production). Module structure: 1. **`variables.tf`**: - Define all input variables with `description`, `type`, and sensible `default` values where appropriate. - Key variables should include: [KEY_VARIABLES_LIST] (e.g., instance_size, vpc_cidr, enable_encryption, backup_retention_days). - Use `validation` blocks for critical inputs (e.g., CIDR format, allowed instance types). - Include a `tags` variable of type `map(string)` that merges with default tags. 2. **`main.tf`**: - Define the core [AWS_SERVICE] resources with all security best practices enabled (encryption at rest, encryption in transit, logging). - Use `locals` for computed values and tag merging. - Include IAM roles/policies following least-privilege principle. - Add security group rules scoped to [NETWORK_ACCESS_PATTERN] (e.g., VPC-only, specific CIDR ranges). 3. **`outputs.tf`**: - Export key resource attributes: ARN, endpoint, ID, and any connection strings. - Include `sensitive = true` for outputs containing secrets. 4. **`versions.tf`**: - Pin AWS provider version and set minimum Terraform version to [TF_VERSION]. 5. **Usage Example**: - Provide a `examples/basic/main.tf` showing how to call this module with typical values. - Show how to reference outputs in a root module. Ensure all resources use `name_prefix` or naming conventions incorporating `var.environment` and `var.project_name`. Include `lifecycle` blocks where appropriate (e.g., `prevent_destroy` for databases).