AWS Solutions Architect
Choose AWS architectures for reasons, not from memory.
Learn to make service decisions under real engineering constraints.
Build the account, identity, networking, resilience, and cost mental models first. Then use architecture scenarios to decide which services fit the constraint. The Services library stays available as reference instead of becoming a list you must memorize.
For engineers preparing for SAA-C03 who also want judgment that remains useful after the exam.
Start with the account and responsibility model that every AWS architecture decision assumes.
After the core journey
- Turn requirements into architecture constraints and tradeoffs.
- Choose services by workload, resilience, security, and cost needs.
- Recognize exam traps without flattening AWS into flashcards.
RecommendedFoundations: 9 lessons available
Begin with Foundations
AWS Account Model
Teams put unrelated workloads in one account and then try to recover isolation with tags, naming conventions, or manual permissions.
AWS Global Infrastructure
Learners memorize service names without knowing whether the service is regional, zonal, edge-based, or globally scoped.
Shared Responsibility Model
Learners memorize the phrase but cannot apply it differently to EC2, S3, RDS, Lambda, and managed databases.
Learning orientation
Core journey first. Supporting resources when you need them.
These sections have different jobs. The labels show whether a destination moves the main journey forward or supports it.
Foundations(9)
Build the account, identity, networking, and responsibility mental models first.
Architecture Scenarios(17)
Practice turning requirements into resilient service choices.
Exam Review(14)
Test service comparisons, domain judgment, and common SAA-C03 traps.
Services(100)
Look up what a service does and when it belongs in an architecture.
Labs(3)
Turn architecture decisions into implementation-ready plans.