Studying AWS.
I actually enjoy
fixing what breaks.
Stefan Timpau — early-career, studying for AWS Solutions Architect – Associate, building a portfolio that shows how I diagnose and fix cloud systems, not just what I'm memorizing for the exam.
Architecture that assumes failure
Multi-AZ by default, least-privilege by habit. If a system can only succeed when everything goes right, it isn't finished.
Diagnose before you guess
Reading logs and metrics before touching anything — CloudWatch, CloudTrail, and knowing where to look when something's down.
Building it so it's repeatable
Moving projects from console clicks to Terraform, with CI/CD and monitoring baked in — so nothing lives only in my head.
Selected work
view all →This site, actually
Static site on S3, served securely — domain, DNS, TLS, and origin access all wired up by hand, on purpose.
Cloud-native eCommerce platform ★ flagship
Full-stack storefront on four ECS Fargate microservices, Cognito auth, and a real checkout-to-SNS-confirmation-email flow — deployed and verified end-to-end, then CI/CD proven live with a least-privilege OIDC deploy role. 13 real incidents diagnosed and fixed, documented in the repo rather than hidden.
Enterprise networking lab
A hands-on AWS networking lab covering VPC design, Peering, Site-to-Site VPN, Client VPN, Transit Gateway (including selective route-table isolation), and PrivateLink — plus monitoring and a least-privilege IAM pass, with the real troubleshooting documented rather than hidden.
Stefan Timpau
I'm an early-career cloud professional studying for AWS Solutions Architect – Associate, building a portfolio of real, hands-on projects rather than just collecting badges — I like the troubleshooting side of the job as much as the building side.
Before cloud, I spent over a decade in high-end security — trusted with confidential information, hands-on with access control and least-privilege long before I knew that's what AWS calls it too.