█
LastWrite
  • > Curriculum
  • > Pricing
  • > For Educators
  • > About
  • > Contact
Log InGet Started

Questions, concerns, bug reports, or suggestions? We read every message, write to us at [email protected].

More ways to reach us →
LastWrite

Structured computer science lessons for aspiring developers and security professionals.

[email protected]

(201) 785-7951

Mon–Fri, 9 AM–5 PM EST

Learn

  • Curriculum
  • Pricing

Company

  • About
  • For Educators & Schools
  • Contact Us

Legal

  • Terms of Service
  • Privacy Policy
© 2026 LastWrite. All rights reserved.
Curriculum/DevOps and Infrastructure/Cloud Platforms — AWS/The Cloud Landscape
35 minBeginner

The Cloud Landscape

After this lesson, you will be able to: Compare AWS, GCP, and Azure; understand why AWS dominates; develop the mental model for thinking about cloud cost.

AWS is the largest cloud provider and the de facto interview standard. This sub-track teaches AWS specifically, but most concepts transfer to GCP and Azure.

This is a free introductory lesson. No purchase required.

The big three (and the others)

AWS (Amazon): ~30-35% market share. Largest service catalog, deepest enterprise. Azure (Microsoft): ~20-25%. Strong in enterprise (Active Directory integration), gaining fast. GCP (Google): ~10-15%. Strong in data + ML; smaller catalog. Others: DigitalOcean / Linode / Vultr for indie / SMB; Cloudflare for edge; Oracle / IBM in legacy enterprise. Pick AWS first; it covers most of the job market. Add Azure if you target Microsoft-heavy industries.

Why AWS dominates (history + lock-in)

AWS launched in 2006 (S3 + EC2). Half a decade head-start meant huge catalog by the time competitors got serious. Network effects: every SaaS integrates with AWS first; cert programs cover AWS; vast hiring pool. Real lock-in: data egress is expensive; rewriting services to GCP / Azure is months of work. Counter-trends: GCP wins on data + ML at large scale; Azure wins on Microsoft-heavy enterprises. AWS is rarely the WRONG choice; it's almost always the safe one.

How to think about cloud cost

Three components: compute (EC2 hours, Lambda invocations), storage (GB-months in S3, EBS, RDS), data transfer (egress is the killer). Egress: free in (data flowing TO AWS), expensive out (data flowing FROM AWS to the internet). $0.09/GB on standard tiers; can dominate the bill at scale. Pricing changes constantly; always check the calculator before estimating. Free tier: 12 months of moderate usage covers most learning. After that, set billing alerts.

💡 Set a billing alert TODAY

Console → Billing → CloudWatch Billing Alarm. Set thresholds at $5, $20, $50 monthly. Free Tier overruns are the #1 surprise bill story. CloudWatch billing alarm = the safety net. Bonus: AWS Budgets gives you per-service breakdown emails monthly. Free; configure once.

Sign up for AWS Free Tier

12 months free for most learning workloads.

  1. 1

    Go to aws.amazon.com/free; sign up with email + credit card (you'll use the free tier; don't enter prod data here)

  2. 2

    For learning, use the root account ONLY to create an IAM user. Then NEVER log in as root again.

  3. 3

    Enable MFA on the root account (Console → Security credentials → MFA).

  4. 4

    Create an IAM user with AdministratorAccess + MFA; use this for everything.

  5. 5

    Set a billing alarm at $5, $20, $50.

  6. 6

    Download the AWS CLI: aws.amazon.com/cli; configure with `aws configure` using the IAM user's access keys.

Quick Check

What's the most common source of unexpected AWS bills for learners?

Pick the realistic answer.

Back to Cloud Platforms — AWS
AWS Core Services→