The reference
Resources
Cornerstone guidance on the AWS decisions that are expensive to reverse. Each one states the trade-off, names the condition under which each option is right, and says where the answer depends on facts only you have.
-
The AWS Well-Architected Framework in Practice
Why the Well-Architected Framework works as a review discipline and fails as a checklist — and how to run one that produces decisions.
-
AWS VPC and Subnet Design: A Practical Reference
Size CIDR blocks, tier subnets, and place NAT gateways so you never have to re-address a production VPC.
-
AWS Multi-Account Architecture and Landing Zones
Decide when account separation beats VPC isolation, and how far to automate account vending before it becomes busywork.
-
Hybrid AWS Connectivity: Direct Connect, VPN and Transit Gateway
Choose between VPN, Direct Connect, and DX+VPN failover based on bandwidth, determinism, and what the workload actually needs.
-
AWS High Availability: Multi-AZ vs Multi-Region
Tell availability apart from durability, size HA to the failure you’re actually defending against, and skip multi-region when backups will do.
-
Choosing AWS Compute: EC2, ECS, EKS, Fargate and Lambda
A decision framework for AWS compute based on operational burden and control, not a feature checklist.
-
AWS Backup and Disaster Recovery: Designing to RTO and RPO
DR strategy starts with business-defined RTO/RPO numbers, not a technology pick — and an untested restore isn’t a plan.
-
AWS vs Azure: An Architecture Decision Framework
A criteria-based framework for choosing AWS or Azure — including the real cases where Azure is the correct answer.
-
AWS Security Baseline for New Accounts
What to configure before the first production workload goes live, ordered by what actually gets exploited first.
-
AWS Migration Planning: A Readiness Framework
Assess the 7 Rs honestly, plan waves around dependencies, and know what actually breaks during cutover.
-
AWS Cost Optimization: A Systematic Approach
A ranked method for cutting AWS spend: eliminate waste, rightsize, commit, then architect — in that order, not reverse.