static-site
operationalStatic portfolio site served through S3, CloudFront, and ACM, with DNS managed in Route 53. Private bucket, public edge — no origin ever exposed directly.
status page — personal infrastructure
I'm Ben, a cloud engineer building and breaking AWS infrastructure until it holds. Below is a live-style board of what I've shipped — static hosting, serverless APIs, and networked compute — with real architecture behind each one.
Static portfolio site served through S3, CloudFront, and ACM, with DNS managed in Route 53. Private bucket, public edge — no origin ever exposed directly.
I'm early in my cloud engineering path and building in public — every project here is deployed with infrastructure-as-code, torn down when I'm done testing, and documented with the decisions behind it, not just the steps.
Currently focused on AWS networking fundamentals, IAM least-privilege patterns, and CI/CD for infrastructure changes.
cloud: provider: aws services: - s3 - cloudfront - acm - route53 - lambda - api_gateway - dynamodb - vpc - ec2 - alb iac: tool: terraform state: remote_s3_lock status: learning_in_public