Mid-Coast Maine • AWS • Terraform • Automation
Cloud engineering with a Maine coastal calm — and production-grade discipline.
I build secure, cost-aware AWS infrastructure using Infrastructure as Code. This site showcases projects designed to demonstrate real-world architecture patterns (global distribution, least-privilege IAM, resiliency, and clean delivery workflows).
Highly Available Static Website
Private S3 origin + CloudFront (OAC) + ACM + Route 53. Designed for secure global delivery with clean teardown and cost controls.
- Private bucket (no public access)
- CloudFront Origin Access Control (SigV4)
- ACM DNS validation automated via Route 53
- HTTPS enforced + modern TLS
Portfolio projects
Real architectures, documented decisions, and IaC you can review. Each project includes: a clear problem statement, diagram, build steps, and lessons learned.
What makes these “portfolio-grade”
- IaC-first: Terraform structure mirrors real teams (separated files, consistent tagging).
- Security posture: private origins, least privilege, explicit trust boundaries.
- Operational thinking: teardown steps, cost controls, and documented tradeoffs.
Skills
Core areas I focus on while building and operating cloud infrastructure.
Infrastructure as Code
Terraform modules, remote state patterns, clean diffs, and repeatable deployments.
Networking & Delivery
VPC design, routing, security groups, CloudFront caching, DNS patterns.
Security
Least privilege IAM, private origins, encryption, and guardrails.
Reliability
Multi-AZ architecture, failure modes, and practical operational runbooks.
Certifications
Current and in-progress certifications that support the portfolio work.
Validated expertise in designing secure, resilient, and cost-optimized architectures on AWS, including networking, storage, compute, and IAM best practices.
Next up
Portfolio-driven progression
Expanding into CI/CD workflows, deeper security controls, and resiliency testing (RTO/RPO).
About
I’m building a portfolio that proves I can ship AWS infrastructure the way teams operate in production: secure defaults, clean IaC, and clear documentation of tradeoffs.
How I build
- Start with a real problem statement
- Design architecture + document tradeoffs
- Implement in Terraform with clean structure
- Validate with plan, deploy, verify, teardown
What you’ll see in each repo
- README with “why” decisions
- Architecture diagram
- Deployment steps + teardown steps
- Cost notes + security considerations