S.M. live

FIG. 01 — REQUEST PATH

Samuel Meneses

Computer Science + M.S. Informatics @ Northeastern University
Building toward cloud engineering, one broken deploy at a time.

DRAWN BYS. MENESES
SHEET01 / 0X
REVLIVE

I'm a Computer Science and M.S. Informatics student at Northeastern University, working toward a role as a cloud engineer. I'd rather understand a system from the ground up than just call its API — this site is where that shows. Every piece of it, from the private S3 bucket to the DNS record pointing at it, I built and broke and fixed myself.

  1. S3 bucket provisioned. Public access blocked — CloudFront is the only way in.

  2. CloudFront distribution deployed with Origin Access Control. No public bucket, no legacy access identity.

  3. samuelmeneses.dev registered and wired through Route 53. ACM certificate issued, validated over DNS.

  4. CI/CD online. GitHub Actions authenticates to AWS via OIDC — no long-lived access keys stored anywhere.

  5. Debug note: GitHub's OIDC sub claim embeds numeric IDs (user@id/repo@id) instead of plain names. Cost an hour, taught me more about federated identity than any tutorial did.

  6. Serverless API is live — Lambda + API Gateway + DynamoDB, called from this page in real time. You're visitor #···.

$ reach samuel --via