One public entry point
The Application Load Balancer sits in public subnets.
An AWS lab built around private networking, scoped identity and reviewable infrastructure.
ARCHITECTURE STUDY · ILLUSTRATIVE
Reconstructed architecture decision from the repository documentation; not a deployed environment.
The Application Load Balancer sits in public subnets.
Application security groups accept traffic from the ALB security group, rather than a broad public range.
Optional EC2 instances use private subnets, no public IP and no inbound SSH. Compute and NAT are disabled by default.
The boundary is expressed in infrastructure code, so a reviewer can inspect who can reach the application before deployment.
Read the source ↗A portfolio lab combining modular Terraform infrastructure with a small FastAPI application, hardened Docker configuration and automated security validation workflows.
A public ALB fronts optional application instances in private subnets. Security-group references restrict backend access; there is no public instance IP or SSH ingress.
IAM roles, IMDSv2 and branch-bound OIDC trust are paired with CloudTrail, an encrypted private S3 audit bucket, CloudWatch and configurable GuardDuty.
Terraform validation, IaC and secret scanning, application checks and container scanning are documented as separate CI gates. Compute and NAT are disabled by default.
An educational lab, with no verified production deployment. HTTPS, VPC endpoints and a deliberately scoped deployment policy remain future work. AWS resources incur costs; CI validation does not deploy them. Private compute also needs a controlled software-delivery path.