A small travel company runs its booking site on a single rented server that goes down during busy weekends. You design its move to a managed cloud setup that survives a failure and has a cost the owners can predict.
A cloud solutions architect designs how a system runs in the cloud: services, networking, security, cost and failure handling. You turn requirements into a design a team can build, and explain the trade-offs to engineers and managers.
Goal: Learn what the cloud is and deploy a simple app with storage, a database and a model call using one provider.
Before you start
Beginner · 7 weeks
Week 1: Cloud vocabulary
Region, zone, virtual machine, container, serverless · Shared responsibility · Pay for use · Accounts and billing alerts
Practice: Create an account, set a budget alert and list five services by purpose.
Practice: Create an account, set a budget alert and list five services by purpose.
Common pitfalls
Think first, then reveal
What is the shared responsibility model?
Think first, then reveal
Why not use the root account?
Think first, then reveal
Virtual machine versus container versus serverless?
Think first, then reveal
How do you avoid surprise bills?
Write down traffic, acceptable downtime, data rules and budget before drawing anything.
Turning business needs into targets for availability, recovery time, data location and cost.
Why this pick
An architecture is only right relative to what the business needs, and those needs differ for every system.
What the role must know
Beginner mistake
Cloud
Design
AI workloads
Think first, then reveal
What is the shared responsibility model?
Think first, then reveal
Why not use the root account?
Think first, then reveal
Virtual machine versus container versus serverless?
Think first, then reveal
How do you avoid surprise bills?
Think first, then reveal
How do you design for availability?
Think first, then reveal
Why use infrastructure as code?
Think first, then reveal
What drives data transfer cost?
Think first, then reveal
Hosted model API versus self-hosting?
Think first, then reveal
How do you decide between regions for resilience?
Think first, then reveal
How do you run FinOps without blocking engineers?
Think first, then reveal
What is vendor lock-in and how much should you avoid it?
Think first, then reveal
How do you control AI infrastructure code from assistants?