cd .. / projects
<inforforge/>

InfraForge

PLANNED
Cloud Infrastructure Engineering•2026•Cloud Infrastructure Engineer•Planned Project
InfraForge primary preview
<about-project/>

InfraForge is the first planned Cloud/DevOps learning build: a production-style Infrastructure as Code project on AWS. The target architecture defines a private, multi-AZ network — VPC with public and private subnets, an ALB, ECS/EC2 compute, an isolated RDS PostgreSQL database, S3 for object storage, and CloudWatch for logs and metrics — all provisioned and versioned with Terraform and containerized with Docker. IAM policies are designed around least privilege so no resource is reachable or configurable beyond what the architecture needs. The scope is the first step in a roadmap — Build to Automate to Deploy to Observe to Secure — so its network, database, and container patterns can be reused by the later projects. This is a planned roadmap build: no AWS infrastructure, Terraform state, or deployment exists yet.

<tech-stack/>
<key-features/>
Versioned Terraform configuration for the full environment (planned)
Multi-AZ VPC with public/private subnet isolation (planned)
ALB routing to ECS/EC2 compute (planned)
Private RDS PostgreSQL with no public exposure (planned)
S3 buckets for object storage and state/artifacts (planned)
Least-privilege IAM roles and policies (planned)
CloudWatch logging and metrics collection (planned)
Docker containerization of application components (planned)
<technical-decisions/>

Why Terraform for this project? (planned)

Declarative, versioned Infrastructure as Code makes the whole environment reproducible and reviewable as a single artifact — the intended foundation for the later DeployFlow automation.

Why a private, multi-AZ network? (planned)

Putting the database in a private subnet and routing traffic only through an ALB models how real production systems isolate sensitive data, which is the honest learning goal of this build.