brianpfeil.com valid

Brian Pfeil

Brian Pfeil — Principal Cloud Architect and AWS Community Builder. Free courses, cloud architecture guides, learning resources and hands-on notes on AWS, serverless and AI.

For agents: Brian Pfeil's personal site: free AWS and serverless courses, cloud architecture guides and notes on AI, including running LLMs locally on Apple Silicon.

awscloud architectureserverlessfree coursesllm local

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T13:24:11.249Z. Cached copy · Source on brianpfeil.com

# Brian Pfeil

> Brian Pfeil — Principal Cloud Architect and AWS Community Builder. Free courses, cloud architecture guides, learning resources and hands-on notes on AWS, serverless and AI.

About Brian Pfeil: 30 years of building things with technology, Principal Cloud Architect and AWS Community Builder, sharing what I learn so others can learn from it. https://brianpfeil.com/about/

The full text of every post and project is in https://brianpfeil.com/llms-full.txt.

## Architecture guides

- [The Architecture Review Checklist: 41 Questions I Ask](https://brianpfeil.com/architecture/architecture-review-checklist/): The questions that come up in almost every cloud architecture review I run — compute, ownership, security, data, networking, resilience, operations and cost — as a checklist you can use before yours.
- [How to Prepare for an Architecture Review](https://brianpfeil.com/architecture/prepare-for-an-architecture-review/): What to bring to a cloud architecture review so it's one meeting, not three: entry criteria, the diagrams reviewers need, the cross-cutting concerns people forget, and how to handle open questions.
- [The Compute Ladder: Serverless-First, Then Work Backwards](https://brianpfeil.com/architecture/compute-ladder/): A simple order of preference for where code runs — SaaS, serverless, containers, servers — why each rung up removes work, and how to design the ideal version first and only step down for a real constraint.
- [Cloud Architecture Anti-Patterns (and What to Do Instead)](https://brianpfeil.com/architecture/architecture-anti-patterns/): Seventeen patterns I flag again and again in cloud architecture reviews — glue-code functions, synchronous long jobs, polling, credentials on disk, jump hosts — each with the alternative I recommend.
- [Architecture Diagrams and Decision Records Reviewers Trust](https://brianpfeil.com/architecture/diagrams-and-decision-records/): How to draw cloud architecture diagrams that answer questions before they're asked, and a lightweight architecture decision record (ADR) template for the choices you'll be asked to defend.
- [Guardrails and Paved Roads: Scaling Cloud Architecture Across Teams](https://brianpfeil.com/architecture/guardrails-and-paved-roads/): How a central cloud team can help dozens of teams build well without becoming a bottleneck: configuration as a service, compliance as code, reusable IaC constructs, identity-based segmentation and small blast radii.

## Courses

- [C++ Standard Library](https://brianpfeil.com/courses/cpp-standard-library/): A practical, category-by-category tour of the most-used C++ standard library classes — containers, strings, smart pointers, algorithms, and more — so you reach for the right one by reflex. (13 lessons)
- [mlx-lm](https://brianpfeil.com/courses/mlx-lm/): Run, quantize, serve, and fine-tune LLMs locally on Apple Silicon with Apple's mlx-lm — the CLI and Python surfaces, from first principles, every example verified on an M4 Pro. (12 less
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=brianpfeil.com · GET /v1/domain/brianpfeil.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for brianpfeil.com:
1. POST https://agentwebmap.com/v1/sites/brianpfeil.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://brianpfeil.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/brianpfeil.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/brianpfeil.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.