# saikiranpi/terraform_modules architecture

> Architecture diagram of the GitHub repository saikiranpi/terraform_modules, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-05-13). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/saikiranpi/terraform_modules
- Repository: https://github.com/saikiranpi/terraform_modules

## Overview

##### Project type and purpose
- This is a Terraform-based Infrastructure-as-Code (IaC) project that provides reusable AWS modules.
- It defines two distinct environments—development and production—each using the same set of modular building blocks (network, compute, ELB, IAM, NAT, security groups).
- Purpose: enable teams (QA, Dev, Prod) to spin up AWS resources independently, with clear separation of concerns and minimal code duplication.

##### File structure
- Top-level “development” and “production” directories each contain Terraform root modules (main.tf, variables.tf, terraform.tfvars) that orchestrate environment-specific resources.
- A “modules” directory houses library modules:
- network (VPC, public/private subnets, routing)
- nat (NAT gateways for private subnets)
- sg (security groups)
- iam (roles and instance profiles)
- elb (load balancer + listener definitions)
- compute (public/private EC2 instances)
- Terraform configuration files (.tf, .tfvars) define inputs, outputs, and environment parameters.

##### README insights
- Emphasizes a two-section architecture (development vs. production).
- Highlights modular design to tailor AWS resources per environment without rewriting code.

a. Main components
- Users/CI pipeline: triggers Terraform applies
- Environment workspaces: Development, Production
- Shared Modules Library: network, nat, sg, iam, elb, compute
- AWS Resources per module:
- VPC, subnets, route tables (Network)
- NAT Gateways (NAT)
- Security Groups (SG)
- IAM Roles & Instance Profiles (IAM)
- Elastic Load Balancer & Listeners (ELB)
- EC2 Instances (Compute)

b. Relationships & interactions
- Root modules in “development/main.tf” and “production/main.tf” each call the library modules in sequence:
1. network → 2. nat → 3. sg → 4. iam → 5. elb → 6. compute
- Data flow: outputs from network (e.g., VPC ID, subnet IDs) feed into NAT, SG, ELB, and compute modules.
- Compute instances attach to subnets, security groups, use IAM instance profiles, and register with the load balancer.

c. Architectural patterns / design principles
- Modular design: each concern isolated in its own Terraform module
- Environment segregation: separate state and configuration per environment
- Input/output contracts: modules communicate via well-defined variables and outputs
- Reusability and DRY: single source of truth for core infrastructure across environments

d. Key technologies
- Terraform CLI
- AWS services: VPC, EC2, ELB, NAT Gateway, IAM, Security Groups
- Terraform remote state (implied for environment isolation)

## Diagram (Mermaid)

```mermaid
flowchart TB
    subgraph "Modules Library"
        NET["Network Module"]:::network
        NAT["NAT Module"]:::network
        SG["Security Groups Module"]:::security
        IAM["IAM Module"]:::security
        ELB["ELB Module"]:::loadbalancer
        CMP["Compute Module"]:::compute
    end

    subgraph "Development Environment"
        DEV_ROOT["Terraform Root Module"]:::root
        DEV_NET["network"]:::network
        DEV_NAT["nat"]:::network
        DEV_SG["sg"]:::security
        DEV_IAM["iam"]:::security
        DEV_ELB["elb"]:::loadbalancer
        DEV_CMP["compute"]:::compute
    end

    subgraph "Production Environment"
        PROD_ROOT["Terraform Root Module"]:::root
        PROD_NET["network"]:::network
        PROD_NAT["nat"]:::network
        PROD_SG["sg"]:::security
        PROD_IAM["iam"]:::security
        PROD_ELB["elb"]:::loadbalancer
        PROD_CMP["compute"]:::compute
    end

    %% Module references into environments
    NET -->|invoked by| DEV_NET
    NAT -->|invoked by| DEV_NAT
    SG -->|invoked by| DEV_SG
    IAM -->|invoked by| DEV_IAM
    ELB -->|invoked by| DEV_ELB
    CMP -->|invoked by| DEV_CMP

    NET -->|invoked by| PROD_NET
    NAT -->|invoked by| PROD_NAT
    SG -->|invoked by| PROD_SG
    IAM -->|invoked by| PROD_IAM
    ELB -->|invoked by| PROD_ELB
    CMP -->|invoked by| PROD_CMP

    %% Development module sequence
    DEV_ROOT -->|calls| DEV_NET
    DEV_NET -->|outputs| DEV_NAT
    DEV_NAT -->|provides| DEV_SG
    DEV_SG -->|secures| DEV_IAM
    DEV_IAM -->|profiles| DEV_ELB
    DEV_ELB -->|registers| DEV_CMP

    %% Production module sequence
    PROD_ROOT -->|calls| PROD_NET
    PROD_NET -->|outputs| PROD_NAT
    PROD_NAT -->|provides| PROD_SG
    PROD_SG -->|secures| PROD_IAM
    PROD_IAM -->|profiles| PROD_ELB
    PROD_ELB -->|registers| PROD_CMP

    %% Click events
    click DEV_ROOT "https://github.com/saikiranpi/terraform_modules/tree/main/development"
    click PROD_ROOT "https://github.com/saikiranpi/terraform_modules/tree/main/production"
    click NET "https://github.com/saikiranpi/terraform_modules/tree/main/modules/network"
    click NAT "https://github.com/saikiranpi/terraform_modules/tree/main/modules/nat"
    click SG "https://github.com/saikiranpi/terraform_modules/tree/main/modules/sg"
    click IAM "https://github.com/saikiranpi/terraform_modules/tree/main/modules/iam"
    click ELB "https://github.com/saikiranpi/terraform_modules/tree/main/modules/elb"
    click CMP "https://github.com/saikiranpi/terraform_modules/tree/main/modules/compute"

    %% Styles
    classDef network fill:#e0f7e9,stroke:#2ca02c,color:#2ca02c
    classDef security fill:#fff4e5,stroke:#ff7f0e,color:#ff7f0e
    classDef compute fill:#e5ecf4,stroke:#1f77b4,color:#1f77b4
    classDef loadbalancer fill:#f3e5f5,stroke:#9467bd,color:#9467bd
    classDef root fill:#eeeeee,stroke:#999999,color:#333333,font-weight:bold
```
