Serverless GIS backends
Lambda + API Gateway + DynamoDB is still the fastest path from a map idea to a durable API — the Cloud Resume Challenge pattern scaled up.
Why AWS
Build, measure, certify
AWS is where I learned cloud by shipping: this resume site, visitor counters, and ski-atlas pipelines. The SAA study plan turns that production muscle into exam-ready architecture judgment.
Edge + static frontends
S3 and CloudFront host this site. Knowing cache behaviors, OAC, and DNS quirks comes up on almost every static-site architecture review.
Study against real stacks
My SAA nights map to production patterns from Global Ski Atlas and this site — not slide-only learning.
IaC discipline
SAM templates and CI/CD for the visitor counter taught me to treat infrastructure like code — and to separate frontend from backend deploys.
Built on AWS
Playground projects
These pages are the AWS lab today — more architecture diagrams and mini-labs will join them.
Cloud Resume Challenge
The full story behind this site — DNS rabbit holes, the visitor counter, SAM, and CI/CD.
Read the journey →SAA-C03
Solutions Architect study plan
Nightly guides and quizzes aimed at AWS Solutions Architect – Associate, tied to real project patterns.
Open the study plan →
Global Ski Atlas on AWS
Docker on ECS/Fargate runs OSM → GeoParquet/PMTiles, then loads Parquet into DynamoDB for ywiki.
Visit globalskiatlas.com →
ywiki
Serverless Markdown wiki seeded from Ski Atlas Parquet into DynamoDB — Cognito write auth and revision workflow.
View on GitHub →Platform labs
Same pattern, more stacks
Mapping and cloud playgrounds — each hub explains why I use the platform and links demos as they ship.