Start here

Level 0 follows real requests through AWS, one step at a time. Three minutes on this page will make every graph easier to read.

1. How AWS is laid out

Everything you'll see sits inside these boxes. Each box is drawn the same way in every graph.

OrganizationAll of a company's AWS accounts, with one bill and shared guardrails.

2. How to read a graph

  • Small boxes are services. The coloured stripe says what kind (the key under each graph lists them).
  • Big boxes are places: accounts, Regions, VPCs, subnets. Something drawn inside a box lives there.
  • Faint lines are connections the request will use.
  • 3The orange arrow is the current step, with its number and title on the graph.
  • 4Red means refused, or what happens when something goes wrong.
  • →Next / Back or the arrow keys move through the steps. Click any step to jump to it.
  • abcUnderlined words open a plain-English definition.
  • { }Show me the real thing reveals the actual JSON, SQL or HTTP. Optional.
  • Exam tips are SAA-C03 facts hiding in that step. Optional too.

3. A good order

Set up AWS

  1. 1Day 0: set up AWSMake an account, lock away root, build an organization, sign in safely.
  2. 2Day 0 with Control TowerThe same result, built for you. Meet preventive and detective guardrails.
  3. 3Create the databaseOne admin click, followed through every check AWS makes.
  4. 4Wrong RegionThe same admin gets refused. See why AdministratorAccess is not the last word.

Design Todo.io

  1. 5Add a todo: EC2 + RDS MySQLThe classic setup: a server in a public subnet, a database in a private one.
  2. 6Switch the database to DynamoDBSame request, but now IAM approves every database call.
  3. 7Switch to LambdaNo server at all. Then try Lambda + MySQL and see why a VPC changes things.
  4. 8Turn on the add-onsA background job through SQS, and live updates pushed back to your browser.
Begin with Day 0: set up AWS →