Originally published at unifiedpathmedia.com.

The short version: AWS (Amazon Web Services) has hundreds of services and you need about a dozen. Here’s the practitioner’s map of what matters for a foundational build, sorted the same way you already learned to think: compute, storage, networking and database. Learn these; cheerfully ignore the rest until you have a real reason to care.

← Part of the AWS Foundations series

Published September 2, 2026.

Last verified November 5, 2026 against AWS’s service documentation.

Who this is for: anyone who has opened the AWS console and been overwhelmed by the list of services. You’ll need first: the idea of compute, storage, networking and databases from Cloud 101.

AWS has hundreds of services, and most tutorials either bury you in all of them or narrow down so fast you miss the useful context. This is the middle path: a practitioner’s map of what matters for a foundational build, grouped the way you learned to think back in Cloud 101: compute, storage, networking, database.

Knowing the services is half the job. The other half is how they fit together, which is cloud architecture, and this is the plain-English version.

Compute

  • EC2 (Elastic Compute Cloud): virtual machines. The default when you want full control over the OS (operating system) and runtime. It’s the service that maps most cleanly to the “server” you already understand.
  • Lambda: serverless functions that run in response to events, with no servers to manage at all. Perfect for small, event-driven jobs where spinning up a whole instance would be overkill.
  • ECS / EKS (Elastic Container Service / Elastic Kubernetes Service): tools for running Docker containers at scale. Docker packages an app with everything it needs to run, so it behaves the same everywhere. ECS is AWS’s own option and gentler to start with. EKS is managed Kubernetes, the tool that automates deploying and scaling containers across a cluster of machines. It’s more powerful, with more moving parts and more opportunities to Google error messages at midnight.

For a foundational build, EC2 is where most people start. It’s familiar enough to be comfortable and cloud-native enough to make you pick up the new habits. Two of those habits: Auto Scaling Groups, which add or remove servers automatically as demand shifts, and spreading across Availability Zones, which are physically separate data centers within the same AWS Region. The Cloud Architecture series covers both in more depth.

Diagram: Core AWS services overview - compute, storage, networking, database

The core AWS services most projects touch, at a glance.

Storage

  • S3 (Simple Storage Service): object storage, the default home for static files, backups and data at rest. It’s durable and spread across Availability Zones by default, so it’s hard to lose things.
  • EBS (Elastic Block Store): block storage attached to a single EC2 instance, like a virtual hard drive bolted to that one machine. It’s the instance’s own persistent disk.
  • EFS (Elastic File System): shared file storage several instances can use at once, for when multiple servers need the same files.

The one-line way to keep them straight: S3 is the warehouse, EBS is the hard drive inside one machine, EFS is the shared drive everybody mounts.

A quick way to confirm these are there, once the CLI (command line interface) from Part 1 is configured:

bash

$ aws ec2 describe-instances --query "Reservations[].Instances[].InstanceId" [] $ aws s3 ls 2026-01-14 09:02:11 unified-path-example-bucket $ aws rds describe-db-instances --query "DBInstances[].DBInstanceIdentifier" [] 

Networking

This one earns its own series. Cloud Networking covers VPCs (virtual private clouds), subnets, route tables, security groups, NAT (network address translation) gateways and Route 53 in depth. They’re the pieces you’ll touch over and over, which is why they get their own track. For now, know that networking is where your resources live and how they talk to each other and the outside world.

Database

  • RDS (Relational Database Service): managed relational databases (PostgreSQL, MySQL and friends). AWS handles the patching, backups and failover, so you’re not personally babysitting a database at 3 a.m.
  • DynamoDB: a managed NoSQL database (one that doesn’t use linked tables) for when your data doesn’t fit a relational model, or when you need enormous scale with simple queries.

What to happily ignore for now

It’s tempting to go spelunking through AWS’s full catalog early, but for a foundational build almost all the value is in the services above. The specialized machine-learning services, the IoT (internet of things) tooling and the advanced analytics platforms are worth knowing about, not worth your attention until you have a real reason to reach for one. A dozen services you understand beats two hundred you’ve merely heard of.

Which service answers which question

Question Common answer
Where does my code run? EC2 (servers) or Lambda (functions)
Where do my files live? S3
How do my pieces talk to each other? VPC, subnets and security groups
Where does my data live? RDS or DynamoDB
Who is allowed to do what? IAM (Identity and Access Management)

One picture to hold in your head

A typical small web app looks like this. A load balancer takes requests and passes them to a couple of servers in different AZs. Those servers read and write a managed database, and user uploads go to object storage. Every box in that description is one of the services above. If you can sketch it on a napkin, you understand the shape of most AWS architectures.

Servers or serverless?

Servers (EC2) give you control and a familiar model. Serverless (like Lambda) removes the servers from your to-do list in exchange for working within its rules. Neither is better in general. For learning, start with servers, because the concepts transfer everywhere.

Next: AWS Part 4: Billing, Tagging & Multi-Account Thinking

← Back to the AWS Foundations series

Thanks for reading. I write a free, plain-English cloud lesson every week: subscribe to the newsletter. The full AWS Foundations series and free cloud tools live at unifiedpathmedia.com.