AWS Road Map: Step by Step Plan by Role and Exam Costs
11 min read ยท 2026-11-03
A good aws road map goes in this order: secure your account and learn IAM, then networking with VPC, then compute, storage and databases, then serverless, containers and infrastructure as code, and finally monitoring, security, cost control and a certification. With steady hands-on practice, six months is a realistic time to design, deploy and run a real application and to sit an Associate exam.
This plan gives you each phase with its duration, concrete steps and a milestone you can check. It also covers which certification fits your role, what the exams cost according to AWS, how to practice without a surprise bill, and how to put training and certifications into a team AWS roadmap you can present to your manager or leadership team.
The roadmap at a glance
Goal: Design, deploy, secure and operate a real application on AWS, and pass an Associate level certification. Duration: 6 months, at about 6 to 8 hours per week
Account and IAM (Weeks 1 to 3)
Set up an account you can practice on safely and understand who can do what.
- Create an account, turn on MFA for the root user, and stop using root for daily work.
- Set up AWS Budgets and billing alerts before you launch anything.
- Learn IAM users, groups, roles and policies, and practice reading policy JSON line by line.
- Use IAM Identity Center for console and CLI access with short lived credentials.
- Install the AWS CLI and run basic commands against S3 and IAM.
Milestone: A secured account with MFA, a budget alert and least privilege access through Identity Center.
Networking and compute (Weeks 4 to 7)
Build a network and run servers inside it the right way.
- Design a VPC with public and private subnets across two Availability Zones.
- Configure route tables, an internet gateway, a NAT gateway and security groups.
- Launch EC2 instances with user data scripts and connect through Session Manager instead of open SSH ports.
- Put instances behind an Application Load Balancer with an Auto Scaling group.
- Use Route 53 for DNS and ACM for TLS certificates.
Milestone: A web app served over HTTPS from auto scaled instances in private subnets.
Storage and databases (Weeks 8 to 11)
Pick the right managed service for files, relational data and key value data.
- Create S3 buckets with versioning, lifecycle rules and public access blocked.
- Serve a static site through CloudFront with origin access control.
- Run RDS or Aurora in private subnets and connect your app to it.
- Model a DynamoDB table around access patterns and partition keys.
- Move secrets into Secrets Manager or Parameter Store.
Milestone: Your app reads from RDS and S3 through IAM roles, with no credentials in the code.
Serverless and events (Weeks 12 to 15)
Build event driven features without managing servers.
- Write Lambda functions and expose them through API Gateway HTTP APIs.
- Decouple services with SQS, SNS and EventBridge rules.
- Orchestrate multi step workflows with Step Functions.
- Add sign in to an API with Amazon Cognito user pools.
- Learn cold starts, concurrency limits, timeouts and dead letter queues.
Milestone: A serverless API with authentication, a background job on a queue and DynamoDB storage.
Containers and infrastructure as code (Weeks 16 to 20)
Run containers and rebuild everything from code.
- Push images to ECR and run a service on ECS with Fargate.
- Define your stack with AWS CDK, CloudFormation or Terraform.
- Build a CI/CD pipeline with GitHub Actions using OIDC roles, or with CodePipeline.
- Look at EKS basics if the jobs you target use Kubernetes.
- Tag every resource for owner, project and cost.
Milestone: One pipeline run recreates your whole application stack from an empty account.
Operate, secure and certify (Weeks 21 to 26)
Run your workload like a professional and prove it.
- Build CloudWatch dashboards, log queries and alarms for your app.
- Turn on CloudTrail, GuardDuty and AWS Config.
- Review your design against the pillars of the Well-Architected Framework.
- Use Cost Explorer to find idle or oversized resources.
- Take practice exams for Solutions Architect Associate or Developer Associate, then book and sit the real one before the end of this phase.
Milestone: An Associate exam passed and one documented, monitored project you can show.
What "AWS roadmap" can mean
People who search "AWS roadmap" or "roadmap AWS" usually want a learning or career path like the one above. There is a second meaning, though. AWS publishes public roadmaps for some of its own services, for example its containers roadmap on GitHub, where the service teams list features they are working on and users can comment.
That product roadmap is useful when you plan a project, because it tells you whether a feature you need is coming. It will not teach you AWS. If your goal is a skill, a new job or a certification, follow a learning path. If your goal is a technical decision, read the public roadmap of the services you depend on and treat it as a direction, not a promise with dates.
Learning AWS fundamentals before you start
You do not need to be a system administrator, but some basics make every service easier to understand. Linux command line, networking ideas like IP addresses, CIDR ranges, DNS and HTTP, and one scripting language such as Python or Bash will save you weeks of confusion.
If you are new to tech, add two to four weeks before phase one to cover these AWS fundamentals: what a server is, how a request reaches a website, and how to read a log file. Then treat AWS as a set of building blocks. There are hundreds of services, but a small core set covers most real architectures. Learn that core deeply and pick up niche services only when a project needs them.
- Required: Linux command line, networking basics, one scripting language.
- Helpful: Git, Docker, a web framework you can deploy.
- Later: Kubernetes, data engineering tools, machine learning services.
AWS certification path: levels, costs and order
AWS certifications come in levels. Foundational covers Cloud Practitioner and AI Practitioner. Associate covers Solutions Architect, Developer, CloudOps Engineer, Data Engineer and Machine Learning Engineer. Professional and Specialty come after, and AWS aims Professional exams at people with two or more years of AWS experience.
According to AWS, on the "Before testing" section of its Certification Policies page, exam prices in USD are 100 for Foundational, 150 for Associate and 300 for Professional and Specialty. The same page says prices are updated at least once a year in May to reflect exchange rates, so check the price in your currency before you book. It also says each exam appointment can only be rescheduled twice, and that non native English speakers taking an exam in English can request a 30 minute extension.
According to the AWS Recertification policy page, a certification is valid for three years from the date you earn it. And according to the AWS Advanced Networking Specialty exam page, that exam is being retired: the last day to take it is December 31, 2026. Do not build a new path around it.
A sensible order for most people:
- Skip Cloud Practitioner if you already work in tech. Take it if your role is non technical or you are switching careers.
- Take one Associate exam that matches your role during phase six, once phases one to five are done and you have a working project.
- Aim for Professional or a Specialty such as Security only after real project experience.
AWS roadmap by role
The six phases are the shared base. After phase three, shift your effort toward the role you want and pick the matching certification.
- Solutions architect: go deeper on VPC design, multi account setups with AWS Organizations, high availability and disaster recovery. Target Solutions Architect Associate, then Professional.
- Developer: spend more time in phases four and five on Lambda, API Gateway, DynamoDB, Cognito and CI/CD. Target Developer Associate.
- DevOps or CloudOps engineer: focus on infrastructure as code, pipelines, CloudWatch, patching and incident response. Target CloudOps Engineer Associate, then DevOps Engineer Professional.
- Data engineer: after phase three, move to S3 data lakes, Glue, Athena, Redshift and Kinesis. Target Data Engineer Associate.
- Machine learning or AI: learn SageMaker and Bedrock after the core phases. Target AI Practitioner first if you are new, then Machine Learning Engineer Associate.
- Security: go deep on IAM policies, KMS, Secrets Manager, GuardDuty, Security Hub and logging. Target Security Specialty once you have hands-on experience.
Practice projects that keep your bill low
Hands-on work is what makes AWS stick, but surprise charges are a real risk. Free Tier terms change over time and do not cover everything, so read the current terms in your billing console. Some resources, such as NAT gateways, load balancers and running databases, charge by the hour even when nobody uses them.
Set a budget alert on day one, prefer serverless services for early projects, and tear down your stack after each session. Once you define it in code, rebuilding takes minutes, so you have no reason to leave it running. Document each project with a diagram, the reason for each service choice, your security decisions and an estimated monthly cost.
- A static portfolio site on S3 and CloudFront with a custom domain and HTTPS.
- A serverless URL shortener with API Gateway, Lambda and DynamoDB.
- An image processing pipeline triggered by S3 uploads through EventBridge and Step Functions.
- A containerized web app on ECS Fargate with RDS, deployed by a pipeline.
Building a team AWS roadmap for training and certifications
If you are an IT lead, engineering manager, project manager or consultant, your question is often different: how do I get my team ready for AWS on a schedule leadership can follow? The technical side of moving systems (assessment, landing zone, migration waves) is covered step by step in the AWS migration plan guide. This section covers the people side: who learns what, by when, and which certification lands before which piece of work.
Start by mapping each person to one role path from the section above. Then place their training phases and exam dates on the same timeline as your delivery work, so skills arrive before the project needs them, not after.
Two calendar rules help. Put exam dates in the plan with slack before key milestones, since rescheduling is limited. And remove the Advanced Networking Specialty from any plan that runs past December 31, 2026; network specialists can target Solutions Architect Professional instead.
- Assign a role path to each person. Owner: engineering manager. Dependency: list of planned AWS workloads. Risk: generic training that does not match the work. Success criterion: every person has one role path and a target exam.
- Foundations training (IAM, VPC, budgets). Owner: cloud lead. Dependency: sandbox accounts with budget alerts. Risk: learners practice in production accounts. Success criterion: everyone completes the phase one and two milestones in a sandbox.
- First Associate exams for the core team. Owner: each engineer, booked with the manager. Dependency: phases one to five done, one working project. Risk: exam dates clash with delivery deadlines, and each appointment can only be rescheduled twice. Success criterion: core team certified before the first pilot goes live.
- Support the pilot workload. Owner: pilot team lead. Dependency: landing zone ready (see the migration plan). Risk: knowledge sits with one person. Success criterion: at least two people can deploy, monitor and roll back the pilot.
- Train ahead of each later stage. Owner: project manager. Dependency: delivery schedule. Risk: training lands after the work it supports. Success criterion: role path finished before the stage it supports starts.
- Specialty, Professional and renewals. Owner: engineering manager. Dependency: real project experience. Risk: certifications lapse after three years. Success criterion: every renewal date sits on the roadmap.
How to know you are ready
You are ready for cloud work when you can design a secure, highly available architecture for a typical web app, explain why you chose each service, deploy it from code, and fix permission and connectivity issues without guessing. You should also be able to estimate its monthly cost and name its biggest cost drivers.
Test yourself with a design exercise. Take written requirements for traffic, data and availability, sketch the architecture on paper, then build it in a weekend with infrastructure as code. If you can defend each choice against the Well-Architected pillars, your skills are ready for real projects.
Common mistakes to avoid
- Launching resources before setting a budget leads to surprise charges, so create a billing alert on day one.
- Using the root account or long lived access keys is risky, so work through Identity Center and IAM roles.
- Giving everything AdministratorAccess hides how IAM works, so write a scoped policy for each workload.
- Building everything by clicking in the console leaves nothing reproducible, so move to infrastructure as code by month four.
- Trying to learn every service spreads you thin, so master the core services before niche ones.
- Studying only for the exam leaves gaps at work, so build and document a real project in every phase.
Frequently asked questions
What is the best AWS road map for a beginner?
Start with the fundamentals of Linux and networking, then follow the order of this plan: IAM, VPC, compute, storage and databases, serverless, containers and code, then operations. Build one small project per phase. Cloud Practitioner is a good first exam if you are new to tech.
How long does it take to learn AWS?
Basic comfort with the core services takes a few weeks. Designing and running a real application with networking, databases, serverless and infrastructure as code takes around six months of steady hands-on practice. Deep expertise in security or data takes longer.
Which AWS certification should I take first?
With technical experience, Solutions Architect Associate is the broadest first choice. Developers focused on serverless often prefer Developer Associate. If you are non technical or switching careers, start with Cloud Practitioner.
How much does an AWS certification exam cost?
According to the AWS Certification Policies page, Foundational exams cost 100 USD, Associate 150 USD, and Professional and Specialty 300 USD. AWS updates prices at least once a year in May to reflect exchange rates. A certification stays valid for three years from the date you earn it.
Can I learn AWS without knowing how to program?
Yes, for the basics and for Cloud Practitioner. Scripting in Python or Bash quickly becomes important for Lambda, automation and infrastructure as code. Most hands-on cloud roles expect you to read and write scripts comfortably.