Free lesson · AWS Fundamentals

Choosing your path

Easy6 min read

Start With The Sentence

Before choosing a path, finish this sentence: "In six months I want to be able to ___."

The answers that lead to different paths look like this:

• "…build and ship application features on AWS without asking an infrastructure team"
• "…own the platform my company's engineers deploy onto"
• "…be on call for a production system and not dread it"
• "…design systems in an interview without freezing when someone asks about scale"
• "…pass a specific exam by a specific date"
• "…stop feeling lost when my colleagues talk about VPCs"

Each of these has a different shortest route. Picking the wrong one costs you months, and the most common wrong pick is defaulting to a certification path when the goal was competence.

The Six Paths

graph TD
    S{What is your goal?} --> P1[Ship features on AWS]
    S --> P2[Own the platform]
    S --> P3[Operate reliably on call]
    S --> P4[Design systems / interview]
    S --> P5[Pass a specific exam]
    S --> P6[General fluency]
    P1 --> D[Developer Path]
    P2 --> O[Platform Path]
    P3 --> R[SRE Path]
    P4 --> A[Architect and Interview Path]
    P5 --> C[Certification Path]
    P6 --> F[Foundations Path]

This diagram is a decision tree starting from the question, what is your goal. Six branches lead to six outcomes. Shipping features on AWS leads to the Developer Path. Owning the platform leads to the Platform Path. Operating reliably on call leads to the SRE Path. Designing systems or interviewing leads to the Architect and Interview Path. Passing a specific exam leads to the Certification Path. General fluency leads to the Foundations Path.

Path 1 - Foundations

For: anyone new to AWS, or anyone who has used a few services without understanding the model underneath. Time: roughly 12–15 hours.

Then pick one of the paths below. Foundations is not a destination - it is the prerequisite everything else assumes.

Important: Modules 02 and 03 - Identity and Networking - are the two that most people skip and every one of them regrets it. Nearly every confusing AWS problem you will hit in your first year is an IAM permission you did not understand or a route table you did not read. Do these properly before moving on. They are the highest-return hours in the entire catalog.

Path 2 - Developer

For: application engineers building services that run on AWS. Time: roughly 30–35 hours. Ends at: Developer – Associate (DVA-C02) if you want the credential.

1. Foundations path above (Modules 00–05)
2. Course 1, Module 06 - Databases
3. Course 1, Module 07 - Application Integration & Messaging
4. Course 1, Module 09 - Infrastructure as Code & Deployment
5. Course 2 - Developer on AWS (14 topics, the connective track)
6. Course 1, Module 08 - Observability, and Module 13 - Cost
7. Optional: Course 7, Module 03 - DVA-C02 overlay

Path 3 - DevOps / Platform Engineering

For: engineers who own the infrastructure other engineers deploy onto. Time: roughly 40–45 hours. Ends at: DevOps Engineer – Professional (DOP-C02).

1. Foundations path (Modules 00–05)
2. Course 1, Module 09 - IaC & Deployment
3. Course 1, Module 08 - Observability & Operations
4. Course 1, Module 10 - Security, Governance & Compliance
5. Course 3 - DevOps & Platform Engineering on AWS (14 topics)
6. Course 1, Module 13 - Cost, FinOps & Optimisation
7. Optional: Course 7, Module 07 - DOP-C02 overlay

Tip: DOP-C02 is a Professional exam that assumes Associate-level knowledge across development and operations. If you are coming from a pure operations background, work Course 2 before Course 3. If you are coming from development, you have the harder gap in Module 10 and Course 4's reliability material.

Path 4 - SRE / CloudOps

For: engineers responsible for keeping production up. Time: roughly 30–35 hours. Ends at: CloudOps Engineer – Associate.

1. Foundations path (Modules 00–05)
2. Course 1, Module 08 - Observability & Operations
3. Course 1, Module 06 - Databases (operational sections)
4. Course 4 - SRE & CloudOps on AWS (13 topics)
5. Course 1, Module 10 - Security, and Module 13 - Cost
6. Optional: Course 7, Module 04 - CloudOps Associate overlay

Path 5 - Architect And Interview

For: engineers designing systems, and anyone with a system design interview coming. Time: roughly 40–50 hours. Ends at: Solutions Architect Associate or Professional, plus interview readiness.

1. Foundations path (Modules 00–05)
2. Course 1, Modules 06 and 07 - Databases, Integration & Messaging
3. Course 5 - AWS Solutions Architecture (12 topics)
4. Course 6 - AWS for System Design Interviews (20 topics)
5. Optional: Course 7, Module 02 - SAA-C03 overlay, then Module 06 - SAP-C02

Important: If your goal is passing a FAANG system design interview, Course 6 matters far more than any certification, and you can start it earlier than this sequence suggests - after Modules 01–05. Certifications test whether you can select the right AWS service. System design interviews test whether you understand the primitive underneath the service, and frequently penalise candidates who name products instead of reasoning about tradeoffs. These are genuinely different skills.

Path 6 - Certification-First

For: you have an exam date and a deadline. Time: varies by exam, typically 40–120 hours.

1. Go directly to the relevant module in Course 7 - Certification Prep
2. Read the exam orientation topic and the blueprint map
3. The blueprint map lists exactly which Course 1–5 topics cover each exam objective. Work that list.
4. Read the gap lessons - material the exam tests that the job does not
5. Work the scenario drill set
6. Use the study plan for pacing

This is the only path that runs backwards - from the exam objectives into the content, rather than from the content toward competence. It is efficient for passing and less effective for retention. If you have the time, run a role path and take the exam at the end of it instead.

Choosing Between Certification And Competence

An honest note, because the answer depends on who you are.

Certifications matter a great deal for consultancies and AWS partners with tier requirements, for government and regulated contracting, for getting past HR screens at mid-market companies, and for engineers changing careers who need a credible signal on a thin résumé.

Certifications matter comparatively little in senior interviews at large product companies, where the loop tests design reasoning and coding rather than service selection.

Both statements are true at once. The mistake is assuming one applies to your situation because you read it somewhere.

Warning: The most common path error is spending four months on certifications when the goal was a job at a company that does not weight them, or skipping certifications entirely when the target employer's partner status requires them. Find out what your specific target actually rewards before committing months. Course 7 contains a topic dedicated to this question, written by an Amazon Principal Engineer and Bar Raiser who has conducted over 300 interviews.

Practice

Exercise: Starter. Write your six-month sentence from the top of this topic. Pick the path that serves it.

Intermediate. Take your chosen path and put dates against each step in a calendar, at a pace you will actually sustain. Most people overestimate weekly study time by roughly double.

Advanced. Find three job postings for the role you want. List every AWS service and concept named across all three. Compare that list against your chosen path and adjust - if something appears in all three postings and nowhere in your path, add the relevant module.

Related Topics

• Module 00 Topic 1 - How to use this course
• Module 00 Topic 3 - Setting up a learning account safely
• Module 00 Topic 5 - How AWS knowledge is actually tested
• Course 7 - Certification Prep

Back to AWS Fundamentals