Engineering work

Projects

Four interconnected projects spanning cloud infrastructure, container orchestration, CI/CD automation, and AWS-native delivery pipelines. Each documented as a full engineering case study.

Projects

Deployment tracks

CI/CD approaches

Stored AWS credentials

01Cloud Infrastructure

↗

Cloud-Native Static Platform on AWS

→ Production-grade static delivery with zero direct S3 exposure.

Private S3 origin with CloudFront CDN, Origin Access Control, ACM HTTPS, and Route 53 DNS. Fully provisioned with Terraform. IAM OIDC for keyless GitHub Actions deployment.

AWS S3CloudFrontTerraformRoute 53ACMNext.js

02Container Orchestration

↗

Kubernetes Delivery Platform

→ Demonstrates full container lifecycle management and orchestration.

Containerised application delivery using Deployments, Services, Ingress, readiness and liveness probes, and Helm packaging. Runs as a parallel deployment track alongside the AWS static path.

KubernetesDockerHelmIngressCI/CD

03CI/CD & Automation

↗

Dual-Track CI/CD Delivery Pipeline

→ No long-lived AWS credentials. Two deploy paths. One pipeline.

GitHub Actions workflow with lint, type-check, test, security scan, and two independent deploy paths: S3/CloudFront and Kubernetes. IAM OIDC for keyless AWS authentication — no stored credentials.

GitHub ActionsIAM OIDCAWSDockerTypeScript

04AWS Native CI/CD

↗

React App Deployment with AWS CodePipeline

→ GitHub push → CodePipeline → CodeBuild → S3. Fully automated.

Full CI/CD pipeline using AWS CodePipeline, CodeBuild, and S3 to automatically build and deploy a React application on every GitHub push. Pipeline lives entirely inside AWS — no GitHub Actions required.

AWS CodePipelineAWS CodeBuildS3Reactbuildspec.yml

Projects 01–03 share a single repository and CI/CD pipeline. Project 04 demonstrates the AWS-native alternative — CodePipeline + CodeBuild — showing two distinct approaches to the same delivery problem.