About Me
I’m Ron, an AWS Cloud Operations candidate with a background in IT support, troubleshooting, documentation, and keeping systems stable. I build real AWS projects to practice the work I want to do professionally: deploying infrastructure, monitoring systems, troubleshooting issues, controlling cost, and explaining decisions clearly.
I’m not presenting myself as a senior cloud engineer. I’m showing practical, hands-on AWS work: live demos, Terraform-managed infrastructure, operational lessons learned, and decisions I can defend.
Proof Snapshot (fast scan)
- Live AWS projects: IoT ingestion, dashboards, scheduled analytics, serverless APIs, private VPC architecture, and chatbot workflows.
- Terraform-first delivery: Infrastructure defined with code, version control, and repeatable deployment practices.
- Cloud Ops mindset: I focus on logs, monitoring, IAM scope, reliability, troubleshooting, and cost control.
My path into tech wasn’t the standard one. I’ve worked in law enforcement, on offshore energy platforms, the petrochemical industry, IT/Network support, and years as a touring musician/road manager. All gave me calmness under pressure, strong communication skills, and a habit of showing up prepared — even when things go sideways.
Lately I’ve been building the fundamentals a good junior architect needs: understanding requirements, choosing AWS services that fit the needs, and building repeatably with Terraform.
What I'm Looking For
I’m targeting remote junior roles in Cloud Operations, Cloud Support, AWS infrastructure, or early-career Cloud Engineering. I’m looking for a team where I can contribute my IT operations background, keep learning from experienced engineers, and support real cloud systems the right way.
I’m especially interested in work involving AWS monitoring, incident response, Terraform, IAM cleanup, cost awareness, documentation, and troubleshooting production-like systems.
How I Work
I'm practical when working in AWS:
- Start with the goal: What are we trying to support, who depends on it, and what does “working” actually mean?
- Keep the design practical: Use the simplest AWS approach that meets the requirement without unnecessary moving parts.
- Build repeatably: Terraform + GitHub so infrastructure is reviewable, documented, and reproducible.
- Make issues visible: Logs, metrics, and basic alarms matter because invisible failures waste time.
- Stay cost-aware: Cloud resources should be useful, justified, and not quietly expensive.
What You'll See in My Projects
The projects on this site are built so I can walk through the operational thinking behind them, not just show a finished demo. You’ll see AWS workflows involving IoT ingestion, dashboards, scheduled analytics, private networking, serverless APIs, image processing, and a Lex chatbot.
The point isn’t that I’ve mastered every service. The point is that I can build carefully, troubleshoot when something breaks, document what I learned, and explain the tradeoffs in plain language.
My Other Interests
Outside of tech, I’m a dog person through and through. My sidekick is Molly, a 12-year-old Lab/Blue Heeler mix who has been present for plenty of late-night Terraform plans and debugging sessions.
I’m also a ham radio operator, with a particular interest in CW/Morse Code.
This is Molly, my beloved senior friend and loyal cloud companion. smiling face
Certifications
Additional Studies
Platform & Infrastructure Foundations
- Microsoft Azure Fundamentals
- Windows Server Administration (2012 & 2016)
Security Awareness
- Kali Linux fundamentals
Professional Communication & Workplace Effectiveness
- Communicating for Results
- The Complete Storytelling Course for Speaking & Presenting
- Professionalism in the Office
*Note: Structured technical and professional training completed through accredited and online learning programs.