█
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/AWS Core Services
40 minBeginner

AWS Core Services

After this lesson, you will be able to: Recognise the core AWS services (EC2, S3, RDS, Lambda, IAM, VPC, CloudFront, Route 53) and know what each is for.

AWS has 200+ services; you'll use about 10 daily. This lesson maps the catalog so you know what to reach for.

Prerequisites:The Cloud Landscape

Compute: EC2, Lambda, Fargate

EC2 (Elastic Compute Cloud): virtual machines. The original AWS service. You pick OS + size; you manage everything. Lambda: serverless functions. Triggers (HTTP, queue, schedule); pay per invocation. No server management. Fargate: serverless containers. ECS / EKS without managing nodes. Heavier per-second cost but no node ops. App Runner: managed container deploy. Push image; AWS handles the rest. The 'just want a URL' option.

Storage: S3, EBS, EFS

S3 (Simple Storage Service): object storage. Web-accessible, durable, cheap. The default for files, backups, static sites, data lakes. EBS (Elastic Block Store): SSD/HDD volumes attached to EC2 instances. The 'disk' for VMs. EFS (Elastic File System): NFS-style shared filesystem. Multiple EC2s mount the same FS. S3 is the workhorse; EBS comes with EC2; EFS is rare unless you need shared filesystems.

Database: RDS, DynamoDB, Aurora

RDS: managed Postgres, MySQL, MariaDB, Oracle, SQL Server. Automated backups, patching, Multi-AZ. Aurora: AWS's own MySQL-compatible (or Postgres-compatible) DB. Better performance + price than RDS at scale; same interface. DynamoDB: managed NoSQL key-value + document. Scales to massive throughput. Different mental model from SQL. For learning: start with RDS Postgres. Aurora later. DynamoDB only when SQL doesn't fit.

Networking: VPC, Route 53, CloudFront

VPC (Virtual Private Cloud): isolated network in AWS. Subnets, route tables, internet gateways. Every account has a default; most non-trivial setups use custom VPCs. Route 53: DNS. Maps your domain to AWS resources. Health-aware (route traffic away from broken regions). CloudFront: CDN. Caches your content at edge locations worldwide. Reduces latency + origin load. ALB / NLB: Application Load Balancer (L7, HTTP-aware) and Network Load Balancer (L4, TCP-aware). The traffic distributors.

Identity + Operations: IAM, CloudWatch, CloudTrail

IAM (Identity and Access Management): WHO can do WHAT. Users, roles, policies. Everything else assumes IAM. We cover this deeply in do-aws-03. CloudWatch: metrics + logs + alarms. The default observability for everything AWS. CloudTrail: audit log of every API call. Find out 'who deleted that bucket'. Always-on; can't be disabled (rightly).

💡 The 80/20 of AWS for most projects

EC2 or Lambda for compute. S3 for storage. RDS for DB. CloudFront for static + cached web. Route 53 for DNS. ALB if you need to load-balance. If you can use those six, you're 80% of the way to a real production stack. The other 194 services are for specific needs; ignore them until you have the need.

Quick Check

You want to deploy a Next.js app + a Postgres DB on AWS with minimal ops. Which combination?

Pick the most reasonable shape.

Sign in and purchase access to unlock this lesson.

Sign in to purchase
←The Cloud Landscape
Back to Cloud Platforms — AWS
IAM in Depth→