From operations to architecture

How DevOps and SRE experience became a cloud systems portfolio

This site is a working record of my move from DevOps and site reliability engineering into Solutions Architecture. The goal was never only credentials — it was to design, deploy, secure, and operate real infrastructure, then document the trade-offs.

That goal led me to the AWS Cloud Resume Challenge, rebuilt here as a production-style platform on AWS.

Background

My work combines DevOps, reliability engineering, teaching, networking, and systems thinking. Operations taught me to investigate methodically; delivery work taught me to automate feedback loops. Architecture is the natural next step: apply that operational judgment earlier in the design.

From certifications to systems

Certifications structured my learning in AWS, AI, networking, and cloud-native platforms. They also made a limit clear: exams do not show how someone designs, troubleshoots, or improves a live system. Projects I own end to end do.

Why this challenge

The challenge connects DevOps practice to architecture: secure hosting, DNS, HTTPS, automation, serverless services, infrastructure as code, and documentation. The visitor counter and contact form make the site an active application, not a brochure.

What I built

  • Static delivery: S3 + CloudFront for the resume and project pages.
  • Secure edge: Route 53 DNS and ACM HTTPS.
  • Automation: Git-based publishing into the static origin.
  • Serverless data path: Lambda, API Gateway, and DynamoDB for visitor counts.
  • IaC (in progress): migrating live AWS resources to Terraform for repeatable infrastructure.
  • Contact path: A serverless form with least-privilege design in mind.

Where this is going

The challenge is a foundation. Next work expands into platform engineering, observability, security, and generative AI from an architectural lens — still documented in public.

Explore the challenge build or the resume for experience and certifications.