RoleMath

Free training - skill primer

Learn AWS architecture for free

A free, source-cited path to learning AWS architecture by designing and deploying small workloads on an AWS account you own — this is a learning path, not a certification and not a job guarantee. Cloud design is learned by building and tearing down real resources, not by reading service names.

What it is

AWS architecture is the practical skill of choosing, arranging, and evaluating Amazon Web Services building blocks so a workload runs securely, reliably, performantly, and at a sensible cost. It is a design skill layered on top of a service catalog: you decide where compute runs (for example EC2 virtual machines, containers, or Lambda functions), how data is stored (object storage in S3, block storage, or managed databases), how a network is drawn (a VPC with subnets, route tables, and security groups), and how identity and access are controlled with IAM. Because these building blocks and the trade-offs between them recur across nearly every cloud project, the skill is broadly transferable — the same architectural reasoning carries across cloud-engineering, solutions-architecture, DevOps, and platform work, and much of the mental model transfers to other cloud providers even though the service names differ.

The skill breaks into a handful of durable areas anchored by the Well-Architected Framework's pillars. Security: applying least-privilege IAM, keeping data private by default, and understanding the shared-responsibility model that splits what AWS secures from what you must secure. Reliability: designing for failure with multiple Availability Zones, backups, and recovery rather than assuming a single instance stays up. Performance efficiency: matching the right service and size to the workload instead of over- or under-provisioning. Cost optimization: understanding how you are billed per-service and choosing the cheapest option that meets the requirement — a discipline you feel immediately when you practice on your own account. Operational excellence: automating and documenting how a system is run and changed. Sustainability: choosing designs, services, and regions that reduce the energy and resource footprint of a workload — the sixth pillar AWS added in 2021. None of these are memorization exercises; they are judgments you sharpen by building small real workloads and reading the framework's questions against them.

The fastest way to get fluent without spending money is to design on paper first, then deploy the smallest possible version on your own AWS free-tier account, read what it costs, and delete it. Treat the official AWS documentation and the Well-Architected Framework as your primary reference rather than following tutorials you do not understand, and use the free-tier limits as a hard boundary you plan around. This primer sequences the free resources and gives you a first hands-on exercise; the resources below are the authoritative places to go deeper. The single most important habit is disciplined cleanup — every resource you create should be stopped or deleted when the exercise ends, because some services bill beyond the free tier.

Why it matters

AWS architecture shows up across cloud-engineering, solutions-architecture, DevOps, and platform roles because AWS is one of the most widely used cloud platforms and almost every project makes compute, storage, network, identity, and cost decisions. It is a foundational design skill that several certifications test directly, and the architectural reasoning transfers between projects, teams, and — in large part — between cloud providers rather than locking you to a single service catalog.

The free path, in order

  1. Create your own free-tier account and set a billing alarm. Sign up for your own AWS free-tier account (never an employer's), then immediately set a billing alarm and review the free-tier limits so cost never surprises you. This safe, owned account is the sandbox for every later step.
  2. Learn the Well-Architected pillars. Read the AWS Well-Architected Framework and internalize its six pillars — operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. Frame every design decision by which pillar it serves.
  3. Master the core building blocks. Use free AWS Skill Builder courses and the docs to understand the essential services: EC2 and Lambda for compute, S3 and managed databases for storage, VPC/subnets/security groups for networking, and IAM for identity and least privilege.
  4. Design before you deploy. Practice drawing a small architecture on paper or a free diagram tool first — where compute runs, how data flows, how access is controlled — and check it against the Well-Architected questions before touching the console.
  5. Deploy a minimal workload within free-tier limits. Build the smallest real version of your design on your own free-tier account, staying inside always-free and 12-month-free limits. Observe how it is billed, then confirm your billing alarm and free-tier dashboard show no surprises.
  6. Evaluate, then tear everything down. Review your deployment against the six pillars, note one improvement per pillar, then stop or delete every resource you created. Disciplined cleanup is part of the skill because some services bill beyond the free tier.

Best free resources

Every resource is free and dated. Official sources are labeled; vetted community resources are labeled separately. Verify a resource is still free on its own page before relying on it.

Try it (free, safe, hands-on)

Design and deploy a tiny free-tier static site with IAM least privilege

Do the core AWS-architecture actions on an account you own: design a minimal workload, deploy it inside free-tier limits, apply least-privilege access, read what it costs, and tear it down completely — the daily loop of cloud design.

You will need: Your own AWS free-tier account (never an employer, school, or shared account), with a billing alarm already set; The AWS Management Console in a web browser (free to access); A text file or free diagram tool to sketch the design first

  1. Set a billing alarm first if you have not already: in the Billing console, create a CloudWatch billing alarm at a low threshold (for example a few dollars) so any unexpected charge notifies you immediately. Confirm it is active before creating anything.
  2. Sketch the design on paper or a diagram tool: a single S3 bucket serving a small static web page, plus an IAM user or role that can write only to that one bucket. Note which Well-Architected pillar each choice serves.
  3. Deploy the minimal version within free-tier limits: create one S3 bucket, upload a simple HTML file, and enable static website hosting. S3 has an always-free and a 12-month-free allowance — keep your usage tiny so it stays free.
  4. Apply least privilege: create an IAM policy that grants access only to that single bucket (not account-wide), attach it to a dedicated user or role, and confirm you did not use your root account for day-to-day actions.
  5. Read the cost: open the Free Tier dashboard and the Billing console and confirm your usage is inside free-tier limits with no surprise charges, and that your billing alarm has not fired.
  6. Tear everything down: empty and delete the S3 bucket, delete the IAM user/role and policy you created, and re-check the Billing console so nothing is left running. Some services bill beyond the free tier, so leaving nothing behind is the point.

What you should see: A small architecture you designed against the Well-Architected pillars, a static site deployed inside free-tier limits, an IAM policy scoped to least privilege, a billing view confirming no surprise charges, and a completely clean teardown — all on an account you own, produced by actions you performed yourself.

Safety: Do this only on your own AWS free-tier account — never an employer, school, or shared account. Stay within always-free and 12-month-free limits, since some services bill beyond the free tier. Set a billing alarm before you start, and stop or delete every resource you create when the exercise ends so nothing keeps billing.

Where this skill gets used

Certifications that test it: aws-solutions-architect-associate, aws-certified-cloud-practitioner.

Roles that need it: Cloud engineer, Solutions architect, DevOps engineer, Cloud administrator.

Sources

Every resource is free and dated; official-first, community clearly labeled. A skill primer is a free learning path, not a certification, not professional experience, and not a job or salary guarantee. Labs run only on your own AWS free-tier account within free-tier limits, with a billing alarm and full teardown, because some services bill beyond the free tier. Born draft, pending human review.

All skill primers