Audience: a beginner who wants a complete learning path, or an engineer filling gaps across AWS.
Review date: 18 October 2026.
Format: separate, linked Markdown chapters with explanations, practical work, checks, and official references.
Start with the learning plan, complete prerequisites, and set up your account and tools. Then follow the numbered technical chapters. Use the projects to prove that you can combine services into a working system.
For step-by-step implementation, open the tutorial collection. It covers the entire roadmap in subject folders, including an 18-part AI/ML sequence, worked examples, verification, troubleshooting, and cleanup. Use its coverage register to trace original topics to tutorials.
This is a broad curriculum covering the main AWS disciplines and a discovery map for specialized services. Core topics receive detailed treatment; specialist topics include what to learn, when they matter, and where to go deeper. AWS changes continuously, so a finite guide cannot contain every API, regional exception, new launch, or service limit. The service coverage map makes the breadth explicit, and the resource guide explains how to close workload-specific gaps.
Do not try to memorize a product catalog. For every service, learn its purpose, security boundary, failure behavior, scaling model, cost drivers, alternatives, and operating procedures.
| Stage | Chapter | What you should be able to do |
|---|---|---|
| Plan | 00 — Learning plan | Choose a pace and role, track evidence, and sequence the work |
| Prepare | 01 — Prerequisites | Work with Linux, networking, Git, code, SQL, and distributed-system basics |
| Prepare | 02 — Account and tooling | Establish secure access, billing visibility, and a usable local environment |
| Foundations | 03 — Cloud foundations | Explain regions, availability zones, shared responsibility, and cloud economics |
| Foundations | 04 — IAM and identity | Design human and workload access with temporary credentials and least privilege |
| Foundations | 05 — Networking and DNS | Trace requests through VPCs, routes, DNS, firewalls, private endpoints, and hybrid networks |
| Foundations | 06 — Compute and load balancing | Run, scale, patch, and troubleshoot EC2-based applications |
| Foundations | 07 — Storage and backup | Select object, block, file, archival, and backup approaches |
| Foundations | 08 — Databases and caching | Model data and choose transactional, key-value, document, graph, search, and cache systems |
| Foundations | 09 — Security and compliance | Protect data, detect threats, investigate findings, and produce control evidence |
| Build | 10 — Serverless and integration | Build APIs and resilient event-driven workflows |
| Build | 11 — Containers and Kubernetes | Deploy secure container workloads with ECS and EKS |
| Build | 12 — Infrastructure as code | Reproduce environments and manage infrastructure changes safely |
| Build | 13 — DevOps and delivery | Build, test, release, observe, and roll back applications |
| Data | 14 — Data engineering and analytics | Build governed batch and streaming data pipelines |
| AI | 15 — AI, ML, and generative AI | Train or integrate models, evaluate outputs, and operate AI systems |
| Operate | 16 — Observability and operations | Use telemetry to diagnose issues and run services reliably |
| Operate | 17 — Reliability and disaster recovery | Define recovery objectives and demonstrate recovery under failure |
| Design | 18 — Architecture and system design | Turn requirements into defensible technical tradeoffs |
| Scale | 19 — Organizations and governance | Establish account boundaries, guardrails, and centralized governance |
| Optimize | 20 — Cost, FinOps, and performance | Explain a bill, optimize unit costs, and tune bottlenecks |
| Extend | 21 — Migration, hybrid, and edge | Assess, migrate, cut over, and operate hybrid workloads |
| Specialize | 22 — Specialized domains | Explore IoT, media, HPC, end-user computing, industry services, and more |
| File | Purpose |
|---|---|
| 23 — Projects and portfolio | Ten substantial project briefs with acceptance criteria and failure drills |
| 24 — Certifications and career paths | Role-based preparation and current exam lifecycle guidance |
| 25 — Interview and design questions | Technical questions, answer expectations, and design exercises |
| 26 — Master completion checklist | Evidence-based gates for foundations, delivery, operations, and specialization |
| 27 — Glossary and mental models | Terms, distinctions, and common misconceptions |
| 28 — Official resources and updates | Source map and a repeatable update process |
| 29 — CLI and SDK reference | PowerShell-first command examples and SDK patterns |
| 30 — Service coverage map | Service families, priority, and links back to the curriculum |
| 31 — Troubleshooting playbook | Diagnostic sequences for common cloud failures |
| 32 — Engineering templates | Reusable design, lab, incident, cost, threat-model, and runbook templates |
| 33 — Guided starter labs | Two worked CLI labs with validation and cleanup |
- Read the prerequisite chapters and explain the key ideas without notes.
- Draw the data path and trust boundaries before deploying anything.
- Estimate costs and identify the exact account, region, and resource names.
- Implement a small version; preserve configuration in version control.
- Verify both successful behavior and an intentional, reversible failure.
- Record telemetry and explain the root cause, rather than keeping only screenshots.
- Remove temporary resources and check for retained storage, snapshots, endpoints, and logs.
- Complete the mastery checklist using evidence from your own work.
The labs are learning instructions, not a claim that infrastructure has already been deployed or tested in your AWS account. Example commands require your own authorized sandbox and suitable permissions. Cost estimates must use the current prices and your region; no chapter promises that a deployment is free.
- Read chapters 00–02 and create a learning journal using chapter 32.
- Verify your CLI identity and region, then inspect account billing and your plan.
- Complete the private S3 lab in chapter 33.
- Explain why the bucket is private, how you authenticated, what requests could cost, and what remains after cleanup.
- Continue with cloud foundations, IAM, and networking before building larger projects.
Official AWS references are provided within chapters. Service availability, lifecycle, pricing, quotas, account-plan restrictions, and exam versions must be checked before use. The AWS documentation portal and AWS service overview are the starting points for new or omitted workload-specific features.
If this roadmap helps you, star the repository or sponsor Hareram Ray on GitHub to support its continued development. You can also report an issue or submit a pull request with corrections, clearer explanations, or new practical examples.