Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Cloud architecture
Compare two cloud services in writing and design a system
What you'll learn
Requirements to design
Architecture trade-offs
Single point of failure
Decision record
Slow dependency
Choosing what to drop
Practice
Write the decision record for a choice that has already been made30 min
Turn a one paragraph brief into the requirements you would design against25 min
Chapter 4
Cloud platforms
Read a cloud bill and find which services cost most
What you'll learn
Core cloud services
Identity and permissions
Service tradeoffs
Cloud cost drivers
Well-Architected review
Practice
Split ten cloud failures between the provider and you15 min
Decide what to encrypt: at rest, in transit, or both20 min
Chapter 4
Networking fundamentals
Trace a web request and write rules for app connections
What you'll learn
Request path
Subnet range
Network layers
Network access controls
Cloud network placement
Joining networks
Practice
Place a three-tier app into a cloud network and write the rules between the parts25 min
Find the three rules that let too much in20 min
Chapter 6
Security fundamentals
Spot phishing emails and fix a system's weak security settings
What you'll learn
CIA triad
Least privilege
Defense in depth
Attack surface
Chapter 6
Access management
Choose the least access that works and flag broad permissions
What you'll learn
Identity and access
Least privilege
Role-based access
Multi-factor authentication
Federation trust
Access audit
Practice
Evaluate an Urgent Access Request Using Least Privilege15 min
Chapter 7
Cloud costs
Build a cost dashboard and set a spend alert
What you'll learn
Cost allocation
Cost per unit
Rightsizing resources
Commitment break-even
Spend that looks wrong
Limits set in advance
Cheaper for the same work
Practice
Build a Reserved Instance Break-Even Analysis and Recommendation30 min
7 more in the plan
Cloud migrationPick how to move several systems and plan the orderCh 2
What you'll learn
Migration strategies
Dependency order
Data synchronisation
Rollback plan
Practice
Sort Three Workloads Into Migration Strategies15 min
Documenting infrastructure workWrite a task guide and draw how system parts connectCh 2
What you'll learn
Runbook purpose
Decision record
Document type
Current version
Infrastructure as codeRead server-building code and find where the real setup differsCh 4
What you'll learn
Desired state
Plan diff
State file
Module boundary
Configuration drift
Practice
Read a Terraform Config and Describe What It Builds15 min
Critical thinkingSpot a weak assumption and ask where numbers come fromCh 8
What you'll learn
The hidden assumption
Argue the other side
The base rate
Fact vs inference
Wanting it to be true
Practice
Spot the Weak Link in an Argument10 min
Problem solvingTest each possible cause of a problem instead of guessingCh 8
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Break an Ambiguous Problem into Actionable Parts20 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 9
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 9
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Practice
Write a Request That Makes It Easy to Say Yes10 min
Your plan
Chapter by chapter.
13 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of a Cloud Architect
StartFree
2~2 wks
Plan cloud moves and document every tradeoff
Skills
3~2 wks
Build a cloud environment managed as code
Project
4~2 wks
Set up cloud networks from code
Skills
51–2 wks
Talk to two working cloud architects
People
6~2 wks
Control who can reach your systems
Skills
7~2 wks
Control cloud costs through engineering
Skills
8~2 wks
Find the cause before you fix it
Skills
9~2 wks
Make yourself understood across a team
Skills
10~2 wks
Capstone: deploy a secure, autoscaling web app
Project
111–2 wks
Answer the questions interviewers ask
Interview
121–2 wks
Decide how you will get in
Decide
13on your timeline
Send your first applications
Apply
The job
What a Cloud Architect does
Decides how an organization's cloud systems should be shaped so apps scale, stay secure, and do not overspend. Works one level above the Cloud Engineer: sets the design and trade-offs while engineers build and run the pieces.
The work
Design the overall shape of cloud systems on AWS, Azure, or Google Cloud Platform (GCP)
Compare services and trade-offs to balance speed, reliability, security, and cost
Set standards for networks, identity and access management (IAM), and data protection
Estimate and control cloud spend with sizing, pricing models, and budget limits
Plan how to move existing systems to the cloud without breaking live services
Write design documents and diagrams that engineers can build from
Review proposed designs with security, finance, and product teams
Guide engineers on patterns and check that builds match the agreed design
A typical day
Review a team's design request and sketch options with their trade-offs
Meet product and security leads to agree requirements, risks, and budget
Compare cloud services and pricing, then pick the best fit
Write or update a design document with diagrams and clear decisions
Walk engineers through a design and answer build questions
Check a live system against cost, security, and reliability targets
Tools
Cloud platforms: AWS, Microsoft Azure, Google Cloud PlatformInfrastructure as code: Terraform, AWS CloudFormationDiagramming: Lucidchart, draw.io, cloud architecture diagramsContainers and scaling: Kubernetes, DockerCost and governance: AWS Cost Explorer, Azure Cost ManagementIdentity and security: cloud IAM, single sign-on, key managementNetworking: virtual networks, load balancers, content delivery networks
Ways in
There is more than one route.
Ways to study
Bachelor degree in computer science, IT, software engineering, or networking
Diploma or certificate in cloud computing or systems architecture
Vendor architect certification such as AWS, Azure, or GCP (recognized worldwide)
Self-study with labs plus a strong portfolio of cloud designs
On-the-job growth from a cloud or DevOps engineering role
How people get their first job
Start as a cloud or DevOps engineer and learn how systems fit together
Earn a vendor associate cloud certification, then a professional architect one
Design and document a small multi-service cloud system in a public portfolio
Shadow a senior architect on design reviews and migration plans
Lead the design of one feature's infrastructure within an engineering team
How long does it take to become a cloud architect with Welica?
The plan is 13 chapters, 5–6 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelor degree in computer science, IT, software engineering, or networking, diploma or certificate in cloud computing or systems architecture, vendor architect certification such as AWS, Azure, or GCP (recognized worldwide), self-study with labs plus a strong portfolio of cloud designs, or on-the-job growth from a cloud or DevOps engineering role.
What is free?
Chapter 1, See the work of a Cloud Architect, is free for good. Premium unlocks the rest of the plan.