The short version
Pick the 8-week plan if you are new to professional-level AWS design or work full time. Pick the 4-week plan only if you already design multi-account AWS solutions and can give about 10 hours a week. Hours below are general estimates, and they vary a lot with your experience.
Before you start
AWS published the SAP-C03 exam guide on October 27, 2026. It weights the five domains 25% (architecture design and implementation built for the cloud), 25% (security, compliance, and governance), 15% (cost-optimized architecture design), 15% (resilience, migration, and business continuity) and 20% (operational excellence and automation). Shift your time toward the heavier domains. The plans below spread time evenly across the domains, with extra weight on the new areas AWS highlighted, because those are the ones most study material misses; adjust them to the weightings.
You will need a hands-on AWS account. Reading about Transit Gateway or Organizations is not the same as having used them. Keep costs low by deleting what you build.
How the plans use practice exams
Practice exams work best at three points.
- Baseline at the start, taken cold. It shows your weak domains. A low score here is normal.
- Checkpoint in the middle, to see if your weak spots moved.
- Readiness check near the end, in one sitting with the clock running.
After each attempt, read the explanation for every question, including the ones you got right. Write down the deciding detail in each scenario. That habit is the skill the exam rewards.
The 4-week plan (about 10 to 12 hours a week)
For people who already work with AWS at architect level.
Week 1: Baseline and cloud-native design.
- Take a first practice set cold and sort misses by domain.
- Study domain 1: containers (ECS, EKS, Fargate), serverless (Lambda, Step Functions), event-driven patterns, API design, and the new service mesh options, VPC Lattice and ECS Service Connect.
- Do one lab where you connect services across two VPCs.
Week 2: Security and governance, then cost.
- Domain 2: AWS Organizations, service control policies, resource control policies, Control Tower, IAM Identity Center, KMS and key policies, cross-account access.
- Domain 3: purchase options, storage tiers, data transfer costs, rightsizing.
- Take a mid-point practice set at the end of the week.
Week 3: Resilience, migration, and operations.
- Domain 4: recovery objectives, backup and disaster recovery strategies, multi-Region design, migration strategies and tools, Fault Injection Service, Resilience Hub.
- Domain 5: CloudFormation and CDK, multi-account pipelines, CloudWatch, Systems Manager, observability.
Week 4: Generative AI, review and test.
- Study the Bedrock topics: model access, cross-Region inference, guardrails, RAG, AgentCore.
- Take a full-length timed set and review every miss.
- Spend the rest on your two weakest domains.
The 8-week plan (about 6 to 8 hours a week)
For people with some AWS experience, or less time per week.
| Week | Focus | What to do |
|---|---|---|
| 1 | Baseline and networking | Cold practice set. Review VPC design, Transit Gateway, PrivateLink, Direct Connect, Route 53 |
| 2 | Domain 1, compute and containers | ECS, EKS, Fargate, Lambda, Step Functions. One lab per service family |
| 3 | Domain 1, data and integration | Databases, streaming, lakehouse, event buses, API patterns |
| 4 | Domain 2, security | Organizations, SCPs and RCPs, IAM, KMS. Midpoint practice set |
| 5 | Domain 3 and governance | Cost options, data transfer, tagging, budgets, Control Tower |
| 6 | Domain 4, resilience and migration | DR strategies, backup, migration tools, resilience testing |
| 7 | Domain 5 and generative AI | Pipelines, observability, Systems Manager, Bedrock topics |
| 8 | Test and review | Full-length timed set, review misses, rest |
A weekly rhythm that works
- Two or three study sessions of 90 minutes for reading and labs.
- One session for practice questions, 30 to 40 at a time, with full review.
- One short session to rewrite your notes into a one-page comparison of confusable services.
Reading the AWS material
The AWS documentation and the Well-Architected Framework are the main sources for this exam. Use them when an explanation leaves a gap. AWS also offers exam preparation content on Skill Builder, and its exam guide lists in-scope services once published.
The last 3 days
- Three days out: take your last full set under real timing. Review only the misses.
- Two days out: reread your comparison sheet and the service-name list from the exam Help button. No new topics.
- The day before: light review for an hour at most. Check your ID, your booking time and your setup (online proctoring needs a clear desk and a working camera). Sleep.
- Exam day: eat, arrive early or log in early, and use the pace check from the format page.
More guides for SAP-C03
- SAP-C03 Sample Questions With Answers
- Is the SAP-C03 Exam Hard? An Honest Look
- SAP-C03 Prerequisites and Skills Check
- SAP-C03 Renewal and Retakes Explained
- Is SAP-C03 Worth It? An Honest Look
- SAP-C03 Cheat Sheet: Key Facts to Review
- DVA-C03 vs SAP-C03: Which AWS Exam First?
Next step
Go through domains explained while you follow the plan, and use the SAP-C03 practice tests at the checkpoints above. For general habits, see how to study for IT certification exams.
Frequently asked questions
How many hours do I need?
Many working architects need 60 to 120 hours, but this varies widely. Strong multi-account experience shortens it.
Should I wait for the exam guide?
No. The guide was published on October 27, 2026. Read it first and weight your time by its domain percentages (25/25/15/15/20).
Can I use SAP-C02 material?
Partly. The core architecture skills carry over, but SAP-C02 material misses the generative AI, resilience engineering and post-quantum topics AWS added.