Portfolio website
The site you're reading. A static portfolio served from S3, distributed globally via CloudFront, with a custom domain on Route 53 and HTTPS via an ACM certificate.
Cloud engineer based in Kansas. AWS and Azure. Currently studying for the CCNA, AWS Advanced Networking, and HashiCorp Terraform Associate.
I came into cloud computing because someone gave me a chance in the field. Over the last five years I improved exponentially. AWS was my start — the platform I grew up on professionally — and now I'm working to fully envelop myself in knowledge of other cloud providers as well.
When a problem lands on my desk, I want to understand the whole shape of it before I start swinging at it. I look for what's actually broken versus what's a symptom, who's affected, and what the smallest honest fix looks like — even if a bigger fix follows.
I'd rather be the person who can take a problem from the first ticket to an architectural fix than someone who only touches one layer of the stack.
I recently stepped away from my role to take time to focus on what's next — pursuing more certifications, focusing on personal projects, and continuing to grow my experience.
This site is the first of those projects. More to come in the projects section as I build them.
Built and maintained virtual desktop environments using AWS WorkSpaces and EC2-based VDI integrated with Auto Scaling Groups for distributed remote workloads.
Ran patch management and change management across multi-account fleets — keeping production environments current and the cutovers boring.
Built Lambda + EventBridge automations and AWS Config rules for scheduled fleet-wide operations and policy enforcement across enterprise accounts.
Implemented Amazon FSx for managed file storage — including SMB share configuration and lifecycle policies for end-user storage scenarios.
Used AWS DataSync to migrate enterprise data between EBS, FSx, and S3 — handling the validation work that proves nothing was lost in the cutover.
Maintained Golden Image workflows across Auto Scaling Groups and performed EC2 rescue operations — including root-volume detachment and side-loading to recover unresponsive instances.
The site you're reading. A static portfolio served from S3, distributed globally via CloudFront, with a custom domain on Route 53 and HTTPS via an ACM certificate.
Additional personal AWS and Azure projects are in the works. Each one will get a write-up here as it's built — including what was used, why, and what I learned.
I was a primary engineer for a couple of managed-service accounts with a mix of end-user support and AWS services. I led incident response for high-severity outages, created documentation and explained it to other engineers, and worked on architectural improvements that aligned with the AWS Well-Architected Framework — while most importantly making sure the work served the customer's needs.
Day-to-day work included incident response, ticket triage, planning upcoming changes to production environments, and addressing customer needs. The day-to-day could range from a simple password reset all the way to pushing out a major change to a production environment.
Stepped away from my previous role to focus on what's next. Using the time to pursue three certifications in parallel and build personal AWS and Azure projects to grow my experience.
A short, dated log of things I've worked through in the lab — what I tried, what I figured out, what tripped me up. I'll add entries as I build.
A place for opinions and observations about cloud, engineering, and the craft — written in my own words as I have them.
Areas I want to learn more about — not commitments, just things I'd open a tab for.